[TESTING] - NAND OMGB (1.2.3)

[[ACL]]

i uploaded 2 files tonight.

1) updated recovery .. just some minor changes yall wont even notice untill your batt dies. :-p
2) latest gapps like promised. it doesnt seem to fix the FC until you change the language. So change it up and you might get 1 crash but should be solid after that. I may have missed a prop somewhere so if anyone has any ideas how to fix this.. please share

[muziling]

Insert UIM card, can not boot into ACL custom bootanimation, maybe need to flash hacked-radio.

Can not boot into bootloader, even hold end call key or select boot into bootloader in system.

And, ACL, forgive me, fail wake make me crazy, so I delete and replace all egl&hw libs with NeoFroyo, then no fail wakeup anymore in last 12 hours and when phone call in, screen can auto light up now.

[Starfox]

Couple of things.

1) The sequence of events for me went like this:
Try to flash rhodimg -> Find out I didn't have HSPL on this one (I think this was the third one replaced), had to find the unlocker, then find out that it needs an internet connection to HSPL. Of course, it also needs an ActiveSync, so can't PAM while doing it (since it is my Internet). Ended up using Wi-Fi Tether to keep a connection long enough for it to HSPL.

Tri-color-flash RHODIMG. Boot into mpl. Windows throws up an unknown device error. I had the ADB set up under haret, so I freak out. NANDROID says something about a driver I needed to download. Flash into Factory, haret and download said driver. Flash mpl again. Driver doesn't take. It actually does _not_ need the driver bundle, but you need to force it to use Android devices -> HTC Dream. Fastboot seems to be working now (freaked out right after driver install, but I see it waiting after it rebooting on its own).

Fastboot recovery. Use fastboot reboot, it complains about flash errors. Try various permutations of fastboot flash recovery/fastboot erase <stuff>. Still nothing. On a whim try fastboot boot recovery.img. I get into cwm-ish screen. Apply omgb. It says successful.

mpl shows valid flash now, but any attempts to boot either results in a single-vibrate reboot (most of the time) OR a dual-vibrate and the splash screen for a second THEN a reboot (usually only once). Try going into recovery again, and flash omgb. No dice. Start from fastboot flash recovery, nothing either. Found out it still can get into tri-color by holding Vol-Dn. Re-flash mpl again, go through the same process. Nothing. Gave up for now and reflashed factory so I can get into haret.

2) Observations:
Technically it doesn't seem to require a recovery flash at all, only need mpl to load recovery via End->fastboot boot recovery.img trick. Other than the convenience factor of having a recovery handy, can you actually bypass having to flash recovery?

I see some kernel parms while mpl attempted to boot omgb. Where are these stored, and what's the procedure for changing it, i.e. overclocking, etc.

Says native tethering isn't working. Are the menu items not present/disabled, or is it just not working when you try to enable it? For me this would be a killer, since I do keep AP Mode on. I could try to figure stuff out via EasyTether to try to debug the issue.

I saw some "expert mode" in the recovery from Oct 1st recovery.img, selecting it dimmed the screen and told me to hit End to get out. It completely refused to respond to keys after that, so I had to pull battery. Was this the charging thing that was addressed in the new recovery this morning?

If I were to try to roll my own kernel, what would be the procedure to get it flashed? I assume I'd have to use anykernel-type thing and create an update.zip to flash via recovery.

And what's the best minimal "wm" rhodimg to keep handy just in case I do need to access FRX? Flashing factory takes too long and seems to unnecessarily kill flash cells just to get to haret.

-- Starfox

[arrrghhh]

Holy post batman, I thought you were dead! jk. Now go make some new version of the StarFox kernel for HaRET .

Seriously tho, I can't answer all your questions. I stripped out anything I couldn't answer, and answered the ones I felt I could answer in-line.

Originally Posted by Starfox

Technically it doesn't seem to require a recovery flash at all, only need mpl to load recovery via End->fastboot boot recovery.img trick. Other than the convenience factor of having a recovery handy, can you actually bypass having to flash recovery?

I don't get what you mean here - you have to have recovery in order to flash/apply OMGB.

Originally Posted by Starfox

I see some kernel parms while mpl attempted to boot omgb. Where are these stored, and what's the procedure for changing it, i.e. overclocking, etc.

Why would you ever want to change these lines...? Overclocking is done natively thru SetCPU. What else would you want to adjust...? I think this adjustment would have to happen when LK is compiled, but I honestly have no idea!

Originally Posted by Starfox

Says native tethering isn't working. Are the menu items not present/disabled, or is it just not working when you try to enable it? For me this would be a killer, since I do keep AP Mode on. I could try to figure stuff out via EasyTether to try to debug the issue.

