Develop Bugs

[Q] did I brick my wifes phone?

Just got this phone for my wife and decided to root it for her. I have the note ii and had no problem with mine using the same method. I used the Samsung galaxy 3 toolkit v2.3.0. Chose option 2 for sprint and then option 2 rooting options. Then # 3 all in one. I already had the drivers on the pc and the phone was set for usb debugging. THe software flashed the phone but when it came back up I get the "samsung" boot screen then the sound of it booting up. The only problem it is a black screen with a blue led light. Thats it, tried to reboot into recovery and download mode but there is nothing there. just reboots to black screen. Now I do have one of those jtag usb ends I have order just in case I needed it and I can boot it into download mode and I can use odin but I have no idea what I need to do to "fix" it. Tried to use the recovery option in the toolbox but that didnt work. Also tried team epic's root tar file but that didnt work either and I am out of ideas. The only thing I know is my wife is going to kill me if I can't get this fixed.
Please help!
ps...since this phone is one day old if i cant fix it I would like to take it back to sprint for another one but I need some way to reset the counter using the download method only or I am hosed.
Q

quantum3 said:
Just got this phone for my wife and decided to root it for her. I have the note ii and had no problem with mine using the same method. I used the Samsung galaxy 3 toolkit v2.3.0. Chose option 2 for sprint and then option 2 rooting options. Then # 3 all in one. I already had the drivers on the pc and the phone was set for usb debugging. THe software flashed the phone but when it came back up I get the "samsung" boot screen then the sound of it booting up. The only problem it is a black screen with a blue led light. Thats it, tried to reboot into recovery and download mode but there is nothing there. just reboots to black screen. Now I do have one of those jtag usb ends I have order just in case I needed it and I can boot it into download mode and I can use odin but I have no idea what I need to do to "fix" it. Tried to use the recovery option in the toolbox but that didnt work. Also tried team epic's root tar file but that didnt work either and I am out of ideas. The only thing I know is my wife is going to kill me if I can't get this fixed.
Please help!
ps...since this phone is one day old if i cant fix it I would like to take it back to sprint for another one but I need some way to reset the counter using the download method only or I am hosed.
Q
Click to expand...
Click to collapse
I dont have my Galaxy S3 yet, but it sounds like all you would need is to flash a stock rom through odin. Look in the android development sub-forum and find a stock odinable rom.

I'm with the above poster. Try an odin repair.
And let this be a lesson to you. Don't mess with the wifey's toys, Murphy's law will bite you every time and she'll remember "forever" and dredge it up when you least expect it.

I hate Murphy's law...but you are so right.
I went to this thread:
http://forum.xda-developers.com/showthread.php?t=1774722
and downloaded SPR Image (JB 4.1.1) and it installed bootloader, system etc (the works) and when I rebooted it worked. I still don't have CWM and I dont even know if i have root BUT it works and I am now out of the doghouse! Thanks for all the help and if you think of anything else I need to know please tell me and thanks again...
PS.. installed goomanager and was able to get TWRP so the phone is rooted. next is the rom toolbox so I can back everything up!

[Q] Sprint SGS3 boots to black screen, please help

Hi all,
I've been using a leaked Touchwiz JB ROM for the past couple of months, and today, I decided that I wanted to return to unrooted stock and then root using the V2.3 toolkit located at http://forum.xda-developers.com/showthread.php?t=1746680.
I wiped everything with TWRP and installed the stock ROM with no problem. Then, I ran the toolkit to root the phone. The toolkit said that everything processed correctly, but now, my phone won't boot up and hangs on a black screen after the Samsung Galaxy S3 logo appears. I can hear the bootup jingle at the black screen, and the LED stays lit with a blue light when it is on this screen, but I can't do anything else. What's worse is that I don't have a custom recovery installed. I can get into Odin download mode, however.
Does anyone have any advice? I really hope that this phone isn't permanently bricked.

