After flashing my first ROM on my new Asus TF300T I attempted to do a restore from CWM recovery and I just get bootloop. I have tried factory reset and wiping cache and dalvic but to no avail. The only way to get my tab working again is to flash back to AOKP. I have read the thread by d_crossfader but It doesn't seem to be the solution to get nand restore to work to get me back to stock. Please Help.
OK so I solved this. Sort of. Flashed a cyanogen rom and then was able to restore but then no wifi. I assume this is a kernel problem. Gonna try going to stock kernel. Can someone tell me how to backup the kernel? do I need TWRP recovery to do this? Is anyone working on an amon-ra style recovery?
Same here but solved it
I had the same problem.
i was on US.29 and wanted to upgrade to US.30 so i said before i upgrade lets try a custom rom so i tried 1) SKANKWICH CM9 KANG build and then 2) [AOKP][Build 40][4.0.4] Unofficial AOKP. I found that both builds was similar but didn't like (for my reasons) and wanted to stay as close to stock. So i tried to restore my 2 hours ago, nandoid backup. Bootloops was the result. Wiped data,factory reset,dalvik cache, and restored 5 times but no hope.
Solved this by installing the SKANKWICH CM9 KANG build from the recovery and when the device started, i downloaded the US.30 and unzipped it to internals storage root. Then restarted the tf300t in recovery,wiped data,factory reset and installed US.30 zip and everything now is fine.
I dont know if the reason is that before the first rom install i forgot to restore (copy paste) the original build.prop file.
Also finaly the machine was unlocked,unrooted without any custom recovery.
I think this is just a bug with nandroid restores, saw a few people having problems.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
i downloaded the US.30 and unzipped it to internals storage root. Then restarted the tf300t in recovery,wiped data,factory reset and installed US.30 zip and everything now is fine.
Click to expand...
Click to collapse
Good to hear! This is what worked for me too.
I then had to flash recovery again and re-root.
I used Thing O Doom's method because his tool claims to solve boot-loops and bricks as well so I figured it would be handy to keep around. Also, it is simple to use.
BE CAREFUL to insert the correct recovery blob if you use his tool though!!!
Here's the link to his thread:
http://forum.xda-developers.com/showthread.php?t=1681155
Will Try
I will try peri-04 one click root to see if i still get bootloops after nandroid restore. But where do u find the recovery blob u said u used for your Tf300?
pankobios said:
I will try peri-04 one click root to see if i still get bootloops after nandroid restore. But where do u find the recovery blob u said u used for your Tf300?
Click to expand...
Click to collapse
Under "CUSTOM RECOVERY" section in the index thread:
http://forum.xda-developers.com/showthread.php?t=1697227
After you get the blob file rename it to "recoveryblob" and replace the one that comes in the PERI folder.
I downloaded Trickdroid and everything is good. before I did the download I backed up stock in TWRP.
When trying to restore stock it says 'completed' in about two seconds and when I then reboot I'm still on Trickdroid.
Was I meant to do a nandroid in cwm? Can't think why TWRP wouldn't just restore.
Obviously I still have the stock image on my sd card in the recovery folder of TWRP, so would there be any other way of flashing/installing it whilst bypassing TWRP if I have to?
I faced a similar problem and I freaked out. I installed MIUI to test it and then after I tried to restore my Trickdroid nandroid. Every time I boot the phone after restoring, it kept asking if I want to use the miui launcher and then an error appeared saying your phone has stopped and nothing works.
I did wipe everything (system, data, cache, dalvik) but the same thing happened over and over. It also refused to install any new ROM. I thought I had a brick. Then after a couple of reboots to recovery, I could install a fresh trickdroid and then on top of it I could restore my nandroid.
Now I am weary of installing anything new. I have a CWM nandroid as well just in case.
Sent from my HTC One S
I included a script which does not allow you to switch from Trickdroid to another ROM as it's the best anyway
Just kidding, try to reflash your Recovery or so
Just had an idea, would it make a difference if I flashed the new boot.img before wiping the current ROM? meaning, before restoring trickdroid, I flashed the kernel of trickdroid.
Because yesterday I had the same experience again this time with CM9 and I had to make a fresh install
Sent from my HTC One S
torxx said:
I included a script which does not allow you to switch from Trickdroid to another ROM as it's the best anyway
Just kidding, try to reflash your Recovery or so
Click to expand...
Click to collapse
Don't worry, I'm sticking with trickdroid, just wanted the peace of mind of knowing I could go back to stock anytime.
Now I can't, I'm stuck with you
Hi All,
I did a back-up before flashing Virtuous rom. If I want to go back to stock, do I just wipe everything, then restore the back- up through TWRP? I also downloaded somewhere stock boot.img. Not sure if I need that. Just making sure I won't brick my htc Butterfly(x920d)
enyaj said:
Hi All,
I did a back-up before flashing Virtuous rom. If I want to go back to stock, do I just wipe everything, then restore the back- up through TWRP? I also downloaded somewhere stock boot.img. Not sure if I need that. Just making sure I won't brick my htc Butterfly(x920d)
Click to expand...
Click to collapse
just restore from the backup that's enough
You will need to flash that boot.img in fastboot also otherwise it may not boot or if its does, then some of the modules like wifi bluetooth may not turn on ... safer to flash the stock boot
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Hi i have restored my Nandroid backup i need stock recovery
i have search everywhere can't find it
They don't exist. Flash a stock firmware to return your device to stock and go from there. Beware that flashing a nandroid backup may be the last thing that phone ever does. Sometimes it's best to just start fresh.
shivadow said:
They don't exist. Flash a stock firmware to return your device to stock and go from there. Beware that flashing a nandroid backup may be the last thing that phone ever does. Sometimes it's best to just start fresh.
Click to expand...
Click to collapse
I have done the SDCard Method and everything is okay