The menu is not available. I assume ACL just needs to enable it...

Originally Posted by Starfox

I saw some "expert mode" in the recovery from Oct 1st recovery.img, selecting it dimmed the screen and told me to hit End to get out. It completely refused to respond to keys after that, so I had to pull battery. Was this the charging thing that was addressed in the new recovery this morning?

No. My batt completely died and would not take a charge (damn phone kept turning on and then failing to boot because of lack of powa). So ACL made a special sauce recovery for me in an attempt to get the device to charge when powered off. It didn't work for me, but ACL was hoping perhaps it would help others.

As for the 'expert mode' you put the phone in, that is unrelated to the charging aspect. Not sure what you did to be honest, I haven't played around much in recovery .

Originally Posted by Starfox

If I were to try to roll my own kernel, what would be the procedure to get it flashed? I assume I'd have to use anykernel-type thing and create an update.zip to flash via recovery.

Well, I am not quite clear if the kernel is in the NBH or in the .zip for OMGB. I don't see how it's part of OMGB, since you need a kernel to boot CWM... This is one I probably shouldn't have answered lol.

Originally Posted by Starfox

And what's the best minimal "wm" rhodimg to keep handy just in case I do need to access FRX? Flashing factory takes too long and seems to unnecessarily kill flash cells just to get to haret.

I have Energy's Titanium. I'm sure there's some smaller stripped ROM, but I didn't want to risk anything not working. I was pretty sure both my RHOD's had bitten the dust... For some reason my tester RHOD started charging batteries, but it won't boot. No big deal, because now I have two charged batteries instead of 0 .

[[ACL]]

Originally Posted by muziling

Insert UIM card, can not boot into ACL custom bootanimation, maybe need to flash hacked-radio.

Can not boot into bootloader, even hold end call key or select boot into bootloader in system.

And, ACL, forgive me, fail wake make me crazy, so I delete and replace all egl&hw libs with NeoFroyo, then no fail wakeup anymore in last 12 hours and when phone call in, screen can auto light up now.

whatever works for you.. =D>

[[ACL]]

Originally Posted by Starfox

Couple of things.

1) The sequence of events for me went like this:
Try to flash rhodimg -> Find out I didn't have HSPL on this one (I think this was the third one replaced), had to find the unlocker, then find out that it needs an internet connection to HSPL. Of course, it also needs an ActiveSync, so can't PAM while doing it (since it is my Internet). Ended up using Wi-Fi Tether to keep a connection long enough for it to HSPL.

Tri-color-flash RHODIMG. Boot into mpl. Windows throws up an unknown device error. I had the ADB set up under haret, so I freak out. NANDROID says something about a driver I needed to download. Flash into Factory, haret and download said driver. Flash mpl again. Driver doesn't take. It actually does _not_ need the driver bundle, but you need to force it to use Android devices -> HTC Dream. Fastboot seems to be working now (freaked out right after driver install, but I see it waiting after it rebooting on its own).

Fastboot recovery. Use fastboot reboot, it complains about flash errors. Try various permutations of fastboot flash recovery/fastboot erase <stuff>. Still nothing. On a whim try fastboot boot recovery.img. I get into cwm-ish screen. Apply omgb. It says successful.

mpl shows valid flash now, but any attempts to boot either results in a single-vibrate reboot (most of the time) OR a dual-vibrate and the splash screen for a second THEN a reboot (usually only once). Try going into recovery again, and flash omgb. No dice. Start from fastboot flash recovery, nothing either. Found out it still can get into tri-color by holding Vol-Dn. Re-flash mpl again, go through the same process. Nothing. Gave up for now and reflashed factory so I can get into haret.

2) Observations:
Technically it doesn't seem to require a recovery flash at all, only need mpl to load recovery via End->fastboot boot recovery.img trick. Other than the convenience factor of having a recovery handy, can you actually bypass having to flash recovery?

I see some kernel parms while mpl attempted to boot omgb. Where are these stored, and what's the procedure for changing it, i.e. overclocking, etc.

Says native tethering isn't working. Are the menu items not present/disabled, or is it just not working when you try to enable it? For me this would be a killer, since I do keep AP Mode on. I could try to figure stuff out via EasyTether to try to debug the issue.

I saw some "expert mode" in the recovery from Oct 1st recovery.img, selecting it dimmed the screen and told me to hit End to get out. It completely refused to respond to keys after that, so I had to pull battery. Was this the charging thing that was addressed in the new recovery this morning?

