Hello, I flashed a nandroid backup from another site that was supposed to help me on getting 3g working with Eclair, but instead of doing that, now my phone does not get to the main menu, only gets to the motorola logo and then shut down itself and does the same thing, all over again, like being in a loop, I entered into recovery and see there's an option to flash an update.zip, which I supposed can be a functional version of Android, my only backup is a nandroid one, but that does not work right? what can I do? please help me thanks
UPDATE: I just fixed it by installing the latest version of RSD LITE and then installing any of the stock sbf for Eclair, thanks anyway, that was close :S
saman0suke1 said:
Hello, I flashed a nandroid backup from another site that was supposed to help me on getting 3g working with Eclair, but instead of doing that, now my phone does not get to the main menu, only gets to the motorola logo and then shut down itself and does the same thing, all over again, like being in a loop, I entered into recovery and see there's an option to flash an update.zip, which I supposed can be a functional version of Android, my only backup is a nandroid one, but that does not work right? what can I do? please help me thanks
UPDATE: I just fixed it by installing the latest version of RSD LITE and then installing any of the stock sbf for Eclair, thanks anyway, that was close :S
Click to expand...
Click to collapse
You could've just gone to the stock recovery nad have cleared the cache and data, that would've worked as well.
shad0wboss said:
You could've just gone to the stock recovery nad have cleared the cache and data, that would've worked as well.
Click to expand...
Click to collapse
That would probably not work as he installed some other rom (nandroid backup) that led him to boot loop, he did the right thing
Related
Hello all,
I have successfully installed CM7 on my Nexus One. However, I have the following problem with CWM: if I ask it to make a backup from within the recovery or from RomManager, CWM (3.0.0.5, latest version available apparently for Nexus One) makes the backup, but after restarting, I am stuck on the CM7 splashscreen: I see the blue Android on his skateboard and the arrow goes around in circles (left it going for 15 minutes just to be sure).
Also, on a sidenote, when I made the initial nandroid backup in CWM from my stock Froyo, after the backup was done I had to go in RomManager and "fix permissions", because all my resident apps kept crashing with "forced close" errors. No idea where that came from. Restoring that backup did the same thing as well. I did not investigate that issue any more though as I was on my way to a CM7 upgrade anyways.
So I now have a perfectly good install of CM7 running, but I am scared of doing a CWM backup. This is far from an ideal situation, and I would love to be able to resolve this
Thanks for any help
Anyone? I really am quite upset with this situation
Use this instead?
http://forum.xda-developers.com/showthread.php?t=611829
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
yannack said:
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
Click to expand...
Click to collapse
Uh oh? It is just a custom recovery, no need to reinstall everything. You only flash the recovery and do the backup you cannot now with the broken CWM. (For my phone, there are even flashable zip files so you can switch b/w CWM and AmonRA "on the fly" via flash zip from recovery, not sure there are some for N1, try to search. )
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Which is why I am nervous at the idea of trying to make such a backup.
On a sidenote, RomManager is indeed able to flash both CWM and RA recoveries for N1 directly, which is quite nice indeed.
yannack said:
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Click to expand...
Click to collapse
I still do not understand why all this. Just flash a working recovery from fastboot (should press power and trackball IIRC on your phone). (And obviously do not use CWM to perform backups when it bricks your phone.)
On another note, flashing removery via ROM Manager resulted in bricked phones for many users, would avoid it personally.
I'm not sure what happened to my tablet. I really can't seem to figure it out. I was using it last night before I went to sleep, and I just closed it away (I have the keyboard dock), and packed it in the case this morning for work. When I took it out to use it at work it had already been stuck in a boot loop. I have wiped, and reinstalled 3 different roms on it since. It's still doing the same thing. Is there anything else I can do? What could have caused this?
I know that you've tried to flash several ROMs, but please check if you've done all the steps described below:
Copy ROM to /sdcard
Reboot in recovery
Wipe /system, /cache and dalvik-cache
Install ROM
Reboot and see if it works
If not, you might also want to delete /data, but make sure you backup it first (you can do that with a nandroid) and use /external_sd to store the ROM (just in case).
You can also try restoring your nandroid backup.
VibrantWind said:
You can also try restoring your nandroid backup.
Click to expand...
Click to collapse
I have tried both. When I flashed the original backup back onto the tablet I got the same result. I have completely wiped all data as far as I know. I even went a step further and formatted my sd card to ensure none of the ROM files were corrupt, then placed them back on the card. Is there even more data I can delete other than the system wipe/cache/dalvic cache?
wipe staging
wipe battery stats
ummmmm yeah those are the only 2 not listed and are not all that usefull to you
Do you have nvflash ? If so i would do a complete wipe ie format everything even recovery etc then flash a nvflash rom then restore my nandroid if i knew the integrity of it was good
Sent from my Transformer TF101 using xda premium
theres a Super wipe I use in mikes Android Revolution HD thread..
I have used this before to fix a few problems I was having..
Check "how to flash" section for it
http://forum.xda-developers.com/showthread.php?t=1245892
I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.
fone_fanatic said:
I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.
Click to expand...
Click to collapse
I have tried the Revolutionary Rom, and after it wipes and installs, and reboots it just says at the Asus eEE screen. What on earth could I have possibly done? Is the super wipe something that can be manually done, or does this only occur while installing the rom?
Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!
MrAutomatic said:
Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!
Click to expand...
Click to collapse
Let me guess... You flashed super-wipe, but didn't install any ROM after...
Don't worry, we're here to help, not judge!
AzureusPT said:
Let me guess... You flashed super-wipe, but didn't install any ROM after...
Click to expand...
Click to collapse
My bet is on that as well! haha
Not going to lie.. I've done that before.
Howdy.
I've been using custom firmware since I got my phone over a year ago, but I'm now having big issues.
I tried to install a 4.2.2 ROM and couldn't boot, even after trying bunch of times, clearing cache, all that jazz..
So.. usually I would just put on another ROM or just restore from a backup, but I'm stuck in a weird situation.
I have a bunch of ROM backups (Clockwork Mod Recovery) going back to April last year, the 1st one is standard AT&T, then various custom ROMS (last one I used was Cynogen 10).
But I can only restore the first AT&T ROM, nothing else will restore. I also cannot even install any ROM the only way I can get a working phone is to go back to the horrible original AT&T ROM..
Clockwork mod recovery also crashes when I try to wipe cache, so think that maybe a clue....
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
eckythump said:
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
Click to expand...
Click to collapse
What version of CWM are you on?
You can always restore to your AT&T backup, transfer all of your other backups to your external SD or computer, ODIN to stock, do a complete wipe of the phone, flash the most recent CWM from Sk8 and try again. I'd say that's your best case scenario.
mrfeuss said:
What version of CWM are you on?
I'm on 6.0.1.4 which I believe is latest. I can't even get the original ROM to restore now either. Ughhhh hope I'm not bricked.
Click to expand...
Click to collapse
Try Odin back to stock before u do brick it that should fix any problems
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
it0ken said:
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
Click to expand...
Click to collapse
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
hyelton said:
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
Click to expand...
Click to collapse
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
it0ken said:
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
Click to expand...
Click to collapse
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
hyelton said:
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
Click to expand...
Click to collapse
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
it0ken said:
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
Click to expand...
Click to collapse
Correct