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!
Related
Hi, i'm a relative noob to rooting and rom flashing but i know the basics and have successfully installed cyanogen on other phones and devices in the past. So essentially I am trying to install jellybean on my infuse 4g (on rogers). I begun with this guide (http://forum.xda-developers.com/showthread.php?t=1776129) but and gotten stuck trying to install entropy's cm9 (http://forum.xda-developers.com/showthread.php?t=1601844). i flashed the rom and then formatted the data, system and cache, but then realized forgot to put the ICS gapps bundle on the sd card before i started. So i flashed once, did the formatting of data, system, cache, then attempted to boot and now im stuck at the samsung screen. It just hangs at that screen every time i try to boot. I have the red CWM screen and can get to CWM, but whenever i try to mount the SD it does not show up on my PC (Mac too) so i can't put any thing on it to flash and fix it.. when i attempt to flash the cm9 rom again it says [bad] and aborts. If anyone could help me out in where to go from here. I have done some reading about setting up ADB to push a rom to it, but will that work if i cant even mount the sd in the first place. CWM allows me to mount and say it should be active but i get nothing on the pc. Also which rom should i use to fix it.. also i follwoed the instructions and have Qksters IMEI backup script run (I'm not exactly sure what this does).
Thanks
phillyjevs said:
Hi, i'm a relative noob to rooting and rom flashing but i know the basics and have successfully installed cyanogen on other phones and devices in the past. So essentially I am trying to install jellybean on my infuse 4g (on rogers). I begun with this guide (http://forum.xda-developers.com/showthread.php?t=1776129) but and gotten stuck trying to install entropy's cm9 (http://forum.xda-developers.com/showthread.php?t=1601844). i flashed the rom and then formatted the data, system and cache, but then realized forgot to put the ICS gapps bundle on the sd card before i started. So i flashed once, did the formatting of data, system, cache, then attempted to boot and now im stuck at the samsung screen. It just hangs at that screen every time i try to boot. I have the red CWM screen and can get to CWM, but whenever i try to mount the SD it does not show up on my PC (Mac too) so i can't put any thing on it to flash and fix it.. when i attempt to flash the cm9 rom again it says [bad] and aborts. If anyone could help me out in where to go from here. I have done some reading about setting up ADB to push a rom to it, but will that work if i cant even mount the sd in the first place. CWM allows me to mount and say it should be active but i get nothing on the pc. Also which rom should i use to fix it.. also i follwoed the instructions and have Qksters IMEI backup script run (I'm not exactly sure what this does).
Thanks
Click to expand...
Click to collapse
the samsung boot loop is to be expected when flashing cm9. If CM9 is not your target Rom, then having GApps on your SD card or not doesnt matter. Carefully refollow the step in CM9 then continue onto cm10. After you do the three finger salute, your cwm will be blue. if all else fails, odin back to stock and start over..just make sure you have GApps when you reach the time to flash cm10.
You need to go to mount then unmount the first set. Then re flashee infinitum.
Sent from my SGH-I997 using xda premium
I used Casual on my device today and I need help. I ran casual and rooted first then secondly ran the script to install insecure aboot to unlock bootloader. the program said this was successful. I then ran script to install cwm recovery. After rooting successfully and then "supposedly successfully" unlocking bootloader and flashing cwm recovery my phone would not boot to cwm but rather booted to stock recovery. since the casual didnt work for cwm after several tries I downloaded Rom manager from play store and used it to flash cwm touch. After this my device will not boot to recovery and gives me the error message from vzw for unauthorized software. Take your device to a vzw store it says. Please help me.
dmiller15 said:
I used Casual on my device today and I need help. I ran casual and rooted first then secondly ran the script to install insecure aboot to unlock bootloader. the program said this was successful. I then ran script to install cwm recovery. After rooting successfully and then "supposedly successfully" unlocking bootloader and flashing cwm recovery my phone would not boot to cwm but rather booted to stock recovery. since the casual didnt work for cwm after several tries I downloaded Rom manager from play store and used it to flash cwm touch. After this my device will not boot to recovery and gives me the error message from vzw for unauthorized software. Take your device to a vzw store it says. Please help me.
Click to expand...
Click to collapse
First thing you need to do is Odin back to stock. Then reroot the exact same way you did with casual, and try all the same steps again.
Next, install ez unlock version 1.2 to make sure your bootloader is unlocked. It's pretty self explanatory, just hit unlock and it's done.
After that you should be good to go, no more triangles telling you to bring the phone to Verizon.
Sent from my SCH-I535 using Tapatalk 2
odin
Thank you. I couldn't find ez unlock through play store so i downloaded the apk and installed from pc. after that i was rooted unlocked and back in action in minutes. Again thank you. this is my first attempt at customizing a device so i thought I crashed hard right after takeoff. :good:
having problems installing 10.1.3 on verizon sgs3
installed cm-10.1.3-d2vzw and gapps-jb-20130812-signed onto my sd card and wipe data/factory reset, then wipe cache partition, then wipe delvic cache
when i select to reboot device it doesn't reboot at all. it buzzes and it flashes the samsung logo for a quick second and then back to a blank screen.
i tried to do 10.1.2 with gapps 20130301 and it worked fine
anyone have any advise?
thank you!
jdowell362 said:
having problems installing 10.1.3 on verizon sgs3
installed cm-10.1.3-d2vzw and gapps-jb-20130812-signed onto my sd card and wipe data/factory reset, then wipe cache partition, then wipe delvic cache
when i select to reboot device it doesn't reboot at all. it buzzes and it flashes the samsung logo for a quick second and then back to a blank screen.
i tried to do 10.1.2 with gapps 20130301 and it worked fine
anyone have any advise?
thank you!
Click to expand...
Click to collapse
this almost matches what happened to me when i first tried and it was because i wasn't successful unlocking my bootloader. Are you able to boot into recovery?
I had trouble running the new release of CM and That particular gapps also but have since switched to first Liquidsmooth and then slimrom and paranoid and all worked just fine with no changes in procedure. So im not sure what could have been wrong. im using the august gapps file with a paranoid rom now and it works wonderfully.
dmiller15 said:
this almost matches what happened to me when i first tried and it was because i wasn't successful unlocking my bootloader. Are you able to boot into recovery?
Click to expand...
Click to collapse
yeah i was able to boot in recovery. that was really the only way i was able to fix my phone. i just wiped it all over again and throw on my last working version of cm10. then i updated to the newest stable version through the cm10 updater itself, not through CWM.
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?
Hi everyone,
this is my first post, so i hope i'm posting it right, following every rule.
I've got a problem with my moto g. At the moment i bought it, I unlocked the bootloader, rooted it, upgraded it into KitKat, tried out a few different roms, installed Xposed, etc. and i never had any problem ( at least not one i coudn't figure out how to resolve).
However yesterday i wanted to try out Cyanogenmod 11, with yesterday's nightly 09/04/2014. I downloaded it from this post :
http//forum.xda-developers.com/showthread.php?t=2608377
Downloaded Gapps, too. Put both of them as zip in the moto g, did the 3 wipes and installed both zip's ( first cyanogen and then gapps).
However, once it rebooted, the cyanogen arrow kept moving around, endlessly. ( i waited for around 20 min)
In case it's relevant, i'll say that at the moment of downloading the nightly i lost internet connection, however i managed to resume the download and decided to keep going.
But after seeing that i didn't manage to install the rom properly I decided to download the nightly again and push it via "adb push .... ".
I installed it again with CWM, but the cyanogen logo kept loading. Nothing happend.
I also tried to install other Roms : GPE, 4.4.2 stock version and i even tried downgrading it to 4.3 ( which had previously worked, but not this time :crying: ) .
Everytime i got the same error, the mobile stucks at the logo ( Google logo, motorola logo, cyanogen logo,... )
My bootloader is unlocked and i've already the 3 wipes, and chache & system format ( via CWM )
and if i try to install a zip via CMW i get the following error : "E: Can't mount /sdcard"
wipe dalvick cache doesn't work and there is no error displayed.
¿Can someone help me?
Thank you very much!
Best way for you right now is to flash your stock firmware back (through fastboot) and try cm11 on that.
small-mallet said:
Best way for you right now is to flash your stock firmware back (through fastboot) and try cm11 on that.
Click to expand...
Click to collapse
Yap you should do a factory flash just download the pack "Moto g back to stock script" and do a full wipe while in fast boot and then flash CW root and install r0m u wish
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.