Related
Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.
If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...
droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.
droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app
T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app
Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1
droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.
Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1
Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!
I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
salissimo said:
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
Click to expand...
Click to collapse
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
exad said:
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Click to expand...
Click to collapse
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
i guess i deserve it
thanks
iElvis said:
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
Click to expand...
Click to collapse
Charge it overnight and see if it turns on at all afterwards.
Sent from my One X using xda app-developers app
Delete.
Sent from my HTC One X using xda premium
salissimo said:
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
Click to expand...
Click to collapse
There's bit of etiquette involved. If the thread is "mature" in the sense that the OP's issue has been resolved, or multiple discussion threads have evolved, then popping in with a related question is fine. It's just not polite to pop in on the second page of someone else's query when people are still trying to help him, unless you have the identical problem.
salissimo said:
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
Click to expand...
Click to collapse
It's possible, but sounds unlikely. I don't think that just changing some setting would stop it from at least powering on. ROM Manager would have had to overwrite something critical that would prevent the CPU from even finding hboot. Had you merely messed up some boot setting, you should still be able to get the boot screen, which would then start looping.
Plug your phone into your PC and see what pops up in Device Manager. I expect you'll get QHUSB_DLOAD, which means you're bricked.
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
salissimo said:
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
Click to expand...
Click to collapse
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
I've never used that unbrick tool but I'm assuming you would need to be able to get to the bootloader to get it to work. Correct me if I'm wrong.
Sent from my HTC One X using xda app-developers app
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
exad said:
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
Click to expand...
Click to collapse
salissimo said:
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
Click to expand...
Click to collapse
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
exad said:
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
Click to expand...
Click to collapse
salissimo said:
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
Click to expand...
Click to collapse
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
If you got it from AT&T, contact them and ask for bit. Whenever they activate a phone, we store it in the system and keeps track of what phone the customer is using.
Sent from my Carbon-ize Evita using xda-developers app
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
exad said:
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
Click to expand...
Click to collapse
do you think mz phone is still under warranty considering it was tampered, and i cracked it open?
thanks!
salissimo said:
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
Click to expand...
Click to collapse
I doubt AT&T can tell you unlocked it. They'll assume it's a power issue like Telus did for me. HTC may or may not warrant it. Mixed results from xda members
Sent from my One X using xda app-developers app
It should be in the EFS nv_data.bin. folder.
Sent from my HTC One X using xda premium
ok so my one x was running the latest AOKP rom then i decided i wanted to go back to stock for some stupid reason. so i flashed the RUU and all was fine.. then i updated it on the phone by going to software update, unaware that doing an OTA update would brick my phone if it was previously rooted (at least from what ive read)
so now my phone will not even power on, doesn't light up when plugged into charger. when i plug into computer it comes up as Qualcomm HS-USB QDLoader 9008.
from what i understand, it can be unbricked, but only using JTAG. is that correct?
it is still under warranty so i took it into rogers and they are sending it for repair to Ontario (i am in vancouver)... what are the chances that they will know that i bricked it myself and end up just sending it back not fixed?
kinda sucks cause now i have no phone for "3-4 weeks"
greenbackz said:
ok so my one x was running the latest AOKP rom then i decided i wanted to go back to stock for some stupid reason. so i flashed the RUU and all was fine.. then i updated it on the phone by going to software update, unaware that doing an OTA update would brick my phone if it was previously rooted (at least from what ive read)
so now my phone will not even power on, doesn't light up when plugged into charger. when i plug into computer it comes up as Qualcomm HS-USB QDLoader 9008.
from what i understand, it can be unbricked, but only using JTAG. is that correct?
it is still under warranty so i took it into rogers and they are sending it for repair to Ontario (i am in vancouver)... what are the chances that they will know that i bricked it myself and end up just sending it back not fixed?
kinda sucks cause now i have no phone for "3-4 weeks"
Click to expand...
Click to collapse
More than likely they won't bother being it won't do anything.
Sent from my HTC One XL using xda premium
As Ken said, they probably can't tell since, ya know it work turn on.
Sent from my evita
RollTribe said:
As Ken said, they probably can't tell since, ya know it work turn on.
Sent from my evita
Click to expand...
Click to collapse
It's on if the computer is recognizing it. Read his post again.
brandontaz2k2 said:
It's on if the computer is recognizing it. Read his post again.
Click to expand...
Click to collapse
Hsusb =. Brick
It's Qualcomm high speed usb dl mode. That only comes up on a brick or if u power on with volume up that puts phone in download mode. And I'd wouldn't recommend playing in that part of the phone at all.
And please if you don't know 100% what your talking about please don't throw out random ideas, one wrong word and you can trash someones phone. Be careful with any advice.
Sent from my HTC One XL using xda premium
31ken31 said:
Hsusb =. Brick
It's Qualcomm high speed usb dl mode. That only comes up on a brick or if u power on with volume up that puts phone in download mode. And I'd wouldn't recommend playing in that part of the phone at all.
And please if you don't know 100% what your talking about please don't throw out random ideas, one wrong word and you can trash someones phone. Be careful with any advice.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i know its bricked for sure. basically i just want to know if there's a way they can tell exactly how it was bricked and/or if it was previously flashed. if it shows up on the computer there's gotta be some kinda way to communicate with it using other equipment right? i took a gamble hoping they won't notice and just repair or replace the phone LOL. :fingers-crossed:
I really don't think there's any way for them to tell. There are only two ways back from this kind of brick, having the motherboard replaced, and jtag repair. Either way I don't think it matters, the partitions are fried, so I highly doubt there is any way to tell how it happened.
Sent from my Evita
31ken31 said:
Hsusb =. Brick
It's Qualcomm high speed usb dl mode. That only comes up on a brick or if u power on with volume up that puts phone in download mode. And I'd wouldn't recommend playing in that part of the phone at all.
And please if you don't know 100% what your talking about please don't throw out random ideas, one wrong word and you can trash someones phone. Be careful with any advice.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
timmaaa said:
I really don't think there's any way for them to tell. There are only two ways back from this kind of brick, having the motherboard replaced, and jtag repair. Either way I don't think it matters, the partitions are fried, so I highly doubt there is any way to tell how it happened.
Sent from my Evita
Click to expand...
Click to collapse
hm.. ic. so is it possible that even a completely stock phone thats never been rooted or anything could have this same problem? i guess i'll find out when i hear from them lol.
Yes, it's possible.
Sent from my Evita
greenbackz said:
hm.. ic. so is it possible that even a completely stock phone thats never been rooted or anything could have this same problem? i guess i'll find out when i hear from them lol.
Click to expand...
Click to collapse
Its been reported here and on AT&T forums, that the RUU and OTA have bricked completely stock One X's. Its not "common", but its happened.
Anything that updates hboot can potentially brick the phone, if the install doesn't go just right.
hate to resurrect an old thread, but just thought i'd update everyone and let them know rogers sent me a refurb phone that was in better condition than the phone i had sent in for repair .
so if anyone hard bricks their phone in the future like i did, if u have a warranty then they can't tell how it was bricked. if u don't have a warranty, u can get it JTAGGED, its the only way to fix it besides a complete mobo swap lol. :good:
So, I stupidly flashed RenderBroken's Custom Kernel for CM11/AoCP/OmniRom & SlimKat on my Nexus 5 running latest CM11 without checking its meant for AT&T Samsung Galaxy S II SGH-I777.
After hitting reboot upon successful flashing Nexus5 went off and doesnt boot at all.
Doesnt get into fastboot or even download mode!
When connect charger, nothing happens and on connecting to PC only shows on device manager as unknown device!
Any way to fix? Or need to take it for repairs?
PLEASE ASSIST!
:crying:
Running (was):
ROM: CM11
Kernel: Chaos Kernel
Kernel that bricked the phone: http://forum.xda-developers.com/showthread.php?t=2582364
Yes. Flashing a kernel not meant for your device is about the only thing that will brick your phone.
If you can't get into the bootloader it's toast.
Sent from my Nexus 10 using Tapatalk
You wouldn't have flashed over the bootloader or recovery so boot into it and reflash if you still have the old kernel on the memory. Otherwise fastboot one from your pc
Sent from my Nexus 5 using Tapatalk
I'm not 100% sure on this one. I've flashed a N4 kernel on this phone and I could still get into fastboot to flash the proper kernel. But with a Samsung kernel, I think they do it differently. I took a look inside the zip and it's flashing a "zimage" and a key layout file which doesn't exist on the N5. You might actually be bricked here.
Thank you for all your efforts, but I think my Nexus5 is indeed totally bricked! Doesnt respond at all to Vol+/- and plugging usb. No Download Mode!
Time to look for an LG Service Centre, just not sure what should I tell them how I attained this which makes them believe its not user induced damage. Also looking at the condition it is at will they still figure it out that the device was unlocked/rooted?
:crying:
Subhojit said:
Thank you for all your efforts, but I think my Nexus5 is indeed totally bricked! Doesnt respond at all to Vol+/- and plugging usb. No Download Mode!
Time to look for an LG Service Centre, just not sure what should I tell them how I attained this which makes them believe its not user induced damage. Also looking at the condition it is at will they still figure it out that the device was unlocked/rooted?
:crying:
Click to expand...
Click to collapse
Try to find a repair center where they offer Jtag service to revive the phone somewhere near you.
gee2012 said:
Try to find a repair center where they offer Jtag service to revive the phone somewhere near you.
Click to expand...
Click to collapse
But would they find out I have tampered with the device?
Subhojit said:
But would they find out I have tampered with the device?
Click to expand...
Click to collapse
Not if they can`t get the N5 to boot or are able to extract information from the device, they`ll probably replace the motherboard and flash the stock rom under warranty.
gee2012 said:
Not if they can`t get the N5 to boot or are able to extract information from the device, they`ll probably replace the motherboard and flash the stock rom under warranty.
Click to expand...
Click to collapse
Hoping the same!
Subhojit said:
So, I stupidly flashed RenderBroken's Custom Kernel for CM11/AoCP/OmniRom & SlimKat on my Nexus 5 running latest CM11 without checking its meant for AT&T Samsung Galaxy S II SGH-I777.
After hitting reboot upon successful flashing Nexus5 went off and doesnt boot at all.
Doesnt get into fastboot or even download mode!
When connect charger, nothing happens and on connecting to PC only shows on device manager as unknown device!
Any way to fix? Or need to take it for repairs?
PLEASE ASSIST!
:crying:
Click to expand...
Click to collapse
I did the same, flashed a non CAF kernel to my CAF based rom, and it didnt boot.
But i could atleast see the google logo in the beginning so i was able to get into fastboot mode and flash another kernel.
So if its completly dead/blank then you need service, if you still have an ok bootloader and sees the google logo you should be able to get into fastboot mode.
hold both volume buttons pressed, and then try to start it up by holding the power button.
( i had to hold the power button for 10+sec for it to start/turn off)
ranarn said:
I did the same, flashed a non CAF kernel to my CAF based rom, and it didnt boot.
But i could atleast see the google logo in the beginning so i was able to get into fastboot mode and flash another kernel.
So if its completly dead/blank then you need service, if you still have an ok bootloader and sees the google logo you should be able to get into fastboot mode.
hold both volume buttons pressed, and then try to start it up by holding the power button.
( i had to hold the power button for 10+sec for it to start/turn off)
Click to expand...
Click to collapse
No, this a CAF based kernel but for an unsupported CAF based ROM. :|
It won't get into bootloader/download mode and service is the only option for me!
Subhojit said:
No, this a CAF based kernel but for an unsupported CAF based ROM. :|
It won't get into bootloader/download mode and service is the only option for me!
Click to expand...
Click to collapse
ok, I am here to choose a device (comparing and looking for errors) and I'm just curious if you normally flashed it ?
so did you flash only the boot image ? or does this package flash other paritions ?
because as far as I know you can flash whatever you want into your boot image... this shouldn't affect the bootloader .. or I am completely wrong ?
LibertyMarine said:
ok, I am here to choose a device (comparing and looking for errors) and I'm just curious if you normally flashed it ?
so did you flash only the boot image ? or does this package flash other paritions ?
because as far as I know you can flash whatever you want into your boot image... this shouldn't affect the bootloader .. or I am completely wrong ?
Click to expand...
Click to collapse
It all depends. It wont overwrite the bootloader but flashing kernels from other devices can short out components, fry them completely and brick the NAND, si yeah
Sent from my Nexus 5 using Tapatalk
rootSU said:
It all depends. It wont overwrite the bootloader but flashing kernels from other devices can short out components, fry them completely and brick the NAND, si yeah
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok, this does actually mean that the bootloader loads some modules from the kernel to boot up ?
LibertyMarine said:
ok, this does actually mean that the bootloader loads some modules from the kernel to boot up ?
Click to expand...
Click to collapse
No, the bootloader tends to have all the kernel elements it needs to boot, but if the NAND is fried that hosts the bootloader or other hardware the bootloader requires to boot, well you're out of luck.
A true brick will mean the device is damaged at a hardware (or firmware of hardware) level. I personally don't believe in such things as "soft bricks". Kernels can most definitely (true / hard) brick a device. The amount of people I saw fry their digitiser chip on the s3 by flashing note 2 kernels and recoveries was absolutely ridiculous. You see, the note 2 digitiser needs much more power than the s3 so the kernel allowed note 2 amounts of power through, frying the chip. This could happen on literally any component if you think about it...
Sent from my Nexus 5 using Tapatalk
rootSU said:
No, the bootloader tends to have all the kernel elements it needs to boot, but if the NAND is fried that hosts the bootloader or other hardware the bootloader requires to boot, well you're out of luck.
A true brick will mean the device is damaged at a hardware (or firmware of hardware) level. I personally don't believe in such things as "soft bricks". Kernels can most definitely (true / hard) brick a device. The amount of people I saw fry their digitiser chip on the s3 by flashing note 2 kernels and recoveries was absolutely ridiculous. You see, the note 2 digitiser needs much more power than the s3 so the kernel allowed note 2 amounts of power through, frying the chip. This could happen on literally any component if you think about it...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ah, ok.. now I understand... so basically you could flash a fish as a boot image.... it doesn't brick your device... but if you boot your device and the boot image is getting loaded and this particular fish boot image has the tendency to exaggerate the amount of power given to the motherboard... your device gets toasted... but if you would boot to the bootloader right after flashing the boot image from recovery... you wouldn't get a bricked device ?
Possibly. But also just flashing something can destroy partitions on the NAND too. In fact, there are so many things that could go wrong but yes in the case of over supply of power as an example, not booting it would save the device
Sent from my Nexus 5 using Tapatalk
rootSU said:
Possibly. But also just flashing something can destroy partitions on the NAND too. In fact, there are so many things that could go wrong but yes in the case of over supply of power as an example, not booting it would save the device
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the information shared!
Hoping that the LG Service guys don't find out I did something as you mentioned it is a h/w (f/w) level issue.
:cyclops:
rootSU said:
Possibly. But also just flashing something can destroy partitions on the NAND too. In fact, there are so many things that could go wrong but yes in the case of over supply of power as an example, not booting it would save the device
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok, thanks very much
sorry that I somehow missed your answer.. I've just pushed the thanks button as some kind of thanks
Have a great weekend !
Hello everyone,
I'm helping a far less android savvy friend with his bricked AT&t G3. He has never rooted or installed anything custom but he has an unexplained bootloop. I know my HTC One inside and out but this is the first LG3 I've ever worked on. Essentially, I'm trying to save his data if at all possible but it's seeming less and less likely as I read more about how the recovery and download mode work on this phone.
It seems like the only way I can get TWRP or any custom recovery onto this phone is if I can get it to boot, so any hope of using adb commands might be ruled out at this point. My question is: Is there any way to get a custom recovery onto this phone through download mode? If not, it seems that a full re-flash to stock might be my only option.
Thanks in advance.
The_mamba said:
Hello everyone,
I'm helping a far less android savvy friend with his bricked AT&t G3. He has never rooted or installed anything custom but he has an unexplained bootloop. I know my HTC One inside and out but this is the first LG3 I've ever worked on. Essentially, I'm trying to save his data if at all possible but it's seeming less and less likely as I read more about how the recovery and download mode work on this phone.
It seems like the only way I can get TWRP or any custom recovery onto this phone is if I can get it to boot, so any hope of using adb commands might be ruled out at this point. My question is: Is there any way to get a custom recovery onto this phone through download mode? If not, it seems that a full re-flash to stock might be my only option.
Thanks in advance.
Click to expand...
Click to collapse
If it's "bricked" brick cannot be brought back brick means it's dead. But if you have download mode it's not fully bricked. But no download mode mainly meant for official use and official firmwares only. Only really suggestion is to use the tot method to fix the phone. But it will indeed wipe everything.
Sent from my iPhone using Tapatalk
hyelton said:
If it's "bricked" brick cannot be brought back brick means it's dead. But if you have download mode it's not fully bricked. But no download mode mainly meant for official use and official firmwares only. Only really suggestion is to use the tot method to fix the phone. But it will indeed wipe everything.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I guess I should have specified that it's soft bricked, not hard bricked. Thanks for the help though, that seems to corroborate most of what I've read. I'll be flashing new firmware, was just hoping to save the data if I could but I knew it was unlikely.
Thanks again.
The_mamba said:
I guess I should have specified that it's soft bricked, not hard bricked. Thanks for the help though, that seems to corroborate most of what I've read. I'll be flashing new firmware, was just hoping to save the data if I could but I knew it was unlikely.
Thanks again.
Click to expand...
Click to collapse
Especially if it's soft brick sadly there's no way of pulling files off the phone.
Sent from my iPhone using Tapatalk
hyelton said:
Especially if it's soft brick sadly there's no way of pulling files off the phone.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Quick question again if you don't mind, and first let me say thanks a lot for the detailed thread about the tot method:
When I'm in device manager under ports I don't see LGE Modem, I just have LGE Mobile USB Port. LGE modem is actually under "modems". Which one should I change the port settings on?
Thanks again man
The_mamba said:
Quick question again if you don't mind, and first let me say thanks a lot for the detailed thread about the tot method:
When I'm in device manager under ports I don't see LGE Modem, I just have LGE Mobile USB Port. LGE modem is actually under "modems". Which one should I change the port settings on?
Thanks again man
Click to expand...
Click to collapse
As long as it's under commutation ports it's fine. It can differ sometimes.
Sent from my iPhone using Tapatalk
hyelton said:
As long as it's under commutation ports it's fine. It can differ sometimes.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So I want to modify "LGE Mobile USB Serial Port" right? Since that's the one under Com ports? "LGE Mobile USB Modem" is listed higher up under "modems", not under com ports.