I've used SFHubs Odin OC to move from ICS back to GB, and then the auto root tool to inject custom recovery. Specifically EL29 Odin OC and then Auto root Rogue Recovery. Several times, no trouble. From my laptop. Recently I used the same laptop to root my friends E4GT with El29 Odin OC (worked just fine) and then Auto root to install Rogue recovery. When I boot into recovery it looks and acts typical. But the recovery cannot properly flash any roms or properly restore a nandroid. It looks normal, but flashes zips too quickly and upon reboot I get a soft brick (hangs at splash screen). Luckily I was able to pull battery and get back to Odin mode.
Does anyone know why this happened? Is the auto root failing because I'm using the same laptop for two different E4GTs? Is there a ghost device borking the recovery installation? Thanks in advance for your help.
issues
Ive had the same thing happen to me.I did 2 things different at the same time so I dont know which one actually helped.
Used a difderntt USB cable(the cable that came for the.phone)
Deleted Odin the downloaded it again.
Worked after that I hope this helps.
Dr. Fed said:
I've used SFHubs Odin OC to move from ICS back to GB, and then the auto root tool to inject custom recovery. Specifically EL29 Odin OC and then Auto root Rogue Recovery. Several times, no trouble. From my laptop. Recently I used the same laptop to root my friends E4GT with El29 Odin OC (worked just fine) and then Auto root to install Rogue recovery. When I boot into recovery it looks and acts typical. But the recovery cannot properly flash any roms or properly restore a nandroid. It looks normal, but flashes zips too quickly and upon reboot I get a soft brick (hangs at splash screen). Luckily I was able to pull battery and get back to Odin mode.
Does anyone know why this happened? Is the auto root failing because I'm using the same laptop for two different E4GTs? Is there a ghost device borking the recovery installation? Thanks in advance for your help.
Click to expand...
Click to collapse
Are you sure your friend's phone has an external sdcard?
If not, pay attention to commands that work on internal or external cards. Some areas you toggle internal/external mode. Some areas you choose specific options that work with internal or external.
sfhub said:
Are you sure your friend's phone has an external sdcard?
If not, pay attention to commands that work on internal or external cards. Some areas you toggle internal/external mode. Some areas you choose specific options that work with internal or external.[/QUO
**********************
First of all, thank you for all your awesome work. I am honored by your reply.
I am not sure exactly what you mean by toggling external vs internal. Rogue gives you the option to choose where to read from or nandroid to; I typically use the external SD.
Yes, my friend's E4GT does have an external SD card. Rogue recovery did write to it when I nandroided her EL29 setup, and it did read the install zip from the SD card as well. I wiped with Calkulin's format-all, then installed the rom (in this case Phantom's excellent Blazer). I knew something was wrong when it flashed, because it flashed way too quickly. After the reboot and subsequent Galaxy S2 splash screen to infinity, I pulled the battery, booted to Odin mode, restored EL29 thanks to your fantastic Odin OC, injected Rogue thanks to your swanky Autoroot tool, attempted another rom flash, same result, Odin OC, back to EL29 stock, Autooot again. Then I attempted to restore the nandroid of her EL29 setup, and that resulted in an MD5 error, which also led to a soft brick. So I Odin OC'd once again and called it a day.
My phone has never had this problem. I think I'll Odin OC and Autoroot tonight, and then restore one of my nandroids just to see if it works. I don't know whats up, but the trouble started when a second phone was added to the equation.
Click to expand...
Click to collapse
Basically when CWM comes back right away from an operation, usually some error occurred. One error might be using an external sdcard when it isn't present. There are other possible errors, but that was the most obvious one to ask about.
sfhub said:
Basically when CWM comes back right away from an operation, usually some error occurred. One error might be using an external sdcard when it isn't present. There are other possible errors, but that was the most obvious one to ask about.
Click to expand...
Click to collapse
I appreciate your help. Thanks for FD10 btw, i just got done OC'ing it...awesome!
Ok i had this same problem. After OCing back to stock rooted EL29 Reinstall CWM rogue with adb auto root. This will give you a fresh copy of CWM rogue and shouldn't throw you into a boot loop. Also make sure you do a full data wipe and wipe all cashes then run Calkins format all zip prior to running the nandroid backup. Should be good. Hope this helps.
Related
Need help I installed midnight rom v2.2 today I did the recommended wipes as instructed. I had cwm 4.0.1.5 and did my backup twice. When I installed midnight every thing went good but then during reboot it just rebooted back into cwm 5.0.2.3 I've pulled the battery and nothing. I can't even get into my restore files ......did flashing the new cwm erase the backup?????I'm stuck what do I do???????
in the older 4.x cwm backups are on the internal sd card
in the newer 5.x cwm backups are on the external card.
(may be the other way around)
as long as you didnt format the actual sd cards your alright the backups are still there.
i think from cwm you can mount both to a pc and just copy the clockwork folder from one to the other. though i may be wrong.
might be easiest to odin a kernel that has the old 4x cwm
check the dev section there are a few floating around.
edit this kernel has the old cwm as both a flashable zip from inside cwm
and a .tar from odin
http://forum.xda-developers.com/showthread.php?t=1284092
sometimes it takes more than 1 wipe/format to fully clear or you could have a bad download.
there are also a few full system .tar files that will get you back up and running on a stock system.
Thanks I used Odin to reflash a kernel with the cwm I needed and was able to restore. Ill try to flash midnight against knowing I'm this now!
no prob.
may think about copying the backups to the other sd card too.
that way they are still there even on the newer 5x cwm if you have a problem.
Would it work if I upgrade to zedomax v6.02 it comes with cwm5 same as what comes in midnight rom2.2 that way I don't go through the same problem if it happens again?
it should but your best bet would be to update to that kernel with cwm5
then create a new backup before continuing.
If your phone boots into CWM after a battery pull, just select reboot system now and that will boot the phone up. I see that on my phone as well at times. Not sure what causes it but that always fixes it for me.
ptfdmedic said:
If your phone boots into CWM after a battery pull, just select reboot system now and that will boot the phone up. I see that on my phone as well at times. Not sure what causes it but that always fixes it for me.
Click to expand...
Click to collapse
I tried that about 5 times it just kept booting into cwm. Maybe a bad download im not sure, but ill try it again and see if it works this time around. Thanks!
Problem solved i just reflashed the rom and it booted up just fine. It works great. Very good rom!
Sent from my SPH-D710 using XDA App
Just a quick FYI for those of you, and possibly a thread for culmination of MobileOdin and ICS info.
So far, I'm 0 for 2 in flashing ICS (FC05 and FC07) to my phone. Each time would spur a "kernel panic upload" right in the middle of flashing the system. I did not have a custom recovery in either case.
A battery-pull was required to reboot my device, and it became soft-bricked. I was able to boot into recovery and download mode.
Since I don't have a PC at home, and my work PC won't let me put Odin on it, I was stuck flashing a custom kernel with Heimdal. No big deal, which let me boot back into CWM and flash Caulk's 2.9.1 back onto the device (I keep a copy of a working, CWM-flashable, full ROM on the external SD card).
silversx80 said:
Just a quick FYI for those of you, and possibly a thread for culmination of MobileOdin and ICS info.
So far, I'm 0 for 2 in flashing ICS (FC05 and FC07) to my phone. Each time would spur a "kernel panic upload" right in the middle of flashing the system. I did not have a custom recovery in either case.
A battery-pull was required to reboot my device, and it became soft-bricked. I was able to boot into recovery and download mode.
Since I don't have a PC at home, and my work PC won't let me put Odin on it, I was stuck flashing a custom kernel with Heimdal. No big deal, which let me boot back into CWM and flash Caulk's 2.9.1 back onto the device (I keep a copy of a working, CWM-flashable, full ROM on the external SD card).
Click to expand...
Click to collapse
Good info. Ive flashed kernels to the ICS roms using mobile ODIN but ive always gone back to EL29 and flashed using Rogue CWM for new roms.
RainMotorsports said:
Good info. Ive flashed kernels to the ICS roms using mobile ODIN but ive always gone back to EL29 and flashed using Rogue CWM for new roms.
Click to expand...
Click to collapse
Same here. Mobile Odin for kernels and CWM for roms works for me, and I flash a lot.
Sent from my Galaxy S II, AOKP style.
So I actually encountered this issue when attempt to flash a different modem that basically was not part of an original leak. So in my case I am running leak FF18 that was fresh ODIN'd was experiencing wifi issues (like a lot of people currently are on the ICS builds) and attempted to flash a different modem (FD26) to remedy the issue. On a side note the FD26 did remedy my wifi issues HOWEVER it introduced the beloved "couldn’t install on USB storage or SD card " error when attempting to install certain apps. The app I was testing with was Crackle. Anyways knowing that this was the only change I had made to my system I tried to flash back the FF18 modem. That was a not go So after a bunch of research I came across an article that basically said to permanently remedy the situation you needed to reOdin. So I figured how about we half ass it the the odin that still preserves data. Cause frankly I am getting tired of rebuilding my device. BINGO! that did the trick. After that I reflashed my custom ROM I am running (Blazer ICS edition) and was able to install all apps.
So now that we are done with the long drawn out story. The take away from this is:
-flashing different modems (and possibly kernels) other than what comes bundled with leak can cause this issue
-grab a copy of the ODIN bundle for your specific leak that preserves data if you dont want a data loss and reflash
-install any app to your liking
I hope this helps somebody
Cheers!
I found something a little different. I figured out a couple of ways to change the modem for ics. If you are already on ff18 and have ff18 modem and want to change to a different one, there are a few ways to go about it. One is to mobile odin flash agat's repack for ff18. Boot into his recovery, wipe cache and dalvik then flash whatever modem cwm zip. After that, boot back into system, update profile then prl then reboot. Use mobile oding to put back the original stock ff18 kernel and that will fix the unable to install thing. Another way is if you're coming from gb and know which modem you want, boot into recovery in gb and flash the desired modem. After that, use mobile odin to flash ff18 one click full wipe version. It won't install the modem so that snafu can work for your benefit. I could say more but it's time for bed for me.
This isn't the case. Agat63 has been working extensively with this error.. It has to do with the zimage file. I Odin every time I update and at this moment I cannot install apps to sd and SB Nation won't install unless I unmount my card. I am glad you've have success with your method, but I'm pretty sure if you install a repacked kernel right now you'll be back to the same situation.
The Root said:
This isn't the case. Agat63 has been working extensively with this error.. It has to do with the zimage file. I Odin every time I update and at this moment I cannot install apps to sd and SB Nation won't install unless I unmount my card. I am glad you've have success with your method, but I'm pretty sure if you install a repacked kernel right now you'll be back to the same situation.
Click to expand...
Click to collapse
I was able to reproduce this issue about 4 times last night without fail. Amd every single time I reOdined my phone issue was resolved everytime
Sent from my SPH-D710 using XDA
I had this same problem and couldn't find the answer I wanted anywhere. I tried factory reset and formatting the SD but it didn't work. Phone isn't rooted or anything. In the end I unmounted the SD card and then I was able to install the game then mount the SD card and it worked great.
thank you that totally worked
zoey said:
I had this same problem and couldn't find the answer I wanted anywhere. I tried factory reset and formatting the SD but it didn't work. Phone isn't rooted or anything. In the end I unmounted the SD card and then I was able to install the game then mount the SD card and it worked great.
Click to expand...
Click to collapse
thanks, that totally worked for me.
Do you think this is a ROM issue that will be fixed?
Hello. First post because I'm usually pretty good at finding solutions to my problems just searching. I can't find the solution to my current issue and I hope you fine folks can give me some advice.
Issue arose while clean flashing my d2att to the most recent Task650 AOKP build using the latest TWRP. Did my nandroid to internal sd like usual, factory reset, and format system. Done this 100 times with no issues. This time, TWRP crashed while formatting system and phone vibrates, reboots, hangs on the new kernel splash screen for Task650s Rom. Pull the battery, replace, then boot recovery with the volume home power method. TWRP splash screen shows, screen goes black, vibrates twice, then reboots back into previously mentioned kernel splash and hangs.
So I can't boot recovery and I can't boot my phone. I enter download mode and try to Odin the most recent twrp tar. Same. I try a previous twrp tar. Same.
I think I can use a rooted stock image to get back up and running, but I don't want to lose the contents of my internal sd.
How can I fix this with minimal data loss? Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Ugh.
AFAIK, you're stuck and will have to Odin back to stock JB just to get running properly again.
Maybe try to Odin stock recovery? I'm pretty sure it's out there somewhere to flash. Then use it to wipe cache/dalvik and then Odin TWRP again. Or try to Odin CWM?
You can use ADB to copy all the files from your phone over to your computer so you don't lose anything. The commands to do this are out there somewhere. I don't know them off the top of my head.
CZ Eddie said:
Ugh.
AFAIK, you're stuck and will have to Odin back to stock JB just to get running properly again.
Maybe try to Odin stock recovery? I'm pretty sure it's out there somewhere to flash. Then use it to wipe cache/dalvik and then Odin TWRP again. Or try to Odin CWM?
You can use ADB to copy all the files from your phone over to your computer so you don't lose anything. The commands to do this are out there somewhere. I don't know them off the top of my head.
Click to expand...
Click to collapse
Thanks for the feedback CZ. I didn't want to mess around with ADB so I just used Odin to flash rooted stock and expected to lose some data. Much to my surprise, once the phone was back up and running, my data was still on the internal SD. So everything is good now and I shall go back to lurking!
GhastlyTT said:
Thanks for the feedback CZ. I didn't want to mess around with ADB so I just used Odin to flash rooted stock and expected to lose some data. Much to my surprise, once the phone was back up and running, my data was still on the internal SD. So everything is good now and I shall go back to lurking!
Click to expand...
Click to collapse
Odin won't delete /data only a factory reset in stock recovery will
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
wings9130 said:
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
Click to expand...
Click to collapse
If you can get into recovery mode, you can just restore a nandroid backup (if you have one made). If you don't have one, you can wipe /system, /data, and the caches and reflash your Rom (provided you have it saved on your SD card).
If none of the above work, download mode is your best friend.
You can get into Download (Odin) Mode. That's a good thing. Sextape has the md4 TAR file for your over in their thread (warning, outside link). They have the stock unrooted as well as stock rooted file. Since you have already wiped your data, you might as well flash the "Restore" version:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
If you know how to use Odin, you can just downlaod the TAR file, but I recommend using their auto-extractor (the exe file), since it's well tested and there's less chance of user error.
All that being said, I'm curious to how your phone became "softbricked." Did you install any apps or mods recently that could've caused it? Custom Kernel?
It sounds like you eventually ended up wiping /system, which would be why you can't boot up now. I haven't heard of it automatically going into download mode because of that, but I haven't tested it on my phone, either.
try rwilco 12's android file repository. he has everything you will need
http://www.rwilco12.com/
You can also take the sd card out plug into a computer download a rom zip put it on the sd card pop it back into the phone and flash through the custom recovery which should be there.
Sent from the future via Xparent Green Tapatalk 2
Thanks for the help everyone. I guess I didn't soft brick the phone I just wiped it and there was no rom on it.