Ok here goes. I got another G1 from T Mobile. I did a backup using nandroid 2.1. The new phone had 1.5 on it already from T Mobile. I down graded it to rc29 and rooted. I went to restore my backup and everything seemed to be ok untill it reboots. I had no errors doing the restore with nandroid. System, userdata, and boot images all had ok's. The only backup it will let me do is one from May and I was running JF 1.5 crb21. I have upgraded to JF 1.51 crb43 and did a backup of that but when I try to restore it freezes on te G1 screen. I now have Nandroid GUI and everything goes smooth untill it reboots with any new backup. It will let me put any version of android on but will not let me restore it. I have used Hard SPL and Engineering SPL. I'm pulling my hair out here.
Anybody want to try?
Not 100% sure this will work, but might as well give it a try:
First try completely wiping the phone. Let it boot (if it does) into Android.
Then, try to re-restore the backups you have by turning it off and Home + Pwr
I did that already. Next.
oxman504 said:
Ok here goes. I got another G1 from T Mobile. I did a backup using nandroid 2.1. The new phone had 1.5 on it already from T Mobile. I down graded it to rc29 and rooted. I went to restore my backup and everything seemed to be ok untill it reboots. I had no errors doing the restore with nandroid. System, userdata, and boot images all had ok's. The only backup it will let me do is one from May and I was running JF 1.5 crb21. I have upgraded to JF 1.51 crb43 and did a backup of that but when I try to restore it freezes on te G1 screen. I now have Nandroid GUI and everything goes smooth untill it reboots with any new backup. It will let me put any version of android on but will not let me restore it. I have used Hard SPL and Engineering SPL. I'm pulling my hair out here.
Click to expand...
Click to collapse
if you know how to use adb,type in adb logcat and see whats going on.
if not, put JF's latest rom on your SD card, rename it update.zip
do a nandroid restore, stay or reboot into recovery, and flash the JF rom and see if that helps. if not you will have to learn how to use abd
Related
I've been running JACHero 2.7.3 lately and happy with it, I've also been using the cm-recovery 1.3.1 recovery image but noticed there was a v1.4 with a few new features and also thought I'd try out Drizzy's TouchFLO 3D to see if it appealed to me more. Here's what I've done so far..
Hero 2.7.3, cm recovery v1.3.1 - nandroid backup done a few days ago.
Updated cm recovery to v1.4 while in Hero.
Rebooted, nandroid backup done from v1.4 recovery image.
Wiped then applied Drizzy's firmware.
Repaired permission (always do, just in case) then rebooted.
Phone starts up, G1 splash and then I get to the Hero splash image where it goes into a loop. It won't go past the Hero splash at that point.
Figuring I might not have formatted I recreated the partitions on the SD card, can't fail to be formatted that way. I also decide to reflash JACHero 2.7.3 and try to restore my nandroid backup from about 10 minutes earlier.
Restore completes, I reboot and it got stuck on the Hero splash again. I've just managed to flash it again and it has gone into the OS but it's a blank slate. I've got both a nandroid 2.1 and 2.2 backup but trying to restore the 2.1 with 2.2 failed.
The question I'm looking for an answer and help on is would I be better off putting cm recovery 1.3.1 on and using the old backup or is there something I'm doing wrong with the 1.4 recovery and nandroid backup? I can go about setting the phone up again manually but that's the point of the backup. Help :/
OK, I'm not sure what stopped the Hero splash lock-up but it's gone now. I restored the backup and it worked... all I had to do was reinstall applications since they were all showing as broken links. False alarm or pain in the butt freak problem, either way it's resolved.
Dyonas said:
I've been running JACHero 2.7.3 lately and happy with it, I've also been using the cm-recovery 1.3.1 recovery image but noticed there was a v1.4 with a few new features and also thought I'd try out Drizzy's TouchFLO 3D to see if it appealed to me more. Here's what I've done so far..
Hero 2.7.3, cm recovery v1.3.1 - nandroid backup done a few days ago.
Updated cm recovery to v1.4 while in Hero.
Rebooted, nandroid backup done from v1.4 recovery image.
Wiped then applied Drizzy's firmware.
Repaired permission (always do, just in case) then rebooted.
Phone starts up, G1 splash and then I get to the Hero splash image where it goes into a loop. It won't go past the Hero splash at that point.
Figuring I might not have formatted I recreated the partitions on the SD card, can't fail to be formatted that way. I also decide to reflash JACHero 2.7.3 and try to restore my nandroid backup from about 10 minutes earlier.
Restore completes, I reboot and it got stuck on the Hero splash again. I've just managed to flash it again and it has gone into the OS but it's a blank slate. I've got both a nandroid 2.1 and 2.2 backup but trying to restore the 2.1 with 2.2 failed.
The question I'm looking for an answer and help on is would I be better off putting cm recovery 1.3.1 on and using the old backup or is there something I'm doing wrong with the 1.4 recovery and nandroid backup? I can go about setting the phone up again manually but that's the point of the backup. Help :/
Click to expand...
Click to collapse
If I'm not mistaken, the new nandroid version in Cyanogen's 1.4 gives the subfolder under the nandroid folder a different name than the 1.3 version. 1.4 may not be able to find your backup because its looking for the wrong folder. I believe the folder under the "HT blah blah" used to be just a numeric date in 1.3. Now in 1.4 it is alpha-numeric. You may look into this as being the culprit and try to flash 1.3 back to perform the nandroid restore.
ok so i was getting ready to flash newvision v3 by jac and drizzy...so i went to bootloader....wiped my ext3 and then wiped my phone... then i did a nandroid backup and I flashed... then restored it...after that its on the g1 screen and i havent tried recovery yet and i just realized that since i wiped before nandroid it didnt really backup anything...what should i do???just reflash if recovery works???
Noobyflasher said:
ok so i was getting ready to flash newvision v3 by jac and drizzy...so i went to bootloader....wiped my ext3 and then wiped my phone... then i did a nandroid backup and I flashed... then restored it...after that its on the g1 screen and i havent tried recovery yet and i just realized that since i wiped before nandroid it didnt really backup anything...what should i do???just reflash if recovery works???
Click to expand...
Click to collapse
Yeah, you confused your steps a little. Seeing that you did a nandroid after all of the wiping, you essentially just made a backup of your boot, data, recovery, and system images but your cache image is not gonna contain much because you wiped I'm pretty sure. If you flashed your new ROM, you can't flash your nandroid backup as that will take you back to your old ROM. Nandroid isn't a back up tool in the way you want to you use (settings, preferences etc) It is a tool that will restore your system in case you mess something up. If you want the new drizzy JAC build, you just flash that and leave your nandroid for a rainy day or if you screw up a flash and get a bootloop.
I was trying to go from Drizzy's touchflo 3D to JACxDrizzy's ROM.
I have fat32, ext3, and linux-swap, all the appropriate size
So, i followed the usual steps:
boot to recovery, nandroid backup (i have 1.4 recovery btw), wipe, flash, boot.
Except, the phone got stuck in a bootloop. So i booted to fastboot, then used the "fastboot flash ____ ____img" commands to restore.
Also a bootloop.
I thought of using the 1.4's nandroid restore function, but that does not work since after backing up, I moved the backup to my desktop, changed the folder name, and deleted the backup from my phone. I tried to adb push the files back in, but recovery still said that the backups were not in the phone.
So I wiped everything, including ext3, then tried again, this time going back to my previous build, Drizzy's touchflo 3d. It seemed to be working - i went to recovery and selected the flash update.zip option. Then the options disappeared, as usual, and the text (showing the progress of the flashing) began to show up. However, the phone froze after the first two lines of text.
I decided to wait. Eventually, my phone shut down. I tried to boot my phone in all 3 ways (standard, recovery, and fastboot) but none of them worked. The red LED blinked twice and the phone has no response.
How do I get my G1 to boot, and after that, how do i get nandroid to work?
EDIT: Ok I feel stupid now. The phone just ran out of battery. But the question still stands: How do i get nandroid to work?
since you nuked your ext3 your nandroid probably will not work because the hero rom will be looking for the files necessary for it on your ext3 but they are not there so it will bootloop. try flashing whatever rom you want to with a cleanly formatted card and see if it will boot up.
I don't know why, by Drizzy's builds always require EXT formatting, but JAC's don't. So you got a bootloop because you didn't wipe your ext3. I always just use Cyan's recovery to restore a nandroid backup. If that flails I guess you have to start over.
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
Did you even wipe when going between the 2 roms?
Ace42 said:
Did you even wipe when going between the 2 roms?
Click to expand...
Click to collapse
Mmmm I usually do, but maybe thats were I went wrong. I've wiped since and it's still stuck though.
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
Wipe everything, including your ext partition. But backup your apps first.
After that, flash the rom again and see if that works.
Bavilo said:
Wipe everything, including your ext partition. But backup your apps first.
After that, flash the rom again and see if that works.
Click to expand...
Click to collapse
Will removing the SD work in the same way? I'm not sure how to wipe the ext 4 partition. (I'm not concerned about my apps and that).
Thanks for the help!
EDIT: Stated in the [xROM Eclair/AOSP] [2.01] thread that a wipe isn't needed before update, 'came from cyan 4.2.11.1 and don't have to wipe anything'
emoray said:
Will removing the SD work in the same way? I'm not sure how to wipe the ext 4 partition. (I'm not concerned about my apps and that).
Thanks for the help!
EDIT: Stated in the [xROM Eclair/AOSP] [2.01] thread that a wipe isn't needed before update, 'came from cyan 4.2.11.1 and don't have to wipe anything'
Click to expand...
Click to collapse
"update" means coming from the previous xrom. you must wipe coming from cyans rom.
emoray said:
I'm currently stuck at the g1/tmobile screen.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
Click to expand...
Click to collapse
Why would you have no backup after running nandroid? Nandroid does not overwrite your old backup when you create a new one. They are timestamped in /sdcard/nandroid/SERIALNUMBEROFDEVICE/timestamp
Running the nandroid script from the console in recovery mode lets you choose the backup you want to restore. Just some food for thought
jmhecker said:
Why would you have no backup after running nandroid? Nandroid does not overwrite your old backup when you create a new one. They are timestamped in /sdcard/nandroid/SERIALNUMBEROFDEVICE/timestamp
Running the nandroid script from the console in recovery mode lets you choose the backup you want to restore. Just some food for thought
Click to expand...
Click to collapse
Ahhh well that'd been great if I hadn't just wiped my SD card to reformat the ext partition! DAMN!
Is it possible to mount the CD card whilst in recovery mode? Then with a clean EXT2/SD card, a wipe and reflashing the rom should work surely?
ums_enable if you have a custom recovery - do it in the console
and next time post in the right section please
not the right post
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
just wipe and start from scratch .repartition ,reflash and you'll be good
try hooking it up to adb and get a logcat while its on the boot screen and see if it is doing something, might just need to wait it out. My G1 was recently on the G1 boot screen for over an hour while busybox was re-writing a filesystem.
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Tylerspilker said:
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Click to expand...
Click to collapse
I have the same issue using Amon Ra's recovery with Nandroid.
I end up pulling the battery and rebooting.
Take a look in your Nandroid backup folder on your SD card....you will see files that are several GB in size.
The nandroid appears to get stuck in a loop.
I have not had a successful nandroid backup made since CM-Recovery. I might go back to it but Amon Ra has a lot more stuff.
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Tylerspilker said:
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Click to expand...
Click to collapse
Which Amon_Ra? I had the same issue on 1.5.x and 1.6.2.
Still no joy on nandroid or BART.