Develop Bugs

GNex Bricked?

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.

How to Root Nexus 10 on Win/Mac/Linux! [Step-by-Step VIDEO Tutorials]

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!

Has my phone bitten the dust?

Really hope somebody can help.
I have had a galaxy note 2 for about 6 months on Vodafone UK N7100.
Today while i was at work i felt something hot in my pocket, my phone was very hot (i was not doing anything with it) The phone was stuck on the Samsung boot screen.
After a few minutes of looking at this i realised it was stuck and removed the battery. SInce then i have been unable to get past the boot screen, i can't get into download mode or reboot mode. The only things to note. When i turn my phone on a red light flashes. When i plug my charger in the charge icon appears on screen but it does not charge.
Really hoping somebody can help.
I had rooted my phone if that helps (it did not cause this problem and has been functioning rooted for months)
Update
Just managed to get to a screen which warned me about installing custom software and did i want to continue. I said yes and it is now downloading something

How did you get to that screen?
Sent from my Desire S using xda app-developers app

The Mole said:
Really hope somebody can help.
I have had a galaxy note 2 for about 6 months on Vodafone UK N7100.
Today while i was at work i felt something hot in my pocket, my phone was very hot (i was not doing anything with it) The phone was stuck on the Samsung boot screen.
After a few minutes of looking at this i realised it was stuck and removed the battery. SInce then i have been unable to get past the boot screen, i can't get into download mode or reboot mode. The only things to note. When i turn my phone on a red light flashes. When i plug my charger in the charge icon appears on screen but it does not charge.
Really hoping somebody can help.
I had rooted my phone if that helps (it did not cause this problem and has been functioning rooted for months)
Update
Just managed to get to a screen which warned me about installing custom software and did i want to continue. I said yes and it is now downloading something
Click to expand...
Click to collapse
does it get recognize in odin if yes try to flash stock rom and revive your phone hopefully u are not using the 4.1.1 rom better get a 4.1.2 and bring it to life :good:
if u can get to download mode now then flashed philz recovery first. After flashing recovery wipe dalvik, cache partition & then data reset.then u can flash stock using odin. try this if the first one doesnt work

shhbz said:
does it get recognize in odin if yes try to flash stock rom and revive your phone hopefully u are not using the 4.1.1 rom better get a 4.1.2 and bring it to life :good:
if u can get to download mode now then flashed philz recovery first. After flashing recovery wipe dalvik, cache partition & then data reset.then u can flash stock using odin. try this if the first one doesnt work
Click to expand...
Click to collapse
I got there through home volume down and power during boot up.
I can't get into recovery though (using volume up)
Which version of odin should i be using? I am using 3.07
I am using the rom suggested in this guide http://reviews.cnet.co.uk/mobile-ph...e-2-from-rooted-to-factory-settings-50010623/
If i should not be using that where can i get the one i should be using.
When i try to install the stock rom linked above i get the message failed no PIT partition
Thanks for all the help so far

The Mole said:
I got there through home volume down and power during boot up.
I can't get into recovery though (using volume up)
Which version of odin should i be using? I am using 3.07
I am using the rom suggested in this guide http://reviews.cnet.co.uk/mobile-ph...e-2-from-rooted-to-factory-settings-50010623/
If i should not be using that where can i get the one i should be using.
When i try to install the stock rom linked above i get the message failed no PIT partition
Thanks for all the help so far
Click to expand...
Click to collapse
this would be your last hope http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 follow the guide properly marked in red and remember to tick re partition in odin, if this doesnt work then your phone has been affected by sds due to 4.1.1 rom so u need to take it to service for motherboard replacement which is borne by samsung so no worries, and remember never to use a 4.1.1 rom in note 2 get the 4.1.2 rom or rather they will install that only this time and in future just go through dr.ketan thread http://forum.xda-developers.com/showthread.php?t=1896696 here it will guide you perfect instead following some untidy guides
for odin use 3.04 it works great though i havent tried new version as 3.04 works great you will get it in ketan thread

shhbz said:
this would be your last hope http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 follow the guide properly marked in red and remember to tick re partition in odin, if this doesnt work then your phone has been affected by sds due to 4.1.1 rom so u need to take it to service for motherboard replacement which is borne by samsung so no worries, and remember never to use a 4.1.1 rom in note 2 get the 4.1.2 rom or rather they will install that only this time and in future just go through dr.ketan thread http://forum.xda-developers.com/showthread.php?t=1896696 here it will guide you perfect instead following some untidy guides
for odin use 3.04 it works great though i havent tried new version as 3.04 works great you will get it in ketan thread
Click to expand...
Click to collapse
Thanks for the advice i am downloading the file now.
I did not manage to install the rom i suggested i was using so i don't think that could have been the issue. My phone just seemed to get hot then stop working, i hope as you suggested it is not my motherboard. Did you say that i should still be covered by the warrenty even though i had rooted my device?

