Related
I attempted to install Mikfroyo, and for whatever reason it failed and left me in a perpetual boot loop. I recovered a previous nand, and now I'm having issues with my unlock and everything is running considerably slower. I've tried to wipe several times and recover but to no avail. What should I do now? I'm using clockwork recovery should I switch to AmonRA? Thanks for the help
what unlock method did you use?
I would try wiping and reflashing and see if it fixes the issues. It seems weird that you are haivng them after you nand as it should revert everything back. you didnt change anything else or add any app theme kernel?
This is going from bad to worse it won't recover from a previous nandroid back up now it gets stuck at Checking Md5 Sums and then nothing. Is clockwork the only way to wipe this thing or can I wipe it another way and just load a new ROM?
if you can get Amon Ra recovery isntalled you can try that I have problems now again with clockwork ussually reflashign it or using amon works
Dont freak out if you dont see your nandback ups thorugh amon ra. It looks in a diffrent place. you have 2 options youc an either wipe data with amon and try to flash the update.zip to clockwork and nandroiding or you can move the back up from clockwork>backup to a new directoty on the root of your SD card called backup.
once in the correct folder amon will see and be able to restore them.
download rom manager from the market and use it to reinstall clockwork. If already says you have the latest version of clockwork installed, use it to install AR and just use AR going forward (just don't try restoring a clockwork nand with AR), or use it again to reinstall clockwork after you've successfully installed AR.
hello I just replaced a broken EVO and now that it is rooted I am trying to restore my old backup from my previous evo.. I am having a problem though
I go through all the normal process to restore a backup and everything works fine the super user permission pops up and the phone reboots but instead of rebooting directly into the reboot session it just boots me into the clockwork mod recovery recovery menu.. when i select the folder the recovery files are located in it shows up blank.. what am I doing wrong here? In the past when I selected to restore a backup from inside the os it just rebooted and started restoring automatically.. I feel like an extra step has now been added and I dont know what it is?
I should also not that while I do not know if it is related or not when I try to restore the backup from the nandroid section of the recovery menu it hangs on checking md5 sums and then says error while flashing boot image!
mind you this is on 2 separate backups I created in the past with clockwork mod recovery
It's probably not a good idea to use an old nandroid backup on a new phone. Think of how kernels run well on some EVO phones and not others. Your current phone might even be one of the EVOs with new hardware.
Sent from my HTC EVO using XDA app
ok but can I still get all my apps and data back?
it would be terrible to lose all of that
and now to make matters even worse my phone is stuck on an endless loop on clockwork mod recovery I every time I select reboot system now instead of it booting into the stock rooted rom it just reloads the clockwork mod recovery menu.. what gives?
yeah, not good to load a backup from a different phone. This has been documented as happening. Just reflash whatever rom you want then radios then kernel. Sorry but if you didn't use a backup prog I thinkyou will have to manually restore apps. You may want to try titanium backup, solves the problem, use it and follow the backup instructions in Titanium backup wiki on their web site and you should be good to go next time.
Did you try a battery pull and reboot?
Sent from my HTC EVO using XDA app
Nandroid backups are phone specific, you can't move them from phone to phone. You probably hosed your RSA keys which means your 4g may be broke. If I were you I would try to flash a stock rom and then reroot if needed. If that gets you out of the bootloop your in. You maybe visiting a Sprint store for a replacement phone again.
guys I could really use some help here please!
I went back to the stock rooted rom today.. all day I was adding apps making changes restarting the phone no problems.. I finally get my phone set up how I like it so I decided it was a great time to make a backup so I open clockwork mod recovery and select backup it gives me the superuser permissions prompt and restarts.. instead of starting the backup automatically it sends me directly to the clockwork mod recovery menu and now it will not load the phone's OS at all just reboot after reboot into clockwork mod recovery this is a 1 day old evo what is going on here!!??
KingKash420 said:
guys I could really use some help here please!
I went back to the stock rooted rom today.. all day I was adding apps making changes restarting the phone no problems.. I finally get my phone set up how I like it so I decided it was a great time to make a backup so I open clockwork mod recovery and select backup it gives me the superuser permissions prompt and restarts.. instead of starting the backup automatically it sends me directly to the clockwork mod recovery menu and now it will not load the phone's OS at all just reboot after reboot into clockwork mod recovery this is a 1 day old evo what is going on here!!??
Click to expand...
Click to collapse
Hey that exact thing happened to me. it happened the first time i ever loaded anything on my phone. I freaked out. Turned out the Clockword mod recovery I had must have had something wrong. I went back into the part where you load the CWM from the computer. My phone is different than yours so I cant be sure but you go into bootloader by pressing stuff, its where the logo stays there the whole time. then you flash the CWM again. and then reload the operating system and stuff. should work but just redo the CWM again. Hope it works out for you. Hope thats what it is for you too.
So i tried to flash muiu rom thru rom manager and got caught in a reset loop at the boot screen. I then flashed a old cm7 zip from the recovery screen just to get the phone to boot. When i tried to restore my backup from rom manager it takes me to the recovery screen and does not restore ( just stays at the recovery screen). i really would like to restore that backup. any suggestions?????
Well, this won't help your back up problem, but trying wiping everything you can, except the SD Card and the flash MIUI in Recovery.
ROM Manager is really not a dependable way to flash a ROM.
Also, you try to reflash your recovery before you do anything and try the back up again.
Oh, and if you're not on it now, use Amon Ra for Recovery. Plenty of threads that tell you how to get it.
Thanks but is there any way to restore the backup I made with rom manager in recovery?
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
I will be travelling and i wont have access to odin for a little while, so i'm less inclined to go breaking things till i get back home. I thought maybe someone here has run into this or knows how to fix this.
Thanks for the help
Dom
wascalwabbit said:
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
Click to expand...
Click to collapse
Was the original CM11 nandroid made with the same recovery make and version which would not install it? I am pretty sure TWRP will not install a CWM or Philz nandroid. I don't know if there are issues installing a 2.6.x.x TWRP nandroid with the 2.8.x.x version of TWRP.
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
wascalwabbit said:
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
Click to expand...
Click to collapse
Since Philz was originally based on CWM I wouldn't expect it to work with TWRP nandroids either.
Have you tried installing only specific partitions of the nandroid, such as the /data/data partition where the user installed apps are stored. As opposed to restoring the entire nandroid. I have heard mention of this, but in your case it may be problematic since your nandroid is of CM11 and the ROM you are running is SlimKat.
Oh that's a great idea, thanks, that may work. I i'll just flash CM and then restore data. I'm literally heading into the jungle right now, so in not sure if I'll be able to try this out for few days, but I will as soon as I get a chance.
Thanks for tour help
Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.
Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.
In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0
It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.
Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.
I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.
I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)
I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.
Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it
Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.