If I were to try to roll my own kernel, what would be the procedure to get it flashed? I assume I'd have to use anykernel-type thing and create an update.zip to flash via recovery.

And what's the best minimal "wm" rhodimg to keep handy just in case I do need to access FRX? Flashing factory takes too long and seems to unnecessarily kill flash cells just to get to haret.

-- Starfox

- Try to catch up on the status of the project. most of this has been talked about already

- To change cmdline you need to make your own boot.img. I disabled almost all cmdline params anyways since they are useless.

- tethering will get fixed. Arrgg has a list of the issues on the project page.

- the recovery will get updated again. I posted something incase of emergency inscase someone found themselves with a dead batt. The advanced menu is sorta useless right now. This hasnt really been updated since froyo to be honest.

- my sources are free, you can roll what you want. Hoever if you want to help i do need more hands on the userland side of things not so much the kernel. The ril right now is purely cdma and wont work with gsm since i killed the auth. Was fine for sprint and verizon but now that we have possible world users need to reimplement that in smooth way without changing the framework like we did on xdandroid.

Also i have 0 tests done with camera. i just dont have the time so that needs to be looked into.

[[ACL]]

Don't get too attached to the version that is up now since there have been some fixes and a new one should be uploaded either tonight or tomm morning.

Finally got those incall buttons thanks to arrggss attention to detail. I'm debugging some teathering now and hopefully have that solved soon. Changed the delay of the light sensor on wakeup since that may be related to the delayed wakes.

[arrrghhh]

Originally Posted by [ACL]

Don't get too attached to the version that is up now since there have been some fixes and a new one should be uploaded either tonight or tomm morning.

Finally got those incall buttons thanks to arrggss attention to detail. I'm debugging some teathering now and hopefully have that solved soon. Changed the delay of the light sensor on wakeup since that may be related to the delayed wakes.

Thanks dude.

I flashed the new NBH, flashed recovery... but I can't boot into recovery. At all. I can get LK to detect button presses (says POWER BUTTON PRESSED) and it starts going thru the normal process - I see 'booting linux' and the cmdline passed... however, normally I'd get a double vibe, the tux symbol, then CWM. I don't get this at all! I just get a blank screen, a single vibe, then the HTC logo. So it just keeps rebooting :/.

I'm wondering if it's the new version of recovery you rolled for me when I killed my batts. Do you have the old recovery kicking around? My dumbass just deleted it, thinking newer=better .

That's the only thing I can assume is wrong, the new version of recovery. If not... well I guess I have a hardware problem then. I'll go try this on my tester RHOD now, in an attempt to rule out bad hw.

Edit - couple of things. My tester RHOD is seemingly dead. Won't go past the HTC logo screen with any ROM - LK or WinMo. It charges batteries, so I guess it still does its job lol.

As for my main device - pulling the SIM seemed to resolve it. I keep forgetting I put that SIM in there, and pulling it allowed me to boot to recovery. Not sure if that was it or not, but I haven't been able to boot recovery otherwise!!

Edit 2 - New in-call screen is perfect bro. Kudos!

Edit 3 - I can't win. GMail seems to be a bust - but I am restoring data from an old setup. I might try w/o that... Yes, I flashed gapps. At first I flashed gapps, then did a data restore. There was no GMail app, and so I downloaded it from the Market - but it didn't show up in Accounts & Sync. So I go reflash gapps, still not thar... Perhaps I'll have to ditch my data restore and just use TB. The data restore is sweeeet tho .

Edit 4 - Seems both issues are fixed with calls dude - I will do some extensive testing, but preliminary testing the phone wakes up better for incoming calls (still not stellar, but at least functional) and it's waking from sleep on long calls just as expected! Need to try a really long call, but I was just playing around and it was going to sleep quickly when in-call, and waking up pretty quickly when I pulled my finger away from the screen. So far - awesome, awesome, awesome!!

[Starfox]

Originally Posted by arrrghhh

Edit - couple of things. My tester RHOD is seemingly dead. Won't go past the HTC logo screen with any ROM - LK or WinMo. It charges batteries, so I guess it still does its job lol.

Try flashing an official ROM, then downgrade the SPL afterwards. Sometimes the SPL needs to be "reset" to factory when it won't boot. If it works with locked SPL, you can HSPL again and it should work...

-- Starfox

[arrrghhh]

Originally Posted by Starfox

Try flashing an official ROM, then downgrade the SPL afterwards. Sometimes the SPL needs to be "reset" to factory when it won't boot. If it works with locked SPL, you can HSPL again and it should work...

-- Starfox

Cool, I'll try that. I was also suggested task29, need to find a Windoze box...