The Mole said:
Thanks for the advice i am downloading the file now.
I did not manage to install the rom i suggested i was using so i don't think that could have been the issue. My phone just seemed to get hot then stop working, i hope as you suggested it is not my motherboard. Did you say that i should still be covered by the warrenty even though i had rooted my device?
Click to expand...
Click to collapse
well your reply is quite confusing
1.did you manage to flash the rom with pit in odin. was it successful or you get any errors
2.does your phone start now
3.if not then your phone has died and it needs to be taken to service guys ,but just check what the status of your phone in download mode is it official or custom . if its official then no worries just go ahead and take it to service guys and tell them abt your issue that the phone stopped working while in pocket dont info them that you rooted it ever just make them blv that it was a sds caused by 4.1.1 rom so they replace it free.
i mean your motherboard

Sorry if i am confusing matters.
I did not manage to flash anything it was just coming up with failed no PIT partition.
Current binary samsung official
My system status is custom
Are these ok to return my phone with?
I decided to take the advice offered and download the recovery but got confused.
Do i need all of the files from that link or just 1?
I downloaded the first one N7100XXDMB2_Factory
It contained
boot
cache
hidden
modem.bin
recovery
sboot.bin
system
tz
None of these are the md5 format
i am now thinking i should have downloaded XXDLJ2_OXA_Factory
Is that correct or was i right with the first file. If i was right downloading the first file then where do i get the md5 files required for odin to do my factory restore.
Know these are very noobish questions just doint want to do anything wrong

In answers to your questions....
1) Did i manage to flash the rom with it in odin
No
I got confused which files i should be using and did not want to do anything without being sure
2) My phone does not start
3) When i am in download mode my phone shows
Current binary Samsung official
My system status is custom
Are these ok to return my phone with?

The Mole said:
Sorry if i am confusing matters.
I did not manage to flash anything it was just coming up with failed no PIT partition.
Current binary samsung official
My system status is custom
Are these ok to return my phone with?
I decided to take the advice offered and download the recovery but got confused.
Do i need all of the files from that link or just 1?
I downloaded the first one N7100XXDMB2_Factory
It contained
boot
cache
hidden
modem.bin
recovery
sboot.bin
system
tz
None of these are the md5 format
i am now thinking i should have downloaded XXDLJ2_OXA_Factory
Is that correct or was i right with the first file. If i was right downloading the first file then where do i get the md5 files required for odin to do my factory restore.
Know these are very noobish questions just doint want to do anything wrong
Click to expand...
Click to collapse
well follow this video but just select all file required and then flash instead flashing twice hope this video helps as u need to select individual file
https://www.youtube.com/watch?v=CMSsoCqZr1w if you still face prob ask the uploader in that thread maybe he can help you and as far as system status is concerned u need to either flash a stock rom or get into recovery to wipe data and factory reset or ven this https://www.youtube.com/watch?v=PpWcM44On88 for your proper understanding. dont you get .tar file and pit file in that download
are u able to enter into recovery mode as first post u mentioned download mode not working now u say its working

shhbz said:
well follow this video but just select all file required and then flash instead flashing twice hope this video helps as u need to select individual file
https://www.youtube.com/watch?v=CMSsoCqZr1w if you still face prob ask the uploader in that thread maybe he can help you and as far as system status is concerned u need to either flash a stock rom or get into recovery to wipe data and factory reset or ven this https://www.youtube.com/watch?v=PpWcM44On88 for your proper understanding
are u able to enter into recovery mode as first post u mentioned download mode not working now u say its working
Click to expand...
Click to collapse
Sorry recovery mode is not working, only download mode, i will have a look at the suggested video.
Thanks again for your continued help

The Mole said:
Sorry recovery mode is not working, only download mode, i will have a look at the suggested video.
Thanks again for your continued help
Click to expand...
Click to collapse
well initially it was a bootloader issue but destroying the pit became an issues hopefully u get it back to life this time

shhbz said:
well initially it was a bootloader issue but destroying the pit became an issues hopefully u get it back to life this time
Click to expand...
Click to collapse
I have managed to get hold of the correct files, however when i try to run them in ODIN ODIN does not get past the stage get PIT for mapping.
Can i try anything without the PIT stage?

The Mole said:
I have managed to get hold of the correct files, however when i try to run them in ODIN ODIN does not get past the stage get PIT for mapping.
Can i try anything without the PIT stage?
Click to expand...
Click to collapse
If your phone doesn't have a partition map, then no, you can't.
You can try, as a last resort, using this guide: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
I had a similar problem not too long ago (although it started with all apps crashing and then stuck at bootscreen) and managed to fix my phone.
Sent from my GT-N7100

