Ok, using a Samsung galaxy s5, kltespr, running 5.0 lollipop. recovery twrp 2.8.1 Been failing to install a custom rom tried a nightlie from cyanogenmod 12.1 i belive..didnt work recovered had no problems. Reboot recovery to try again. Pulled my sd card, did the stupid thing and typed yes to wipe all data, thinking once i put sd back in my recovery would fix it. Turns out i didnt have 100% backup now i dont have a ui...any pointers??
Odin a full tar and start over
Related
I tried following some guide online to get my S3 rooted and running stock Jelly Bean and all was going so well...Casual Root worked like a charm, cyanogen all set. But when I went to install the ROM and Gapps in recovery it kept getting hung up. I assumed this was due to encryption on the device from my work email, so I went back to factory andremoved the account and decrypted the device.
Then it was back to recovery to flash the ROM and Gapps. All seemed to go well,the ROM installed fine, Gapps installed fine, but reboot got stuck at the cyanagenmod loop. I had mad a backup of the original ROM, but I must have saved it to the internal SD card by accident before i factory wiped. I thought my best bet would be to load the Gapps and ROM onto my external SD and flash from there, but I cant get it to mount.
The one good thing that I can do is get to the Odin boot screen. Anyone think there's a chance I can get Odin to flash something that will boot? And does anyone have suggestions of what to flash?
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?
Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking
Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk
Confirmed also an old recovery for me as well. Thank you very much!
Okay this is a weird one, Note 10.1 runs out of battery a few nights ago, go to plug it in for charging and it hangs on the "samsung galaxy note 10.1 screen". I had been running Cyanogen 11 for a few months just fine and before that Omni (Both 4.4.2) no dramas with CWM recovery 6.0.3.6. I can still get to Download/ODIN mode and CWM.
Now here is the fun part(s)
1. Firstly I tried reflashing the roms from CWM, after all I flashed both of them from the same recovery and they were still on the external sdcard. Both gave set metadata recursive status 7 error messages.
1.NB Whenever I selected the internal storage to search for a zip CWM would close immediately (crash?) and go back to the galaxy note 10.1 screen and hang there still. Also does this on other options, so I can't reach the backup I made on the internal storage
2. After googling that it seems that 6.0.3.6 can't flash 4.4.2 roms so I flash a later version using ODIN, it says success on the PC side, yet nothing changes in tablet, same when trying with twrp. CWM 6.0.3.6 won't budge
3. Try flashing the official rom (N8010XXUCMK2_N8010XSACNA2_HOME) from sammobile using ODIN, same problems as before, download mode shows the bar filling up so does ODIN, says it passed, still nothing.
4. Try old 10.2 Cyanogen build, no error message but still hangs on samsung galaxy note screen
5. Try repartitioning whilst flashing, various .pit also used, no dice. However I can now mount /data from cwm still can't mount /efs
6. Read about eMMC bug possibly being induced by Cyanogenmod, open up tablet to to check numbers on eMMC module, doesn't match any of the affected numbers.
7. Try above steps multiple times, including flashing each right after each other.
8. Cry
9. Look at new tablet options (Damn no good ones with softkeys)
10. Back to desperate flashing ODINing and scrolling through CWM
So any ideas?
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
jika23 said:
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
Click to expand...
Click to collapse
Where exactly is the PIT file I should be looking for? Been looking for a while now.
hi folks,
My device was on cm11 and I wanted to try the slim6 rom and the new TWRP update for the recovery. I tried the TRWP unified version of Andi but after the flash succeded , everything from the tablet (Rom, data, system, etc..) was completly erased. Now the new recovery dosent read anything, even if I put a SD card with the files to flash. I tried to flash a another recovery with odin but the odin program freeze when I select the recovery . I can't find any working links for stock firmware and the one from sammobile crash most of the time before the end.
Any ideas of what happened on my device ?