Related
I am trying to update via .exe (cab sender) posted by SuperSport and it fails after finishing backup and restarting device:
Name: NOKIA Lumia 900
KITLName: ACE86B69AF3BE4D
Manufacturer: NOKIA
ModelId: 4
Model: Lumia 900
MobileOperator: 000-88
Version: 07.10.08107.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.01 seconds
Checking system requirements: Completed in 0.13 seconds
Downloading updates: Completed in 2.7 seconds
Checking system requirements: Completed in 0.01 seconds
Transferring updates: Completed in 1.04 seconds
Preparing to install: Completed in 6.01 seconds
Restarting your phone: Completed in 30.1 seconds
Creating a backup: Completed in 296.37 seconds
Checking your phone's status: Completed in 0 seconds
Restarting your phone: Completed in 31.4 seconds
Completing updates: Completed in 5.04 seconds
Error:
Update device 012bdf92 - f11f2be1 - 9b295831 - c35970e3 Complete with error code
: 80070013, error message: An unexpected error has occurred.
What may I do?
ankerael said:
I am trying to update via .exe (cab sender) posted by SuperSport and it fails after finishing backup and restarting device:
Name: NOKIA Lumia 900
KITLName: ACE86B69AF3BE4D
Manufacturer: NOKIA
ModelId: 4
Model: Lumia 900
MobileOperator: 000-88
Version: 07.10.08107.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.01 seconds
Checking system requirements: Completed in 0.13 seconds
Downloading updates: Completed in 2.7 seconds
Checking system requirements: Completed in 0.01 seconds
Transferring updates: Completed in 1.04 seconds
Preparing to install: Completed in 6.01 seconds
Restarting your phone: Completed in 30.1 seconds
Creating a backup: Completed in 296.37 seconds
Checking your phone's status: Completed in 0 seconds
Restarting your phone: Completed in 31.4 seconds
Completing updates: Completed in 5.04 seconds
Error:
Update device 012bdf92 - f11f2be1 - 9b295831 - c35970e3 Complete with error code
: 80070013, error message: An unexpected error has occurred.
What may I do?
Click to expand...
Click to collapse
SuperSport may suggest you do a hard reset after having done a backup first. Wait until he instructs you what to do.
ok so i have my play (r800x) unlocked and everything but i installed omnius and it gave me this log when i identified the phone
Code:
[code]
Action journal
17:09:32 Identify
17:09:32 Shows detailed information about the connected phone.
17:09:32 Operating system: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
17:09:32 Application version: 1.38.4753
17:09:32 . The action name is 'Identification'
17:09:32 Selected phone type: Xperia™ PLAY
17:09:32 Selected connection method: USB EROM
17:09:32 i Instructions
17:09:32 i 1. Make sure the phone battery is charged to at least 50%.
17:09:32 i 2. Switch off the phone!
17:09:32 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
17:09:32 i 4. Press and hold the return back button, then connect the cable to the phone!
17:09:32 . The action started waiting for the user
17:09:44 . The action finished waiting for the user
17:09:44 Connecting via SEMC USB Flash Device (USB1)...
17:09:44 Device driver version: 2.2.0.5
17:09:44 Detected chipset: MSM7X30
17:09:44 Boot mode: EROM
17:09:44 EROM version: 1241-3656 R9A021
17:09:44 IMEI: A100001713D1A9
17:09:45 Device ID: 65EE28BC0613A8CC0C72EE449ED67DF6ED81A858
17:09:45 Minimum loader AID: 0001
17:09:45 Color: Red SEMC
17:09:45 The phone is rooted.
17:09:45 i Unsigned flashing is disabled.
17:09:45 Sending loader...
17:09:45 Waiting for loader response...
17:09:47 Phone model (from TA): R800x
17:09:47 Current CXC (from TA): 1243-3001_3.0.1.E.0.88
17:09:47 Current CDA (from TA): 1245-4101_R91C
17:09:47 Current FS (from TA): VERIZON_3.0.1.E.0.88
17:09:47 i The phone is not locked to a network.
17:09:47 i Simlock origin: SEMC
17:09:47 s Successfully done.
17:09:47 . The action entered shutdown phase
17:09:47 . The action reported success
Additional details
---
2F B4 6E 69 5C EB 9C F5 36 FD 40 C1 3A DB D8 84
D9 94
---
[/CODE]
does this mean that my bootloader is still locked i'm wondering from line "17:09:45 i Unsigned flashing is disabled." or is it unlocked as i used fastboot and it erased the blocks from the bootloader and it completed successfully
Looks like it is unlocked.... Well at least to me it does.
Sent from my R800x
Lordomn said:
Looks like it is unlocked.... Well at least to me it does.
Sent from my R800x
Click to expand...
Click to collapse
ok thanks a whole bunch for your input but what about the unsigned flashing being disabled?
IF you wan't to check if your bootloader is unlocked, put the phone in fastboot mode and run "fastboot getvar secure"
what that does is check the device security
yes is locked
no is unlocked
As for the unsigned flashing disabled, in flash mode you can't flash anything not signed by SONY. fastboot will let you flash things though.
chevyowner said:
IF you wan't to check if your bootloader is unlocked, put the phone in fastboot mode and run "fastboot getvar secure"
what that does is check the device security
yes is locked
no is unlocked
As for the unsigned flashing disabled, in flash mode you can't flash anything not signed by SONY. fastboot will let you flash things though.
Click to expand...
Click to collapse
OK thanks so much as this is my first device other then the Samsung fascinate that I will flash kernels with so I'm just cautious as also this is my only phone
Sent from my GBTweaked v7.1 r800x using Tapatalk 2
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
zonda2323 said:
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
Click to expand...
Click to collapse
Try this. Take the battery out and then put it back and turn the phone on.
Are you on CWM 4? If yes, its a bug in that version. When you charge the phone while turned off, to turn it on you'll have to take the battery out and put it back in.
zonda2323 said:
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
Click to expand...
Click to collapse
Clear battery stats. Switch off the phone. Charge straight for 2.5-3 hrs. Disconnect the charger. Power on.
Sent from my Nexus 4
I'll chime here, as I do have the same problem...
lakshan_456 said:
Are you on CWM 4? If yes, its a bug in that version. When you charge the phone while turned off, to turn it on you'll have to take the battery out and put it back in.
Click to expand...
Click to collapse
I do have v2.5.0.1 --> also buggy?
What is your suggestion on ROM/CWM to avoid this kind of problems?
gobz said:
Clear battery stats. Switch off the phone. Charge straight for 2.5-3 hrs. Disconnect the charger. Power on.
Click to expand...
Click to collapse
Will this solve the problem permanently or do I have to repeat this everytime?
@OP: Have you solved the problem?
Thanks,
Guntram
Guntram said:
I'll chime here, as I do have the same problem...
I do have v2.5.0.1 --> also buggy?
What is your suggestion on ROM/CWM to avoid this kind of problems?
Thanks,
Guntram
Click to expand...
Click to collapse
I'd recommend this one,
http://forum.xda-developers.com/showthread.php?t=1014498
Cheers
lakshan_456 said:
I'd recommend this one,
http://forum.xda-developers.com/showthread.php?t=1014498
Cheers
Click to expand...
Click to collapse
I can't get it installed...tried the zip from the thread (with CWM-2.5) and
fastboot flash recovery ./recovery.img
The latter yields:
sending 'recovery' (3010 KB)...
OKAY [ 0.846s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.556s
Here (http://forum.xda-developers.com/showthread.php?t=2277112) they write about "unsigned" images...
Any ideas?
Guntram said:
I can't get it installed...tried the zip from the thread (with CWM-2.5) and
fastboot flash recovery ./recovery.img
The latter yields:
sending 'recovery' (3010 KB)...
OKAY [ 0.846s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.556s
Here (http://forum.xda-developers.com/showthread.php?t=2277112) they write about "unsigned" images...
Any ideas?
Click to expand...
Click to collapse
Did you try the PC49IMG.zip method? It's in the last page of that thread.
And, I'm not very acquainted with fastboot. Sorry...
Sent from my HTC Wildfire using Tapatalk 2
lakshan_456 said:
Did you try the PC49IMG.zip method? It's in the last page of that thread.
Click to expand...
Click to collapse
I downloaded the zip and flashed it via Recovery - but this seems to fail (I don't get any error message, but it simply doesn't succeed).
I also tried unrevoked3.
Do I miss something? My "active time" with the Wildfire was some years ago...
Guntram said:
I downloaded the zip and flashed it via Recovery - but this seems to fail (I don't get any error message, but it simply doesn't succeed).
I also tried unrevoked3.
Do I miss something? My "active time" with the Wildfire was some years ago...
Click to expand...
Click to collapse
The zip isn't flashed from recovery. The process is explained in the post which has the zip file attached. Please try following that instructions.
Sent from my HTC Wildfire using Tapatalk 2
lakshan_456 said:
The zip isn't flashed from recovery. The process is explained in the post which has the zip file attached. Please try following that instructions.
Click to expand...
Click to collapse
I always thought, the recovery-zip-installation would simulate the very same process. I tried this way, too.
However, this didn't work, either ;-(. I put it into SDCARD-root, chose Reboot into Bootloader -> there it seems to check the corresponding ZIP but no questioning to install it...
Maybe some problem of my HBOOT-version? I'm still on 0.8 (and couldn't find any update instructions, yet).
How did you install your recovery? The zip method was posted just at the end of the thread?
Guntram said:
I always thought, the recovery-zip-installation would simulate the very same process. I tried this way, too.
However, this didn't work, either ;-(. I put it into SDCARD-root, chose Reboot into Bootloader -> there it seems to check the corresponding ZIP but no questioning to install it...
Maybe some problem of my HBOOT-version? I'm still on 0.8 (and couldn't find any update instructions, yet).
How did you install your recovery? The zip method was posted just at the end of the thread?
Click to expand...
Click to collapse
Yes, I use the pc49.zip method.
And, yes. Maybe your hboot version is causing this. But I'm not familiar with these issues.
Maybe @heavy_metal_man can help you. As I know he has lot of knowledge regarding these than myself.
Sent from my HTC Wildfire using Tapatalk 2
zonda2323 said:
So my Wildfire was working fine but run out of charge, now when I put it on charge the notification led just flashes red and wont turn on the phone :crying:
Click to expand...
Click to collapse
does your phone power on at all? or just the red led flash. this is usually caused my the battery being fully depleted and the bootloader not having enough power to boot at all. if leaving it on charge for 24H+ does not fix the issue then either buy a new battery and/or a external wall charger like this one . you may need an adapter for the wall, depending where you live. This should not fail and in future be careful to never fully deplete your battery
Guntram said:
I always thought, the recovery-zip-installation would simulate the very same process. I tried this way, too.
However, this didn't work, either ;-(. I put it into SDCARD-root, chose Reboot into Bootloader -> there it seems to check the corresponding ZIP but no questioning to install it...
Maybe some problem of my HBOOT-version? I'm still on 0.8 (and couldn't find any update instructions, yet).
How did you install your recovery? The zip method was posted just at the end of the thread?
Click to expand...
Click to collapse
since you rooted your phone using unrevoked your hboots security was never deactivated, just bypassed temporarily. this means that if you know what your doing with root, you can flash a custom recovery but i dont recommend this as its a but outdated. i recommend you upgrade your hboot stock rom and radio using a RUU. then run the program revolutionary to remove the security on your bootloader. then fastboot and pc49img.zip methods will be available to you, so you can flash a more updated recovery without issue Since you have fastboot commands set up on your pc please issue the command
Code:
Fastboot getvar cid
for me and post the cid here. i will then have a look for you and see if i can find a ruu for you to upgrade easily
lakshan_456 said:
Yes, I use the pc49.zip method.
And, yes. Maybe your hboot version is causing this. But I'm not familiar with these issues.
Maybe @heavy_metal_man can help you. As I know he has lot of knowledge regarding these than myself.
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
cheers for the heads up
Hello heavy_metal_man and thanks for chiming in!
I have my phone always on a charger, but sometimes it seems to be shut down and remain unresponsive until I remove the battery. So I do rule out a battery issue (though not any other hardware issues ).
This happens sometimes(!) when I'm on charging (via computer USB) and simply shut down the phone. It becomes unresponsive, the red LED still glows and I have to remove the batter.
Trying to get a RUU with the HBOOT 1.00 included resulted in the following (using OpenRUU from http://forum.xda-developers.com/showthread.php?t=711298 and a RUU downloaded from http://forum.xda-developers.com/showthread.php?t=1275680, namely the first FROYO ROM, second download link) :
Code:
42turkeys presents...
____ _____ _ _ _ _
/ __ \ | __ \| | | | | | |
| | | |_ __ ___ _ __ | |__) | | | | | | | FASTBOOT
| | | | '_ \ / _ \ '_ \| _ /| | | | | | | FLASH
| |__| | |_) | __/ | | | | \ \| |__| | |__| | VERSION
\____/| .__/ \___|_| |_|_| \_\____/ \_____/
| |
|_| Version 1.1.2-LINUX
1. HTC GSM Hero
2. HTC Desire
3. HTC Tattoo
4. HTC CDMA Hero
5. HTC Legend
6. HTC Droid Incredible
7. HTC EVO 4G
8. Other
Please enter the corresponding number above: 8
WARNING! THE UPDATE PROCESS WILL ERASE ALL DATA, APPS & APP DATA ON YOUR DEVICE! (But not SDCard)
Please reboot your device into fastboot by turning your phone on holding power + back
When you see FASTBOOT USB on the screen press enter.
Press enter to Continue
If you see a device below then your device is ready to be updated and you have the correct drivers installed.
[sudo] password for guntram:
HT076PY02508 fastboot
If you could see your device above then you are ready to proceed.
If not, then you need to make sure that your device is connected in fastboot mode and that you have the drivers/HTC Sync installed.
Press enter to continue...
Fetching Current Device Info...
ROM Version:
version-main: 1.25.405.1
Press enter to continue...
Bootloader Version:
version-bootloader: 0.80.0007
Device:
product: buzz
Battery Status: (Must be good or better to proceed)
battery-status: good
OK to proceed? (Press enter)
Erasing Cache...
erasing 'cache'... OKAY
Done!
Rebooting in RUU mode...
... OKAY
Flashing ROM... DO NOT TOUCH YOUR DEVICE!
< waiting for device >
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
You may get an error message above (HBOOT Pre Update!) don't worry, this is normal.
Reflashing... DO NOT TOUCH YOUR DEVICE!
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
If you got another error message above, please run this script again.
If the process completed with no errors the second time, you have successfully updated/downgraded your ROM!
Press enter to continue...
Rebooting Device... (First boot will take a while)
[sudo] password for guntram:
rebooting...
OK to disconnect
Thanks for using OpenRUU! If you can, please donate so I can buy some hosting to implement some cool features...
Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=max%40maxmarroni%2eco%2euk&lc=GB&item_name=OpenRUU&no_note=1&no_shipping=1¤cy_code=GBP&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted
Have a nice day... :)
Press enter to exit.
This procedure also created a ROM.zip - may this be of any use? It seems to be not flashable via recovery.
The demanded cid: VODAP129
Thanks,
Guntram
heavy_metal_man said:
does your phone power on at all? or just the red led flash. this is usually caused my the battery being fully depleted and the bootloader not having enough power to boot at all. if leaving it on charge for 24H+ does not fix the issue then either buy a new battery and/or a external wall charger like this one . you may need an adapter for the wall, depending where you live. This should not fail and in future be careful to never fully deplete your battery
since you rooted your phone using unrevoked your hboots security was never deactivated, just bypassed temporarily. this means that if you know what your doing with root, you can flash a custom recovery but i dont recommend this as its a but outdated. i recommend you upgrade your hboot stock rom and radio using a RUU. then run the program revolutionary to remove the security on your bootloader. then fastboot and pc49img.zip methods will be available to you, so you can flash a more updated recovery without issue Since you have fastboot commands set up on your pc please issue the command
Code:
Fastboot getvar cid
for me and post the cid here. i will then have a look for you and see if i can find a ruu for you to upgrade easily
cheers for the heads up
Click to expand...
Click to collapse
Guntram said:
Hello heavy_metal_man and thanks for chiming in!
I have my phone always on a charger, but sometimes it seems to be shut down and remain unresponsive until I remove the battery. So I do rule out a battery issue (though not any other hardware issues ).
This happens sometimes(!) when I'm on charging (via computer USB) and simply shut down the phone. It becomes unresponsive, the red LED still glows and I have to remove the batter.
Trying to get a RUU with the HBOOT 1.00 included resulted in the following (using OpenRUU from http://forum.xda-developers.com/showthread.php?t=711298 and a RUU downloaded from http://forum.xda-developers.com/showthread.php?t=1275680, namely the first FROYO ROM, second download link) :
Code:
42turkeys presents...
____ _____ _ _ _ _
/ __ \ | __ \| | | | | | |
| | | |_ __ ___ _ __ | |__) | | | | | | | FASTBOOT
| | | | '_ \ / _ \ '_ \| _ /| | | | | | | FLASH
| |__| | |_) | __/ | | | | \ \| |__| | |__| | VERSION
\____/| .__/ \___|_| |_|_| \_\____/ \_____/
| |
|_| Version 1.1.2-LINUX
1. HTC GSM Hero
2. HTC Desire
3. HTC Tattoo
4. HTC CDMA Hero
5. HTC Legend
6. HTC Droid Incredible
7. HTC EVO 4G
8. Other
Please enter the corresponding number above: 8
WARNING! THE UPDATE PROCESS WILL ERASE ALL DATA, APPS & APP DATA ON YOUR DEVICE! (But not SDCard)
Please reboot your device into fastboot by turning your phone on holding power + back
When you see FASTBOOT USB on the screen press enter.
Press enter to Continue
If you see a device below then your device is ready to be updated and you have the correct drivers installed.
[sudo] password for guntram:
HT076PY02508 fastboot
If you could see your device above then you are ready to proceed.
If not, then you need to make sure that your device is connected in fastboot mode and that you have the drivers/HTC Sync installed.
Press enter to continue...
Fetching Current Device Info...
ROM Version:
version-main: 1.25.405.1
Press enter to continue...
Bootloader Version:
version-bootloader: 0.80.0007
Device:
product: buzz
Battery Status: (Must be good or better to proceed)
battery-status: good
OK to proceed? (Press enter)
Erasing Cache...
erasing 'cache'... OKAY
Done!
Rebooting in RUU mode...
... OKAY
Flashing ROM... DO NOT TOUCH YOUR DEVICE!
< waiting for device >
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
You may get an error message above (HBOOT Pre Update!) don't worry, this is normal.
Reflashing... DO NOT TOUCH YOUR DEVICE!
sending 'zip' (127911 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
If you got another error message above, please run this script again.
If the process completed with no errors the second time, you have successfully updated/downgraded your ROM!
Press enter to continue...
Rebooting Device... (First boot will take a while)
[sudo] password for guntram:
rebooting...
OK to disconnect
Thanks for using OpenRUU! If you can, please donate so I can buy some hosting to implement some cool features...
Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=max%40maxmarroni%2eco%2euk&lc=GB&item_name=OpenRUU&no_note=1&no_shipping=1¤cy_code=GBP&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted
Have a nice day... :)
Press enter to exit.
This procedure also created a ROM.zip - may this be of any use? It seems to be not flashable via recovery.
The demanded cid: VODAP129
Thanks,
Guntram
Click to expand...
Click to collapse
ok, im on the lookout for a RUU for you. can you upload the rom.zip from that program somewhere for me to download. im interested in what it has outputted. also, what hboot and recovery version are you on?
UPDATE: ok we are out of luck for an official update from vodaphone that has hboot 1.01.0001 as they upgraded straight to hboot 1.01.0002. but this is not the end
we can use a Goldcard to bypass the htc's check of the phone cid, allowing us to flash other carriers updates. as such we can flash a WWE (world wide english, unbranded) rom with the hboot we need.
follow this part of my guide
Code:
step 6. now we need to make a gold card. if you already have one, you can skip this part. first using your working android phone, download and install Goldcard helper from the android market. Run the app and copy down your sd cards reverse cid.
step 7. now go to this website [URL="http://huygens.hoxnet.com/goldcard.html"]here[/URL] and enter in your reverse cid. it will then let you download a goldcard.img.
step 8. now go back to our c:\adb\ folder and run the goldcardtool.exe, this will flash the goldcard to your sd card. Warning! this will format your card!!
step 9. once that is done we are now ready for the final push
once you have made a working goldcard then run the RUU in this download package all going well your device will flash the update. if it gives you the error 42, or 131 then the goldcard has failed.
once you have that ran and successfully then reboot and quick setup your phone and then run this tool called revolutionary as this will make your bootloader s-off
finally install this recovery here to fix the charging issue. place it onto the sdcard and allow the bootloader to flash the recovery
then its just install any custom rom you want pal
more info on revolutionary instructions here
Guntram said:
Bootloader Version:
version-bootloader: 0.80.0007
Click to expand...
Click to collapse
rom.zip is here:
https://www.dropbox.com/s/ttjpn8uw9drwtja/rom.zip
Guntram said:
rom.zip is here:
https://www.dropbox.com/s/ttjpn8uw9drwtja/rom.zip
Click to expand...
Click to collapse
turns out, i believe this is the same as you are downloading from me you will still need to have a goldcard functioning and the clickable ruu is more user friendly
heavy_metal_man said:
finally install this recovery here to fix the charging issue
Click to expand...
Click to collapse
Download link won't work .
Does this CWM involve the same "improvements" as the one from arco68 (http://forum.xda-developers.com/showthread.php?t=1014498)?
Guntram said:
Download link won't work .
Does this CWM involve the same "improvements" as the one from arco68 (http://forum.xda-developers.com/showthread.php?t=1014498)?
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip new link from source. All cwm Recovery's v.5 + up to some 6+ have the charging bug fixed.
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
once you have made a working goldcard then run the RUU in this download package all going well your device will flash the update.
Click to expand...
Click to collapse
I did this with the help of OpenRUU (no Windows here) and it (for the first time) installed the ROM. But my bootloader is still claims to be 0.80?
heavy_metal_man said:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip new link from source. All cwm Recovery's v.5 + up to some 6+ have the charging bug fixed.
Click to expand...
Click to collapse
You're awesome! Thanks!
Guntram said:
I did this with the help of OpenRUU (no Windows here) and it (for the first time) installed the ROM. But my bootloader is still claims to be 0.80?
You're awesome! Thanks!
Click to expand...
Click to collapse
Are you sure it installed the rom? The rom.zip that you linked to me earlier, rename it to PC49IMG.zip and put it onto the root of your SD card. Them boot into the bootloader and let it pick it up. If it asks you to flash it say yes, if it does not then your goldcard has failed.
Sent from my Nexus 7 using Tapatalk 4
So, long story short - I hard bricked my phone by trying to flash .bin files when they should have been .img files (rookie mistake). Anyways, once i flashed those the screen went black and the phone would not respond to anything. When i plugged the phone in it showed up as Qualcomm 9008 blah blah blah so i followed this method: http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853. I was able to flash some of my partitions but then suddenly the screen changed to this:
http://i.imgur.com/G0n16LP.jpg
I believe it was after flashing tz. Regardless, I could not flash any more partitions.
So i plugged in my battery and reconnected it to my computer and it shows up as this: http://i.imgur.com/zRKaNZC.jpg. For those who can't see it it shows up as LGE AndroidNet USB Serial Port. It also shows up as LGE AndroidNet USB Modem. Any idea on how to fix my phone from this? I've installed the Qualcomm Drivers as well as the ADB universal drivers and the LG Drivers for my phone. Using LG Mobile Support Tool the flashing goes until it says it can't connect to the phone. QPST can't see it, LG Flash Tool gives me "Model Information Check Fail" and any KDZ Flashing tool can not flash it.
I heard talk about shorting capacitors to put it into 9006 mode in order to see the partitions. Does anyone know which capacitors?
Any help would be great considering there is not a whole lot of (free) information out there on this.
Click to expand...
Click to collapse
So I fixed my phone. For everyone wondering how to do it follow this thread: http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091.
If you're stuck in the serial mode you have to short the pins on your emmc. Short then pins as described in the above thread and then plug your usb in. Then follow the steps in the thread and flash.
Man I'm in the same boat as you. I couldn't get the Qualcomm tool to work though.
Nothing seems to be working at the moment and neither flashtool or anything else seem to be finding my device.
I'd like to avoid sending it to LG if I can as I need this phone.
Have you had any luck at all?
Look's like your phone diag port. May need your msl/spc to get qualcomm tool to work.
fergie716 said:
How to Get your MSL/SPC
**NOTE** This will only work if your phone is able to turn on
Make sure you have the LG Drivers Installed on your computer (link is in 1st post for that)
Open up your dialer and enter ##DIAG#
Enable DIAG Mode
Connect your phone to your computer
On your phone change the USB Connection type to Charge Only (pull down your statusbar and click on USB Connected)
Download CdmaDevTerm on your computer(I prefer this version)
Extract the CdmaDevTermZip
Inside the extracted folder double click on the cdmaTerm file to start the application
On the right hand side of the CdmaDevTerm screen select "Scan ports"
Next select the LGE AndroidNet USB Serial Port from the drop down menu (mine was COM6) then click Connect
In the SPC/Lock Options change NV to LG from the drop down menu
Now click Read SPC
Success!
Click to expand...
Click to collapse
This looks like your phone is charging, that might mean your boot or aboot partitions are ok. Or maybe recovery, i'm not sure which one is used for phone off charging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jcfunk said:
Look's like your phone diag port. May need your msl/spc to get qualcomm tool to work.
This looks like your phone is charging, that might mean your boot or aboot partitions are ok. Or maybe recovery, i'm not sure which one is used for phone off charging.
Click to expand...
Click to collapse
I connected to it (I think) and got the spc number but it doesn't show up in the qualcomm tool/ i don't know what to do with the number haha.
jfedorchuk said:
I connected to it (I think) and got the spc number but it doesn't show up in the qualcomm tool/ i don't know what to do with the number haha.
Click to expand...
Click to collapse
Qualcomm tool, do you mean qpst?
if so you need to add port to server configuration tool. Or maybe try CDMAworkshop.
Have you tried volume + and USB insert?
maybe download or fastboot mode will start
jcfunk said:
Qualcomm tool, do you mean qpst?
if so you need to add port to server configuration tool. Or maybe try CDMAworkshop.
Have you tried volume + and USB insert?
maybe download or fastboot mode will start
Click to expand...
Click to collapse
Ya the qpst. I looked and the port doesn't show up as a phone. It just shows up as the serial port and won't allow me to connect. I'll look for the cdmaworkshop tool though. I'm probably going to just try to short the capactitors to get it into 9006 mode and reflash the partitions. Does anyone know where the specific capacitors are? There was a youtube video of it but the owner flipped out and made it private.... so much for advancing the community.
I tried the volume up and insert but nothing shows up. I'm curious if this were to go in for warranty if the company to fix it would be able to tell if its rooted or if they would be in the same position i am where nothing shows up.
Does it show comm7 , i know there is a box that is checked, in the add port screen, that keeps it from seeing the port. When i get home i'll take a screen shot
I too am having this exact issue.
I'm on the same boat. I don't even know how it happened since I wasn't even trying to flash a ROM. One person told me to look at tablets hard brick but I've had no luck yet. Phone was stuck in a recovery bootloop so I tried to wipe/restore backup which didn't work. Popped the battery, went to download mode, started flashing TOT, got an error (yes I had the right files), popped battery again hoping it was a bad connection but nope. I got it the other week :/ as a replacement because my G2 had hardware issues. There's gotta be a way somewhere. In the mean time, I had my gf call my service provider claiming she got a popup about an upgrade, clicked yes and came back to a black screen. They said to bring it in because it's within 14 days of the refurbished. I'm going to take it in but I'm hoping there's a way to get the phone to not load anything at all (led or the boot error during LG), or do sales reps not know enough and/or don't care enough?
I got it working!!! Somehow I got TWRP'd to boot then restored my backup of 4.4.2 stock. AT&T connecting/dropping and Baseband: "Unknown" before it randomly rebooted into download mode which I'm at now. I tried flashing TOT through COM41 but it wasn't successful. Not sure what to do now.
I had some paragraph typed and it must've not gone through. I got it back to the home screen and AT&T logo once "firmware upgrade" was an option again. I still don't know how I switched it from Qualcomm to LGE Mobile, maybe some files I deleted thinking an app backdoor'd it and injected files. After a fun and exciting 12+ hours straight with errors, bootloops, reading forums, videos, downloading/un-install. I managed a way that worked and booted back into a fresh device.
Flash Tools < BOARD_DL < Booted into Status 2
LG Suite < Restore < Fail
Flash Tools < UPGRADE_DL < Fail at 6%
Flash Tools < BOARD_DL < Fail at download mode
Device Manager < Show Hidden < Portable Devices < Un-install all MTP
Flash Tools < BOARD_DL < got to 8x% < Phone Reboot into AAT < Click < Power+Click on "Normal Boot"
LG Logo < AT&T Logo < Brand new G3
Click to expand...
Click to collapse
Hopefully this method will work for you, and who ever else has the same problem.
Here's part of the log. Not sure if hopeful or not.
[ 9:46:27] == PROPERTY INFO
[ 9:46:27] 1. download cable = USER
[ 9:46:27] 2. battery level = 77
[ 9:46:27] 3. download type =
[ 9:46:27] 4. download speed = 0
[ 9:46:27] 5. usb version = UHS
[ 9:46:27] 6. hardware revision = rev_10
[ 9:46:27] 7. download sw version =
[ 9:46:27] 8. device sw version = D85010d
[ 9:46:27] 9. secure device = S
[ 9:46:27] 10. laf sw version = 1.0
[ 9:46:27] 11. device factory version = LGD850AT-01-V10d-310-410-JUN-19-2014+0
[ 9:46:27] 12. device factory out version = LGD850AT-00-V10d-ATT-US-JUN-19-2014+0
[ 9:46:27] 13. pid = HD58S140925001695
[ 9:46:27] 14. imei = XXXXXXXXXXXXXXXXXXXX
[ 9:46:27] 15. model name = LG-D850
[ 9:46:27] 16. device build type = U
[ 9:46:27] 17. chipset platform = msm8974
[ 9:46:27] 18. target_operator = ATT
[ 9:46:27] 19. target_country = US
[ 9:46:27] 20. ap_factory_reset_status = 2
[ 9:46:27] 21. cp_factory_reset_status = 0
[ 9:46:27] 22. isDownloadNotFinish = 0
[ 9:46:27] 23. qem = 0
[ 9:46:27] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 9:46:27] 25. is one binary dual plan = 0
[ 9:46:27] 26. memroy size = 61071360
[ 9:46:27] 27. memory_id = 032GE4
[ 9:46:27] 28. bootloader_ver = MiniOS 3.0
[ 9:46:27] LAF : Bin_User_Mode
[ 9:46:27] isValidateSecureImage Device is a qfused.
[ 9:46:27] found sbl1 Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found aboot Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found rpm Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found tz Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] Secure Image Check Success
[ 9:46:27] * Set AP factory_reset= 0
[ 9:46:27] * Set qem_reset= 1
GrayNullFox said:
I'm on the same boat. I don't even know how it happened since I wasn't even trying to flash a ROM. One person told me to look at tablets hard brick but I've had no luck yet. Phone was stuck in a recovery bootloop so I tried to wipe/restore backup which didn't work. Popped the battery, went to download mode, started flashing TOT, got an error (yes I had the right files), popped battery again hoping it was a bad connection but nope. I got it the other week :/ as a replacement because my G2 had hardware issues. There's gotta be a way somewhere. In the mean time, I had my gf call my service provider claiming she got a popup about an upgrade, clicked yes and came back to a black screen. They said to bring it in because it's within 14 days of the refurbished. I'm going to take it in but I'm hoping there's a way to get the phone to not load anything at all (led or the boot error during LG), or do sales reps not know enough and/or don't care enough?
I got it working!!! Somehow I got TWRP'd to boot then restored my backup of 4.4.2 stock. AT&T connecting/dropping and Baseband: "Unknown" before it randomly rebooted into download mode which I'm at now. I tried flashing TOT through COM41 but it wasn't successful. Not sure what to do now.
I had some paragraph typed and it must've not gone through. I got it back to the home screen and AT&T logo once "firmware upgrade" was an option again. I still don't know how I switched it from Qualcomm to LGE Mobile, maybe some files I deleted thinking an app backdoor'd it and injected files. After a fun and exciting 12+ hours straight with errors, bootloops, reading forums, videos, downloading/un-install. I managed a way that worked and booted back into a fresh device.
Hopefully this method will work for you, and who ever else has the same problem.
Here's part of the log. Not sure if hopeful or not.
[ 9:46:27] == PROPERTY INFO
[ 9:46:27] 1. download cable = USER
[ 9:46:27] 2. battery level = 77
[ 9:46:27] 3. download type =
[ 9:46:27] 4. download speed = 0
[ 9:46:27] 5. usb version = UHS
[ 9:46:27] 6. hardware revision = rev_10
[ 9:46:27] 7. download sw version =
[ 9:46:27] 8. device sw version = D85010d
[ 9:46:27] 9. secure device = S
[ 9:46:27] 10. laf sw version = 1.0
[ 9:46:27] 11. device factory version = LGD850AT-01-V10d-310-410-JUN-19-2014+0
[ 9:46:27] 12. device factory out version = LGD850AT-00-V10d-ATT-US-JUN-19-2014+0
[ 9:46:27] 13. pid = HD58S140925001695
[ 9:46:27] 14. imei = XXXXXXXXXXXXXXXXXXXX
[ 9:46:27] 15. model name = LG-D850
[ 9:46:27] 16. device build type = U
[ 9:46:27] 17. chipset platform = msm8974
[ 9:46:27] 18. target_operator = ATT
[ 9:46:27] 19. target_country = US
[ 9:46:27] 20. ap_factory_reset_status = 2
[ 9:46:27] 21. cp_factory_reset_status = 0
[ 9:46:27] 22. isDownloadNotFinish = 0
[ 9:46:27] 23. qem = 0
[ 9:46:27] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 9:46:27] 25. is one binary dual plan = 0
[ 9:46:27] 26. memroy size = 61071360
[ 9:46:27] 27. memory_id = 032GE4
[ 9:46:27] 28. bootloader_ver = MiniOS 3.0
[ 9:46:27] LAF : Bin_User_Mode
[ 9:46:27] isValidateSecureImage Device is a qfused.
[ 9:46:27] found sbl1 Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found aboot Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found rpm Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found tz Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] Secure Image Check Success
[ 9:46:27] * Set AP factory_reset= 0
[ 9:46:27] * Set qem_reset= 1
Click to expand...
Click to collapse
I appreciate you going through this, but I don't think that you were bricked to the point that we are.
-No Download Mode
-No Recovery
-Black Screen & nothing on it.
-When plugged in via USB it shows up on the pc as: LGE AndroidNet USB Serial Port
-LG Flash Tools will not work.
-When plugged in with no battery, the screen lights up with a symbol with a battery and an exclamation point.
ElectroSh0ck said:
I appreciate you going through this, but I don't think that you were bricked to the point that we are.
-No Download Mode
-No Recovery
-Black Screen & nothing on it.
-When plugged in via USB it shows up on the pc as: LGE AndroidNet USB Serial Port
-LG Flash Tools will not work.
-When plugged in with no battery, the screen lights up with a symbol with a battery and an exclamation point.
Click to expand...
Click to collapse
That's how I was. Secure info boot < red and blue led with black screen, no factory restore. I don't know how I got TWRP to boot. I started messing around with the device manager, deleting any files stored on the computer related to any LG device (AndroidNet, QualComm, MTP, etc) along with popping the battery in with the charge screen and reading a logs.
I hope you guys can get it fixed.
Not even getting a secure info boot here. Black screen no leds
Sent from my SM-N910V using XDA Free mobile app
Same here
After rooting it and installing TRWP, I was getting an Error when rebooting into recovery "Secure Boot error". I found a solution at this page: http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977 and I was trying to replicate. At the Terminal command step "su" worked, the second line didn't, the third line worked and the final one didn't. I know that the third line bricked my phone.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot (writes “zeroes” to the partition to “wipe” it out)
Since then the phone is almost dead. No way to wake it up, I've tried every combination of buttons and USB plugin. The only signs that is alive are that when I connect it without the battery to USB it shows the with the phone connected and the yellow triangle with a question mark and that is detected as LGE Androidnet USB and modem in the Device Manager. I tried the TOT method and the KDZ method, nothing worked. In Qpst it is detected as Phone in Download Mode and in QPST Configuration as Sahara Memory Dump (Connected Phone: Q/QCP-XXX).
LGNPST detects it as UNKNOWN, only Emergency active, and doesn't do anything when trying to upload the bin file, gives Error: Could not switch to download mode.
Getting crazy here.
What DLL did you use to get LGNPST to give you that error?
ElectroSh0ck said:
What DLL did you use to get LGNPST to give you that error?
Click to expand...
Click to collapse
The default one... LGNPST_LS970.dll It was the only one that it let me use.
alex_da_fixeru said:
The default one... LGNPST_LS970.dll It was the only one that it let me use.
Click to expand...
Click to collapse
Ah okay that makes sense. We will need a DLL specific to the model of G3 that we have. It is basically telling the program how to interact with the phone in emergency mode. I have tried the DLL's used to flash TOTs, but they will not register in Windows.
ElectroSh0ck said:
Ah okay that makes sense. We will need a DLL specific to the model of G3 that we have. It is basically telling the program how to interact with the phone in emergency mode. I have tried the DLL's used to flash TOTs, but they will not register in Windows.
Click to expand...
Click to collapse
I can't seem to find the correct .dll for LG G3. Anyone has it?
Wouldn't it be the one that came with your firmware file?
Sent from my Nexus 7 using XDA Free mobile app
danmak89 said:
Wouldn't it be the one that came with your firmware file?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I would think that was the case, but they will not show up in LGNPST. I can get the ones to work that others have provided specifically for LGNPST, but not the ones used to flash a TOT with LG Flash Tool.
ElectroSh0ck said:
I would think that was the case, but they will not show up in LGNPST. I can get the ones to work that others have provided specifically for LGNPST, but not the ones used to flash a TOT with LG Flash Tool.
Click to expand...
Click to collapse
Ah man. I managed to get my device recognised as LGE AndroidNet USB Serial Port but there's still another driver that won't install and I don't know which one it would need to be.
Device just won't boot in to any mode, no LEDs, nothing. Obvious tools don't work like flashtool, b2bsupport. I'm considering swapping out the main board as they don't seem too expensive but I'm trying to see if I can solve this first.
I refuse to accept that this is 100% bricked.
Sent from my Nexus 7 using XDA Free mobile app
Recently, I discovered that I had this old device in my drawers so I decided to take it out to see if I could get it running. It wasn't charging or turning on at all, so I took the back off and replaced battery and connector, nothing. So, after plugging it in to my computer, I noticed a weird device named "CLOVERVIEW", which searching that up, is usually associated with ASUS devices, which is really weird. I followed a guide to repair a dead boot, using a zip file provided here.
I put the files into the correct spots in Phone Flash Tool 4.4.4, yet I only receive an error when flashing. It appears the IFW file flashes fine, but the DnX FW does not. Log provided below.
----
06/20/23 23:13:48.280 INFO : Loading Flash file ...
06/20/23 23:13:48.280 INFO : Ready to flash!
06/20/23 23:13:49.317 INFO : Port 0/4: Start flashing BLANKPHONE flash file for
06/20/23 23:13:49.317 INFO : Port 0/4: IFW flash started - SN : CDC36BFD990D9446
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 0
06/20/23 23:13:49.361 INFO : XFSTK-STATUS Detecting Intel Device - Attempt #0
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 5
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FW download is in progress ...
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-PROGRESS SN: CDC36BFD990D9446 3
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Softfuses Binary absent. Please provide binary.
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FAIL
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Errors encounter during FW download. Aborting ...
06/20/23 23:13:50.491 INFO : Port 0/4: IFW flash success - SN : CDC36BFD990D9446
06/20/23 23:16:51.438 ERROR : Port 0/4: Device on port 0/4 timeout to enum adb (TIMEOUT = 180)
----
I'm not exactly sure what to do from here, the device still appears in Device Manager and I can't do anything about it from this point.