jjkjustin said:
Hi all,
I've been using a leaked Touchwiz JB ROM for the past couple of months, and today, I decided that I wanted to return to unrooted stock and then root using the V2.3 toolkit located at http://forum.xda-developers.com/showthread.php?t=1746680.
I wiped everything with TWRP and installed the stock ROM with no problem. Then, I ran the toolkit to root the phone. The toolkit said that everything processed correctly, but now, my phone won't boot up and hangs on a black screen after the Samsung Galaxy S3 logo appears. I can hear the bootup jingle at the black screen, and the LED stays lit with a blue light when it is on this screen, but I can't do anything else. What's worse is that I don't have a custom recovery installed. I can get into Odin download mode, however.
Does anyone have any advice? I really hope that this phone isn't permanently bricked.
Click to expand...
Click to collapse
Get back to stock here-http://www.qbking77.com/samsung-galaxy-s-iii9.html
Re-root via this method here- http://www.qbking77.com/samsung-galaxy-s-iii7.html
This should help ya get everything in order.
This will put CWM Recovery on there. I rooted this method with no issues.. Hope it helps get your phone back into order.

milky1112 said:
Get back to stock here-http://www.qbking77.com/samsung-galaxy-s-iii9.html
Re-root via this method here- http://www.qbking77.com/samsung-galaxy-s-iii7.html
This should help ya get everything in order.
This will put CWM Recovery on there. I rooted this method with no issues.. Hope it helps get your phone back into order.
Click to expand...
Click to collapse
Thanks a ton for the quick response. I'll get to work on this now.

I ended up fixing it by installing a prerooted JB ROM via Odin.

Sprint SGS3 boots to black screen with blue led light
milky1112 said:
Get back to stock here-http://www.qbking77.com/samsung-galaxy-s-iii9.html
Re-root via this method here- http://www.qbking77.com/samsung-galaxy-s-iii7.html
This should help ya get everything in order.
This will put CWM Recovery on there. I rooted this method with no issues.. Hope it helps get your phone back into order.
Click to expand...
Click to collapse
Hello,
Would this suggestion also happen to fix this problem?
I mistakenly followed the instructions of a video on youtube on how to root a Samsung GSIII and accidentally soft bricked my phone. The problem was (as the creator of the video says) that the video was outdated and I ended up flashing the 4.0.4 boot image on a 4.1.1 Samsung GSIII. So far my phone boots up with the Samsung logo, but falls short at a black screen with a pulsing blue led light. When I plug the phone to the computer, It get recognized just the same way as it would if it had booted up fully. I searched most forum posts but haven't come up to a solid solution. I might need to search some more, but can u confirm if your suggestion is likely to fix my problem.
Forum page of the toolkit used http://forum.xda-developers.com/showthread.php?t=1746680&highlight=bricked

Doldrey said:
Hello,
Would this suggestion also happen to fix this problem?
I mistakenly followed the instructions of a video on youtube on how to root a Samsung GSIII and accidentally soft bricked my phone. The problem was (as the creator of the video says) that the video was outdated and I ended up flashing the 4.0.4 boot image on a 4.1.1 Samsung GSIII. So far my phone boots up with the Samsung logo, but falls short at a black screen with a pulsing blue led light. When I plug the phone to the computer, It get recognized just the same way as it would if it had booted up fully. I searched most forum posts but haven't come up to a solid solution. I might need to search some more, but can u confirm if your suggestion is likely to fix my problem.
Forum page of the toolkit used http://forum.xda-developers.com/showthread.php?t=1746680&highlight=bricked
Click to expand...
Click to collapse
qbking77 also has a video that walks you through the steps to recover from a "soft brick". It involves using Odin and a stock JB .tar file. I haven't looked at the video in a while, so I do not know if the link to the stock file is current. qbking77's video: http://www.youtube.com/watch?v=ypmqJbZqOaU&list=PL7011CD883D5201B8&index=29
There is also this thread on XDA: http://forum.xda-developers.com/showthread.php?t=1904099

I flashed and got stuck at the Samsung screen with the blue led..... from recovery all I did was reset/ factory settings and was back in business.
Parnelli98 said:
qbking77 also has a video that walks you through the steps to recover from a "soft brick". It involves using Odin and a stock JB .tar file. I haven't looked at the video in a while, so I do not know if the link to the stock file is current. qbking77's video: http://www.youtube.com/watch?v=ypmqJbZqOaU&list=PL7011CD883D5201B8&index=29
There is also this thread on XDA: http://forum.xda-developers.com/showthread.php?t=1904099
Click to expand...
Click to collapse

[Q] ATT SGH-I313 Note 2 bricked/soft brick issues

So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!

titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100

titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app

Galaxy Note 2 Superbork

Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!

I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?

Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app

Would like to return phone to Normal State

I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-

dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob

rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will

I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?

Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/