Related
Hi,
I have Desire Z, that is dead, the only thing i can access is fastboot mode, yesterday i was able to enter "fastboot oem rebootRUU" and it seems to be ok, but today my phone frezzes every time to something i fastboot mode, og sends comands to it.
can som one help me, my phone is not rootet,
i have tried to flash recovery, but i'm not allowed, i need help, some ideas?
every i have put the P10IMG on Sd card, the phone starts to update, but it frezzes in the first step ( bootloader )
some info:
if you need more, just ask, and i wil provide it.
S-On
Hboot 0.85.0013
radio 26.10.04.03_m
( sorry for my bad english)
thirst thing i would try is to wipe cache...
so enter bootloader, choose recovery = a red triangle should show up then push power & volume up; select wipe cache and reboot
if this didn´t help do a foctory reset = same procedure as above only select factory reset in recovery...
...and remove the PC10IMG.zip from your sdcard so you can enter recovery
I have tried that, but the bootloader, frezzes, and the phone shuts down, and vibrates many times, then its dead again.
every thing i do in bootloader, results in a frezz, and i must start over again.
hm.. not good
another thing you could try is to enter usb fastboot mode (power & tp) connect your phone to pc and then start the ruu (.exe) on pc and maybe it does the update..
after it´s done enter recovery and wipe...
be sure that the ruu is higher or the same like the one previously installed and that it is the right one (asia, europe, bell, ...)
you can´t flash a recovery or anything trough fastboot if you do not have eng hboot or a rooted phone
EDIT: or when you in fastboot mode start cmd.exe go to your tools and type "fastboot oem boot" - maybe you are lucky
When i start the update it stops at the first step ( bootloader ) and its the same version, so it starts, but stops right away.
when i but it in recovery mode, the phone just vibrates a lot, and shuts down.
is there away to install a custom boot, or maybe root the phone now? nothing seems to work.. please help me..
every time i type somthing in cmd, it states to many links as an error. when i type "fastboot oem rebootRUU" the answer is "to many links"
sry, but i think there is not much you can do anymore...
maybe someone else knows better
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...
Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).
I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?
Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.
That's the bootloader. What procedure are you using for fastboot?
Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere
You cannot run a RUU from adb. Only fastboot.
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.
Have you tried booting into bootloader and choosing fastboot before trying the RUU?
Yep. Same USB connection error despite having 'FASTBOOT USB' showing....
Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?
Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!
Hello,
Is any chance to repair by RIFF JTAG with this phone:
I was doing root in my Desire z (vision) and i had few problems during this operation like:
1. I had "Potential exploit area found at address fbb9b200:e00" instead of "fbb4d600:a00"
2. After command "/data/local/tmp/rage" I had "Forked 2830 childs" (or something similar" instead of "Forked @##$%# childs" but i was stupid and i go forward
3. After command"/data/local/tmp/root sync" my phone stuck and i pull out battery
4. When I turned on phone after this operation it stuck on htc logo, in bootloader i saw that it was S-Off already
5. I tried flash recovery.img by fastboot but i had answer "failed"
6. Next i tried unroot and i flashed stock rom by PC10IMG in bootloader to come back to stock
7. I saw error "FAIL-PU" on bootloader, recovery, radio etc all FAIL-PU
8. I knew that something its wrong so i tried everthing include few commands: fastboot oem reinit_nand, fastboot oem rebootRUU, fastboot erase system, fastboot erase userdata"
9. This commands led to total brick and after this i cant turn on phone
i cant go to bootloader nothing only blackscreen even after POWER+VOL DOWN
When i connect to charger, light orange diod
When i press POWER+VOL UP starting few vibrations.
What do You thing about this, what i can to do?
Being it doesn't sound like any hardware issue JTAG should work fine, and as of Noe this would be the only that would fix this
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
I gave this desire z to a service. They didn't fixed it and told me that they think that processor is broken on 98% in they opinion...
What do You think about it? Is it possible to destroy processor during root in my case? I described everything what i did Should i try with another service?
Can you boot to recovery, and see if it throws any error messages there?
-Nipqer
Nipqer said:
Can you boot to recovery, and see if it throws any error messages there?
-Nipqer
Click to expand...
Click to collapse
No way. I cannot boot phone at all.
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
573v3 said:
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
Click to expand...
Click to collapse
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
MWGiants said:
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
Click to expand...
Click to collapse
congrats. it is good to know it is fixable
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Hakem said:
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Click to expand...
Click to collapse
Fastboot boot laf.img
But beware this doesnt work for D855. His LS980 has a unlocked bootloader
Ok thanks
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
bikrame said:
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
Click to expand...
Click to collapse
Hi, sorry for the late reply. I hope you've already fixed it, but if you're still having this problem then let me explain. "laf.img" is the "download mode" partition. The reason you can't use twrp.img (which is a recovery partition image) is because you're "too far gone" so to speak and not even at the point to try and get into recovery. You need to restore download mode first. If you have fastboot properly working (not going to explain that, look it up, there is plenty of info about that on here and other sites), then you can do what I did. (Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work, I cant tell you about that because I don't have one and haven't played around with one). Anyway, if you have fastboot working properly (read my first post about how it can be working as long as the phone is responsive, even if you don't get back the "devices comman", you may need to play around with the drivers to get this to work) then you need to obtain an laf.img from somwhere. I found a complete set of .img's for my model somewhere (don't remember if it was on this site or somewhere else). It took a lot of searching, but I'm sure you can find one. Once you have that and the working fastboot then run the command "fastboot boot [location of your laf.img]laf.img"
GOOD LUCK!!!
itsbighead said:
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's interesting...do you have any idea why that would be? Is it a locked bootloader like someone else mentioned? (I don't know much about the D855 model, never got to play with one). Maybe there is a workaround we can come up with...
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
I realized the problem with the mismatched aboot after the fact... ironically it all worked out because after all of this I am now back to the original kitkat and can just root and flash as you said lol.
Complete Fix Guide
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Can you please post where you got your laf file? I have the same problem :crying:
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
can you please help. adb shows my device and fastboot wont. when i type in fastboot devices it doesnt show anything. tried to run commands but it always gets stuck on waiting for device..
MWGiants said:
(Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work,
Click to expand...
Click to collapse
What to do with D855 than, my friend have D855 and it's stcked in fastboot mode, doesn't allow to flash anything?
lg g3 f410 stuck at fastboot
i tried the solution it didnot work. phone accepts the cmds but remain stuck at fastboot any other method?