Related
Hello everyone.
I have tried searching a few threads but i have not found the right info i needed. Here is my story. I am also sorry i am new to Android so i have no knowledge of what Rooting & such is.
I bought a S3 from someone on Kijiji. The phone worked fine & he told me he JUST unlocked the device. I said alright & went ahead & bought the phone from him. I came home & looked at the device. The Device Status said " Modified" What does that mean?. I started downloading apps & a app called "SuperUser" wanted permissions to some apps i downloaded. So searched & found it it was rooted because of that app.
After that i downloaded " Rom Manager" seeing as a few people told me to do it to check if it has been trully rooted. ( Bad idea). I did the Factory reset from there & boom the phone just shut off & never came back alive. Did all the reset that everyone said & nothing. Computer wont even see its on or anything. Odin wont show anything either " Thinking he may have rooted it" I tried charging it & nothing. I tried the Vol down, power & home button but nothing will show up. Black screen. When i take the battery out & plug the phone on the charger the red LED comes on but comes off after a few seconds.
Seeing as it may be hardbricked, i contacted Rogers & they are sending me out a replacement S3 for $35. The thing is i want to ask you guys, will they see if it has been truly rooted & such? Rogers tech support agent told me they send it to Samsung & they deal with it & if they see its been rooted i will be charged around $600 for the refurbished device they are sending me. The phone was warranty until Sept 13, 2013.
So all in all, what does "Modified" On the device status mean & will Samsung see if it has been rooted if the phone won't even power on or anything at all? I am just worried that i will have to pay $600 fee for the refurb device.
Thank you for you time & i am sorry if this has been answered somewhere.
Bump for any help. Thanks
Dimitri.k said:
After that i downloaded " Rom Manager" seeing as a few people told me to do it to check if it has been trully rooted. ( Bad idea).
Click to expand...
Click to collapse
What exactly did you do in Rom Manager? Did you flash a recovery from there and say choose the wrong recovery? If so you hard bricked it for sure cause it will have written the recovery to the wrong partition (most likely the bootloader partition). If you did not do that, then need exact info on what you did inside Rom Manager.
MODIFIED on the status only means its rooted, thats all, nothing bad.
Dixit
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
BTW to answer your other question, Samsung will probably not be able to tell it was rooted since from your description you clearly hard bricked it to the point where the bootloader was wiped. So Samsung would have to re-write that bootloader which takes JTAG work for them to find out your phone was rooted, I doubt they will do that, plenty of others have been in your situation and Samsung as replaced it without a problem. I dont think their service dept goes to the level of JTAG'ing a device to check if it rooted or check what happened.
Hello Dixit & thank you for the reply.
I opened up Rom Manager & pressed the " Reboot into Recovery" Once i pressed that, the phone just shut off & never came back alive ever again. The person that sold me it STILL says he never rooted the phone. Of course we all know why but anyways. I did all the power trickes like holding down the Vol down, Home & power button & nothing comes up at all.
Before all this happened i did see the Status saying " Modified" That is why i asked about it. Rogers techs told me that Samsung will try & force the phone to wake up or force the software back into the phone. They told me if Samsung find out its been rooted, it will cost $600 for me to pay for the refurb device. Funny thing is Refurb S3 from Telus is at $349.99 yet Rogers claims Samsung will charge $600 for it..
Anyways i am a bit worried as well.
dixit said:
What exactly did you do in Rom Manager? Did you flash a recovery from there and say choose the wrong recovery? If so you hard bricked it for sure cause it will have written the recovery to the wrong partition (most likely the bootloader partition). If you did not do that, then need exact info on what you did inside Rom Manager.
MODIFIED on the status only means its rooted, thats all, nothing bad.
Dixit
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
BTW to answer your other question, Samsung will probably not be able to tell it was rooted since from your description you clearly hard bricked it to the point where the bootloader was wiped. So Samsung would have to re-write that bootloader which takes JTAG work for them to find out your phone was rooted, I doubt they will do that, plenty of others have been in your situation and Samsung as replaced it without a problem. I dont think their service dept goes to the level of JTAG'ing a device to check if it rooted or check what happened.
Click to expand...
Click to collapse
Almost the same that happened to me... I sent the phone to Samsung
*10/22/2012//16:21:22//0001773863//Web Chat//ASC*
10/22/2012 3:20 PM-Khatie Rodrigez: Accessory: BATTERY,BATTERY COVER,CHARGER
*10/22/2012//16:21:21//0001773863//Web Chat//ASC*
10/22/2012 3:20 PM-Khatie Rodrigez: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)
*10/22/2012//13:59:08//STADL1037//Web Chat//Customer*
1) Inquiry: BP ci on the status of the order he send the phonwe thru USPS
2) Steps Taken:INFOR
M the customer that if the package was recievedc today still has not being procees into his account yet TAT was given 5-7 bus day
3) Resources used:gcic
4) Additional comments:
5) Outcome:educ customer
Currently waiting for an update
Holding Volume Down + Home + Power won't boot it into Download Mode at all? If it's a firmware issue you'd just need to get to download mode to reflash via ODIN.
Dimitri.k said:
Hello Dixit & thank you for the reply.
I opened up Rom Manager & pressed the " Reboot into Recovery" Once i pressed that, the phone just shut off & never came back alive ever again. The person that sold me it STILL says he never rooted the phone. Of course we all know why but anyways. I did all the power trickes like holding down the Vol down, Home & power button & nothing comes up at all.
Before all this happened i did see the Status saying " Modified" That is why i asked about it. Rogers techs told me that Samsung will try & force the phone to wake up or force the software back into the phone. They told me if Samsung find out its been rooted, it will cost $600 for me to pay for the refurb device. Funny thing is Refurb S3 from Telus is at $349.99 yet Rogers claims Samsung will charge $600 for it..
Anyways i am a bit worried as well.
Click to expand...
Click to collapse
Well first off what the previous owner did isnt harmful as it was just rooted and was working fine when you got it. You can easily unroot and clear everything including putting it back to original stock recovery in about 30mins.
Now on your issue, I dont know if Rom Manager attempted to flash a recovery or not, normally just hitting the Reboot into Recovery basically issues a ADB Recovery command that just tells the phone to boot into recovery, that is not harmful in anyway. Looks more like the RomManager flashed a recovery and did so by flashing something that is not for the GS3 which then wiped the bootloader partition and basically hard bricked it.
If you too scared to send it to Samsung, then pay the $50 some dollars it costs to have the JTAG service done by MobiletechVideos
Dixit
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
this_is_nick6 said:
Holding Volume Down + Home + Power won't boot it into Download Mode at all? If it's a firmware issue you'd just need to get to download mode to reflash via ODIN.
Click to expand...
Click to collapse
Nope wont help here, the bootloader partition looks like it got wiped out, nothing you can do except JTAG it at this point. If the SAMSUNG doesnt come up or the phone dont vibrate its toast. I had the same issue happen, same results of how just the LED comes on for 5secs and then goes off. Computer wont see anything except QUSB_DLOAD on the Device Manager. Meaning it would only work if someone had the QPST tool files to revive it but to date no one has those files or information.
dixit said:
Well first off what the previous owner did isnt harmful as it was just rooted and was working fine when you got it. You can easily unroot and clear everything including putting it back to original stock recovery in about 30mins.
Now on your issue, I dont know if Rom Manager attempted to flash a recovery or not, normally just hitting the Reboot into Recovery basically issues a ADB Recovery command that just tells the phone to boot into recovery, that is not harmful in anyway. Looks more like the RomManager flashed a recovery and did so by flashing something that is not for the GS3 which then wiped the bootloader partition and basically hard bricked it.
If you too scared to send it to Samsung, then pay the $50 some dollars it costs to have the JTAG service done by MobiletechVideos
Dixit
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
Nope wont help here, the bootloader partition looks like it got wiped out, nothing you can do except JTAG it at this point. If the SAMSUNG doesnt come up or the phone dont vibrate its toast. I had the same issue happen, same results of how just the LED comes on for 5secs and then goes off. Computer wont see anything except QUSB_DLOAD on the Device Manager. Meaning it would only work if someone had the QPST tool files to revive it but to date no one has those files or information.
Click to expand...
Click to collapse
Ouch.. that's rough..
I was hoping for his sake it was something much simpler.. lol
You should be able to force the phone into download mode with a Jig. Before you do that, I'd recommend doing some research to figure out what you need to do to properly re-image the phone.
And this is why those new to android should really do their research before modding their devices...I suggest every new android user read up on ADB and get that properly setup on their PC...ADB is very handy!!!! I have never once used an app to flash a recovery for a phone as choosing the wrong one can wipe bootlader partitions as seems to be the case here...I use either fast boot or ADB..using this I can double check to make sure I have selected the correct recovery and that it will flash to the proper partition...to the OP chances are Samsung won't go far as performing a JTAG in which case they won't see the phone is rooted and will just send you out a new phone...if you'd rather not deal with Samsung get in touch with mobiletechvideos and pay for the JTAG as another user has recommended.. its actually a great service as it makes your device essentially brick proof after the JTAG mod.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Thank you everyone for your help. The guy would owned it first still denies he did anything to it. I am waitinf for Rogers to send me a refurb S3 and I'm sending my back to them.
Also I never knew what to do with ROM MANAGER. I am new to thi stuff and I am sorry I did not read all about this before. I was to happy enjoying the phone and all.... I won't be rooting my other one seeing as I do NOT know how to root and such. I do not want to ruin this one. Also when I went into Rom Mer I pressed " reboot to recovery" that's how the phone stopped working. I have no idea what the other person did on it.
Dimitri.k said:
Thank you everyone for your help. The guy would owned it first still denies he did anything to it. I am waitinf for Rogers to send me a refurb S3 and I'm sending my back to them.
Also I never knew what to do with ROM MANAGER. I am new to thi stuff and I am sorry I did not read all about this before. I was to happy enjoying the phone and all.... I won't be rooting my other one seeing as I do NOT know how to root and such. I do not want to ruin this one. Also when I went into Rom Mer I pressed " reboot to recovery" that's how the phone stopped working. I have no idea what the other person did on it.
Click to expand...
Click to collapse
Btw whether he did anything to it or not, it's not his fault that your phone bricked. There's nothing he could've done that would brick your phone just by going into recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Deoxlar said:
Btw whether he did anything to it or not, it's not his fault that your phone bricked. There's nothing he could've done that would brick your phone just by going into recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I fully understand that BUT he could have been honest by saying that he did root it. He knew I never knew anything about rooting and such. So he never admitted he did. Oh well. Lesson learned. Never believe anyone.
Rogers SGS3,in Download Mode,Now what?
this_is_nick6 said:
Holding Volume Down + Home + Power won't boot it into Download Mode at all? If it's a firmware issue you'd just need to get to download mode to reflash via ODIN.
Click to expand...
Click to collapse
I have bricked my Samsung Galaxy S3 with Rogers in Canada. I cant get passed the Samsung Boot scren. I can get into Download mode. It just hangs there. What am I supposed to do when its saying downloading? I am totally frazzled.Please help
Dimitri.k said:
Hello everyone.
I have tried searching a few threads but i have not found the right info i needed. Here is my story. I am also sorry i am new to Android so i have no knowledge of what Rooting & such is.
I bought a S3 from someone on Kijiji. The phone worked fine & he told me he JUST unlocked the device. I said alright & went ahead & bought the phone from him. I came home & looked at the device. The Device Status said " Modified" What does that mean?. I started downloading apps & a app called "SuperUser" wanted permissions to some apps i downloaded. So searched & found it it was rooted because of that app.
After that i downloaded " Rom Manager" seeing as a few people told me to do it to check if it has been trully rooted. ( Bad idea). I did the Factory reset from there & boom the phone just shut off & never came back alive. Did all the reset that everyone said & nothing. Computer wont even see its on or anything. Odin wont show anything either " Thinking he may have rooted it" I tried charging it & nothing. I tried the Vol down, power & home button but nothing will show up. Black screen. When i take the battery out & plug the phone on the charger the red LED comes on but comes off after a few seconds.
Seeing as it may be hardbricked, i contacted Rogers & they are sending me out a replacement S3 for $35. The thing is i want to ask you guys, will they see if it has been truly rooted & such? Rogers tech support agent told me they send it to Samsung & they deal with it & if they see its been rooted i will be charged around $600 for the refurbished device they are sending me. The phone was warranty until Sept 13, 2013.
So all in all, what does "Modified" On the device status mean & will Samsung see if it has been rooted if the phone won't even power on or anything at all? I am just worried that i will have to pay $600 fee for the refurb device.
Thank you for you time & i am sorry if this has been answered somewhere.
Click to expand...
Click to collapse
been there done that.. i hard bricked my galaxy s3 too samsung fixes it for free. just blame the software update and wala trihey feel bad for you and should fix the phone for free since its hard bricked (you cant turn it on or anything) they have no proof really. id send it to samsung like i did
vance74 said:
I have bricked my Samsung Galaxy S3 with Rogers in Canada. I cant get passed the Samsung Boot scren. I can get into Download mode. It just hangs there. What am I supposed to do when its saying downloading? I am totally frazzled.Please help
Click to expand...
Click to collapse
Research. Use Odin to flash a rogers ROM.
Sent from my A510 using Tapatalk 2
vance74 said:
I have bricked my Samsung Galaxy S3 with Rogers in Canada. I cant get passed the Samsung Boot scren. I can get into Download mode. It just hangs there. What am I supposed to do when its saying downloading? I am totally frazzled.Please help
Click to expand...
Click to collapse
Odin a stock rogers firmware thats all you gotta do bud it would unroot your device and allow you to get past that screen. and then you can reroot if you want to
Not sure if its because I'm stupid or faulty hardware or both.
So, HOX is unrooted, s-off with super cid (from e-bay). Got it for my dad.
A few days ago it froze, and when rebooting it just threw endless FCs and would not let the system finish loading up properly.
I did a factory reset from the fastboot, afterwards it worked ok.
But, the day after, it froze again. This time, when rebooting, it just showed a blank black screen after the HTC splash screen and did not go anywhere.
I went again to the fastboot screen, and then for some reason I went on to the stock recovery (I'm stupid). This time I did the "wipe user data/factory reset" from there, after also wiping chache and stuff (I'm used to do this in my rooted HOX with custom recovery).
After that, I did a reboot from the stock reovery. It went to the HTC splash screen, and here I was stupid again. I'm not sure how long he was like that, if for a minute or 5 or 10 (I did some other stuff in between). I thought it was stuck, and instinctively shut it down and the tried to turn it on again. I forgot I did the factory reset and that it might have been in the middle of the installation.
After that, the phone did not respond to anything. It won't charge, won't turn on, won't show any led indication, and in windows it is noted as the infamous APX. I have spent the entire day reading about it and I'm afraid the phone is lost.
I think I got the proper APX driver (it is seen as NVidia USB Bootrecovery driver for mobile devices). I tried some versions of nvflash. One shows "unknown device", other shows some info on the device when trying "nvflash --creat" but gets stuck at "starting nvflash" when trying "nvflash --sync".
So, my first question is, are the stock recovery "factory reset" and the fastboot reset the same?
When I do a factory reset in fastboot it resets and makes a "fresh install", while in the stock recovery it does some stuff but does not reboot automatically. I am afraid that I "wiped" the entire system partition when I did the reset after the stock recovery factory reset.
Have there been any advances in the APX field in the last year? Is there any hope?
If not, will anyone be willing to buy an APX S-OFF HOX in mid 2014? Or should I just throw it into the blender?
Thanks in advance,
Gabriel
this should help
gavrushka said:
Not sure if its because I'm stupid or faulty hardware or both.
So, HOX is unrooted, s-off with super cid (from e-bay). Got it for my dad.
A few days ago it froze, and when rebooting it just threw endless FCs and would not let the system finish loading up properly.
I did a factory reset from the fastboot, afterwards it worked ok.
But, the day after, it froze again. This time, when rebooting, it just showed a blank black screen after the HTC splash screen and did not go anywhere.
I went again to the fastboot screen, and then for some reason I went on to the stock recovery (I'm stupid). This time I did the "wipe user data/factory reset" from there, after also wiping chache and stuff (I'm used to do this in my rooted HOX with custom recovery).
After that, I did a reboot from the stock reovery. It went to the HTC splash screen, and here I was stupid again. I'm not sure how long he was like that, if for a minute or 5 or 10 (I did some other stuff in between). I thought it was stuck, and instinctively shut it down and the tried to turn it on again. I forgot I did the factory reset and that it might have been in the middle of the installation.
After that, the phone did not respond to anything. It won't charge, won't turn on, won't show any led indication, and in windows it is noted as the infamous APX. I have spent the entire day reading about it and I'm afraid the phone is lost.
I think I got the proper APX driver (it is seen as NVidia USB Bootrecovery driver for mobile devices). I tried some versions of nvflash. One shows "unknown device", other shows some info on the device when trying "nvflash --creat" but gets stuck at "starting nvflash" when trying "nvflash --sync".
So, my first question is, are the stock recovery "factory reset" and the fastboot reset the same?
When I do a factory reset in fastboot it resets and makes a "fresh install", while in the stock recovery it does some stuff but does not reboot automatically. I am afraid that I "wiped" the entire system partition when I did the reset after the stock recovery factory reset.
Have there been any advances in the APX field in the last year? Is there any hope?
If not, will anyone be willing to buy an APX S-OFF HOX in mid 2014? Or should I just throw it into the blender?
Thanks in advance,
Gabriel
Click to expand...
Click to collapse
http://www.hackmyandroid.com/comprehensive-guide-on-unbricking-the-htc-one-x/4216
AND/OR
http://forum.xda-developers.com/showthread.php?t=1609190
---------- Post added at 08:32 PM ---------- Previous post was at 08:25 PM ----------
And yes they are the same. (factory reset)
This is a very simple fix, takes some time and a bit of common sense and patience, but if you follow the links i posted you should be fine. I have done almost everything possible to my HOX including what you did and they helped
Watch out....APX is in most cases a very dead hox. A new mainboard is the solution to a 100% fix !
The rest of the fixes that are available are mainly temp fixes.
m.jordan89 said:
http://www.hackmyandroid.com/comprehensive-guide-on-unbricking-the-htc-one-x/4216
AND/OR
http://forum.xda-developers.com/showthread.php?t=1609190
---------- Post added at 08:32 PM ---------- Previous post was at 08:25 PM ----------
And yes they are the same. (factory reset)
This is a very simple fix, takes some time and a bit of common sense and patience, but if you follow the links i posted you should be fine. I have done almost everything possible to my HOX including what you did and they helped
Click to expand...
Click to collapse
I'm sorry, but I have said that my phone won't even turn on - the links are all about a "turnable" phone that can go to bootloader, so I can't use them...
Try This out
gavrushka said:
I'm sorry, but I have said that my phone won't even turn on - the links are all about a "turnable" phone that can go to bootloader, so I can't use them...
Click to expand...
Click to collapse
I had the same issue and I think this is what i did to get it to come on. try it, not like you have anything to lose.
your gonna need masking tap, your phone, the charger and a wall outlet
Now what your gonna do is tightly and i do mean as tight as possible tape the phone power button down
Cut a length of tape a little longer then the length of the phone
Line up the middle of the tape with the power button
Pressing down the power button, stretch out the tape over it and secure the rest of the tape to the back and front of the phone in such a way as to ensure that the power button stays down
Do the same for the volume up and down buttons
Once you feel certain that the above is done properly plug it into the wall to charge and leave it.
I think i left mine over night but i think its best you just leave it in a dark area with the screen facing up to charge so you will know when it turns on.
I advise even if it doesn't turn on in a time you see appropriate message me here and I will see if i come up with anything else
Dead boot repair available for this model nv flash with sbk if you want files just pm me and try to run it.
Sent from my SM-N7505 using XDA Free mobile app
Coolmfarshard said:
Dead boot repair available for this model nv flash with sbk if you want files just pm me and try to run it.
Sent from my SM-N7505 using XDA Free mobile app
Click to expand...
Click to collapse
the solution not working something wrong with this maybe you talk for THIS are you tested or just give some advice?
This is latest files with sbk
Send your email I'd I'll share with you
Just give a try
Sent from my SM-N7505 using XDA Free mobile app
Coolmfarshard said:
This is latest files with sbk
Send your email I'd I'll share with you
Just give a try
Sent from my SM-N7505 using XDA Free mobile app
Click to expand...
Click to collapse
hi would you share with me please??? let me know greets. Javier.
javigc said:
hi would you share with me please??? let me know greets. Javier.
Click to expand...
Click to collapse
he shared HERE but you must to find the corect drivers try THIS DRIVERS and report if you have succsess
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Dlome said:
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Click to expand...
Click to collapse
I would return it
Since I cant do anything until Monday I decided to mess with the phone a little more, I was able to get a custom recovery installed finally so hopefully all I need to do is install a new rom but the problem is the recovery is unable to mount my SD card to perform the install. I can read the sd card when it is in my old phone but not on the HTC One. Currently have Philz Touch installed as the recovery.
Is there any way to fix this or even bypass it all together?
Edit: I have been able to side load CM11 Nightly onto the phone so now it is functioning. I am having an issue with sound though so hopefully I can fix that.
clsA said:
I would return it
Click to expand...
Click to collapse
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
redpoint73 said:
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
Click to expand...
Click to collapse
This sounded like a hardware problem to me
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
Click to expand...
Click to collapse
it's hard to mess the phone up when you can't even get the bootloader unlocked
clsA said:
it's hard to mess the phone up when you can't even get the bootloader unlocked
Click to expand...
Click to collapse
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
redpoint73 said:
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
Click to expand...
Click to collapse
Fair enough ... I read it wrong I guess
clsA said:
Fair enough ... I read it wrong I guess
Click to expand...
Click to collapse
Naw, really looks more like a matter of the OP needs being clear enough, and not giving enough info. If anything, best to get clarification before suggesting warranty service (especially once mods have been started - but again it was hard from the OP's description to know how far it got). Although if it was in fact a hardware defect, of course a warranty claim is valid.
Hey guys my verizon g4 is stuck in bootloop and im not rooted, i cant get the past the lg boot screen, it stays on their for around 20 seconds goes black and back to lg screen.
I can get into recovery but none of the options do anything ive tried safe mode, usb debug mode i even tried factory reset they all just go back to the lg screen.
I was just watching a video on facebook when it froze restarted and now im stuck, ive been restarting it all day and i was able to get it to boot up twice but it froze again within seconds any help is appreciated
it might be the defective motherboard issue that people are having. you could try reflashing the system, but if that doesn't work you probably need a new motherboard/phone
Not an answer, but an experience.
I have an HTC ONE M8, VZW. I s-offed it and rooted it right when I got it. I began adding some of my google apps and it did what your G4 is doing, stuck on VZW screen.
Since I was s-off I was able to get a recovery in and ready. I was able to get a custom rom onto the phones external sd. I flashed it with the recovery and the flash took, no more vzw screen lock up.
Your experience makes me wonder what VZW is doing to force bootloops on unlocked or rooted phones with their retail products. Paranoid maybe, but I can see VZW deliberately adding code to stick it to rooted users.....................................I say this still knowing that many have rooted the current run of devices without issues...........................
luck
i read about the problems with the motherboard going bad, im assuming thats what happened to mine. Lg sent me a replacement under warranty
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
killa408shark said:
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
Click to expand...
Click to collapse
What is the 13B KDZ and how did you flash it? Im having same exact issue.
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
b3y0ndd34th said:
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
Click to expand...
Click to collapse
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
mainlygreen said:
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
Click to expand...
Click to collapse
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
same issue of mine I was out then it cut off & wouldn't come back on but now it charges up & makes it to the boot screen
b3y0ndd34th said:
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
Click to expand...
Click to collapse
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
bhuvesh89 said:
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
Click to expand...
Click to collapse
They mailed me a new one, no battery, no back. I put my battery, sim card, sd card, and back on the new phone, fired it up. Rolled it back, rooted it, then I mailed the old one back.
Personally, I love this phone, but I think I will be getting a nexus next.
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.
Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...
enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.
Mine is @ LG as I haven't bought from Google... Let's see...
talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.
Nexus are impossible to brick, unless you flash stock factory image...
I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus