• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Should have done a nand backup

P

ppbb

Well-Known Member
Let this be a lesson to everyone here. Do a NAND back up before flashing anything. (Erisuser thank you)

I got excited, flashed a new theme with new keyboard. did not nand. Now having issues with the keyboard. may have to reflash everything.

Moral of this story. NAND!!!
:(
:D
 
Maybe you should try to uninstall the keyboard and reinstall it. That often helps. Try the simple things first. :)

Which keyboard is it? Maybe I can just send you an original apk in case the one you have is messed up.
 
I had the same problem trying to install that keyboard last week - though, I hate to tell you, I did a Nandroid first. I'd already learned that lesson ... (I renamed that backup "kf.v30-20100825-premultitouch"; it's still there ;) ).
 
Sorry, tried to just extract the apk from the zip, but when I tested it, it didn't work. Dunno. I don't care for the keyboard at all so never use it and don't know what the issue is for me.
 
You may be able to just reflash the ROM without wiping also. (Or, get used to using HTC_IME again...)
 
i did a dalvik wipe and then reflashed the rom ( Tazz 2.0 vanilla) over it with no issues. I did lose a couple of widgets in the process, but nothing I couldn't track down in the market.

I did flash the Dark Froyo V 1.0 as that version worked fine.
 
scary alien said:
I've heard "nonsensikal v4.6 blue" is pretty good...:eek:

Oh, no I didn't!!! [yes, I did! :D]
Click to expand...

One thing that I failed to mention when ppbb went down into that black hole for a couple of days was that we could have kept him there longer by re-building a boot image for him that had adbd turned on, and he could have lost^H^H^H^Hspent even more of his life debugging :)

We wouldn't even need to re-build a flashable ROM for him - the whole thing can be crowbar'ed into place with the following steps:

- Wipe
- Flash the original ROM file
- Make an Nandroid Backup (yes, *after* flashing)
- Duplicate the Nandroid Backup, replacing the old boot.img with the new boot.img, and fix up the nandroid.md5 file with the (new) MD5 signature
- Restore the crowbar'ed/foobar'ed Nandroid backup.
- Boot


Note that the same procedure can be used to crowbar a different kernel into an old ROM without going to the trouble of assembling a new ROM. (Or even the boot image from another ROM - but that's likely to cause trouble, so let's not go there.)

:D

eu1


ps ppbb I'm 1/2 serious - if you want me to make a boot image for you, I will - just tell me which ROM.
 
erisuser1 said:
One thing that I failed to mention when ppbb went down into that black hole for a couple of days was that we could have kept him there longer by re-building a boot image for him that had adbd turned on, and he could have lost^H^H^H^Hspent even more of his life debugging :)

We wouldn't even need to re-build a flashable ROM for him - the whole thing can be crowbar'ed into place with the following steps:

- Wipe
- Flash the original ROM file
- Make an Nandroid Backup (yes, *after* flashing)
- Duplicate the Nandroid Backup, replacing the old boot.img with the new boot.img, and fix up the nandroid.md5 file with the (new) MD5 signature
- Restore the crowbar'ed/foobar'ed Nandroid backup.
- Boot


Note that the same procedure can be used to crowbar a different kernel into an old ROM without going to the trouble of assembling a new ROM. (Or even the boot image from another ROM - but that's likely to cause trouble, so let's not go there.)

:D

eu1


ps ppbb I'm 1/2 serious - if you want me to make a boot image for you, I will - just tell me which ROM.
Click to expand...

eu1, wow! You really are like a mad scientist, aren't you? :D

So, is there a reasonable explaination (that us mere mortals might grok) as to why a ROM would (might) load from a Nandroid backup vs. one that is flashed via recovery?

Thanks and cheers!

P.S. thank you for the interesting write-up in the trackball thread about alternatives to flashing a ROM w/o using recovery. I PM'd Amon_RA yesterday regarding changing his Eris recovery to have a non-trackball version (I'm willing to help; no reply yet, lol...in hindsight, I probably should have simply posted on the thread).
 
scary alien said:
So, is there a reasonable explaination (that us mere mortals might grok) as to why a ROM would (might) load from a Nandroid backup vs. one that is flashed via recovery?
Click to expand...

I didn't say that it would get further along in the booting; I was suggesting that as a means to enable adbd by default in that ROM so that a logcat dump could be generated to aid in diagnosing the problem he was having. The thing that most casual users don't realize is that when bootloops are occurring, the kernel has booted far enough that you can actually run a shell on the phone - if the adbd daemon has been started. Thanks for asking the question though - it gave me an idea for a way to do that that is even easier.

scary alien said:
P.S. thank you for the interesting write-up in the trackball thread about alternatives to flashing a ROM w/o using recovery. I PM'd Amon_RA yesterday regarding changing his Eris recovery to have a non-trackball version (I'm willing to help; no reply yet, lol...in hindsight, I probably should have simply posted on the thread).
Click to expand...

Search for early posts of his in the Eris dev forum on XDA - he needed someone to dump something from the phone so that he could code a version of his recovery for the Eris. Something similar to a keysym map, so that he could map the trackball and other key presses to the correct functions. The reason I mention this is that I recall seeing devs doing keysym mapping (on other phones?) in "init.rc" - if that is possible with his init parser, you might not need his help.

eu1


Edit - PS, not to split hairs or anything, but I don't want my instructions over in that other thread to be misinterpreted: it's not done "w/o using recovery", but rather by using the recovery boot "w/o using the physical buttons on the phone".
 
erisuser1 said:
One thing that I failed to mention when ppbb went down into that black hole for a couple of days was that we could have kept him there longer by re-building a boot image for him that had adbd turned on, and he could have lost^H^H^H^Hspent even more of his life debugging :)

We wouldn't even need to re-build a flashable ROM for him - the whole thing can be crowbar'ed into place with the following steps:

- Wipe
- Flash the original ROM file
- Make an Nandroid Backup (yes, *after* flashing)
- Duplicate the Nandroid Backup, replacing the old boot.img with the new boot.img, and fix up the nandroid.md5 file with the (new) MD5 signature
- Restore the crowbar'ed/foobar'ed Nandroid backup.
- Boot


Note that the same procedure can be used to crowbar a different kernel into an old ROM without going to the trouble of assembling a new ROM. (Or even the boot image from another ROM - but that's likely to cause trouble, so let's not go there.)

:D

eu1


ps ppbb I'm 1/2 serious - if you want me to make a boot image for you, I will - just tell me which ROM.
Click to expand...

eu1 much appreciated, but I think I am going to stick with Tazz 2.0 for now. I have everything dialed in perfect and really like the way my phone works now.

Your contributions and many helpful posts have explained and helped me so much.

Thank you.
 
You must log in or register to reply here.
Back
Top Bottom