I keep getting the standard recovery screen on start up..
-reboot system now
-apply update from ADB
-apply update from external storage
-wipe data/factory reset
etc...
I have successfully rooted my device with SuperSU from this http://forum.xda-developers.com/showthread.php?t=2487142
I have TWRP, GooManager, and ROM Manager installed and haven't had any luck so far.
I have on my external sd card, a folder labeled "download" with: Aokp_jfltevzw_jb-mr1_ milestone-2.zip and Gapps-jb-20130812-signed.zip
I tried doing a recovery through Rom Manager v5.5.3.0 ClockworkMod 6.0.4.4
Whats going wrong here?
Dekdo said:
I keep getting the standard recovery screen on start up..
-reboot system now
-apply update from ADB
-apply update from external storage
-wipe data/factory reset
etc...
I have successfully rooted my device with SuperSU from this http://forum.xda-developers.com/showthread.php?t=2487142
I have TWRP, GooManager, and ROM Manager installed and haven't had any luck so far.
I have on my external sd card, a folder labeled "download" with: Aokp_jfltevzw_jb-mr1_ milestone-2.zip and Gapps-jb-20130812-signed.zip
I tried doing a recovery through Rom Manager v5.5.3.0 ClockworkMod 6.0.4.4
Whats going wrong here?
Click to expand...
Click to collapse
You're on the MI1 build? If so, your only option is Safestrap.
riker147 said:
You're on the MI1 build? If so, your only option is Safestrap.
Click to expand...
Click to collapse
yeah I'm on the MI1 build.
so should i just get safestrap and remove the goo manager, twrp, and rom manager?
Dekdo said:
yeah I'm on the MI1 build.
so should i just get safestrap and remove the goo manager, twrp, and rom manager?
Click to expand...
Click to collapse
Yup. You'll need to at least a no-wipe MI1 (see the Android Development forum). That'll get you working again. Then probably will need to re-root.
And no, you can't downgrade to MDK. Or anything else earlier than MI1.
I'd love to know where there's instructions telling people to use Goo Manager without telling them first that doing that on anything later than build MDK will softbrick their phones. It would save others from the same fate you have with a dead phone.
k1mu said:
Yup. You'll need to at least a no-wipe MI1 (see the Android Development forum). That'll get you working again. Then probably will need to re-root.
And no, you can't downgrade to MDK. Or anything else earlier than MI1.
I'd love to know where there's instructions telling people to use Goo Manager without telling them first that doing that on anything later than build MDK will softbrick their phones. It would save others from the same fate you have with a dead phone.
Click to expand...
Click to collapse
My phone isnt dead, its working completely fine. I dont believe i ended up using goo manager for anything.
Can you elaborate more on a "no-wipe" MI1
Why would i need to re-root?
awesome there are basically no roms for MI1... what a waste of time. Im gonna unroot and go back to stock and just update to 4.3
Related
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
jmdearras said:
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
Click to expand...
Click to collapse
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
k1mu said:
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
Click to expand...
Click to collapse
Do you know what GooManager does before rebooting? I'd like to manually remove it.
Where is the stock ROM for Verizon 4.2.2? Or can I just Odin 4.3?
Thanks much!
Jim
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
First, you should have done more research. You can't install a custom recovery on 4.3 (or MJ7). The only thing available is a "questionable" root method. No custom ROMs and no Safestrap.
Second, once an update has been applied, there is no way of going back.
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
If that doesn't work, try this one. http://forum.xda-developers.com/showthread.php?t=2507253.
Make sure you read ALL instructions first.
Good luck.
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
k1mu said:
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
Click to expand...
Click to collapse
Thanks! Knowing this, I think I will just stick with root but no recovery...hopefully, something will change and allow me to unstick myself from this situation in the future.
riker147 said:
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
Click to expand...
Click to collapse
This worked well when I had the same issue. I did lose root even with Survival Mode enabled on SuperSU, but otherwise no issues. Thank you.
So, I need to get back to pure stock, un-everything, however, I have a problem standing in my way:
I have SafeStrap installed (3.62 if I recall correctly), but I had to recover a bad install and now I can't even boot into SafeStrap anymore but the still boots into the Cyanogenmod ROM I installed. I have ME7 installed on my stock partition. Is there anyway I can force the phone to boot into SafeStrap, or boot into my stock partition, or update through Loki?
Edit: So I installed SafeStrap 3.65 and discovered that I recovered my Cyanogenmod install onto my stock ROM partition. Not sure if this is bad or not... :/
Edit 2: Okay... I found my old SD card with my original ME7 backup on it, so I'm back to that. Now I need to uninstall a bad Clockworkmod install because it's preventing me from updating.
spendle said:
So, I need to get back to pure stock, un-everything, however, I have a problem standing in my way:
I have SafeStrap installed (3.62 if I recall correctly), but I had to recover a bad install and now I can't even boot into SafeStrap anymore but the still boots into the Cyanogenmod ROM I installed. I have ME7 installed on my stock partition. Is there anyway I can force the phone to boot into SafeStrap, or boot into my stock partition, or update through Loki?
Edit: So I installed SafeStrap 3.65 and discovered that I recovered my Cyanogenmod install onto my stock ROM partition. Not sure if this is bad or not... :/
Edit 2: Okay... I found my old SD card with my original ME7 backup on it, so I'm back to that. Now I need to uninstall a bad Clockworkmod install because it's preventing me from updating.
Click to expand...
Click to collapse
odin you stock full wipe firmware
why did you install cyanogen mod with safestrap? you cannot do that lol.
but anyways. Yes use odin and use stock firmware tar to recover fully to stock.
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
porter46985 said:
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
Click to expand...
Click to collapse
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
statikeffeck said:
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
liljoe727 said:
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
Click to expand...
Click to collapse
I would but I honestly have no confidence in anyone reading a sticky haha
joshm.1219 said:
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
I would but I honestly have no confidence in anyone reading a sticky haha
Click to expand...
Click to collapse
That would be.... revolutionary. Lol.
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
I check the CWM recovery version on my device and currently I'm running version 6.0.3.2. Could that be the reason I keep getting the error unable to mount the sd card? Does anyone have a current version of CWM recovery that's flashable over ODIN? I'm thinking that's my last resort before attempting to restore the MDK TAR.
Bullhead00 said:
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
Click to expand...
Click to collapse
MDK TAR sounds like the only way to go. Make sure to get the MDK one though!
Theoretically, there are other ways, such as flashing a new recovery from your current one, but with Loki, that would probably be harder than what its worth.
Does anyone have any clue why I wasn't able to use ROM manager to flash CWM recovery?
ODIN MDK TAR file worked. I still don't know what went wrong and why CWM recovery couldn't mount my SD card so I could flash a ROM.