My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
ShotgunSam said:
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
Click to expand...
Click to collapse
How did you get there? Did it "just happen" ?
What happens if you pull the battery and hold all 3 buttons to boot into bootloader?
Unless you were flashing a bootloader and it crashed, it isnt bricked. Boot to bootloader (vol down + vol up + power) and flash a stock image with fastboot
I use fastboot for everything, i'd rather not touch ODIN.
ShotgunSam said:
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
Click to expand...
Click to collapse
It's not bricked unless it's a brick, as in it won't power on at all.
Give us some more info and we can try to help. What have you done to it so far? What were you doing when it got to this point?
Ok all I was trying to do was root it using birdmans instructions on rootzwiki. Unlocked the bootloade.r fine, tried to flash cwm and it pushed it fine. But when I rebooted it would bootloop, I could get into cwm but not mount anything.
So I tried some instructions here to odin back a stock image, I had a charge, so I am comfortable with odin, it wrote everything, but failed. Now I get the screen described above and can't get to any other screen no matter what I press.
ShotgunSam said:
Ok all I was trying to do was root it using birdmans instructions on rootzwiki. Unlocked the bootloade.r fine, tried to flash cwm and it pushed it fine. But when I rebooted it would bootloop, I could get into cwm but not mount anything.
So I tried some instructions here to odin back a stock image, I had a charge, so I am comfortable with odin, it wrote everything, but failed. Now I get the screen described above and can't get to any other screen no matter what I press.
Click to expand...
Click to collapse
Your original boot loop was probably due to not clearing the cache?
CanaganD said:
Your original boot loop was probably due to not clearing the cache?
Click to expand...
Click to collapse
I wish, each step everything was cleared and then tried clearing multiple times after the loops started.
the odd thing was when i tried to mount usb through cwm, it couldn't find some sort of files. I was trying to install via zip the su.zip, but the only folder that was showing up on cwm was the clockworkmod folder, no other choices,
Okay, well I am back to the boot looping after successfully flashing odin, it didn't fix the original problem of bootlooping at the google screen.
I cannot mount anything to put anything on the sdcard. From what I can tell, I will have to push something using adb commands. but I am not sure what exactly.
so you used this below and it wont boot?
http://forum.xda-developers.com/showthread.php?t=1394051
no, the original bootloop happened when doing this:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
I attempted to use the Odin to fix it, which it did not.
ShotgunSam said:
no, the original bootloop happened when doing this:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
I attempted to use the Odin to fix it, which it did not.
Click to expand...
Click to collapse
Im asking what file did you use in odin?
I think I know what you did wrong. Did you use the correct cwm image.
321jurgen said:
I think I know what you did wrong. Did you use the correct cwm image.
Click to expand...
Click to collapse
I used the toro image. would it had put cwm on there if I used the gsm image?
I am currently working through http://forum.xda-developers.com/showthread.php?t=1399210
to try to fix it.
Sorry I see now you have verizon. That means you need to have the toro. I will do some research hopefully I can help you. I thought I had the same problem because I came in the same situation when I used the wrong cwm image.
droidstyle said:
so you used this below and it wont boot?
http://forum.xda-developers.com/showthread.php?t=1394051
Click to expand...
Click to collapse
yes, that is what I tried to flash through odin, it failed the first couple of times but when I changed computers, it flashed, but did not fix the boot loop.
Update, I flashed a stock image via adb through the instructions I mentioned above.....and..... SUCCESS!
I think my original problem was I freaked out when it cycled the colored thing longer than normal. After flashing the stock image today, it cycled the color things for a long time, then rebooted itself and cycled through a long time again. but eventually came up.
I appreciate everyone who took time to read this thread and chimed in.
Related
Well, something strange happened and i have no idea what the prob is
yesterday i installed a new kernel for my gnex and made a backup (using CWM) before flashing. Today i decided to go back to the previous kernel so i just went to recovery and restored from the backup. It installed successfully and then i rebooted my phone twice just to be sure everything was working and it was untill 4-5 hours later, I was playing a game (temple run) when suddenly the phone turned off and restarted by itself, i though maybe the game crashed and its restarting but i kept waiting for an hour but the phone was just stuck at the google logo. After waiting, i decided to go to recovery and flash a new kernal or restore but when i went to the bootloader and selected recovery, the phone didnt go into recovery but its stuck in google loop again. so somehow i think the recovery has been deleted of something like that because it gets stuck in loop if i go to recovery :/
i am on 4.0.3 codenamed android rom
Thanks
EDIT: I have already tried removing the battery for some time but still i am not able to enter recovery. i thought recovery was to prevent such things :$
You should probably use search next time. It's happened to quite a few people (myself included).
Use fastboot/ODIN to flash stock rom again.
case0 said:
You should probably use search next time. It's happened to quite a few people (myself included).
Use fastboot/ODIN to flash stock rom again.
Click to expand...
Click to collapse
Thanks but i wont be able to recover my data using this right?:/
No I don't think so, it sucks. I thought they had fixed this bug in 4.0.3 though which is strange. I lost my data twice within a month because of this, when I was on 4.0.2 (or maybe 4.01). Haven't had it since I rooted and updated.
Try flashing the recovery again. Maybe it will work.
case0 said:
No I don't think so, it sucks. I thought they had fixed this bug in 4.0.3 though which is strange. I lost my data twice within a month because of this, when I was on 4.0.2 (or maybe 4.01). Haven't had it since I rooted and updated.
Click to expand...
Click to collapse
can you tell me which tut to follow? i searched and found ODIN files for 4.0.4 and 4.0.2 but i'm on 4.0.3
sry but this is my first android phone and i have no previous knowledge
efrant said:
Try flashing the recovery again. Maybe it will work.
Click to expand...
Click to collapse
already tried that. manually and also using toolkit but i get the same error something like "recovery status read failed too many links"
Thanks for replies btw
rollerdyke44 said:
can you tell me which tut to follow? i searched and found ODIN files for 4.0.4 and 4.0.2 but i'm on 4.0.3
sry but this is my first android phone and i have no previous knowledge
already tried that. manually and also using toolkit but i get the same error something like "recovery status read failed too many links"
Thanks for replies btw
Click to expand...
Click to collapse
Use the Odin files for 4.0.4. Why are you looking for 4.0.3?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Use the Odin files for 4.0.4. Why are you looking for 4.0.3?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
well i am on codenamed android based on 4.0.3 so i was looking for 4.0.3 files for ODIN. this will flash my firmware to stock 4.0.4 right?
And do you know of ANY WAY i can fix my phone so that i can recover my data? I have tried everything but to no avail. i have tried flashing recovery, booting recovery (not flashing) using different usb ports and cables, flashing boot.img from codename android and everything i read online :/
rollerdyke44 said:
this will flash my firmware to stock 4.0.4 right?
Click to expand...
Click to collapse
Yes.
rollerdyke44 said:
And do you know of ANY WAY i can fix my phone so that i can recover my data? I have tried everything but to no avail. i have tried flashing recovery, booting recovery (not flashing) using different usb ports and cables, flashing boot.img from codename android and everything i read online :/
Click to expand...
Click to collapse
What happens when you boot CWM?
In order to recover anything, you need to be booted either into Android or CWM.
Maybe try using the "no-wipe" odin files, which may allow you to either boot into the ROM or allow you to boot CWM, and then you can retrieve your data. However, if this does work, I would recommend you wipe right after you retrieve your data, then restore your files, as you may have issues later on running with that data on your device.
efrant said:
Yes.
What happens when you boot CWM?
In order to recover anything, you need to be booted either into Android or CWM.
Maybe try using the "no-wipe" odin files, which may allow you to either boot into the ROM or allow you to boot CWM, and then you can retrieve your data. However, if this does work, I would recommend you wipe right after you retrieve your data, then restore your files, as you may have issues later on running with that data on your device.
Click to expand...
Click to collapse
thanks for your quick reply mate
I am not able to boot into recovery. When i select enter recovery from bootloader then it just loops on the google logo. When i try to reinstall cwm then it fails everytime with the error i mentioned above
ohh and btw, sometimes when the cwm installation fails then the bootloader gets stuck and the screen becomes kind of blurry and i have to take out the battery...... is that normal?
And i'll first try the no wipe files (from here http://forum.xda-developers.com/showthread.php?t=1586807&highlight=odin) and see if that works
rollerdyke44 said:
thanks for your quick reply mate
I am not able to boot into recovery. When i select enter recovery from bootloader then it just loops on the google logo. When i try to reinstall cwm then it fails everytime with the error i mentioned above
ohh and btw, sometimes when the cwm installation fails then the bootloader gets stuck and the screen becomes kind of blurry and i have to take out the battery...... is that normal?
And i'll first try the no wipe files (from here http://forum.xda-developers.com/showthread.php?t=1586807&highlight=odin) and see if that works
Click to expand...
Click to collapse
What happens when you boot CWM via fastboot?
fastboot boot cwm.img
efrant said:
What happens when you boot CWM via fastboot?
fastboot boot cwm.img
Click to expand...
Click to collapse
i get a blurry recovery mode picture (that hat kind of thing) for a couple of secs and then the phone reboots and again in boot loop[
rollerdyke44 said:
i get a blurry recovery mode picture (that hat kind of thing) for a couple of secs and then the phone reboots and again in boot loop[
Click to expand...
Click to collapse
Oou, that doesn't sound good. Not sure you'd be able to save your data.
efrant said:
Oou, that doesn't sound good. Not sure you'd be able to save your data.
Click to expand...
Click to collapse
well lets hope for the best
And i was on codenamed 4.0.3 so if i use the "no-wipe" files for 4.0.4 it should not cause anymore problems right?
I'll first use ODIN with no wipe files and if that doesnt work then i guess i'll say bye bye to my data and do a full wipe.
Thanks for you help mate and i will reply with the result in an hour or so (dinner time now )
Thanks again
EDIT:
so i ran ODIN but now its stuck. the start button has been greyed out with the following message
"<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
"
and the phone is on the ODIN download mode screen :/
EDIT 2:
when i use the full image, then the ODIN downloading screen on my nexus becomes blurry when ODIN on pc shows "<ID:0/011> NAND Write Start!! "
PLease help as i really dont know what else can i do
Fu*kkkkk
i think its bricked now i cant even access the bootloader the phone doesnt even turn on now i cant even get the google logo just a black screen
rollerdyke44 said:
Fu*kkkkk
i think its bricked now i cant even access the bootloader the phone doesnt even turn on now i cant even get the google logo just a black screen
Click to expand...
Click to collapse
It may not be bricked. Not being able to get into the bootloader can happen when you flash via odin.
Can you not boot into download mode (hold volume down and then press and hold power)? If you can, then you can still flash via odin.
I haven't really used odin too much, so I won't be able to help you troubleshoot too much (maybe ask in Chainfire's thread), but: if you can boot into download mode, do it, and re-follow the instructions in this post to-the-letter. Use the full odin image, not the no-wipe one.
efrant said:
It may not be bricked. Not being able to get into the bootloader can happen when you flash via odin.
Can you not boot into download mode (hold volume down and then press and hold power)? If you can, then you can still flash via odin.
I haven't really used odin too much, so I won't be able to help you troubleshoot too much (maybe ask in Chainfire's thread), but: if you can boot into download mode, do it, and re-follow the instructions in this post to-the-letter. Use the full odin image, not the no-wipe one.
Click to expand...
Click to collapse
noooooo
i cant even get the fone in download mode. the phone screen is completely black!!!! Wont even vibrate which shows its starting up
pleaaassseeee heeelppp
now i am getting scared for my nexus
rollerdyke44 said:
noooooo
i cant even get the fone in download mode. the phone screen is completely black!!!! Wont even vibrate which shows its starting up
pleaaassseeee heeelppp
now i am getting scared for my nexus
Click to expand...
Click to collapse
Take a slow deep breath and exhale. Take out the battery. Wait for a while. Put the battery back in.
Hold down the volume down button (not the volume up) and then press and hold power for 15 secs. See if that gets you into download mode. Even if nothing shows up on the screen, try following the steps in the odin thread.
You did make sure only the checkmarks that needed to be there were there in odin, correct?
efrant said:
Take a slow deep breath and exhale. Take out the battery. Wait for a while. Put the battery back in.
Hold down the volume down button (not the volume up) and then press and hold power for 15 secs. See if that gets you into download mode. Even if nothing shows up on the screen, try following the steps in the odin thread.
You did make sure only the checkmarks that needed to be there were there in odin, correct?
Click to expand...
Click to collapse
Which checkmarks should be used?
TwinkyOfHope said:
Which checkmarks should be used?
Click to expand...
Click to collapse
Why don't you take a look at the linked (a few posts up) odin thread and see for yourself?
Here's a video tutorial on how to root your Nexus 10 for noobs!
Windows video tutorial:
Mac video tutorial:
Linux video tutorial:
All the files you need in one zip (adb+SuperSU+fastboot+Windows drivers):
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
Step-by-Step tutorial with photos here:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
Also, if you get stuck on bootloop after unlocking bootloader (This happened to me couple times), do a factory reset in stock recovery to fix:
Thanks to shimp208 for the sideload method and working CWM, ChainFire for awesome SuperSU and to all the developers who are worked on CWM recovery!
So the CWM that was just updated by Koushik on CWM does not work properly or does it work? Was asking based on this
While CWM Recovery is still being fixed
Click to expand...
Click to collapse
Edit: There's no driver issue if it were on a Mac right? Especially adb sideloading the CWM SuperSu zip?
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
johno86 said:
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
Click to expand...
Click to collapse
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. No red triangle. It boots into CWM and then after 20 seconds restarts itself and hits the bootanimation loop. Any clue what to do next? Trying to flash the stock image but having issues using cmds in windows cmd
*edit
I cleared cache through cmd and i got to the red triangle...thank ****ing the lord. DTWAZERE, I will remember tonight. Thank you for your help.
johno86 said:
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. Any clue what to do next? Trying to flash the stock image but having issues getting it into fastboot now...
Click to expand...
Click to collapse
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
dtwazere said:
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
Click to expand...
Click to collapse
Yeah this is exactly what I did and it worked. I'll wait on flashing anything until there's a stable recovery. I was fairly confident in what I was doing until that happened. Not being able to input commands from cmd prompt made me sick so I'll wait for a dev to release something that works without having to quickly install the drivers again within a 15-20 second timeframe. Too much stress.
cant boot
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
Heh im having the same issue.
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
deevooneh said:
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
Click to expand...
Click to collapse
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
i did everything, and it all went successfully after a few tried. Now i am stuck with the JB X load screen.
How do i get the stock google rom and how do i flash it?
lc684760 said:
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
Click to expand...
Click to collapse
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
deevooneh said:
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
Click to expand...
Click to collapse
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
lc684760 said:
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
Click to expand...
Click to collapse
How do we get back to stock? Might need to reattempt this.
If you are stuck on the boot animation (X) screen... power off your device and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
dtwazere said:
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
Click to expand...
Click to collapse
deevooneh said:
How do we get back to stock? Might need to reattempt this.
Click to expand...
Click to collapse
Stock is here
https://developers.google.com/android/nexus/images#mantarayjop40c
Still need a way to get CWM stable, so we have time to copy to sd
craigacgomez said:
If you are stuck on the boot animation (X) screen... power off you devices and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
Click to expand...
Click to collapse
THIS WORKED!!
Youre a genius. thanks!
When I try to install the manta drivers manually and tell it to search the same area that it searched and found the android bootloader drivers for fastboot mode it says that the drivers couldn't be found and installed. Am I missing something? Also if i try to do fastboot flash recovery it gives me an error message stating that it cannot determine the image filename for the recovery image.
Well i guess i did it the long way around.
Went to https://developers.google.com/android/nexus/images#mantarayjop40c
and downloaded the Nexus 10 file. extracted, and the actual files in the Nexus10Root folder.
Opened the flash-all.sh and entered each command manually because it was erroring out running the script.
After the 3rd command it booted right into android!
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess. i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery. i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys. just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
jamesquags said:
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess.
i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery.
i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys.
just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
Click to expand...
Click to collapse
First of all, good job on searching before posting! :good:
Second, if you want help, try using capital letters at the start of a sentence and using paragraphs. It makes it sooo much easier to read that way.
Third, just keep trying. But from what you're saying about a file-system issue, that could be bad? It's not familiar to me anyways. Hope it didn't damage the internal SD.
If nothing else works, then try the USB-JIG to access Recovery mode. They're like $5 on eBay.
Okay, try these things.
1) Odin a non-rooted, stock ROM that comes with a 3E recovery and try to access that recovery.
If that doesn't work, move onto this step:
2) Odin a different recovery. I attached one to this post. Just unzip it and then odin it. :CWM-Recovery-LTE-SGS3-v5.tar:
Try to get recovery again after a battery pull.
If that doesn't do it, then try this next:
1) Odin a rooted ROM onto the phone.
2) Download the attached "openrecovery-twrp-2.3.1.0-d2att" and unzip it.
3) Download this ADB & Fastboot tool and extract it to your C:/ drive with subfolders using this path: "C:/Android/platform-tools/".
Here is the file to download:
http://www.androidfilehost.com/?fid=9390135922294523275
4) Rename the openrecovery-twrp-2.3.1.0-d2att to "recovery" and place it into the Platform-tools folder.
5) Open the JPEG and follow the EXACT same commands in the pic. This will install TWRP recovery for you.
Then try once again to get into recovery.
If it still doesn't work, then buy a USB Jig.
REPLY
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
jamesquags said:
"Failed to Open Serial [COM] Port".
Click to expand...
Click to collapse
Have you installed the phone drivers? They're linked from the Odin thread.
smelenchuk said:
Have you installed the phone drivers? They're linked from the Odin thread.
Click to expand...
Click to collapse
Yes i have installed the drivers. I have flashed multiple .tar files today.
jamesquags said:
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
Click to expand...
Click to collapse
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
CZ Eddie said:
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
Click to expand...
Click to collapse
After flashing the ROOTED STOCK ROM, I tried about 7 times to boot into recovery. It finally did!!! I then was able to do a wipe data and cache and I'm all set.
Thanks so much for helping me out. -jim
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go if the power button but still press the home + volume up
Sent from my SGH-I747 using Tapatalk 2
jerrycoffman45 said:
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go of the power button but still press the home + volume up
Click to expand...
Click to collapse
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
CZ Eddie said:
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
Click to expand...
Click to collapse
i dont know i have always done it that way well learned something new just tried it your way thanks
So I was installing modaco switch on my phone and it worked for a bit but then when I rebooted it it wouldn't turn on. I've tried flashing it in odin and nothing happened and it still doesn't work. I was wondering if anyone else had any ideas.
Can you access Odin? If so, I recommend flashing back to stock first.
joshua.justice said:
So I was installing modaco switch on my phone and it worked for a bit but then when I rebooted it it wouldn't turn on. I've tried flashing it in odin and nothing happened and it still doesn't work. I was wondering if anyone else had any ideas.
Click to expand...
Click to collapse
Are you able to get your device into ODIN/Download mode?
If so, flash the Samsung Stock Firmware as macboy3000 suggested.
To get your device into ODIN mode:
Power down device
Press Power and Vol down buttons and hold
Device should show an image
Press Vol up and you'll be in ODIN mode
Some helpful tips:
Follow the instructions via the red link in my sig.
Be sure to have enough juice in your battery
Have a good usb cord. This is the reason many ODIN flashes fail.
Check your md5 checksum match between the download file and your download prior to flashing the stock Firmware.
macboy3000 said:
Can you access Odin? If so, I recommend flashing back to stock first.
Click to expand...
Click to collapse
Biker1 said:
Are you able to get your device into ODIN/Download mode?
If so, flash the Samsung Stock Firmware as macboy3000 suggested.
To get your device into ODIN mode:
Power down device
Press Power and Vol down buttons and hold
Device should show an image
Press Vol up and you'll be in ODIN mode
Some helpful tips:
Follow the instructions via the red link in my sig.
Be sure to have enough juice in your battery
Have a good usb cord. This is the reason many ODIN flashes fail.
Check your md5 checksum match between the download file and your download prior to flashing the stock Firmware.
Click to expand...
Click to collapse
I tried flashing it twice and it still said successful when it finished flashing but continued to boot loop.
I'm not sure what would cause think
joshua.justice said:
I tried flashing it twice and it still said successful when it finished flashing but continued to boot loop.
I'm not sure what would cause think
Click to expand...
Click to collapse
After you flashed ODIN, did you go into stock recovery and Factory reset, then reboot, both from within Recovery?
Biker1 said:
After you flashed ODIN, did you go into stock recovery and Factory reset, then reboot, both from within Recovery?
Click to expand...
Click to collapse
No, I don't think it'll boot the stock recovery but I'll try that
If you flash stock and still receive boot loops, try going into recovery and wiping data and cache.
take out your sdcard too just for the hell of it.
I just reread your post, and your device is working fine, it's just that you want to know how to get Modaco Switch to work on your device with stability, because it stops working shortly after it's installed.
I had thought your device stopped working. I don't think ODIN will be your answer, and I don't about Modaco.
Maybe:
See if others have Modaco Switch working with stability, and if so:
try wiping cache & dalvik cache in Recovery, or try wiping first.
Biker1 said:
I just reread your post, and your device is working fine, it's just that you want to know how to get Modaco Switch to work on your device with stability, because it stops working shortly after it's installed.
I had thought your device stopped working. I don't think ODIN will be your answer, and I don't about Modaco.
Maybe:
See if others have Modaco Switch working with stability, and if so:
try wiping cache & dalvik cache in Recovery, or try wiping first.
Click to expand...
Click to collapse
It's not working fine. It doesn't boot at all. I tried going into recovery and it still boot loops even after flashing with odin.
joshua.justice said:
It's not working fine. It doesn't boot at all. I tried going into recovery and it still boot loops even after flashing with odin.
Click to expand...
Click to collapse
Ah, so I did read it right the first time. I saw the title the 1st time but I didn't see it the 2nd time, which is why I thought just Modaco wasn't turning on when I read your post without reading the title the 2nd time.
Plus I missed all the follow up posts. That's what I get for running around on my phone trying to read threads
With that being said, then what I wrote should resolve your issues.
Follow my RED link in my sig, and that should help to resolve your issues. I wrote out the steps previously, but looking at the link may help you
Biker1 said:
Ah, so I did read it right the first time. I saw the title the 1st time but I didn't see it the 2nd time, which is why I thought just Modaco wasn't turning on when I read your post without reading the title the 2nd time.
Plus I missed all the follow up posts. That's what I get for running around on my phone trying to read threads
With that being said, then what I wrote should resolve your issues.
Follow my RED link in my sig, and that should help to resolve your issues. I wrote out the steps previously, but looking at the link may help you
Click to expand...
Click to collapse
It doesn't boot into recovery so how can I wipe those?
joshua.justice said:
It doesn't boot into recovery so how can I wipe those?
Click to expand...
Click to collapse
You mentioned in the op you tried flashing in ODIN.
What exactly is your phone able to do?
Do you see anything on the display?
Does it boot into anything?
Etc...
What does 'tried going into recovery but it still boot loops' mean?
If you go step by step what you did before the issue and after, including Exactly what status your device is in, it will help in attempting to troubleshoot and resolve your issues.
I can get it into download mode but flashing Odin does nothing. When I hit the power button to turn it on it goes all the way until the t mobile logo and stalls. Sometimes it just vibrations off and on with a dark screen. When I try to go into recovery with the volume up and power keys or says 'rebooting recovery' in blue like it always does but then it just goes to booting normally and then hangs there.
joshua.justice said:
I can get it into download mode but flashing Odin does nothing. When I hit the power button to turn it on it goes all the way until the t mobile logo and stalls. Sometimes it just vibrations off and on with a dark screen. When I try to go into recovery with the volume up and power keys or says 'rebooting recovery' in blue like it always does but then it just goes to booting normally and then hangs there.
Click to expand...
Click to collapse
Can you confirm what version of the S4 you have?
The SGH-M919?
Not trying to be stupid or anything, just making sure.
Have you tried this..
1. Flash a recovery image using Heimdall (I'd suggest ClockworkMod)
2. Reboot to recovery. (Hopefully it goes through this time)
3. adb sideload a ROM to your device.
4. Flash the ROM.
5. Win?
Just trying to think of ways you can get your device back up and running.
joshua.justice said:
I can get it into download mode but flashing Odin does nothing. When I hit the power button to turn it on it goes all the way until the t mobile logo and stalls. Sometimes it just vibrations off and on with a dark screen. When I try to go into recovery with the volume up and power keys or says 'rebooting recovery' in blue like it always does but then it just goes to booting normally and then hangs there.
Click to expand...
Click to collapse
You have to:
Power down device
Don't power up
Press Power and Vol down buttons simultaneously
Press Vol up button
You should be in ODIN mode
Biker1 said:
You have to:
Power down device
Don't power up
Press Power and Vol down buttons simultaneously
Press Vol up button
You should be in ODIN mode
Click to expand...
Click to collapse
I did that. It's caked download mode. That's where I flashed Odin off my computer.
I noticed after flashing stock with Odin, I get bootloops, unless I do a factory reset. After stock flashes, it reboots into recovery and wipes cache by itself. When it finishes that and it starts to reboot by itself, I press the volume up button and go into recovery. I do a factory reset and reboot and all is fine, no bootloops.
norml said:
I noticed after flashing stock with Odin, I get bootloops, unless I do a factory reset. After stock flashes, it reboots into recovery and wipes cache by itself. When it finishes that and it starts to reboot by itself, I press the volume up button and go into recovery. I do a factory reset and reboot and all is fine, no bootloops.
Click to expand...
Click to collapse
Mine doesn't do that though. It just boot loops without going into recovery.
joshua.justice said:
Mine doesn't do that though. It just boot loops without going into recovery.
Click to expand...
Click to collapse
I understand that, my post is describing what happens when you flash a stock tar, not bootlooping, I am describing exactly what happens during the process of flashing a stock tar and how to avoid bootlooping, step by step. I guess you weren't paying attention when you flashed a stock tar with Odin, it reboots for the first time by itself and goes into stock recovery and wipes cache by itself, it's a normal process, maybe that part confused you. Any hows, good luck, I have explained step by step what I do to avoid bootloops and my directions are clear and simple. Bye.
I have left my phone off for 2 days and when i go ahead to start it up it is stuck on the "Samsung galaxy s4"
Logo. I cannot enter recovery, only download mode. I flashed .tar stock file and still that doesn't work. Can anyone help me,?
Subzero000 said:
I have left my phone off for 2 days and when i go ahead to start it up it is stuck on the "Samsung galaxy s4"
Logo. I cannot enter recovery, only download mode. I flashed .tar stock file and still that doesn't work. Can anyone help me,?
Click to expand...
Click to collapse
Flash it twice. Boot into download - Flash once. Remove Battery. Boot into download - Flash again. Don't try to boot between flashes.
Also, get your .tar from here:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob
rlichtefeld said:
Flash it twice. Boot into download - Flash once. Remove Battery. Boot into download - Flash again. Don't try to boot between flashes.
Also, get your .tar from here:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob
Click to expand...
Click to collapse
Ive tried this process a million times and ive tried it again. It isnt working, and can only go into download mode. When i try to boot into recovery it just shows the blue saying "recovery booting..." but never goes into recovery, nor does it boot. Maybe a PIT file would work? Even though i think i dont need one, idk
Subzero000 said:
Ive tried this process a million times and ive tried it again. It isnt working, and can only go into download mode. When i try to boot into recovery it just shows the blue saying "recovery booting..." but never goes into recovery, nor does it boot. Maybe a PIT file would work? Even though i think i dont need one, idk
Click to expand...
Click to collapse
Try a different computer to flash it, or it is done for. Does ODIN indicate that there was an error flashing?
There is nothing else we can do for you on this forum, if it won't flash the stock firmware. That is the last resort. The firmware has everything you should need to be able to get it back working, if it is software related. It could be hardware.
Rob
rlichtefeld said:
Try a different computer to flash it, or it is done for. Does ODIN indicate that there was an error flashing?
There is nothing else we can do for you on this forum, if it won't flash the stock firmware. That is the last resort. The firmware has everything you should need to be able to get it back working, if it is software related. It could be hardware.
Rob
Click to expand...
Click to collapse
The stock firmware is what i have been flashing and it Odin does say 'Successful'. Since it has everything i need then i guess the phone is done for i opened the phone to checke the hardware, it seems the battery is a bit swelled, do u think that may play a role in this? And when i plug it in to charge the phone doesnt show battery status picture instead, it just keeps vibrating as if i were to plug in and remove the charger. The charger is brand new btw. I really appreciate ur help Rob.
rlichtefeld said:
Try a different computer to flash it, or it is done for. Does ODIN indicate that there was an error flashing?
There is nothing else we can do for you on this forum, if it won't flash the stock firmware. That is the last resort. The firmware has everything you should need to be able to get it back working, if it is software related. It could be hardware.
Rob
Click to expand...
Click to collapse
I'm getting somewhere, it seems as if only CWM recovery and PhilZ recovery work. Twrp does not work. I installed 3 custom roms and still didnt work, i tried restoring a back up and the phone restarts in the middle of it making as if it crashes. I went into the root of the phone and i realized the only folder that DOES NOT open is the 'boot' which now i am thinking when i flash anything the boot isnt sticking. Do u know if there is a boot tar file or zip that i can flash?
Subzero000 said:
I'm getting somewhere, it seems as if only CWM recovery and PhilZ recovery work. Twrp does not work. I installed 3 custom roms and still didnt work, i tried restoring a back up and the phone restarts in the middle of it making as if it crashes. I went into the root of the phone and i realized the only folder that DOES NOT open is the 'boot' which now i am thinking when i flash anything the boot isnt sticking. Do u know if there is a boot tar file or zip that i can flash?
Click to expand...
Click to collapse
If it is the boot partition, you'll need to update the firmware, not just the ROM. You'll have to do that with ODIN and a PC, not CWM nor PhilZ. TWRP works fine as long as you use v2.8.4.0 or earlier. The v2.8.7.0 has bugs.
If you are flashing different recoveries, you should be able to flash the firmware. Again, you HAVE to flash twice in a row for it to stick. Flash with ODIN. Remove battery. Flash again. Then, boot the phone.
Rob
rlichtefeld said:
If it is the boot partition, you'll need to update the firmware, not just the ROM. You'll have to do that with ODIN and a PC, not CWM nor PhilZ. TWRP works fine as long as you use v2.8.4.0 or earlier. The v2.8.7.0 has bugs.
If you are flashing different recoveries, you should be able to flash the firmware. Again, you HAVE to flash twice in a row for it to stick. Flash with ODIN. Remove battery. Flash again. Then, boot the phone.
Rob
Click to expand...
Click to collapse
I tried the oldest twrp and doesnt work, maybe ill try 2.8.4.0. I did that with odin. As soon as it installs and vibrates and shuts the screen i remove the battery and put it back in and go back into download mode and flashed again. It still did not stick. Or should i flash, then as soon it reboots i hold down volume to enter download mode, rather than remove battery?
Subzero000 said:
I tried the oldest twrp and doesnt work, maybe ill try 2.8.4.0. I did that with odin. As soon as it installs and vibrates and shuts the screen i remove the battery and put it back in and go back into download mode and flashed again. It still did not stick. Or should i flash, then as soon it reboots i hold down volume to enter download mode, rather than remove battery?
Click to expand...
Click to collapse
Uncheck the Reboot box on ODIN. Don't let it reboot. That is the problem. '
In ODIN. Load the .tar. Uncheck Reboot.
Boot into Download mode and Flash. DO NOT REBOOT.
Pull the battery.
Wait a few minutes.
Put the battery back in.
Boot into Download Mode. Flash.
Then reboot.
There are several threads about how to do this on this section of the forum and on the General section.
Rob
rlichtefeld said:
Uncheck the Reboot box on ODIN. Don't let it reboot. That is the problem. '
In ODIN. Load the .tar. Uncheck Reboot.
Boot into Download mode and Flash. DO NOT REBOOT.
Pull the battery.
Wait a few minutes.
Put the battery back in.
Boot into Download Mode. Flash.
Then reboot.
There are several threads about how to do this on this section of the forum and on the General section.
Rob
Click to expand...
Click to collapse
I did exactly that, i waited 10 minutes with the battery removed and redid process again. Not working ? why is it only cwm working and not twrp? I wonder whats making it work...
Subzero000 said:
I did exactly that, i waited 10 minutes with the battery removed and redid process again. Not working ? why is it only cwm working and not twrp? I wonder whats making it work...
Click to expand...
Click to collapse
At this point, I have no idea. But, IIRC when you flash the firmware, it should be replacing your custom Recovery (CWM) with the Stock Recovery.
So, are you flashing CWM after you are flashing the firmware? Or, are you trying to use CWM to flash the firmware? If so, that is the issue. You have to use ODIN with a computer to flash the firmware.
CWM, Philz and TWRP are for flashing ROMs, kernels, etc, not firmware.
Rob
rlichtefeld said:
At this point, I have no idea. But, IIRC when you flash the firmware, it should be replacing your custom Recovery (CWM) with the Stock Recovery.
So, are you flashing CWM after you are flashing the firmware? Or, are you trying to use CWM to flash the firmware? If so, that is the issue. You have to use ODIN with a computer to flash the firmware.
CWM, Philz and TWRP are for flashing ROMs, kernels, etc, not firmware.
Rob
Click to expand...
Click to collapse
No, i am not flashing anything after i flash the firmware. I am using odin to flash the stock firmware. Even stock revovery doesn't work. When u flash and it attempts to boot ,it shows the blue letters 'recovery booting' with the galaxy s4 logo and stays stuck there. At this point i am very lost. Do you think it's a power button issue?
Subzero000 said:
No, i am not flashing anything after i flash the firmware. I am using odin to flash the stock firmware. Even stock revovery doesn't work. When u flash and it attempts to boot ,it shows the blue letters 'recovery booting' with the galaxy s4 logo and stays stuck there. At this point i am very lost. Do you think it's a power button issue?
Click to expand...
Click to collapse
I would not think it is the power button, since you say it does turn on. And, it does seem the Volume rocker works, since it tries to get into Recovery and does get into Download mode.
Which version of the firmware are you trying to flash?
Depending on the version of the bootloader/modems, etc. you can't downgrade versions of the firmware. You can only flash the same version or higher.
Are you flashing the 4.4.4 from here?
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Are you sure you have a SGH-M919 version of the S4? If you look under the battery, it should have a sticker with that model number.
rlichtefeld said:
I would not think it is the power button, since you say it does turn on. And, it does seem the Volume rocker works, since it tries to get into Recovery and does get into Download mode.
Which version of the firmware are you trying to flash?
Depending on the version of the bootloader/modems, etc. you can't downgrade versions of the firmware. You can only flash the same version or higher.
Are you flashing the 4.4.4 from here?
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Are you sure you have a SGH-M919 version of the S4? If you look under the battery, it should have a sticker with that model number.
Click to expand...
Click to collapse
I tried the firmware from that posting and dkd not work so, i went and got it from sammobile.com and still didnt work. I had this phone for 2 years and yes it is Sgh-m919 4.4.4 i had on it. And i flashed a i9505 custom rom on it through twrp and worked flawlessley. The phone was off for 2 days and i turned it on and this happened :/
rlichtefeld said:
I would not think it is the power button, since you say it does turn on. And, it does seem the Volume rocker works, since it tries to get into Recovery and does get into Download mode.
Which version of the firmware are you trying to flash?
Depending on the version of the bootloader/modems, etc. you can't downgrade versions of the firmware. You can only flash the same version or higher.
Are you flashing the 4.4.4 from here?
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Are you sure you have a SGH-M919 version of the S4? If you look under the battery, it should have a sticker with that model number.
Click to expand...
Click to collapse
Sir, i after following the procedure and didnt work i left the phone battery out and phone off for 3-4 days. I put the battery in today, literally just now and it somehow worked amd booted normally... it instantly sent goosebumps throughout my body because it just seemed so odd and unexpected with no reasoning for it to work now. Do u have any idea of what it may have been?
Subzero000 said:
Sir, i after following the procedure and didnt work i left the phone battery out and phone off for 3-4 days. I put the battery in today, literally just now and it somehow worked amd booted normally... it instantly sent goosebumps throughout my body because it just seemed so odd and unexpected with no reasoning for it to work now. Do u have any idea of what it may have been?
Click to expand...
Click to collapse
I have no idea. Just thank the gods of electronics and carry on.
But, it could be some sort of hardware connection that is sometimes connected and sometimes not. You may want to start looking for a backup or spare.
Rob
rlichtefeld said:
I have no idea. Just thank the gods of electronics and carry on.
But, it could be some sort of hardware connection that is sometimes connected and sometimes not. You may want to start looking for a backup or spare.
Rob
Click to expand...
Click to collapse
Id like to thank you a lot as u are an outstanding helper on xda. I warmly appreciate your kindness to guide me through the issue. Best wishes to you