Related
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
androidnj7 said:
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
Click to expand...
Click to collapse
At any point can you get it to answer
Fastboot devices
?
dottat said:
At any point can you get it to answer
Fastboot devices
?
Click to expand...
Click to collapse
I can not get it to receive any signals from me in the bootloader as it shuts down immediately. I tried connecting it to my computer for use with adb, but fastboot WAS enabled and developer tools were DISABLED (i think), plus it cannot keep a constant connection, so that wasn't working.
After doing some research I think I can save it IF I can get it to a stable state from the one it is currently in, and then using the bootloader screen to do a factory reset ( or use
"adb reboot recovery"), but like I said that is depenednet on getting it to stop the boot loop.
I also tried doing something called an RUU (I have limited knowledge of this, i sued the dottat one), but since it cannot establish a constant connection, it did not work.
Im open to any suggestions at this point! Thanks
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
androidnj7 said:
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
Click to expand...
Click to collapse
Possibly. What does the device show up as in device manager?
dottat said:
Possibly. What does the device show up as in device manager?
Click to expand...
Click to collapse
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
androidnj7 said:
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
Click to expand...
Click to collapse
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
dottat said:
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
Click to expand...
Click to collapse
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
androidnj7 said:
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
Click to expand...
Click to collapse
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
dottat said:
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
Click to expand...
Click to collapse
You are right unfortunately, I can absolutley not stay in the bootloader with any sort of stability. I read on another thread that opening it up and disconnecting the battery from the motherboard would help, so thats what I did. As soon as I sealed it back up, the reboot-loop started right up again. My guess is that the motherboard is fried, its either that or the battery is holding no charge whatsoever.
If the board is fried, im done right?
if its the battery, is there any way to manually charge not going through the board?
Thanks for all your help btw!
My wife started her Kindle Fire HDX 7” 5 days ago it took a while thinking and then went to the Fastboot screen. The device has not been rooted and is just a straight forward Kindle Fire HDX.
I tried restarting the Kindle etc. but every time it still only boots up to Fastboot screen, I connected the Kindle up to my PC's while I can not see any files on it, I can see the device.
Is there any way I can fix it or does she have a expensive paper weight?
Need more info
hilsdon1 said:
My wife started her Kindle Fire HDX 7” 5 days ago it took a while thinking and then went to the Fastboot screen. The device has not been rooted and is just a straight forward Kindle Fire HDX.
I tried restarting the Kindle etc. but every time it still only boots up to Fastboot screen, I connected the Kindle up to my PC's while I can not see any files on it, I can see the device.
Is there any way I can fix it or does she have a expensive paper weight?
Click to expand...
Click to collapse
Have you tried getting into recovery by holding down the Power and VolumeUp(+) buttons together?
draxie said:
Have you tried getting into recovery by holding down the Power and VolumeUp(+) buttons together?
Click to expand...
Click to collapse
Yes tried this still only boots to fast boot screen?
Try this: http://forum.xda-developers.com/showpost.php?p=58270390&postcount=4
EncryptedCurse said:
Try this: http://forum.xda-developers.com/showpost.php?p=58270390&postcount=4
Click to expand...
Click to collapse
Thanks for this it did not work but came close.
The first command fastboot -i 0x1949 oem idme bootmode 4000 comes back with a message on the Kindle and the CMD screen, as:-
Fail: oem idme not allowed for locked HW.
The second command fastboot -i 0x1949 reboot
reboots the Kindle back to fastboot menu.
Scary... but probably a timing issue only
hilsdon1 said:
Yes tried this still only boots to fast boot screen?
Click to expand...
Click to collapse
Try a few more times and do it "carefully" !
Seriously: last weekend I was messing around with the 4.5.2 kernel (boots, adb works, but no screen),
and at some point during my endevaours I got into this same scary situation, but I managed to get back to TWRP
after a few tries. I think it could be a timing issue. Easy to get confused when stressed...
So, here's my suggesttion:
Hold the Power button until the unit switches off.
Then hold Power + VolumeUp until the display lights up.
Let go off the buttons.
With some luck your recovery will show up.. keeping fingers crossed!
Thanks for the reply, have tried over 30 times still no luck. Will carry on trying.
Hate that white kindle fire logo! Especially as of all our machines this was the only untouched one. All the others have been tweeked or rooted I was not allowed to touch this one!
Oh well pretty paper weight.
hilsdon1 said:
Thanks for the reply, have tried over 30 times still no luck. Will carry on trying.
Hate that white kindle fire logo! Especially as of all our machines this was the only untouched one. All the others have been tweeked or rooted I was not allowed to touch this one!
Oh well pretty paper weight.
Click to expand...
Click to collapse
Have you tried Amazon's customer service?
They tend to be fairly helpful and your device was not even tampered with, you say...
I'd be interested to hear what they have to say.
A replacement would be a likely option..
draxie said:
Have you tried Amazon's customer service?
They tend to be fairly helpful and your device was not even tampered with, you say...
I'd be interested to hear what they have to say.
A replacement would be a likely option..
Click to expand...
Click to collapse
Actually, having read through the fastboot source code, I think I may have found another solution
using the "fastboot -i 0x1949 update magic.zip" command, where you' ll need to get a pristine
boot.img and system.img from a working Kindle and zip those along with an android-info.txt file
to create magic.zip... (I'll post more details, if needed, when I have time; now, off to bed.!)
Interestingly, the "update" command is NOT blocked on my otherwise locked HDX 8.9!
I'd expect signature checking (if not at flash time, then at boot time); so, be careful what
you put in your zip file.
Thanks everyone for help and advice in the end the device had to be replaced. One thing I learnt was to hold the power button down for 40 seconds and then press power button and + button. Amazon support gave me that one. To do factory reset.
However even after that it started up but to Encryption failed screen do factory reset, even after factory reset would go no further
Robert
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Why you did that? You can't update rooted phone
Idiocrate said:
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Click to expand...
Click to collapse
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
piskr said:
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
Click to expand...
Click to collapse
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
james194zt said:
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
Click to expand...
Click to collapse
ok I'm looking for a solution for hours now... so I just lokked how works our phone and I think the trouble must be in the preloader, because I can't even make my phone being recognized by any computer and I can't access to recovery.
I found this :
http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/
Which could help. I'll leave that topic on for some days (if it could help someone) and I'll open a new one to know if there is any easier solution ! thanks and good luck.
I sorted mine, it was only 2 days old so I got it replaced by the shop I bought it on. I would say it was something like a pre loader from what I saw. I have never bricked an Android phone and I must have had 15-20 of them since my first HTC Magic and before that Windows Mobile which again I messed with tons reloading with all sorts of ROM's!! These phones are wayyyy too sensitive to being messed with, I always remember though that you never mess with the boot loaders, but it looks like these updates do to get it bricked to that point.
Idiocrate said:
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
Click to expand...
Click to collapse
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
piskr said:
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
Click to expand...
Click to collapse
Euuum..... maybe yes ? I used fastboot but I don't think it really matters now, there's nothing working on it. And I've sometimes hold the buttons for 30-40 second while praying lol
korenisko said:
Why you did that? You can't update rooted phone
Click to expand...
Click to collapse
local update
I just hard bricked my Honor 7 the same way. Is there really no solution? Other China-Phones are pretty much unbrickable, since you can always fix it via the preloader. No such luck here? Back to the shop and hope they actually replace it? While I admit it was stupid to just hastily start the OTA while having twrp and not stock recovery (no root, though), this is a terrible design flaw on Huaweis side.
Anyway... any hope or no chance?
i just hard bricked my honor 7 PLK-L01
it the same thing it is doing . not recognized by the computer
tried all the combination of buttons. but no hope
and it only vibrates when tried to turn on
Need urgent help please
@Idiocrate try to boot into bootloader mode just by pressing Vol DOWN button and simultaneously connecting it to a PC, don't press Power button, if it boots into it, then follow the method given by @piskr in third post.
I know this has probably been covered to death in various posts here but I have tried a lot of what is written here and haven't been able to fix my hdx. I am currently stuck in a fastboot loop. Though sometimes it boots into bulk mode, which is strange, but I can get it back into fastboot eventually. Anyone out there able to walk me through steps to figure out what I did and get it back to working, preferably with TWRP and Lineage OS installed. I will just take getting back in to Fire OS atm sine this is giving me a headache. Anyway, I am using a win 10 machine and have fastboot ready on the KF right now. I am going to leave it this way for the time being. I originally used this https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240 to go about getting this to where I could install a custom ROM but missed the adb composite drivers before I ran the unlock.bat. I have since gotten that straightened out and even ran the unlock.bat and it succeeded. I have reflashed recovery.img and a boot.img though it isn't the right one. (I was desperate and tried some dumb stuff and flashed the boot.img from my lineage os zip via fastboot)(yeah I know, stupid, but like I said, desperate)
Enough rambling for now. Anyway think they can help me with this issue? @draxie maybe? or @Davey126.
Please and thank you!
FumundaSaq said:
I know this has probably been covered to death in various posts here but I have tried a lot of what is written here and haven't been able to fix my hdx. I am currently stuck in a fastboot loop. Though sometimes it boots into bulk mode, which is strange, but I can get it back into fastboot eventually. Anyone out there able to walk me through steps to figure out what I did and get it back to working, preferably with TWRP and Lineage OS installed. I will just take getting back in to Fire OS atm sine this is giving me a headache. Anyway, I am using a win 10 machine and have fastboot ready on the KF right now. I am going to leave it this way for the time being. I originally used this https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240 to go about getting this to where I could install a custom ROM but missed the adb composite drivers before I ran the unlock.bat. I have since gotten that straightened out and even ran the unlock.bat and it succeeded. I have reflashed recovery.img and a boot.img though it isn't the right one. (I was desperate and tried some dumb stuff and flashed the boot.img from my lineage os zip via fastboot)(yeah I know, stupid, but like I said, desperate)
Enough rambling for now. Anyway think they can help me with this issue? @draxie maybe? or @Davey126.
Please and thank you!
Click to expand...
Click to collapse
Above my pay-grade upon learning you flashed the LineageOS boot.img. Most likely will need to fix this (if repairable) from bulk mode. I believe @draxie is the only one with sufficient knowledge to take this on; also know he's usually quite busy.
Davey126 said:
Above my pay-grade upon learning you flashed the LineageOS boot.img. Most likely will need to fix this (if repairable) from bulk mode. I believe @draxie is the only one with sufficient knowledge to take this on; also know he's usually quite busy.
Click to expand...
Click to collapse
Thanks anyway. I know i screwed it up pretty badly but hoping since i can still get into fastboot and bulk mode that maybe it's still salvageable. Not holding my breath at this point. Thanks again
You should be fine
FumundaSaq said:
Thanks anyway. I know i screwed it up pretty badly but hoping since i can still get into fastboot and bulk mode that maybe it's still salvageable. Not holding my breath at this point. Thanks again
Click to expand...
Click to collapse
As long as your HDX responds to fastboot commands as expected,
your desired outcome should be achievable. Now, since you got
desperate and did a bunch of random stuff, let's start with checking
if that HDX is unlocked. (I suspect it isn't, otherwise that boot.img
from Lineage should just work.)
Code:
fastboot -i 0x1949 oem idme \?
Next, if it were still locked, do you have the unlock code?
If so, try to unlock, and if that works, see if that fixes booting.
Code:
fastboot -i 0x1949 flash unlock unlock.code
If the unlock fails or you're still having problems after a successful
unlock, I'd need to get some clarity regarding that bulk mode you
mention. Since it's -apperently- entered spontaneously (is it?) and
appears to be recoverable without too much effort(correct?), I'd
expect this to be the Sahara-style serial communication bulk mode,
and not the one that exposes all partitions to the host OS (you'd know,
since the latter generates a ton of dialogs asking to format those).
What cable (or cables) are you using? That serial bulk mode can be
consistently entered with a fastboot cable, but I find the kind of
intermittent triggering you describe rather strange...
Ok. First of, thanks @draxie for helping. Second i am including the pic i took of the txt on hdx screen after input of both commands. I honestly don't know what i am looking for so i will let you see it and tell me.
As for the bulk mode, it is the mode that produces the 8 or 9 drives in Windows(and Linux). The intermittent part is that sometimes it isn't recognized correctly by Windows. Sometimes it is recognized as the qloader 9008 like it should be. Sometimes Windows says it is an unrecognized usb device.
Hopefully that makes sense.
FumundaSaq said:
Ok. First of, thanks @draxie for helping. Second i am including the pic i took of the txt on hdx screen after input of both commands. I honestly don't know what i am looking for so i will let you see it and tell me.
As for the bulk mode, it is the mode that produces the 8 or 9 drives in Windows(and Linux). The intermittent part is that sometimes it isn't recognized correctly by Windows. Sometimes it is recognized as the qloader 9008 like it should be. Sometimes Windows says it is an unrecognized usb device.
Hopefully that makes sense.
Click to expand...
Click to collapse
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
draxie said:
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
Click to expand...
Click to collapse
@draxie - keep in mind he can boot a suitable twrp image from fastboot if the bootloader is unlocked. Might provide an expedited path to a bootable system partition.
draxie said:
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
Click to expand...
Click to collapse
Holding volume up and power just gets me back into fastboot. As for the sometimes boots into bulk mode, i didn't really mean spontaneous just that there are times when i tried to force it into bulk mode that Windows sar it only as unrecognized usb device and other times Windows sees it correctly. It only attempted bulk mode when i tried to put it there. Sorry for the misunderstanding. I'm new to this bulk mode thing.
If i remember, i put it into bulk mode using the commands
Fastboot -i 0x1949 erase aboot
Fastboot -i 0x1949 reboot
I probably messed up something doing that so feel free to berate me for that
I will follow whatever instructions you have. I really appreciate the help.
@draxie Just tested the volume up + power again and booted into twrp! Not sure why it never did before. Maybe I am just an idiot or didn't wait long enough. I did reboot with vol up and power but got a grey kindle logo and then nothing. Connected it to my pc and tried adb devices and there was one. The SN was strange, it read 0123456789abcd which obviously isn't correct. But I sent the command adb reboot recovery and then let it shut off, held the vol up and power and now I'm in twrp!
I sideloaded Lineage os and gapps now. It is working! Thanks for the help!!! Not sure what I was doing wrong before but I appreciate your guidance. Thanks to both @draxie and @Davey126 for bearing with me. You guys have the patience of Saints!
FumundaSaq said:
I sideloaded Lineage os and gapps now. It is working! Thanks for the help!!! Not sure what I was doing wrong before but I appreciate your guidance. Thanks to both @draxie and @Davey126 for bearing with me. You guys have the patience of Saints!
Click to expand...
Click to collapse
I'm still confused by your story, but I'm glad it worked in the end.
draxie said:
I'm still confused by your story, but I'm glad it worked in the end.
Click to expand...
Click to collapse
I realize that you probably are. For all I know it would have worked to begin with. I don't know what happened. I'm just strange that way.
If you have a specific question I would be glad to try to answer it.
FumundaSaq said:
Holding volume up and power just gets me back into fastboot. As for the sometimes boots into bulk mode, i didn't really mean spontaneous just that there are times when i tried to force it into bulk mode that Windows sar it only as unrecognized usb device and other times Windows sees it correctly. It only attempted bulk mode when i tried to put it there. Sorry for the misunderstanding. I'm new to this bulk mode thing.
If i remember, i put it into bulk mode using the commands
Fastboot -i 0x1949 erase aboot
Fastboot -i 0x1949 reboot
I probably messed up something doing that so feel free to berate me for that
I will follow whatever instructions you have. I really appreciate the help.
@draxie Just tested the volume up + power again and booted into twrp! Not sure why it never did before. Maybe I am just an idiot or didn't wait long enough. I did reboot with vol up and power but got a grey kindle logo and then nothing. Connected it to my pc and tried adb devices and there was one. The SN was strange, it read 0123456789abcd which obviously isn't correct. But I sent the command adb reboot recovery and then let it shut off, held the vol up and power and now I'm in twrp!
Click to expand...
Click to collapse
I, too, am stuck in fastboot mode after I seemingly flashed TWRP and aboot. Could you elaborate what you did to fix the issue? I held power button + Vol UP and no TWRP mode, just goes back to fastboot...I think my issue is I forgot to run get_code.bat before erasing aboot, and now I can't unlock nor boot into the stock ROM. Is there anyway to unlock through just fastboot or even restore the stock ROM? I don't mind reloading and going through the process all over again.
This was the thread I was following: https://forum.xda-developers.com/ki...loader-firmware-t3463982/page106#post76073370
Praxxer1 said:
I, too, am stuck in fastboot mode after I seemingly flashed TWRP and aboot. Could you elaborate what you did to fix the issue? I held power button + Vol UP and no TWRP mode, just goes back to fastboot...I think my issue is I forgot to run get_code.bat before erasing aboot, and now I can't unlock nor boot into the stock ROM. Is there anyway to unlock through just fastboot or even restore the stock ROM? I don't mind reloading and going through the process all over again.
This was the thread I was following: https://forum.xda-developers.com/ki...loader-firmware-t3463982/page106#post76073370
Click to expand...
Click to collapse
Cross post - answered in other thread.
Hello dear all,
I have managed to brick my LG G5 like an Old Mill Brick.
My LG G5 (lg g5 h850 titan) does not boot. It comes with an error message as follows: Your device is corrupt. It cannot be trusted and will not boot.
What I already did to Unbrick:
Tried to unlock the OEM. No way from USB Debugging as I cannot go into OS.
Tried unlock the OEM from fastboot (remote: oem unlock is not allowed).
Tried to flash some things like (boot.img, system.img) even adb sideload stuff. Nothing works. I cannot flash anything because (flashing not allowed) because OEM is not unlocked, but cannot unlock the OEM because it is not allowed. WHAT in the brick do I have to do now?
Cause of the brick of the bricks:
The LG G5 was on LineageOS, all stable and solid. When a prompt appeared telling me that I have to update the OS. So I was like yeah ok whatever. BUT, it did from OTA. I also had a specific LineageOS APP for updating the OS. After some minutes (updating) I immediately panic and started worrying. BECAUSE, I knew what time it was (my device is dead). I wanted to turn my phone off but it was already in Recovery (TWRP). So I just hit cancel. BUT after booting up the LG G5 that corrupt device error appeared and I cannot manage to get rid of it.
Please I need your help! I also watched and tried (2+ hours) to manage to solve this via Google and different links and Unbrick guides but nothing happens. I cannot unlock the OEM because it is not allowed. I cannot flash anystuff because the OEM is not unlocked.
Update: So, there is no Recovery System present. No stock Recovery, No TWRP. And I think no OS either. So only thing that is present is the bootloader screen smh.
Can you still get to TWRP?
firenemesis7 said:
Can you still get to TWRP?
Click to expand...
Click to collapse
No If I hold the volume down button and Power and when the LG Logo appears I release the power off and press again nothing happens. It goes again into that error. I can go in bootloader but can't do anything with adb or fastboot.
I think TWRP is gone too :/
You should be able to get into download mode. Hold the volume up button with phone fully powered down. While you hold the volume up button insert the usb cable. Then you can flash the full system kdz with LGUP
https://www.youtube.com/watch?v=_V7Mtd3eKzk
firenemesis7 said:
You should be able to get into download mode. Hold the volume up button with phone fully powered down. While you hold the volume up button insert the usb cable. Then you can flash the full system kdz with LGUP
https://www.youtube.com/watch?v=_V7Mtd3eKzk
Click to expand...
Click to collapse
Thank you very much! I didn't know I could do it in anotherway. Will definitely try this! Thanks again!