My wifi kinda stopped working,so i restarted the phone. When the phone restarted it got stuck on bootloader and i cant move past it. I tried normal powerup,recovery all of which led to bootloader menu again and again with the same error "hab check failed,failed to validate boot image".
I tried flashing it with fastboot following this tutorial http://forum.xda-developers.com/showthread.php?p=52772182#post52772182
To know the android version i typed this command {mfastboot getvar ro.build.version.full} for which i got this {Blur_Version.23.201.3.condor_retaildsds.retaildsdsall.en.03}
so i downloaded this firmware {XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml} the one which i could get.
then i ran those commands,heres the screenshot of those commands and the errors i got:
https://postimg.org/image/gmtygv2ab/
https://postimg.org/image/bpwtxvlvx/
the only thing i havent treid is unlocking the bootloader and then flashing it.Should i try that?
This problem has occured once in the past but then i took the phone to motorola service center and they fixed it.I dont want to waste any more money on his phone.
khiladi_786 said:
My wifi kinda stopped working,so i restarted the phone. When the phone restarted it got stuck on bootloader and i cant move past it. I tried normal powerup,recovery all of which led to bootloader menu again and again with the same error "hab check failed,failed to validate boot image".
I tried flashing it with fastboot following this tutorial http://forum.xda-developers.com/showthread.php?p=52772182#post52772182
To know the android version i typed this command {mfastboot getvar ro.build.version.full} for which i got this {Blur_Version.23.201.3.condor_retaildsds.retaildsdsall.en.03}
so i downloaded this firmware {XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml} the one which i could get.
then i ran those commands,heres the screenshot of those commands and the errors i got:
https://postimg.org/image/gmtygv2ab/
https://postimg.org/image/bpwtxvlvx/
the only thing i havent treid is unlocking the bootloader and then flashing it.Should i try that?
This problem has occured once in the past but then i took the phone to motorola service center and they fixed it.I dont want to waste any more money on his phone.
Click to expand...
Click to collapse
Since no one has replied yet, I unlocked my bootloader and then tried flashing the phone.
Every command got executed except this one "mfastboot flash partition gpt.bin".Please help me i m begging. I m so close to fixing my phone.
khiladi_786 said:
Since no one has replied yet, I unlocked my bootloader and then tried flashing the phone.
Every command got executed except this one "mfastboot flash partition gpt.bin".Please help me i m begging. I m so close to fixing my phone.
Click to expand...
Click to collapse
Don't run the commands manually, use the .Bat file.
Might work
Related
Hi everyone! As stated in the title my phone(p769) wont boot completely, I was in the middle of doing the bootloader unlock when I accidecntly replaced the bin during the root process of it with the wrong bin. Instead of replacing it with the v6 tmobile usa one I used the v5 canadian one. Now when I boot my phone up the lg screen is there and then eventually it just hits an android with a red exclamation point. I've tried Re-flashing while its in s/w upgrade mode with the flasher set to emergency, and Ive tried pressing the home button + vol down + power to no avail(it goes through the process but the same thing happens)
Any help at all would be greatly appreciated and many thanks in advance!
Edit: Also when I try to reflash, it just says it cant communicate with my phone. Ive uninstalled and reinstalled the drivers several times but seeing as how I cant acutally get into the phone Im not sure what else to do.
Edit 2: So ive been trying do something witht his for the past three hours and I cant get anywhere with it. I cant get the phone to show up as an adb device while its in s/w upgrade mode, and at the red exclamation point screenit shows up but as recovery and the lg tools fail to communicate with it. I would really appreciate if anyone knew how to deal with this.
Just in case anyone stumbles upon this and has the same issue I would like to say that i finally got mine fixed.
It has been a long day of frustrations but I finally got it there with the help of some awesome tutorials.
In order to fix it I had to fastboot my phone and flash the default loader and boot then my device would show up in my adb devices and I could sucessfully flash and root it.
hufger said:
Just in case anyone stumbles upon this and has the same issue I would like to say that i finally got mine fixed.
It has been a long day of frustrations but I finally got it there with the help of some awesome tutorials.
In order to fix it I had to fastboot my phone and flash the default loader and boot then my device would show up in my adb devices and I could sucessfully flash and root it.
Click to expand...
Click to collapse
how you resolve it?
saman_z1384 said:
how you resolve it?
Click to expand...
Click to collapse
I followed the fastboot tutorial and searched around in the help forum for people with similar issues and found a post where lelus posted both of the files I needed to flash with fastboot, from there I just put my phone in s/w upgrade mode and followed Lelus guide for root/flash
Well i have been looking all over for help with my phone. I have figured out that i tried to flash a rom without unlocking my bootloader. Well im running windows 8.1 and for some reason i couldnt get my computer to recognize the phone at all. After using 3 or 4 different guides i gave up for a few days so not to get too aggrivated. I mean its my own fault but my back up phone sucks lol. So i borrowed my wifes laptop running win 7. I Followed this guide androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html. For the first time since i started trying to solve my issue everything seemed to work got the s/w screen to appear in reverse and using the cmd prompt that says wiating for device then starting the .bat file from the download it says on the bat cmd prompt that everything worked. well at the bottom its says done then comes up with C:\fastboot\yours. i have been browsing google but i havent been able to find what i am supossed to do with the yours file. i tried putting a kdz file into the file location and running it from that but no luck. after a few min the phone auto reboots and comes back with the security error screen and not the backwards one. i have tried doing the hard reset at the point but no luck. if someone could please help with what i need to do with the fastboot/yours area that would be awesome. Or at least point me in the right direction cuz google isnt wanting to be my friend with the searches.
Android noob in training:
Sobih
help
Well i have tried several times now with using my wifes windows 7 laptop. i can get everything to work with the screen coming up backwards and in the command prompts it says that the fastboot is done then loads the command fastboot/yours which with the file i downloaded that file was empty. really unsure on what i need to do at this point. from the guides i have read it seems that im at like a step or 2 from getting the phone to work but after 30 seconds while still plugged in it reboots and loads the secruity error screen. from what i have read i should be able to do a factory reset by holding the volume and home button and then pressing the power for 3 seconds but it just reboots into the error. any help would be much appreciated i really dont want to have to buy a new phone.
Seems like that guide is more for when flashing a recovery on the locked bootloader and things go wrong. It was suggested a few posts down on the first page of that guide that if your problem happened when you were trying to flash a rom you might want to follow this : http://androidforums.com/optimus-l9-all-things-root/792689-guide-unbrick-manual-update-updated.html or http://forum.xda-developers.com/showthread.php?t=2085344 (the xda one seems more complete) .
sigh
Well im still stuck on the security error screen. i got the phone to boot into the backwards fastboot screen 1 time and cant remember how to do it again. i can boot into the s/w upgrade mode. if i go to use the lg support tool being that im in the united stats my options is upgrade recovery or help. well if i go to upgrade recovery im told that my phone has the latest upgrade already. if i try and use the moduptest that come in a lot of the unbricking guides it makes me turn the internet back on even with having hte shttps and everything else that is listed in the various folders. i only have the omap44 on my device manager 1 time but there is also 2 lg mobile modems. im thinking my issue lies with the fact thta i dont have the adb file for the device manager. i have donwloaded and uninstalled various times but still no luck. i dont remeber how i got the phone to the backwards fastboot but i remember i was following a guide and the op had to open one file and while that one was stuck on "waiting for device" he opened another one becasue that was the only way he could get it to connect. Any help would be awesome. not trying to rely on everyone else but after several weeks trial and error im at my wits end with it.
thanks
sobih
Here's how it started:
I was happily using the tablet (pollux_windy), when something prompted me to upgrade to 7.11 Lineage OS images. One of the things noteworthy here is that I was never able to go to recovery by pressing VOLUME_UP. I was always using adb to reboot to recovery
I installed it and used OpenGapps aroma installer to install what I wanted. I removed a few CM account related stuff
The tablet booted but was being stuck on the first screen on initial setup that displays a big LineageOS logo in green and there was no other option on it. I thought maybe the tablet is being slow and left it overnight to see if anything appears. Nope.. nothing did.
I tried a lot to go to recovery to reflash or flash something good. But as I mentioned before, I wasn't able to get into recovery by key combinations.
I tried to use Sony Companion to do a Software Repair. It kept complaining that bootloader was unlocked
I tried to use flashtool on mac to flash a stock FTF. It kept giving error (ERROR - null, ERROR - Error flashing. Aborted)
Since it looked like the only problem with using Sony Companion was that bootloader was unlocked. So I proceeded to lock the bootloader from flashtool. I believe this was where I messed up. I locked it successfully
I then proceeded to use software companion but it keeps giving me error with a small message about UEGetPhoneInfoFailure. I searched a few forum and posts but it seems that there's no solution for this (?)
I tried to unlock my bootloader again. I did it through the official method the first time and repeated it but fastboot write failed and it wasn't unlocked. Flashtool is not able to unlock it as well. Flashtool error is (Your phone bootloader cannot be officially unlocked)
I tried various versions of flashtool in MacOS and in Windows, trying to flash any FTF. I get a new error along with the one I mentioned above (-: Processing of loader.sin finished with errors)
I'm now typing this post
I'll appreciate if someone can help here.
I got this device when it first came out. I've loved it since now. It was an ace. It's not waterproof anymore because I did a few repairs on my own. But it worked flawlessly and battery life was great. I wouldn't mind saying goodbye to it as it's pretty old, but trying to revive it and have it living as it's cooler than a dead tablet
kishu27 said:
I'll appreciate if someone can help here.
Click to expand...
Click to collapse
Don't panic!
7.1.1 ROMs have some issues when reverting back to stock ROM.
Switch off device by holding VOL+Power for 5-7 sec, then read -> https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Rootk1t said:
Don't panic!
7.1.1 ROMs have some issues when reverting back to stock ROM.
Switch off device by holding VOL+Power for 5-7 sec, then read -> https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Click to expand...
Click to collapse
One thing I always practice and preach about Sony devices is not to panic .. Flash mode and Flashtool has saved my a** so many times.
So, thanks to you, I resolved the issue. I was doing the same thing but had a couple of pieces in the process that needed correction.
I let go of my Windows VM on Mac and prepped my old laptop fresh on Windows 10. Driver installation kept failing because of unsigned driver issue and bcdedit didn't do anything despite returning a success. Advanced startup worked. The second thing that might be wrong with my original attempt was the stock FTF version. 5.1.1 didn't work. I got hold of a german unbranded version on 4.1.2 and used it instead. Then reflashed to 5.1.1 and everything is golden.
Thanks again :good:
So I bought a Moto E XT1526 from FreedomPop for my parents. Been working great for over a month. Then not sure what happened, dad calls me and said it is not working anymore. The phone is stuck in AP Fastboot mode. Tried recovery and Factory reset but it just reboots back in to AP Fastboot mode.
Tried unlocking and get the error, ' Check ;Allow OEM Unlock' in Developer Options. Well....cant cuz phone doesn't boot up.
Tried reflashing to stock and get error, Failed (Remote failure).
Is it a brick now? Not sure how it got to this state as my parents are not techy at all and does not mess with settings. Thx for reading.
emanon1982 said:
So I bought a Moto E XT1526 from FreedomPop for my parents. Been working great for over a month. Then not sure what happened, dad calls me and said it is not working anymore. The phone is stuck in AP Fastboot mode. Tried recovery and Factory reset but it just reboots back in to AP Fastboot mode.
Tried unlocking and get the error, ' Check ;Allow OEM Unlock' in Developer Options. Well....cant cuz phone doesn't boot up.
Tried reflashing to stock and get error, Failed (Remote failure).
Is it a brick now? Not sure how it got to this state as my parents are not techy at all and does not mess with settings. Thx for reading.
Click to expand...
Click to collapse
If the device is being recognized by adb flashing stock firmware is probably your only chance of repairing it. It might not work if android debugging isn't turned on in developer settings. Try flashing only the recovery and system. I'm not sure what else to tell you.
Not sure, but probably an OTA killed it if the phone was running an older version and was being updated.
Try downloading the 'latest' stock Rom and try updating it again. You will have to do a little research on this, there is a step-wise flashing method, with erasing the partitions, try searching threads which specifically talk about unbricking, that should help.
please i need urgent help with my phone, it started about two weeks ago, i was using my phone and all of a sudden my phone just froze and then rebooted itself, i didn't know what to do so i ignored it and continued using my phone as usual, then after two to three days it happened again, i still didn't know what to do so i ignored it for the second time.
now my problem is that last week it happened again but while rebooting it got stuck at dm-verity corruption, your phone is corrupted and can not be trusted, i tried all i could to reboot it but it's not working,
i did some search on google to know what to do, i found this article on google but after trying it i found out that my device bootloader was locked and i can not unlock it except if the oem unlock toggle is on in the developer option in the phone. then i did some more research and found another article after downloading all the software required, i tried it but sp flash tool keeps saying ERROR: STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001).
i tried using wipe factory setting via recovery menu but it reboots and shows dm-verity error anytime i click it, please i need help.