I have an MDK S4 and have been flashing custom roms all along.
It had been like a whole week since my last flash so I downloaded Chaos rom and wiped my data and went to install it just like I've done 100 times before with other roms. When I swipped on install it came up with a red "Failed" message. I thought this was odd, but I've had it happen before with corrupt/incomplete/errored downloads.
Since I had already wiped I went to go do a fresh install of the basic NG2 rom I was on prior to wiping and got another "Failed" message.
Flashed my recovery image (which thankfully worked.) I repeated the whole wiping/attempting to flash/restoring my recovery image cycle again hoping it would work the second time around... which it left me back on my recovery image.
Not sure what went wrong. Tried to update TWRP to a newer version through goo manager, but that doesn't seem to be working either.
Thoughts?
Worked perfectly. Thanks!
Related
'm running stock Froyo on a T-mobile Vibrant. I tried to get Rom Manager to backup the current rom. When it boots into recovery and I select reinstall packages it fails on signature. Apparently this is a 2E/3E Recovery issue.
So I went ahead and ran the 3e_recovery installer
http://forum.xda-developers.com/showthread.php?t=833423
which says it succeeded. Now when I run backup the current rom, it boots to recovery, and reinstall packages no longer complains about signature. instead it just reboots back into recovery so quickly that I can't really read the 4 lines of messages, though I can just make out a "replacing stock .. " as one of the last lines.
Reboot system still does work, so I can get back into normal operation, but I'm stuck as far as gettting a backup.
Help!
Well things have changed a bit.
I went ahead and did the KB5 upgrade, which got me back to stock recovery. So now I'm back to the case where CWM will fail on signature.
How are other Vibrant users dealing with this?
- what color is it?(lol, thats funny. I werk in parts)
- is there an update zip? what happens if you flash that?
kmandel said:
'm running stock Froyo on a T-mobile Vibrant. I tried to get Rom Manager to backup the current rom. When it boots into recovery and I select reinstall packages it fails on signature. Apparently this is a 2E/3E Recovery issue.
So I went ahead and ran the 3e_recovery installer
http://forum.xda-developers.com/showthread.php?t=833423
which says it succeeded. Now when I run backup the current rom, it boots to recovery, and reinstall packages no longer complains about signature. instead it just reboots back into recovery so quickly that I can't really read the 4 lines of messages, though I can just make out a "replacing stock .. " as one of the last lines.
Reboot system still does work, so I can get back into normal operation, but I'm stuck as far as gettting a backup.
Help!
Click to expand...
Click to collapse
i have exactly the same issue...i tried everything posted here but not working...last chance is to odin back i guess
If I were you I would do a back up then> odin back to stock then> root then> download Rom manager Then> Flash a new custom Rom. The Stock TMO one is sucky and does not run as smooth as the custom ones. Then you will an awesome phone
I've been running Gingeritis for ages and decided to upgrade. My first choice was CM7, so I download it, throw it on my SD Card, boot into recovery, wipe everything then attempt to flash. I get no error message but when I go to reboot it stays locked on the HTC screen.
I've updated to the newest radio and am now running, or at least I think it flashed correctly, IMOSEYON (AOSP) leanKernel.
I've tried other ROMS and my phone won't take anything, it just stays on the HTC screen after giving me no errors during flashing.
Any help? I'm pulling my hair out over here.
Attempted a factory reset and wiped everything on the phone and nothing. It won't boot at all and there's nothing I can recover to now. Wonderful, am I screwed now?
Do u have a backup you can revert back to?
Not anymore. I cleared everything hoping to go back to stock, I think all I have left is a blank slate.
Update your recovery version.
How would I go about doing that?
What recovery are you using now? Then I will search for your latest version. The recovery can be in a PG05IMG.zip. Installation is the same as when you flashed the updated radios.
I'm on clockwork recovery, could that really be the problem not allowing it to fully flash the ROM?
Also, when I'm in recovery and trying to install these new ROMS they "finish" in less than 20 seconds...I know that's not normal.
OK. Thank you for letting me know your recovery. Latest version of clockwork is 5.0.2.1
ClockworkMod Recovery flashable from bootloader - xda-developers http://bit.ly/w0BGFZ
Installed CWM and rooted my phone tonight, everything went well. I have a canadian sgh-i527m. I took a backup through cwm and tried to install cyanogenmod and it failed. I don't recall the error....tried two other and both both failed as well. Now I can reboot and get into recovery but when i try and restart the phone, it just reboots itself a couple times and goes back to recovery on its own.
I I tried restoring the backup and says it's successful, but then it hangs at the glowing samsung screen. I wiped the cache and device and can only get to recovery. I'm downloading the stock os for bell and will install that through odin in the morning, but can anyone help with what i'm doing wrong? I never had any issues installing many roms to my note II.
Hello, i will try to be thorough.
BUT, i am a noob and didnt write down everything i did.
Have a I717 at&t note 1. with the 4.1.2 update originally OTA installed by keis.
I recently rooted it using Saferoot. it went well and i didnt see any problems. i flashed a custom rom and didnt like it so using clockworkmod recovery i went back to the 4.1.2. I then tried pac lollipop >pac_quicyatt_lp.beta-1.unofficial_20150327< i liked this rom but needed to flash Gapps.
This is where the trouble started. i didnt/dont know the proper procedure to flash the Gapps on top of or into the rom.
I first tried >gapps-5.0.x-20150404-minimal-edition-signed.zip< and it looked like it loaded correctly. but nothing appeared in the phone. the pac rom was still working well.
I then did more research and tried >gapps-lp-20150222-signed.zip< , again it looked like it loaded well but nothing showed up "in" the phone.
right here is where things got screwy. i had been using clorkworkmod for recovery and rebooting. and i think somewhere in developer settings i clicked something about how rebooting is handled.
because after trying to install the Gapps it went into Cyanogen recovery... and loops.
no matter what i do it goes back to cyanogen recovery.
I never knowingly installed cyanogen and dont know why it all of a sudden is going into cyanogen recovery over and over.
a list of things that may have bearing:
1. i tried reinstalling the pac rom. it loads and completes but it still just goes to recovery.
2. tried different ways of clearing cache and data wipes.
3. computer, kies, and odin 3.09 do not recognize phone.
4. have proper drivers on computer. phone was previously recognized by kies and cpu (4.1.2).
5. currently the only way to get anything into phone is by pulling sd card and reinstalling with info on it then using cyanogen recovery.
6. i have searched for about 11 hours and tried a bunch of things. but just restarts in cyanogen recovery
7. i was scared to fully try things i found that wernt specifically for the i717.
8. i could not find an original gingerbread rom. they all seemed fishy (needed downloaders. or ended in .zip.rar)
9. had backed up with clockworkmod and with titanium recovery (while in 4.1.2).
I dont know if i can reach the clockworkmod save through cyanogen recovery.... if so it seems like a great option.
10. at the bottom of the screen while loading rom is.... ---->>> E: cannot load volume /misc
11. only pac rom will successfully re-flash (even though it still just goes back to cyanogen). any other flash and it crashes halfway through.... i then restart and it just loops back to cyanogen recovery.
I searched here and tried the five recommended posts.
I could not try a lot of the "fixes" because the phone isnt recognized by cpu or odin (computer does beep when connected but doesnt show up anywhere).
Can you help me get back my phone please?
Randall
added
This is the only site i am asking for help on. I am willing to reply quickly and put in the time!
Thank you very much for reading this far.
Randall
Hello everyone,
I have made some mistakes:
I installed lineage os yesterday, everything worked well, installed some apps, and installed an app (banking app I didn't trusted), so I decided to make a reboot.
I probably didn't made a "clean" reboot. I just went into TWRP and wiped all folders, thinking to then install the OS again.
Thing is, when installing Lineage now I only get "error 7" and changing the Assert line in the zip, changes nothing. I tried to flash another ROM, "Light Rom" on the phone successfully, but it didn't started anymore and went into reboot loop.
I'm now a bit lost, since it was the first flash I did (hich was successfull the first time but I probably screwed up the second time.
Before every Flash, I always clean the Dalvik, Cache, Data and System folder.
I hace the latest TWRP Version, and also made sure to download the latest Lineage version.
What can I do now?
I'm flashing with Odin
When Trying to flash the normal Samsung firmware, I get the error msg:
SW Rev. Check Fail (Bootoader) Device: 12 Binary: 7
I also have no recovery. I know, I have probably done everything wrong I coould do wrong XD, this is going to be a lesson having no backup...
Can I even do something with the phone tho? Or is it just dead now and unusable?
Deleted member 11382503 said:
Hello everyone,
I have made some mistakes:
I installed lineage os yesterday, everything worked well, installed some apps, and installed an app (banking app I didn't trusted), so I decided to make a reboot.
I probably didn't made a "clean" reboot. I just went into TWRP and wiped all folders, thinking to then install the OS again.
Thing is, when installing Lineage now I only get "error 7" and changing the Assert line in the zip, changes nothing. I tried to flash another ROM, "Light Rom" on the phone successfully, but it didn't started anymore and went into reboot loop.
I'm now a bit lost, since it was the first flash I did (hich was successfull the first time but I probably screwed up the second time.
Before every Flash, I always clean the Dalvik, Cache, Data and System folder.
I hace the latest TWRP Version, and also made sure to download the latest Lineage version.
What can I do now?
I'm flashing with Odin
When Trying to flash the normal Samsung firmware, I get the error msg:
SW Rev. Check Fail (Bootoader) Device: 12 Binary: 7
I also have no recovery. I know, I have probably done everything wrong I coould do wrong XD, this is going to be a lesson having no backup...
Can I even do something with the phone tho? Or is it just dead now and unusable?
Click to expand...
Click to collapse
You get the 'SW Rev. Check Fail (Bootoader) Device: 12 Binary: 7' thing because you're trying to flash a older firmware, you can't downgrade.
Use samfirm or frija to download the latest stock rom of your csc.
And you got error 7 because u are using twrp 3.4 or 3.5, read first, flash after. Rom devs recommend twrp 3.3.1.0/.1