vladeco said:
If your phone doesn't have a partition map, then no, you can't.
You can try, as a last resort, using this guide: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
I had a similar problem not too long ago (although it started with all apps crashing and then stuck at bootscreen) and managed to fix my phone.
Sent from my GT-N7100
Click to expand...
Click to collapse
Sounds like the same issue i have had. Apps kept crashing, i never thought it was the phone just the apps. I will look into the link thanks very much
CAn i just ask what is an EFS and how do i get a backup of it

If you need any help I'm here. Cheers!
Sent from my GT-N7100

vladeco said:
If you need any help I'm here. Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
Thanks can i just ask what EFS is and how i get a backup of mine before i carry out your guide.

The Mole said:
Thanks can i just ask what ENS is and how i get a backup of mine before i carry out your guide.
Click to expand...
Click to collapse
EFS is a part of the system that stores your serial number, IMEI and everything related to your phone specifically. You are generally able to back it up using a custom recovery or using software on your PC while the phone is rooted and booted on the android OS. Since you cannot boot into recovery and also can't boot into android itself, I don't think you would be able to back it up.
If you ever installed a custom rom with AROMA, there is a chance you have it backed up already. But if you don't explicitly remember...

vladeco said:
EFS is a part of the system that stores your serial number, IMEI and everything related to your phone specifically. You are generally able to back it up using a custom recovery or using software on your PC while the phone is rooted and booted on the android OS. Since you cannot boot into recovery and also can't boot into android itself, I don't think you would be able to back it up.
If you ever installed a custom rom with AROMA, there is a chance you have it backed up already. But if you don't explicitly remember...
Click to expand...
Click to collapse
Ah ok,
I will give the guide a go and let you know how i go.
Thanks again

I get the error message write operation failed in ODIN, i am guessing that means its dead.
Do you happen to know if i take it back to my phone company to fix if they will be able to tell i had rooted it
on the download screen i have
Current binary samsung official
My system status is custom
could they tell anything from that?

[Q] its bad

Tried Cyanogen 10.2 d2spr
Sprint Galaxy s3 L710
Android 4.3
Odin 1.85
Got superuser and used goomanager w twrps
made backups
Tried to flash cyanogen and i got error missing md5
tried a fix where you edit the updater-scripts in the cyanogen zip and that didnt work
Then I read that switching to cws would fix the problem, I read that you can d/l the cws zip and use twrps to flash it
Basically I was way over my head and shoulda kept the restore to stock option because that WAS working
Phone wont boot normal. volumeup and power and menu just flashes"recovery booting" or something really fast in the top left corner and shuts back off
Idk... Odin doesnt recognize the phone anymore
Definitely dont know what im doing anymore

thecuddy said:
Tried Cyanogen 10.2 d2spr
Sprint Galaxy s3 L710
Android 4.3
Odin 1.85
Got superuser and used goomanager w twrps
made backups
Tried to flash cyanogen and i got error missing md5
tried a fix where you edit the updater-scripts in the cyanogen zip and that didnt work
Then I read that switching to cws would fix the problem, I read that you can d/l the cws zip and use twrps to flash it
Basically I was way over my head and shoulda kept the restore to stock option because that WAS working
Phone wont boot normal. volumeup and power and menu just flashes"recovery booting" or something really fast in the top left corner and shuts back off
Idk... Odin doesnt recognize the phone anymore
Definitely dont know what im doing anymore
Click to expand...
Click to collapse
Can you get into download mode or are you just plugging into the computer; Odin won't recognize your phone unless it is in download mode first. Also, I find Odin 3.07 to be a bit better than 1.85.

Mr. Struck said:
Can you get into download mode or are you just plugging into the computer; Odin won't recognize your phone unless it is in download mode first. Also, I find Odin 3.07 to be a bit better than 1.85.
Click to expand...
Click to collapse
it doesnt do anything when i try to get to download mode.
If its plugged to the computer or wall, it will boot loop without a samsung screen
Not plugged in boots to samsung screen with blue text top left and shuts off right after. can barely read the blue text its so fast

thecuddy said:
it doesnt do anything when i try to get to download mode.
If its plugged to the computer or wall, it will boot loop without a samsung screen
Not plugged in boots to samsung screen with blue text top left and shuts off right after. can barely read the blue text its so fast
Click to expand...
Click to collapse
To be clear, you are holding Volume Down (not Volume Up, which is for Recovery Mode), Home Key, and Power Button all at the same time until the main Download screen appears?

Mr. Struck said:
To be clear, you are holding Volume Down (not Volume Up, which is for Recovery Mode), Home Key, and Power Button all at the same time until the main Download screen appears?
Click to expand...
Click to collapse
ok. i wasnt holding that one long enough. so now use odin? <3

Mr. Struck said:
To be clear, you are holding Volume Down (not Volume Up, which is for Recovery Mode), Home Key, and Power Button all at the same time until the main Download screen appears?
Click to expand...
Click to collapse
Ran odin and now i can get it to boot to cwm instead of twrps. should i go for the install again or call it quits. i dunno what exactly went wrong or how to go about the install from this point. thank you

thecuddy said:
ok. i wasnt holding that one long enough. so now use odin? <3
Click to expand...
Click to collapse
You need a couple of things first. You will want to use Odin to push the latest version of Philz Touch, as it is a much better recovery than either CWM or TWRP. There is an option in Philz to restore TWRP backups, so as long as the backup you made earlier was of a proper working ROM (I would assume of your stock version), then you can use Philz to restore it. If you aren't comfortable switching recoveries right away, use Odin to push TWRP again. Basically, I want to make sure you have a working custom recovery in place before proceeding any further. Also, don't use a third-party to download/install ROM's, you need to be downloading from the official source. If you are wanting to run Cyanogen, go to their website and download directly from them.
Philz Touch XDA Thread by CNexus
http://www.cyanogenmod.org/
Once you have pushed the recovery onto your phone (make sure the Reboot option is unchecked in Odin, otherwise it will boot up too soon), pull your battery out for about ten seconds, replace, and then use the button sequence for Recovery Mode, make sure to hold the buttons past the vibration until the actual screen pops up.
---------- Post added at 12:35 AM ---------- Previous post was at 12:26 AM ----------
thecuddy said:
Ran odin and now i can get it to boot to cwm instead of twrps. should i go for the install again or call it quits. i dunno what exactly went wrong or how to go about the install from this point. thank you
Click to expand...
Click to collapse
If you received an MD5 error on the first install, you most likely have a bad download, so you probably won't be able to flash it with CWM either. I am assuming that when you made your backup, you used TWRP, in which case you cannot restore that with CWM, you will need either Philz Touch or TWRP. We need to get you booted back into a working system before proceeding, as you should have no OS installed currently if you wiped everything properly before attempting to flash Cyanogen.

I feel like Im going to have three different recoveries on the phone if I do that. I don't understand what im doing fundamentally. All I can do right now is follow instructions. And I'm scared now lol. How do I increase your thanks meter ahah Maybe I should do more research. Should what I was trying to do work in the first place?

thecuddy said:
I feel like Im going to have three different recoveries on the phone if I do that. I don't understand what im doing fundamentally. All I can do right now is follow instructions. And I'm scared now lol. How do I increase your thanks meter ahah Maybe I should do more research. Should what I was trying to do work in the first place?
Click to expand...
Click to collapse
Only one recovery can exist at a time, so whatever one you pushed or flashed most recently will be the current one. Which one did you have on the phone when you made your backup? That will be a good starting point.

Mr. Struck said:
Only one recovery can exist at a time, so whatever one you pushed or flashed most recently will be the current one. Which one did you have on the phone when you made your backup? That will be a good starting point.
Click to expand...
Click to collapse
Started with twrps. Got md5 error. Reverted to backup. Then got cwm zip and booted to twps and tried to install it. Then problem.

thecuddy said:
Started with twrps. Got md5 error. Reverted to backup. Then got cwm zip and booted to twps and tried to install it. Then problem.
Click to expand...
Click to collapse
So as I mentioned earlier, you will need to get either TWRP back as your recovery, in order to restore the backup you made with it, or you will want to switch to Philz, which is the best recovery option available anyway, and use Philz to restore your TWRP backup. I think for starters you will want to use TWRP just to get back up and running, and then switch to Philz soon so that you aren't too overwhelmed tonight.
http://techerrata.com/browse/twrp2/d2spr
Choose the tar file for either version 2.6.3.0 or 2.6.3.1 and use Odin to push it onto your phone (2.6.3.1 is the newest version, but doesn't install properly on some devices; 2.6.3.0 should work for our purposes if 2.6.3.1 doesn't install properly for you). Then follow my instructions a couple of posts back about booting into recovery after using Odin.

Ill have to do this tomorrow. I pushed the tar through with odin and the phone is running at stock with supersu. Im not sure if my recovery is cwm or twrp now. But I have spent all day doing this. Ill continue tomorrow thnx again.

thecuddy said:
Ill have to do this tomorrow. I pushed the tar through with odin and the phone is running at stock with supersu. Im not sure if my recovery is cwm or twrp now. But I have spent all day doing this. Ill continue tomorrow thnx again.
Click to expand...
Click to collapse
You should now have TWRP as your custom recovery. Feel free to PM me if needed tomorrow for any advice going forward.

Soft-brick solution issue

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