Related
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
Do you have AT&T insurance? Maybe the phone can have an accident? I would know of no other way to fix it if Odin isn't recognizing it. ):
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
I've seen the repeated vibrating issue before from flashing the wrong file. Download mode was still accessible. Try again by hooking up the phone to the USB slot without the battery in it. Hold Vol Down + Home while inserting the battery. See if download mode will come up. If it does, Odin may not fix it, and you may end up using KIES, and that's if it does go into Download mode.
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Gfrt94yn said:
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Click to expand...
Click to collapse
Good deal man, glad you got a new one.
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is locked yes, but Loki is there to workaround that. What is the build version on your replacement?
JDQ39.I337UCUAMDL
Is Loki on xda? I haven't found anything like that yet, although I've heard many references to that
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Update:
Maybe I should open my eyes lol, found it in about 30 seconds
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Your phone is ready to flash, just make sure the ROM you flash has been Lokied or you'd have to flash a Loki kernel/LokiDoki after flashing the ROM (but before rebooting).
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Ladies and Gentlemen, I am proud to announce that I've successfully flashed a rom without bricking my phone! *applause*
I thank(ed) you all for the help!
GS4 running slimbean and kanged key lime pie theme.
GiantBallSack said:
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Click to expand...
Click to collapse
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
godefroi said:
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
Click to expand...
Click to collapse
Yes
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I take no credit for this method, I felt it needed to be re-posted here. I snagged it from Shabbypenguins post over on Phandroid. It was originally for the Boost Mobile SGS3, but works for the Note 3 and several other devices.
What do I mean by hard brick?
Your phone doesn't power up, visibly charge, reach a boot-screen of any kind or go into download mode. Basically, it acts like it won't power on at all. Hard bricked. Even if you nuke the aboot, sbl1, boot, etc... like I did, this method will revive your phone!
This is a great safety net for those who want to test bootloader exploits!
What do you need?
Bricked Galaxy Note 3 (SM-900A)
microSD card (all data will be erased from this sdcard)
microSD card reader
Linux / OS X (can be running in vmware/virtual box on windows)
Unbrick Image (MI9)
Stock Odin Files
Unbricking Instructions
Boot Linux / OS X / VMware / Virtual Box
Download the unbrick image listed in the item's needed list
Open terminal on your OS
Insert your microSD card into the reader
Plug your microSD card reader into your computer
Run
Code:
dmesg | tail
you should see something that mentions where it is mounted via /sdX
Code:
sudo dd if=/<path_to_debrick.img> of=/dev/sdX
again where X is the microSD card ignoring the partition numbers as they should be overwritten
I had to do this a couple times for the image to actually take
Code:
sudo fdisk -l /dev/sdX
should show approximately 29 partitions (I just unplugged and replugged the usb, lots of windows popped up from the partitions)
remove the microSD card from the reader
remove the battery and sim from your device
insert your unbrick microSD into your phone
insert the battery and press the power button, it should boot
reboot into Download mode either via adb or Volume Down + Home + Power
use stock odin files to restore your phone
Thanks to the following:
Shabbypenguin for pointing me to this!
gTan64 for finding the fix while repairing their friend's phone.
KAsp3rd for showing Shabbypenguin this and assisting him throughout it
Thanks so much, you guys rock!
This is the good stuff!
designgears said:
It was originally for the Boost Mobile SGS3, but works for the Note 3 and several other devices.
Click to expand...
Click to collapse
We have several people with unrecoverable boot looped devices over in the 900T forum because of failed nandroid restores. They can get to download mode but flashing via odin to stock does not fix it. They are stuck in boot loops even after flashing via odin. In your opinion, would the unbrick image adapted to the 900T help them?
http://forum.xda-developers.com/showthread.php?p=46313784#post46313784
mircury said:
We have several people with unrecoverable boot looped devices over in the 900T forum because of failed nandroid restores. They can get to download mode but flashing via odin to stock does not fix it. They are stuck in boot loops even after flashing via odin. In your opinion, would the unbrick image adapted to the 900T help them?
http://forum.xda-developers.com/showthread.php?p=46313784#post46313784
Click to expand...
Click to collapse
I remember on the note 1 sometimes even after restoring stick via odin you would get a bootloop. In that case you had to do a factory reset after flashing stock and it got everything working again. Hopefully yur problems are something that easy to fix.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
this is for people who really brick, you overwrite your aboot/sbl's. on the SGS3 this was done by flashing an international rom as their kernel was on MMCBLK0p5 while us SGS3 that was our aboot (bootloader). whats particularly good about this is it means that designgears can nuke his bootloader trying to find exploits/unlock etc and still end up working device by the end of the night (like was done last night). to cut any questions on it, dont bother with trying to sdcard boot the tmobile bootloaders
this is more of a in case things go bad kind of scenario where you cant get to download mode, and if this guide is too confusing etc there is always a jtag (mobiletechvideos is one of the big ones on xda i believe).
shabbypenguin said:
this is for people who really brick, you overwrite your aboot/sbl's. on the SGS3 this was done by flashing an international rom as their kernel was on MMCBLK0p5 while us SGS3 that was our aboot (bootloader). whats particularly good about this is it means that designgears can nuke his bootloader trying to find exploits/unlock etc and still end up working device by the end of the night (like was done last night). to cut any questions on it, dont bother with trying to sdcard boot the tmobile bootloaders
this is more of a in case things go bad kind of scenario where you cant get to download mode, and if this guide is too confusing etc there is always a jtag (mobiletechvideos is one of the big ones on xda i believe).
Click to expand...
Click to collapse
Sir in note 3 case original bootloader is there even custom recovery is there but stock rom flashed by odin still you are not able to come out of bootloop even you make full wipe after. This is strange as odin or kies emaegeny recovery firmware not come to save you this time. My phone in service center and still not hear from them anything..
Sent from my GT-I9505 using xda premium
mwazeer said:
Sir in note 3 case original bootloader is there even custom recovery is there but stock rom flashed by odin still you are not able to come out of bootloop even you make full wipe after. This is strange as odin or kies emaegeny recovery firmware not come to save you this time. My phone in service center and still not hear from them anything..
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
the "download mode" with red text? if thats what it is you need to pull battery, put it back in. power on as if you were going to download mode and the red text will be missing, flash stock rom and then wipe in stock recovery and youll be all set
shabbypenguin said:
the "download mode" with red text? if thats what it is you need to pull battery, put it back in. power on as if you were going to download mode and the red text will be missing, flash stock rom and then wipe in stock recovery and youll be all set
Click to expand...
Click to collapse
Sir there is no red text and its normal download mode with knox counter 0x1.
Sent from my GT-I9505 using xda premium
mwazeer said:
Sir there is no red text and its normal download mode with knox counter 0x1.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Are you using the stock odin files? It should boot into recovery after flashing and wipe the device and install a few more files.
mwazeer said:
Sir there is no red text and its normal download mode with knox counter 0x1.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
odd, im truly sorry but ive no idea then. :/ i know the recovery guys are working hard but its very confusing etc.
designgears said:
Are you using the stock odin files? It should boot into recovery after flashing and wipe the device and install a few more files.
Click to expand...
Click to collapse
Yes we used all type of odin 3.04. To 3.09 and flash pure stock rom and then wipe everything in stock recovery and still get bootloop and missing baseband version so no network and no imei number. This problem come after nadroid backup restore not for me but many xda members of internional note and t mobile. All are crying. Some get replacement some of there phone in service center and no body report about result from service center.
Sent from my GT-I9505 using xda premium
Looks interesting. Getting my Note 3 soon for app/ROM development. One question. Will this work on Telus Note 3? It's Canadian. If not is there a method smiler to this? Really value my devices and don't want to hardbrick them.
could this be used as a way to exploit a 9005 rom to flash and unbrand our device :silly:
This should really be stickied!
God we gotta get this thing unlocked
Sent from my Note 3
I have an issue where I tried to follow http://forum.xda-developers.com/showthread.php?t=2474422 to Root with knox 0x0 but it dies prematurely on the flash and now I get a "firmware error" screen saying i should go back to kies and reflash. Would this solve my problem and would it increase the counter to 1?
Samsung Galaxy NOTE 3 UnRoot-Bricked-Fixed
mwazeer said:
Sir in note 3 case original bootloader is there even custom recovery is there but stock rom flashed by odin still you are not able to come out of bootloop even you make full wipe after. This is strange as odin or kies emaegeny recovery firmware not come to save you this time. My phone in service center and still not hear from them anything..
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
SOLVED!!!!
Had the same issue and its cuz the USB debugging was turned off in the Developer apps to my luck I had it on, but turned it off 1 week prior to my ph crashing... :crying: lol I tried EVERYTHING for 3 days and I'm tech savy lol What I ended up doing was using my fiance's note 3 to back up all her files via the SD card on her phone and then loaded it into mine and it worked like a charm. It's even a free app from the play store called "Root Browser" and NO you do not have to root their phone to copy their files... Copy the files, on the broken phone do the recovery mode (Volume Up + Home Key + Power Button) then load from external source. Be sure to wipe your data and all that before installing on the broken ph.... and bada-bing bada-bang! FIXED! :angel:
I suggest downloading that in the future and keeping that spare SD card in the GUN SAFE!!! just in case you happen to re-root your phone later lol
Hope this helps out since I about threw my Note 3 at the wall from all the looping frustration...lol Tried Odin, Kies3 and nothing... even the ABD cmd and no luck.... Idk why I didn't think about doing that in the past lol GOOD LUCK!:fingers-crossed:
---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------
mircury said:
We have several people with unrecoverable boot looped devices over in the 900T forum because of failed nandroid restores. They can get to download mode but flashing via odin to stock does not fix it. They are stuck in boot loops even after flashing via odin. In your opinion, would the unbrick image adapted to the 900T help them?
http://forum.xda-developers.com/showthread.php?p=46313784#post46313784
Click to expand...
Click to collapse
SOLVED!!!!
Had the same issue and its cuz the USB debugging was turned off in the Developer apps to my luck I had it on, but turned it off 1 week prior to my ph crashing... lol I tried EVERYTHING for 3 days and I'm tech savy lol What I ended up doing was using my fiance's note 3 to back up all her files via the SD card on her phone and then loaded it into mine and it worked like a charm. It's even a free app from the play store called "Root Browser" and NO you do not have to root their phone to copy their files... Copy the files, on the broken phone do the recovery mode (Volume Up + Home Key + Power Button) then load from external source. Be sure to wipe your data and all that before installing on the broken ph.... and bada-bing bada-bang! FIXED!
I suggest downloading that in the future and keeping that spare SD card in the GUN SAFE!!! just in case you happen to re-root your phone later lol
Hope this helps out since I about threw my Note 3 at the wall from all the looping frustration...lol Tried Odin, Kies3 and nothing... even the ABD cmd and no luck.... Idk why I didn't think about doing that in the past lol GOOD LUCK!
I am confused and holding on to buying the note 3 yet due to these issues. Is sm 900A different than 9005A? Does att sell 2 different versions?
HookedOnDroids said:
SOLVED!!!!
Had the same issue and its cuz the USB debugging was turned off in the Developer apps to my luck I had it on, but turned it off 1 week prior to my ph crashing... :crying: lol I tried EVERYTHING for 3 days and I'm tech savy lol What I ended up doing was using my fiance's note 3 to back up all her files via the SD card on her phone and then loaded it into mine and it worked like a charm. It's even a free app from the play store called "Root Browser" and NO you do not have to root their phone to copy their files... Copy the files, on the broken phone do the recovery mode (Volume Up + Home Key + Power Button) then load from external source. Be sure to wipe your data and all that before installing on the broken ph.... and bada-bing bada-bang! FIXED! :angel:
I suggest downloading that in the future and keeping that spare SD card in the GUN SAFE!!! just in case you happen to re-root your phone later lol
Hope this helps out since I about threw my Note 3 at the wall from all the looping frustration...lol Tried Odin, Kies3 and nothing... even the ABD cmd and no luck.... Idk why I didn't think about doing that in the past lol GOOD LUCK!:fingers-crossed:
---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------
SOLVED!!!!
Had the same issue and its cuz the USB debugging was turned off in the Developer apps to my luck I had it on, but turned it off 1 week prior to my ph crashing... lol I tried EVERYTHING for 3 days and I'm tech savy lol What I ended up doing was using my fiance's note 3 to back up all her files via the SD card on her phone and then loaded it into mine and it worked like a charm. It's even a free app from the play store called "Root Browser" and NO you do not have to root their phone to copy their files... Copy the files, on the broken phone do the recovery mode (Volume Up + Home Key + Power Button) then load from external source. Be sure to wipe your data and all that before installing on the broken ph.... and bada-bing bada-bang! FIXED!
I suggest downloading that in the future and keeping that spare SD card in the GUN SAFE!!! just in case you happen to re-root your phone later lol
Hope this helps out since I about threw my Note 3 at the wall from all the looping frustration...lol Tried Odin, Kies3 and nothing... even the ABD cmd and no luck.... Idk why I didn't think about doing that in the past lol GOOD LUCK!
Click to expand...
Click to collapse
what files did you download off your wife phone onto sd card....using rom toolbox with root explorer....sorry for newb question...any help appreciated....
Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks
re: download/recovery modes
Nurmi_CEO said:
Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks
Click to expand...
Click to collapse
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!
Misterjunky said:
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!
Click to expand...
Click to collapse
Tried....no go still nothing
Nurmi_CEO said:
Tried....no go still nothing
Click to expand...
Click to collapse
Can you link to the specific rom you flashed. It's sounds to me like you might have flashed a bad or wrong rom.
Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.
Nurmi_CEO said:
Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.
Click to expand...
Click to collapse
I can't tell if the t01teatt is for your specific device. I haven't seen the t01te before. I would have expected something different. The symptoms you describe sounds like a bricked device caused by flashing a rom not for your specific device.
I assume your MDL cause you have a custom recovery.
Did you use Auto Loki recovery?
If you didn't use Auto Loki recovery did you flash the Loki doki zip ?
We need all steps you took from start to end before you rebooted your phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app
the phone was bone stock locked att i337. I unlocked it via the service hidden menu on YouTube. it worked fine.
next I rooted it with the motochopper, flashed twrp with goo manager and rebooted to recovery. my first load with twrp seemed to hang up and freeze, so I pulled the battery and rebooted into twrp.
I loaded the liquidsmooth to1att and gapps to be flashed. both seemed to flash successfully, and then I hit restart. forgot to wipe cache and dalvik, planned on rebooting back into recovery to wipe/maybe reflash and wipe cache.
the phone turned off and never turned back on.
I had a T-Mobile sim card in the entire time.
thanks and please help. sending this from my crappy evo lte
Did a little searching and I think the t01te is the note ii. Check out mobiletechvideos.com. they might be able to jtag it.
after root the phone was working fine on the stock ROM.
Nurmi_CEO said:
after root the phone was working fine on the stock ROM.
Click to expand...
Click to collapse
It's the rom you flashed after that which is causing the problem. Like I said I think it was for the note II and not the i337
Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk
rushi.1986 said:
Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
send in for repair? only option? thanks for help
Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
If Odin doesn't recognize it, and I think you said it doesn't, then yea I think that's your only hope. But I'd keep trying to get it into download mode and have Odin recognize it. I haven't seen a hard brick of the i337.
Use the original usb cable, the usb ports in the back of the computer, and if that doesn't work try a different computer.
The build.prop in that ROM you flashed says it is for the SAMSUNG-SGH-I317 which is the Galaxy Note II. That's why it is bricked. Make sure you don't try to flash that one again. If you do get it to come up in download mode make sure you have the correct file before trying to flash again.
Good luck!
Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"
rushi.1986 said:
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"
Click to expand...
Click to collapse
...and end up with an MF3 phone?
It's better to send it off for Jtag like JD said. If it never had the MF3 bootloader on it, there shouldn't be a problem with them putting MDL back on it (as long as there isn't a hardware issue). To me, the cost is well worth it.
scott14719 said:
...and end up with an MF3 phone?
Click to expand...
Click to collapse
Good point! I didn't think of that..
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
simon_lefisch said:
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
Click to expand...
Click to collapse
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
ericdabbs said:
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
Click to expand...
Click to collapse
ok. i was on stock. rooted with the IO method. wanted to flash a ROM (clean rom). downloaded ROM, wipe dalvik/cache/data. after reboot, phone booted into recovery mode. tried going into download mode to revert back to stock and LG FlashTool failed. said phone was the wrong model number (D802). the ROM i Downloaded said it was for VZW G2. obviously it wasnt. so i finally ended up using fastboot to push boot image and it booted, but in about phone, it says it D802 model (i just got it to boot, where as before i was stuck in fastboot mode). now i need to return to stock, but dont know how. any ideas?
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Gnarfsan said:
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Click to expand...
Click to collapse
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
simon_lefisch said:
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
Click to expand...
Click to collapse
Even following the steps posted in that thread?
Gnarfsan said:
Even following the steps posted in that thread?
Click to expand...
Click to collapse
yes. not sure why its doing that. is there any way that download mode can be deleted from the phone? also, how do you get into fastboot mode?
EDIT: nevermind. i finally got it into download mode!! (thank god!!) flashing right now. damn that was a pain in the ass. i was starting to freak out that i messed up my phone. this is my first LG phone so this process is a little new to me (been on moto for the last few years) thanks for trying to help me out. this was def a learning experience.
Phew, I'm glad to hear that. Some day I will be in the same situation
Sent from my LG-D802 using XDA Premium 4 mobile app
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
trickster2369 said:
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
I was thinking the same thing. It's best to stay out of those modes. Get a recovery installed ASAP and do everything that you need to do from there. I recommend TWRP Recovery.
Sent from my LG-D802 using XDA Premium 4 mobile app
Maybe because when flashing stock rom download mode is needed (atleast in my old sammy phone, maybe same in moto phones)
What's wrong with restoring the backup of the stock rom that should have been made before wiping and flashing a different rom? Not sure what I'm missing here.
Sent from my Nexus 10 using XDA Premium HD app
Download mode is useful to flash the entire phone back to stock using the OEM tools. It's not just for the stock ROM. It's everything. It's useful if you get a bit carried away in TWRP and wipe partitions you really shouldn't be touching. Or if you somehow manage to bork your recovery, or at least can't get into it. It's also good if you want your phone to be completely stock to sell it or to send it in on warranty. I'm sure someone could come up with other scenarios where it's useful.
But yes, it is a good idea to keep a backup of your stock ROM. And as always, know what you're flashing, make sure it's for your phone and check md5s. And be mindful of what you're doing in recovery. You should be able to avoid most issues. Download mode is indeed something you shouldn't be using often but as I said above there are situations where it is useful or necessary. It's actually something I suggest you know how to use. I say it's always a good idea to know how to get back to complete stock for warranty stuff, selling, or if something just goes majorly wrong.
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Semantics said:
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Click to expand...
Click to collapse
Hmm.....interesting. I may try that next time I have to flash to stock.
Sent from my VS980 4G using Tapatalk
Same Problem
simon_lefisch said:
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Can you fill me in on how you used fastboot to install twrp? I am in the same boat right now...
i'm stuck as well in Fastboot and can't figure it out
emmur0 said:
i'm stuck as well in Fastboot and can't figure it out
Click to expand...
Click to collapse
I sent you a pm
You can you adb side load which is the same for flashing rom, pushing, or pulling file from the phone which is the first thing to learn before flashing anything to the new device that you got and know nothing about.
Sent from my LG-LS980 using xda premium
I have looked around the forums for this problem, but could only find something about root checker.
But does the G2 have a flash counter like the Samsung phones does?
What i mean by this is; Will i be able to restore the stock firmware via the LG flash tool, and the stores would never be able to tell it was flashed?
I'm asking because my brother bricked his device, and made the sim card reader stop working. And after we factory reset the phone via Odin and sent it back to be repaired, we got it back without getting it fixed. Turns out we missed the Flash counter, and now that phone is out of warrenty.
Does the G2 have a similar counter build in? If not, good job LG!
Yes, the LG G2 has a rootchecker. Unfortunately there is no way to reset it for now. I've used LG flash tool to restore to stock at least 4 times, but it still shows "ROOTED" in red letters when I switch to download mode. It shows "unrooted" right after restoring to stock, but restart and check it an hour later and it shows "ROOTED." I'm still looking for a solution to this. My GPS is horrible so I want to return it.
benjaminj007 said:
Yes, the LG G2 has a rootchecker. Unfortunately there is no way to reset it for now. I've used LG flash tool to restore to stock at least 4 times, but it still shows "ROOTED" in red letters when I switch to download mode. It shows "unrooted" right after restoring to stock, but restart and check it an hour later and it shows "ROOTED." I'm still looking for a solution to this. My GPS is horrible so I want to return it.
Click to expand...
Click to collapse
Anyone else confirm this?
I though a simple flash to stock resets the flash/rooted message.
bigup7 said:
Anyone else confirm this?
I though a simple flash to stock resets the flash/rooted message.
Click to expand...
Click to collapse
Mine goes back to UNROOTED after flashing to stock. D802.
MalignantQuechnitlan said:
Mine goes back to UNROOTED after flashing to stock. D802.
Click to expand...
Click to collapse
What I understand from benjaminj007's post, his goes to UNROOTED as well, however at some point it reverts to ROOTED. Have you checked yours after some time or just after flashing?
I installed stock somewhere last week, just checked and it still says unrooted.
As far as I remember my 802 also said unrooted after my total reset using lg Flash tool.
Sent from my LG-G2 using Tapatalk