so i decided the odin, to get back to stock so i can flash MIUI, coming from Frosty Jb, and Ktoonzer kernal. i used boot-insecure-tmo-t999uvalem-cwm to on ODIN, the phone rebooted, and then a blue LED started Flashing. it vibrated and kept rebooting. i took out battery, and goutt into Cwm, then wanted to flash MIUI, but it failed because of Build.prop, so i went back into download and flashed boot-insecure-tmo-t999uvalem-cwm again. now it wont boot, and let me get into Download mode or Cwm
Edit: im can get back into and CWM now, but not Download mode. it needed to run though one cycle of bootlooping before it let me in. So now im back on the Frosty jb, And i feel like my phone wont let me Flash anything else.
What happens when you try to go into download mode from Frostys reboot menu?
Maybe flash the UVALH2 deodexed stock rom and try odin again.
But use either the regular fw from sammobile or root66 from MrRobinson.
Where did you get the fw you've been trying to flash?
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
boot-insecure-tmo-t999uvalem-cwm
Is this just a kernel? You had said you were trying to odin back to stock, but this looks to be a cwm flashable file which I doubt is gonna work in odin.
Sent from my SGH-T999 using xda app-developers app
A similar thing happened toe when I tried going to stock from JB. Try ODIN back to stock using mrRobinsons file. Then boot into the recovery and do a factory reset. Note that this will probably wipe your internal storage
Sent from my SGH-T999 using xda app-developers app
nicky9door said:
A similar thing happened toe when I tried going to stock from JB. Try ODIN back to stock using mrRobinsons file. Then boot into the recovery and do a factory reset. Note that this will probably wipe your internal storage
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I've never seen Odin wipe internal or external SD cards. As far as I know, it doesn't even have this capability, which is a good thing.
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Aerowinder said:
I've never seen Odin wipe internal or external SD cards. As far as I know, it doesn't even have this capability, which is a good thing.
Click to expand...
Click to collapse
It wasnt ODIN that wiped my storage. It was running the factory reset from the Samsung 3e Recovery (which I got after I used ODIN to go back to stock)
ishred11 said:
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Click to expand...
Click to collapse
Getting into recovery can be tricky as there's a short window where you have to release the buttons. The most successful way for me is, with the phone off, hold home+power+vol up. When you see the Samsung logo, look at the top of the screen for a line of blue text. If you see this line, immiediately let go of all buttons.
Another option (might be a longshot) would be to try using ADB during the CodenameAndroid (CNA) boot animation. Search for ADB standalone to get the files you need. While your phone is on the CNA bootscreen, plug it intop your computer and try running "adb devices" from the command line (you'll need to be in the same folder as the ADB executable). If you see a serial number, then try running "adb reboot recovery" which should get you into recovery mode
ishred11 said:
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Click to expand...
Click to collapse
Did you remember to wipe everything including factory reset in recovery?
If you're already rooted just press reboot recovery in goo manager. Otherwise try what the above post says.
Sent from my SGH-T999 using xda app-developers app
ishred11 said:
so i decided the odin, to get back to stock so i can flash MIUI, coming from Frosty Jb, and Ktoonzer kernal. i used boot-insecure-tmo-t999uvalem-cwm to on ODIN, the phone rebooted, and then a blue LED started Flashing. it vibrated and kept rebooting. i took out battery, and goutt into Cwm, then wanted to flash MIUI, but it failed because of Build.prop, so i went back into download and flashed boot-insecure-tmo-t999uvalem-cwm again. now it wont boot, and let me get into Download mode or Cwm
Edit: im can get back into and CWM now, but not Download mode. it needed to run though one cycle of bootlooping before it let me in. So now im back on the Frosty jb, And i feel like my phone wont let me Flash anything else.
Click to expand...
Click to collapse
Did you make a Nandroid (Backup) of your ROMS? Always make a Backup before flashing anything on your phone. If the solutions the users have posted doesn't work, then USB JIG can be used as a last resort. I would also like to let you know some kernels corresponds to some ROMS. For an example, Frosty is based on TW (Touch Wiz) and can only be flashed with kernels that supports Touch Wiz. Flashing Ktoonzer kernel with, for an example, CM10 would only result in the phone not being able to boot due to CM10 ROM not supporting Touch Wiz. Make sure you flash a kernel that supports the ROM and before any flashing, make a backup via recovery.
Related
I accidentally flashed the kernel for my old SGS II International to my Epic 4G Touch, but I managed to get it back to stock eventually. Everything was fine for the past couple months, and today I finally decided to install the system update(which I just put off for awhile despite all the prompts). Then it gave me that white triangle and when I rebooted into recovery mode. Now it just stays in recovery mode no matter what I do. Reboot option? Reboots back into recovery? Factory reset option? Boots back into recovery.
The ok button should be the power button right? This is a bit different from my old SGS
i would try pulling the battery and attempting to boot into download
yea, try & get into download mode... power off>vol dn+power until download mode is on the screen. then use ODIN/HEIMDALL to flash a stock tar file.
I should have mentioned that I did remove the battery and leave it out for a few minutes several times. It just kept booting back into recovery. I did eventually find the jig I made which was able to force it into download mode. But heimdall just keeps giving me this "ERROR: Claiming interface failed!" message even though it can detect the phone.
So no one has any idea what to do about this?
Did you try odin? If that fails put a rom(.zip) in sd card and flash from revovery.
Edit: if you are goin to switch from heimdall to odin you have to unistall heimdalls drivers. There are instructions on how to do this in heimdalls readme file.
javi_emma said:
Did you try odin? If that fails put a rom(.zip) in sd card and flash from revovery.
Edit: if you are goin to switch from heimdall to odin you have to unistall heimdalls drivers. There are instructions on how to do this in heimdalls readme file.
Click to expand...
Click to collapse
No, I didn't try Odin because I'm using OS X. I guess I'm going to have to make a windows boot partition. sigh
Well I guess I'll try to flash a rom from recovery first.
Well this is odd. It won't let me write anything to the sd card I normally use in it. It says it's read only. But uh....it always copied things fine if it was IN either this phone or my SGS II International when I tried to copy things.
I should just be able to put the rom on any micro SD card right? I have another 4 GB laying around here I can use if so.
Correct any sd should work!
Sent from my SPH-D710 using Tapatalk
And once again I highlight "apply update from sdcard" and hit the power button...just reboots into recovery mode for the millionth time without doing anything.
Gradius said:
And once again I highlight "apply update from sdcard" and hit the power button...just reboots into recovery mode for the millionth time without doing anything.
Click to expand...
Click to collapse
You may have to go the route of installing Odin and flashing a full stock tar that includes ROM, kernel, and modem so it overwrites everything in that one flash. I don't think it is something you can do by flashing in a recovery
Sent from my Nexus S 4G using xda premium
Gradius said:
And once again I highlight "apply update from sdcard" and hit the power button...just reboots into recovery mode for the millionth time without doing anything.
Click to expand...
Click to collapse
You have the stock recovery. That why. U can't flash an unsigned from from there. You are gonna have to Odin something. Either a full tar or maybe a kernel with cwm to flash something.
Sent from my Nexus S 4G using xda premium
Well anyone want to recommend/link me a tar? I'm making a windows partition right now so I can run Odin.
And yeah I figured it was because I put it back to stock that it wasn't working. But if it's back on stock why am I still getting the white triangle with the orange exclamation?
In fact if it's back to stock the past couple months and been working fine then why did it decide to screw up when I tried to install the OS update?
Gradius said:
In fact if it's back to stock the past couple months and been working fine then why did it decide to screw up when I tried to install the OS update?
Click to expand...
Click to collapse
The OTA updates are not always perfect. It is possible that there was something lingering from before. Let me try to find a link to a one click stock restore for you ...
Sent from my SPH-D710 using xda premium
Here is sfhub's EL29 full stock Gingerbread restore ...
http://forum.xda-developers.com/showthread.php?t=1433101
Sent from my SPH-D710 using xda premium
Haha, double post, haha
Sent from my SPH-D710 using Tapatalk
Checked other threads but didn't see anything like my problem
CWM recovery 6.0.14
Get msg saying can't open /cache /recovery /log. Won't perform any actions like restore or install zip.
Any ideas?
This will help. It will show you how to get your phone back to stock so you can leave it be or start over if you decide. Whatever you do, follow the directions to the T and you should be fine. Good Luck.
act586 said:
Checked other threads but didn't see anything like my problem
CWM recovery 6.0.14
Get msg saying can't open /cache /recovery /log. Won't perform any actions like restore or install zip.
Any ideas?
Click to expand...
Click to collapse
I have some problem with 6.0.1.4 too.. seems my phone is bricked. trying a restore and it is stuck at restoring cache. I was using 5.0.2.7 and installed a couple 4.0.4 roms with no issues. Was wanting to install CM10 and was told I should get 6.0.1.4 Everything is falling apart now.. Might be able to go back to 5.0.2.7 via odin?
---------- Post added at 02:03 PM ---------- Previous post was at 01:39 PM ----------
kalo93406 said:
I have some problem with 6.0.1.4 too.. seems my phone is bricked. trying a restore and it is stuck at restoring cache. I was using 5.0.2.7 and installed a couple 4.0.4 roms with no issues. Was wanting to install CM10 and was told I should get 6.0.1.4 Everything is falling apart now.. Might be able to go back to 5.0.2.7 via odin?
Click to expand...
Click to collapse
I just went back to 5.0.2.7 via odin and on reboot my last ROM is booting up.. It's like nothing has changed.. All of this is a bit sketchy as there is really no good info on how to do thing. Like upgrading from 5.0.2.7 CWM to 6.0.1.4.. why doesn't the CWM website give basic info on steps to use.
I also put ROM manager on my phone to see if that would update to 6.0.1.4 and it just seemed to get stuck.. so removed it
I tried putting 6.0 on from ODIN and that seemed to leave NO CWM on my phone at all.
Then was scared so tried flashing SGH-T989_TMB_1_T989UVKL1_CL799405_REV00.rar to restore my phone to original, and that didn't work. just stuck at startup screen.
Then I restored CWM 5.0.2.7 via odin.. thankfully it worked
Then I found a zip file for 6.0.1.4 so put that on my micro sd via and adapter on my computer. The installed it via 5.0.2.7. Thought I was set with 6.0.1.4 on my phone.. but then it didn't seem to work at all. Luckily could put 5.0.2.7 back on via odin and now Executioner 777 4.0.4 comes right up.
No idea what to do next.. or maybe do nothing as it is very hard to really know what is the best way. :s
6.0.1.4 has issues with our phone. 5.0.2.7 is fine with darkside scripts, twrp is good because you don't need the scripts.
Sent from my SGH-T989
link for twrp??
mintharis said:
6.0.1.4 has issues with our phone. 5.0.2.7 is fine with darkside scripts, twrp is good because you don't need the scripts.
Sent from my SGH-T989
Click to expand...
Click to collapse
I tried to download from the twrp website without success. Any idea where else I couldget it?
BTW, when I followed the instructions linked to in the second post, Odin sat there "initializing" for over 20 minutes before I aborted the process. I was able to flash cwm recovery without problems.
I'm stuck in a boot loop and need to do something. Tried flashing the stock ROM mentioned above without success via Odin.
You don't have to use twrp. Use CWM to get you out of your loop
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Can't run CWM
damastah said:
You don't have to use twrp. Use CWM to get you out of your loop
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
When I try to run CWM recovery the menu comes up then it immediately goes to a dark screen with just the tophat and yellow circle and "ClockworkMod Recovery v5.8.1.3" in white at the bottom of the screen.
Any ideas??
act586 said:
I tried to download from the twrp website without success. Any idea where else I couldget it?
BTW, when I followed the instructions linked to in the second post, Odin sat there "initializing" for over 20 minutes before I aborted the process. I was able to flash cwm recovery without problems.
I'm stuck in a boot loop and need to do something. Tried flashing the stock ROM mentioned above without success via Odin.
Click to expand...
Click to collapse
Try reinstalling drivers then rebooting your PC, then Odin
Sent from my SGH-T989 using xda premium
question about order of restoration
LoopDoGG79 said:
Try reinstalling drivers then rebooting your PC, then Odin
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
OK. I'm going to re-load the drivers on the PC and reboot. Then start Odin. Seeing as CWM isn't currently working, I'll load it thru Odin. Now Reboot the phone and see if CWM works. If yes, install the ROM from there. If not, can I install the ROM from Odin?
Recently had to replace my E4GT and the new device was sent to me with FI27 firmware. I want to install Blue Kuban or something similar, however I can't get the phone to boot into recovery. I can access download mode, which I used to flash a rooted version of the stock rom, however when I try to boot into recovery (holding power and volume up) the phone displays the samsung boot screen twice then boots like normal. Can I flash to a CWM or something through Odin in download mode, to gain access to custom firmware and recovery mode? Assuming I can, is there a preferred firmware to use now?
Get the el26 kernel that had cwm recovery in it and flash thru odin .
When the phone resets pull out the battery and place it back put the phone then boot into recovery
Sent from my SPH-D710 using xda app-developers app
beneboi said:
Recently had to replace my E4GT and the new device was sent to me with FI27 firmware. I want to install Blue Kuban or something similar, however I can't get the phone to boot into recovery. I can access download mode, which I used to flash a rooted version of the stock rom, however when I try to boot into recovery (holding power and volume up) the phone displays the samsung boot screen twice then boots like normal. Can I flash to a CWM or something through Odin in download mode, to gain access to custom firmware and recovery mode? Assuming I can, is there a preferred firmware to use now?
Click to expand...
Click to collapse
Post 2. http://forum.xda-developers.com/showthread.php?t=1953783
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Post 2. http://forum.xda-developers.com/showthread.php?t=1953783
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I really appreciate the guide, and I followed it, installed odin lite, got the right apk for my phone to flash, grabbed the cwm and flashed it, however I still can't boot to recovery and obviously can no longer boot back into the rom I had. I suppose I will wait until I get home and use odin on my pc to flash, as I can access download mode. Can I use the same cwm with the pc version of odin?
Ok, so things have gone from bad to worse.
I was able to flash the stock el26 with odin and got it back to factory, after that i booted into recovery and attempted to install blu kuban (after clearing everything) and it gives me a short write error about not enough space but I have over 10gb free on the phone and 20 on the sd card. I then attempted the mobile odin steps again VERBATIM from your guide and when the phone reset it soft bricked again, however this time it wont boot into recovery or download mode and just sits at the samsung logo screen. When I plug the phone into the pc and attempt to boot into anything the charging animation just freezes on the screen. any help would be greatly appreciated.
(edit) nevermind, im an idiot. figured it out.
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
So I have read flashed, read some more and I have gotten nowhere in 5 hours. Going to reach out here:
Situation: used Mobile Odin to flash the 4.4 modem from Fenny's 4.4.2 Stock ROM with MK2, (I'm a dumbass). Upon reboot I would get the SG4 logo then the blue mobile odin logo, then freeze. Was able to get into TW 2.7 but nothing would write, would say that it appeared that ROM wasn't rooted. Odin'd cf-auto, brought me back to stock recovery, odin'd TW 2.6.3.1 so now i'm back into custom. Went to go to one of my backups on my extSD, and it restored. Now I'm stuck at the SG4 logo. Attempted to flash firmware back to AMDL to start over..... nothing is happening. Still stuck on logo. Looking for any suggestions, $20 bounty for a fix
jrkart99 said:
So I have read flashed, read some more and I have gotten nowhere in 5 hours. Going to reach out here:
Situation: used Mobile Odin to flash the 4.4 modem from Fenny's 4.4.2 Stock ROM with MK2, (I'm a dumbass). Upon reboot I would get the SG4 logo then the blue mobile odin logo, then freeze. Was able to get into TW 2.7 but nothing would write, would say that it appeared that ROM wasn't rooted. Odin'd cf-auto, brought me back to stock recovery, odin'd TW 2.6.3.1 so now i'm back into custom. Went to go to one of my backups on my extSD, and it restored. Now I'm stuck at the SG4 logo. Attempted to flash firmware back to AMDL to start over..... nothing is happening. Still stuck on logo. Looking for any suggestions, $20 bounty for a fix
Click to expand...
Click to collapse
First off, please don't post the same question in multiple threads. The Help thread where you posted this was plenty.
Second, try this.
If you are able to get back into recovery, get back to the part where you had twrp 2.6.3.1.
Then restore your backed up rom like you said you already did. (You may still be at that point, but it's not clear if you overwrote that restore when you tried to use Odin.)
Once you are back at that point, wipe cache and dalvik from your restored rom. See if it boots then.
Skipjacks said:
First off, please don't post the same question in multiple threads. The Help thread where you posted this was plenty.
Second, try this.
If you are able to get back into recovery, get back to the part where you had twrp 2.6.3.1.
Then restore your backed up rom like you said you already did. (You may still be at that point, but it's not clear if you overwrote that restore when you tried to use Odin.)
Once you are back at that point, wipe cache and dalvik from your restored rom. See if it boots then.
Click to expand...
Click to collapse
Sorry, a moment of frustration, I'm usually better than this. I factory wiped on 2.7.0.1, (I installed that since I can't do anything else at the moment) and I'm still stuck. do I dl a rom and try to abd push it?
jrkart99 said:
Sorry, a moment of frustration, I'm usually better than this. I factory wiped on 2.7.0.1, (I installed that since I can't do anything else at the moment) and I'm still stuck. do I dl a rom and try to abd push it?
Click to expand...
Click to collapse
I would recommend downloading the official 4.2.2 tar file and flashing it via Odin from your computer. What bootloader are you on? With the device powered off, press and hold the volume down button, while holding the volume down button, press the power button to turn on your device. Once it vibrates, release the power button. It will prompt you to press volume up to enter download mode, or volume down to cancel and restart. Press volume up. If you do not have Knox use the 4.2.2 tar file and flash that. It seems like your partitions tables are screwed up. So flashing the official tar file will reset that. Afterwards, you will need to flash your custom recovery again through Odin. Then restoring your backups should work.
elesbb said:
I would recommend downloading the official 4.2.2 tar file and flashing it via Odin from your computer. What bootloader are you on? With the device powered off, press and hold the volume down button, while holding the volume down button, press the power button to turn on your device. Once it vibrates, release the power button. It will prompt you to press volume up to enter download mode, or volume down to cancel and restart. Press volume up. If you do not have Knox use the 4.2.2 tar file and flash that. It seems like your partitions tables are screwed up. So flashing the official tar file will reset that. Afterwards, you will need to flash your custom recovery again through Odin. Then restoring your backups should work.
Click to expand...
Click to collapse
Where would i find the official tar? How would i find the bootloader info? I was on mk2. I know I have knox after going to the offical rom
jrkart99 said:
Where would i find the official tar? How would i find the bootloader info? I was on mk2. I know I have knox after going to the offical rom
Click to expand...
Click to collapse
I was on amdl.
jrkart99 said:
I was on amdl.
Click to expand...
Click to collapse
This is the tar file you will need. Flash this in Odin on your PC and let it do its thing. Then reboot back to download and flash your custom recovery. If you try to boot after flashing official tar, it won't boot. You will need to wipe data and the original factory recovery, if you wipe data using that, it will also wipe your internal sd card as well.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
jrkart99 said:
I was on amdl.
Click to expand...
Click to collapse
Here is a good "How To" thread as well.
http://forum.xda-developers.com/showthread.php?t=2258628
elesbb said:
This is the tar file you will need. Flash this in Odin on your PC and let it do its thing. Then reboot back to download and flash your custom recovery. If you try to boot after flashing official tar, it won't boot. You will need to wipe data and the original factory recovery, if you wipe data using that, it will also wipe your internal sd card as well.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
Here is a good "How To" thread as well.
http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
awesome! I found that thread a few posts back and there was no file. I found it on the web. I am flashing now.
Survey says,... Flashed an official tmo tar.md5 file via odin and everything went alright there. immediately went back into dl mode and put in tw 2.7.0.1 back in and booted into that no problem. Factory wiped. Restoring insanity rebirth 4.3,... watching louisville slide in the 2nd,... refresh beer,.. watching louisville regroup,.. kinda,... and,.... after 1 min still stuck at the s4 logo screen.
jrkart99 said:
Survey says,... Flashed an official tmo tar.md5 file via odin and everything went alright there. immediately went back into dl mode and put in tw 2.7.0.1 back in and booted into that no problem. Factory wiped. Restoring insanity rebirth 4.3,... watching louisville slide in the 2nd,... refresh beer,.. watching louisville regroup,.. kinda,... and,.... after 1 min still stuck at the s4 logo screen.
Click to expand...
Click to collapse
Grab a 4.3 kernel and reflash your kernel. If its stuck at the logo screen its more than likely a kernel issue, if stuck at boot animation, its a ROM issue.
elesbb said:
Grab a 4.3 kernel and reflash your kernel. If its stuck at the logo screen its more than likely a kernel issue, if stuck at boot animation, its a ROM issue.
Click to expand...
Click to collapse
how do i get it on the phone from a zip?
jrkart99 said:
how do i get it on the phone from a zip?
Click to expand...
Click to collapse
Using your recovery. You flash it in recovery like a ROM.
elesbb said:
Using your recovery. You flash it in recovery like a ROM.
Click to expand...
Click to collapse
you were right,.. kernal
jrkart99 said:
you were right,.. kernal
Click to expand...
Click to collapse
So is it working?
elesbb said:
So is it working?
Click to expand...
Click to collapse
yes. So after i went back to stock I got it up and running. I then went back to restore insanity 4.3, got the logo freeze again. went back into my original stock back up got it running again,... dl latest insanity 4.4 and flashed new kernal with rom and its fine. pm me a pay pal or email and i'll send you 20.
jrkart99 said:
yes. So after i went back to stock I got it up and running. I then went back to restore insanity 4.3, got the logo freeze again. went back into my original stock back up got it running again,... dl latest insanity 4.4 and flashed new kernal with rom and its fine. pm me a pay pal or email and i'll send you 20.
Click to expand...
Click to collapse
I have a donate button if you really want to. I appreciate it!
here is a direct link too.
http://forum.xda-developers.com/donatetome.php?u=2675647