I use rom manager premium and the touch recovery. I'm having issues installing and restoring roms. First problem is i'll download a rom, try to install, and for some reason it either completely boot loops or just goes back to cwm recovery after trying to reboot. Then when I try to restore to the backup I just made of the working rom it gives me an md5 mismatch error. I did not rename the backup file or put it into a different folder.
Twice I have gone back to complete stock, unrooted and then rooted again and tried and this same issue has come up.
I feel like this all may have started either with me trying an AOKP rom or trying a new 4.0.4 rom.
Any insight on this?
Thanks!
Try using a standard CWM recovery i.e NOT Touch! IIRC it caused a few issues in certain Circumstances
Related
In Brief:
Got New Phone due to light leak. Finally after 2 months
Came with 2.2 on it.
Used the new 2.2 Root Guide with Unrevoked. Worked great.
Installed VirusROMX - working great.
Wanted to try out the Final 6.0 ROM from Cyan.
NanDroided the ViruxROMX
Got an error 7? So I found this link that was to correct that issue.
http://forum.xda-developers.com/showthread.php?t=752832
Flashed the new Hboot and it allowed me to install the CYAN R6.0.
CYAN ROM - Keep on Rebooting and Reloading the CYAN Boot Screen after setup and scrolling some apps.
Removed it and went for a Nandroid Restore.
I get the MD5 Checksum message and then trying to reload boot image. And Boot Image cannot load.
I have tried to reflash the recovery(Clockwork) and still no good.
My working Daily with all my updates and apps are on the Nandroid. I would hate to lose it.
Any help would be appreciated.
Anyone?
Sent from my DROIDX using XDA App
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
tomh1979 said:
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
Click to expand...
Click to collapse
That's is what I tried to do. It would say boot image unloadable and spits me out to the HBOOT options. With no ROM loaded and messes up my current ROM in place.
At least for me when I restored in the past and I have done it often is that I would just restore and not wipe or anything since the restore does all of that for me. Well in this case it does not and when it cannot restore I have to reload a new ROM again in recovery and start the process all over again. I have tried the NANDROID again after going through the entire ROM reload again and still a no go.
I can't nandroid restore my old daily which has text messages and everything that I wanted to reference. I can live without it but the inability to restore any Nandroid is driving me crazy.
It happened when I flashed that HBOOT update on the link I provided in OP. I am just trying to figure out how to reflash the old image back so I don't have to worry about it. The only reason I did it in the first place is to test out the Cyanogen R6 and that wasn't a good experience.
I guess I could post in the thread that started all of this to ask. But I thought I would keep the SECTION POLICE from hounding me about posting in the wrong section
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
tomh1979 said:
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
Click to expand...
Click to collapse
The PC36IMG.zip - I will try the flash.
The Hboot through PC36IMG.zip worked fine. It's the nandroid thats fuxored. Will try later on and see. Thanks for the suggestion.
I had to redo the second part of the Froyo 2.2 update with the Rooted Froyo and the 2.2 unrevoked. It finally worked and I was able to restore. I really want to try out the CM 6.0 again in the future but not at the expense of time to restore to get it back.
So I am trying to remove MIUI and install a diff ROM but I am having serious problems because when I try to install the other ROM from ROM manager, it brings me to the manual recovery every time. I also tried to do a factory reset and it still brings me to the recovery. I have an old backup of my ROM but even trying to restore to that it reboots me into recovery. I am not sure what to do at this point
Just restore it manually through recovery. I've only used ROM Manager maybe twice, to update CWM. Otherwise, I do everything manually so I know it's being done right
Don't try to flash a ROM via ROM Manager, download the ROM's zip file and flash via recovery.
EDIT: What BrettApple said.
Sent from my ADR6300 using xda premium
midnite8 said:
So I am trying to remove MIUI and install a diff ROM but I am having serious problems because when I try to install the other ROM from ROM manager, it brings me to the manual recovery every time. I also tried to do a factory reset and it still brings me to the recovery. I have an old backup of my ROM but even trying to restore to that it reboots me into recovery. I am not sure what to do at this point
Click to expand...
Click to collapse
That's the best way to do things go straight to recovery and do things manually
Sent From My Optimized HTC Incredibly Dinc
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.
Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.
Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!
Don't wipe system in twrp.
makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.
re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!
I'm new to rooting phones and have run into an issue with my SGH-T989. First let me say that I did several days worth of reading and investigation to make sure that I was comfortable moving forward. I rooted the phone without any issues using ODIN3 v1.85 and CWM SuperSU v0.87.
After that, I decided I'd like to try installing a ROM - Beanstalk-4.4.2_R1-v205-Linaro-20131216-hercules.zip. Again, I followed very specific instructions but ran into issues first with the version of JB radio I had on the phone (T989UVLI1).
When the BeanStalk ROM install failed, I tried using CWM Recovery to restore my stock ROM but that also failed on an MD5 hash mismatch. I suspect that's probably because I modified the folder name after I ran the backup- again, following some online instructions but wasn't really thinking when I did it.
I rebooted the phone after the failed stock restore, it went back to a semi-stock state like it was a new phone set up however I was having issues with entering recovery mode through CWM and TitaniumBackup was acting a bit flaky as well.
I was finally able to get the phone to enter CWM Recovery mode by holding down the power and volume up/down buttons and then proceeded to flash the radio to T989UVMC6 and flashed the ROM- however I forgot to wipe the flash before I installed Beanstalk.
Now the phone boots into Beanstalk, but none of the GAPPS work and I can't get into Play Store to try and install anything to fix the problem.
I'm also starting to suspect an issue with the rootware since I'm getting messages to that effect through TB and CWM ROM Manager won't launch without immediately force closing.
Anyone have any suggestions to offer?
Thanks in advance!
Quick update - I got GAPPS installed and so far things seem stable. Still not able to restore my stock ROM though, so I may be stuck with BeanStalk 4.4.2 for now.
I've been running CM11 nightlies for a while now, but recently decided to switch back to the dreaded touchwiz, as some apps weren't operating correctly. I used CWMR to restore the backup I had made previous to installing CWM. Booting up revealed many processes failing during the setup process, as well as the absence of the keyboard. Being a bit noobish, I installed a stock rom/recovery, hoping that would fix the issues. It did not. It stalls at "Just a sec..." before Setup Wizard quits and it loops indefinitely. Problem is I now can't flash a new rom or restore. I've tried installing cwm with no luck since, but take this with a grain of salt as I was admittedly a bit panicky during. Any help is greatly appreciated.
So are you still looking to restore or find any method to have your device boot up again...?
Spark91 said:
So are you still looking to restore or find any method to have your device boot up again...?
Click to expand...
Click to collapse
Yes. I've had no luck the past few days with it. Might give up on it if I can't get it working.
Head to rwilco12's website and under downloads for the Galaxy S II Sprint SPH-D710, Download the Odin OneClick of the stock rooted GB27, You can choose between deodexed or odexed, pick your poison, note that choosing Full Restore wipes internal and No_Data preserves internal storage.
Put device in download mode and restore.
Once you've fully restored, Download AGAT's gb27 source recovery and flash via recovery flasher on device or Odin on PC. Start up into recovery and try restoring your GB27 ROM again. I remember there being a guide when flashing back and forth from cm to tw and there was a specific way you had to restore it, I've lost the thread but still looking for it for you.
But until then, try the Odin one click method and see where it flies there