Attempting to update from RLS9 to RLS10. Had read problems with TWRP so loaded Phitz CWM and made full backup. Have original S4 and rooted. Did full wipe with CWM couple of times but when tried to install RLS10 says bad file. And, my backup file says MD5 mismatch.
So, naturally at this point, I'm in a mess. System/date etc wiped. Only boots to Samsung custom unlock screen.
Have a lot of reading to do. Would appreciate some advise on where to start....
Thanks in advance.
Also have a complete TWRP backup. If I can get back to TWRP instead of CWM, I could recover from that file. Any suggestions?
Download it again on your computer. Transfer it from the puter to phones sd card, recheak md5, and flash
There's an option in Phil's touch to recover from a twrp backup I don't know if it works tho?
hyperdrive powered s4
---------- Post added at 02:02 AM ---------- Previous post was at 01:52 AM ----------
It says in the main thread on philz touch that the twrp restore option works
hyperdrive powered s4
Thank you both for great advise. Was able to get back to CWM recovery and flash TWRP backup file. Not certain if worked 100% but at least enabled me to re-load TWRP via GooManager and then reflash the backup via TWRP. Worked Great!!! My alternative was to Odin back to original.
Once again, thank you, thank you, thank you....both.
Ur welcome glad it worked out.
Sent From My Hyperdriven S4
Related
Hi,
My phone boots to TWRP recovery only. I can boot into TWRP recovery, flush any ROM and set it up but after reboot my phone is not coming up.
It boots to the Samsung logo with BLACKSTAR BLACKJELLY ROM or to the AOKP logo with [ROM][4.3.1]*10/24 update* AOKP for SGH-I717 [The Family/AllianceROM]
Any help?
ursusca said:
Hi,
My phone boots to TWRP recovery only. I can boot into TWRP recovery, flush any ROM and set it up but after reboot my phone is not coming up.
It boots to the Samsung logo with BLACKSTAR BLACKJELLY ROM or to the AOKP logo with [ROM][4.3.1]*10/24 update* AOKP for SGH-I717 [The Family/AllianceROM]
Any help?
Click to expand...
Click to collapse
I got similar problem with beanstalk 4.3.
CWM and TWRP were tried to make backups, and every time of rebooting need a fully wipe and restore.
Even when a rom failed to boot, backup, factory reset and restore will make it bootable once.
Any idea?
---------- Post added at 05:03 PM ---------- Previous post was at 04:28 PM ----------
Not knowing the reason, but I tried to the oldest TWRP I can found (2.2) and it worked well.
First restore with 2.6 then flash 2.2, and after another cycle of backup and restoring, without booting up yet, boot up at last and it works seamlessly with rebooting. Don't know if I can flash back to 2.6 but no need to bother again. 2.2 is just as good, for me.
Hope it help.
hotgly said:
I got similar problem with beanstalk 4.3.
CWM and TWRP were tried to make backups, and every time of rebooting need a fully wipe and restore.
Even when a rom failed to boot, backup, factory reset and restore will make it bootable once.
Any idea?
---------- Post added at 05:03 PM ---------- Previous post was at 04:28 PM ----------
Not knowing the reason, but I tried to the oldest TWRP I can found (2.2) and it worked well.
First restore with 2.6 then flash 2.2, and after another cycle of backup and restoring, without booting up yet, boot up at last and it works seamlessly with rebooting. Don't know if I can flash back to 2.6 but no need to bother again. 2.2 is just as good, for me.
Hope it help.
Click to expand...
Click to collapse
Thank You, Man!!! It helped I've just downloaded the 2.2 viersion from here http://goo.im/devs/OpenRecovery/sgh-i717, flashed it and reinstalled BLACKSTAR
Thank you!! I have been having this same issue, and couldn't figure it out for the past few days. AT&T Samsung SGH-i717.
I started with TWRP 2.6.3.0 and using ROM BeanStalk-4.3.1009-20131015-quincyatt.zip (from thread [Rom][JellyBean][4.2/4.3][4.4 Apha Preview][PAC kernel]).
I used ODIN3.07 to get TWRP 2.6.3.0 set up, then did backups, wiped, and installed 4.3. It would run FLAWLESSLY, until it was powered down, or rebooted, at which point I would get the initial Samsung pop, then black screen. This was happening with 4.3 as well as the backup from stock 4.1.2 (I think).
TWRP files:
http://goo.im/devs/OpenRecovery/sgh-i717
Started with:
openrecovery-twrp-2.6.3.0-quincyatt.img.tar
Downgraded to:
openrecovery-twrp-2.2-sgh-i717-signed.zip
In case anyone is confused, as I was initially..... here is what I did to get it to work....
1. From TWRP 2.6.3.0, wipe & restore backup of 4.3, then shut down.
2. Boot to TWRP, install openrecovery-twrp-2.2-sgh-i717-signed.zip from within TWP, shut down again.
3. Boot to TWRP again, should be at 2.2 now, do a backup of current install.
4. DO NOT REBOOT OR POWER DOWN
5. Restore the back up you JUST MADE
6. Reboot
So far so good, over a dozen test reboots and power offs, no issues yet.
3 new members, helping each other, help themselves.
this is great, some folks who are not afraid to read and the confidence to experiment.
good job to all 3 of you and an official thanks to each by using the thanks button at the bottom left of each post of that person
welcome to all
ursusca said:
Hi,
My phone boots to TWRP recovery only. I can boot into TWRP recovery, flush any ROM and set it up but after reboot my phone is not coming up.
It boots to the Samsung logo with BLACKSTAR BLACKJELLY ROM or to the AOKP logo with [ROM][4.3.1]*10/24 update* AOKP for SGH-I717 [The Family/AllianceROM]
Any help?
Click to expand...
Click to collapse
okay so this is a very old post but i guess i found a working solution for this!
i have Galaxy A7 (SM-A700FD) 5.0.2
in basic terms:
-u need to remove TWRP recovery from your phone totally.
-i Flashed stock android recovery (well i got it by experimenting, as i rooted my phone again by ODIN it replaced the TWRP recovery with android recovery(turn off Auto-Reboot))
-you will be stuck in boot loop mode (stuck with the logo- good news is you are out of TWRP recovery boot loop)
-you have to get to boot loader anyhow (either by adb commands or vol down, home, Power key pressed all together)
-Flash TWRP recovery again using ODIN (turn of Auto-Reboot)
-hold the power key which will try to restart the phone.
-still it is boot loop mode.
-enter Boot loader (pressing Power key, Volume down, home- all three keys together or by adb commands)
-enter TWRP recovery (pressing Power key, Volume up, Home key- all three keys together or by adb commands)
-Restore your backup
-and you are good to go
hotgly said:
I got similar problem with beanstalk 4.3.
CWM and TWRP were tried to make backups, and every time of rebooting need a fully wipe and restore.
Even when a rom failed to boot, backup, factory reset and restore will make it bootable once.
Any idea?
---------- Post added at 05:03 PM ---------- Previous post was at 04:28 PM ----------
Not knowing the reason, but I tried to the oldest TWRP I can found (2.2) and it worked well.
First restore with 2.6 then flash 2.2, and after another cycle of backup and restoring, without booting up yet, boot up at last and it works seamlessly with rebooting. Don't know if I can flash back to 2.6 but no need to bother again. 2.2 is just as good, for me.
Hope it help.
Click to expand...
Click to collapse
Thank you very much for this tip! :laugh: Simply went to the official twrp .me site, chose the first img, and flashed it in the way described there. Phone booted fully now.
I have an S4 rooted on MDK with TWRP 2.5.0.2
I have been on Eclipse TW 2.0 since he put it out, and decided to try CM11 today. I flashed, booted, set it up and upon reboot I get stuck at the splash screen.
I restored my backup, which won't boot. I flashed the new Eclipse ROM, which booted and upon reboot it hangs at the splash screen,
I restored my orignal nandroid and it booted, but upon reboot it hangs at the splash screen.
No matter what I do now, I can only get one boot before it hangs on that splash screen. I have done "Fix Permissions" and wiped dalvik/cache
Any ideas? at this point I am even thinking of just odin back to MDK and re-rooting if it is possible.
Is TWRP out of date or something? This is really weird.
sparkerjc said:
I have an S4 rooted on MDK with TWRP 2.5.0.2
I have been on Eclipse TW 2.0 since he put it out, and decided to try CM11 today. I flashed, booted, set it up and upon reboot I get stuck at the splash screen.
I restored my backup, which won't boot. I flashed the new Eclipse ROM, which booted and upon reboot it hangs at the splash screen,
I restored my orignal nandroid and it booted, but upon reboot it hangs at the splash screen.
No matter what I do now, I can only get one boot before it hangs on that splash screen. I have done "Fix Permissions" and wiped dalvik/cache
Any ideas? at this point I am even thinking of just odin back to MDK and re-rooting if it is possible.
Is TWRP out of date or something? This is really weird.
Click to expand...
Click to collapse
In my experience the hanging at samsung splash screen has been normal upon reboots about 50% of the time on any aosp rom ive run. Have you tried when it hangs at the samsung screen to do a battery pull and try to turn device back on? For me this always fixes the issue.
Well, I pulled the battery about 20 tines last night and I think it boots about 10% of the time, even after flashing back to a TW ROM.
Any suggestions to try?
sparkerjc said:
Well, I pulled the battery about 20 tines last night and I think it boots about 10% of the time, even after flashing back to a TW ROM.
Any suggestions to try?
Click to expand...
Click to collapse
Wow thats terrible. Have you tried changing recoveries? I know most people have great luck with twrp 2.5.0.2 which you are running but maybe try cwm to see if it helps? I am currently running philz touch recovery based off of cwm 6.0.4.5 and it seems to happen less frequently. Also twrp has an updated version that you may try if you prefer that recovery. Just a thought
---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------
You can try twrp manager from the play store. Advanced then install recovery to get updated to the most recent version. I believe the goomanager install of twrp is borked at this point.
---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------
sparkerjc said:
I have an S4 rooted on MDK with TWRP 2.5.0.2
I have been on Eclipse TW 2.0 since he put it out, and decided to try CM11 today. I flashed, booted, set it up and upon reboot I get stuck at the splash screen.
I restored my backup, which won't boot. I flashed the new Eclipse ROM, which booted and upon reboot it hangs at the splash screen,
I restored my orignal nandroid and it booted, but upon reboot it hangs at the splash screen.
No matter what I do now, I can only get one boot before it hangs on that splash screen. I have done "Fix Permissions" and wiped dalvik/cache
Any ideas? at this point I am even thinking of just odin back to MDK and re-rooting if it is possible.
Is TWRP out of date or something? This is really weird.
Click to expand...
Click to collapse
Here is cwm 6.0.4.4 if you want to try that as well. It's already loki'd so just flash it.
https://www.dropbox.com/s/ldlgv0iaxf1j8ya/recovery-cwm-touch-6.0.4.4-jfltevzw(loki).zip
Remember that your backups will not work when you change/update recoveries so you will want to make sure to backup your current setup if you want.
flyinj54 said:
Wow thats terrible. Have you tried changing recoveries? I know most people have great luck with twrp 2.5.0.2 which you are running but maybe try cwm to see if it helps? I am currently running philz touch recovery based off of cwm 6.0.4.5 and it seems to happen less frequently. Also twrp has an updated version that you may try if you prefer that recovery. Just a thought
---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------
You can try twrp manager from the play store. Advanced then install recovery to get updated to the most recent version. I believe the goomanager install of twrp is borked at this point.
---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------
Here is cwm 6.0.4.4 if you want to try that as well. It's already loki'd so just flash it.
https://www.dropbox.com/s/ldlgv0iaxf1j8ya/recovery-cwm-touch-6.0.4.4-jfltevzw(loki).zip
Remember that your backups will not work when you change/update recoveries so you will want to make sure to backup your current setup if you want.
Click to expand...
Click to collapse
Thanks for the help, my current backup appears to be no good anyway so I'm kind of hosed.
Once I get stuck at that splash I have only made it through 1 time by fixing permissions, then it froze the next boot. 5-6 battery pulls and it still won't go.
I'm afraid to try a new recovery, I'm afraid to do anything really. I almost want to just odin to MDK and start over. Currently I am on a fresh install of CM11, on the first boot just trying to make it through my work day without rebooting lol.
Took me 5 flashes to get it to boot at all.
After pull the battery,did you hold the vol up and the power and wait until the phone vibrate and release the power button and keep holding the vol up until vibrate again and then choose your nandroid.....
android-incredible said:
After pull the battery,did you hold the vol up and the power and wait until the phone vibrate and release the power button and keep holding the vol up until vibrate again and then choose your nandroid.....
Click to expand...
Click to collapse
No I just booted into TWRP and did it from the menus. Is there something special about doing it this way?
I have tried to install smartdroid in my s3 using TWRP as recovery manager. Since I previously backed up my stock rom I was able to back from a flashing problem I had "some changes failed". As I saw this can be overcame using Philz I changed the recovery. Then I tried to install, again, the smartdroid. This time it finishes but never booted up correctly.
Now, I am not able to reload my backed up rom (as it was made with TWRP and now I have Philz) nor installing smartdroid. So well, I want to install TWRP but I haven't seen the zip file to install it from Philz recovery What can I do?. Can I use odin from Philz?
Thanks
I didn't remember the download mode!, This post saved my day http://forum.xda-developers.com/galaxy-s3/help/twrp-flashing-tar-t2680354
Hi,
Im relatively new to the Z Ultra.
I have an unlocked bootloader, rooted phone.
Recently, I went from the stock ROM rooted to Paranoidandroid.
Now I have decided to go back to my stock Firmware. I have a Nandroid backup.
The issue is I am stuck inside a recovery from PA that does not want to restore my stock Sony ROM.
What is the best way for me to go from my AOSP ROM back to my Sony one via a restore in recovery?
Thanks.
ukjm2k said:
Hi,
Im relatively new to the Z Ultra.
I have an unlocked bootloader, rooted phone.
Recently, I went from the stock ROM rooted to Paranoidandroid.
Now I have decided to go back to my stock Firmware. I have a Nandroid backup.
The issue is I am stuck inside a recovery from PA that does not want to restore my stock Sony ROM.
What is the best way for me to go from my AOSP ROM back to my Sony one via a restore in recovery?
Thanks.
Click to expand...
Click to collapse
Is it just not showing the backup or does it give an error when trying to restore?
Well the recovery that comes with PA custom ROM, CWM v6.0.5.0 will not allow me to browse to the TWRP recovery location that was used to backup the Sony stock ROM, so I copied the backup to the CMW folder.
When trying to restore it prompts about missing MD5 sums for all the backup partitions, but when I say proceed anyway it gives an MD5 error.
Actually, here is the full error:
Checking md5....
No MD5 verification performed...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image...
Before trying the restore this stock ROM, should I be flashing a boot.img for stock ROM?
Where is this?
Thanks.
ukjm2k said:
Well the recovery that comes with PA custom ROM, CWM v6.0.5.0 will not allow me to browse to the TWRP recovery location that was used to backup the Sony stock ROM, so I copied the backup to the CMW folder.
When trying to restore it prompts about missing MD5 sums for all the backup partitions, but when I say proceed anyway it gives an MD5 error.
Click to expand...
Click to collapse
Okay I would make sure you still have a copy in the twrp folder and use FlashTool to flash a boot img. that has twrp recovery. It doesn't need to be compatible with PA as you won't be booting into ROM but booting straight to recovery to restore backup.
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
ukjm2k said:
Actually, here is the full error:
Checking md5....
No MD5 verification performed...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image...
Before trying the restore this stock ROM, should I be flashing a boot.img for stock ROM?
Where is this?
Thanks.
Click to expand...
Click to collapse
Basically just need boot img. with twrp to restore with, it will be overwritten with whichever one you had when backup was made.
Got you!
Downloaded a kernel that had TWRP recovery, flashed the .img via Fastboot, then booted into TWRP, restored.
Thanks for the help, and sorry about the double post!
ukjm2k said:
Got you!
Downloaded a kernel that had TWRP recovery, flashed the .img via Fastboot, then booted into TWRP, restored.
Thanks for the help, and sorry about the double post!
Click to expand...
Click to collapse
You're welcome. Just glad it was an easy fix!
Yeah, I am too!
I'm new to all this flash.img flashing first, my last phone this wasnt needed.
Thanks again.
ukjm2k said:
Yeah, I am too!
I'm new to all this flash.img flashing first, my last phone this wasnt needed.
Thanks again.
Click to expand...
Click to collapse
It's not normally needed here either, just on odd occasions like this, or when you first need recovery
Tried flashing SR KK Rom.. Was on AOKP 4.4.4 but was super buggy.
Flashed without issue, but stuck in red verizon bootup screen. I skipped flashing via ODIN the 4.3 firmware. I resorted back to stored TWRP backup, all good and usable.
To try and fix, i changed from TWRP to Philz per recommendation int he thread. Then reflashed. No go still. Tried to go back to TWRP backup, but Philz doesnt like it, and now i cant get to my phone via USB to reinstall TWRP.
I have AOKP still on my phnoe, so tried to reflash, but no dice.
I'm stuck with an unusable phone, and it looks like NO way to fix it.
I can access phone and flash via ODIN. But, i can not see phone via USB (in order to copy over ZIPs). I can mount my external SD, but then when i unmount, data goes away.
So screwed - need help so bad.
Rom that started it all:
http://forum.xda-developers.com/showthread.php?t=2582313
Okay, used ADB push to get TWRP to the phone. That worked... Restored backup, but because of flashing the 4.3 firmware, lost root per TWRP
However, when i boot now, it just sits at "Samsung Galaxy Note II" screen. Doesnt go any further. EFf me.
EDIT: I see why.. backup restore failed. arghhhhhhhhhhhh
I cant flash anything. Everything fails.
Bump
Stop trying to restore backups and wipe everything in twrp and then flash a clean a rom of your choice.
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
DatacomGuy said:
Bump
Click to expand...
Click to collapse
No need to bump your thread. We have small, but talented group of ppl that can help you but bumping because of no response instantly isn't good taste.