Related
My VS980, I had updated to 39A through the manual OTA method, rooted with the new LG root method, everything worked fine, until I flashed a wrong boot.img file using the dd command. Now the boot screen says Secure booting error, and it doesnot boot. I tried getting into the fastboot mode (I erased the laf partition after rooting), but fastboot won't execute any commands
Code:
sh-3.2# fastboot flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (9712 KB)...
OKAY [ 0.356s]
writing 'recovery'...
^C
sh-3.2#
and it waits for ever at writing recovery, I waited close to an hour before doing ^C.
I didnot install custom recovery yet, and I could get only to factory reset on the recovery screen (using Vol Down + power)
Can someone help me out to get out of this brick?
rishie said:
My VS980, I had updated to 39A through the manual OTA method, rooted with the new LG root method, everything worked fine, until I flashed a wrong boot.img file using the dd command. Now the boot screen says Secure booting error, and it doesnot boot. I tried getting into the fastboot mode (I erased the laf partition after rooting), but fastboot won't execute any commands
Code:
sh-3.2# fastboot flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (9712 KB)...
OKAY [ 0.356s]
writing 'recovery'...
^C
sh-3.2#
and it waits for ever at writing recovery.
I didnot install custom recovery yet, and I could get only to factory reset on the recovery screen (using Vol Down + power)
Can someone help me out to get out of this brick?
Click to expand...
Click to collapse
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW8BCUME0231ASHA4A40RQX/VS98027A_05.kdz
install LG drivers to windows 7 PC, download mode, LG Flash tool, KDZ link above, reroot at 27A, Autorec to install TWRP recovery 2.7.0.0, update to Blastagator's latest BUMPED recovery 2.8.5.1, flash 39A XDABBEB's bootstack, flash 39A stock rom made by XDABBEB's (already rooted).
Hi HueyT, Thanks for the reply, but currently I don't have download mode, as I erased laf partition. Now my g2 boots to fastboot mode, with Vol Up + USB Cable. If I can enter the stock recovery menu, then I can try sideloading any files but that too is not working.
rishie said:
Hi HueyT, Thanks for the reply, but currently I don't have download mode, as I erased laf partition. Now my g2 boots to fastboot mode, with Vol Up + USB Cable. If I can enter the stock recovery menu, then I can try sideloading any files but that too is not working.
Click to expand...
Click to collapse
http://forums.androidcentral.com/t-...-installing-custom-recovery-via-fastboot.html
HueyT said:
http://forums.androidcentral.com/t-...-installing-custom-recovery-via-fastboot.html
Click to expand...
Click to collapse
The same command I was trying to execute, but is not working, fastboot doesnot go past writing 'recovery'... step, I waited for almost 1 hour to see if the command completes, but it never completes.
rishie said:
Hi HueyT, Thanks for the reply, but currently I don't have download mode, as I erased laf partition. Now my g2 boots to fastboot mode, with Vol Up + USB Cable. If I can enter the stock recovery menu, then I can try sideloading any files but that too is not working.
Click to expand...
Click to collapse
You need to restore your laf partition. I personally don't have experience doing this, but it looks like there are a couple threads detailing how to do it in fastboot:
http://forum.xda-developers.com/showthread.php?t=2477595
http://forum.xda-developers.com/showthread.php?t=2779007
Instead of using the files included in those threads, downloaded the 39A bootstack zip from the resource thread and extract out the relevant files needed
Thanks for the reply.
I tried all of the following fastboot commands, using the 39a bootstack (ofc, one by one, waited for almost 15-20 min before cancelling the command):
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot -w
All the above commands stop at writing "****" ... section.
Basically the problem is that, the partitions are not getting modified by the fastboot in any way, something like a locked bootloader preventing fastboot from writing anything to the partitions.
i updated x620 recently with 5.9.20s , i was not getting volte so i tried to downgrade it by installing twrp, but now phone is showing your mobile is not running original le firmware so it cant start and then it goes shutdown , i can enter into fastboot mode , i tried different firmwares already , but m getting error of
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (21706 KB)...
OKAY [ 0.928s]
writing 'recovery'...
(bootloader) Fastboot oem devices is unlock
FAILED (remote: size too large)
finished. total time: 0.947s
please tell me wat sud i do now
Try a different ADB and fastboot. It seems rather odd that it would state that recovery is too large unless the recovery partition got corrupted or something.
Fixed it , i was using latest twrp in old rom
But stucked in new problem , i want to have volte support , through twrp i can only install custom roms , is there a way to flash stock rom ?
Method to flash it by putting update.zip in root directory is giving error as signature failed in stock recovery , and in twrp stock rom cnt be flashed
Amit2310 said:
Fixed it , i was using latest twrp in old rom
But stucked in new problem , i want to have volte support , through twrp i can only install custom roms , is there a way to flash stock rom ?
Method to flash it by putting update.zip in root directory is giving error as signature failed in stock recovery , and in twrp stock rom cnt be flashed
Click to expand...
Click to collapse
Try with chinese Twrp
solved ,, the rom i downloaded was corrupt
Hi guys I have a problem now when trying to flash custom recovery using adb fastboot this log always appear:
fastboot flash recovery recovery.img
sending 'recovery' (10704 KB)...
OKAY [ 0.341s]
writing 'recovery'...
#FAILED (remote: Command not allowed)
finished. total time: 0.345s
SO,I dialed *#*#7378423#*#* and I found that my bootloader is unlocked
then I USED sony flash tool and flashed official 4.4.2 then tried and nothing
WIPED EVERY THING then flashed official 5.1.1 and tried to flash recovery and nothing happened
so I ROOTED 5.1.1 by KINGOROOT and dowloaded flashify then when tried to flash recovery.img it gives me message (recovery partition not found) and so are the boot (boot partition not found)
what can I do help please !
No one can fix my problem?!!
I just did it .....same problem like you. I rename the recovery img to boot.img then flash it to boot.img . Then it boot up twrp.
tllim73 said:
I just did it .....same problem like you. I rename the recovery img to boot.img then flash it to boot.img . Then it boot up twrp.
Click to expand...
Click to collapse
But thus I will flash boot not recovery, I know it will work because I did that but the orginal problem isn't solved
I flashed the Android Wear 2.0 OTA update and now the watch won't boot. I get the "Device Software Can't Be Checked For Corruption" error and it's telling me to go to g.com/ABH.
It won't go into recovery mode, but will go into fastboot mode. I grabbed the stock images from here, and flashed the stock boot, system, and recovery imgs, but the error persists.
https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Am I screwed? Or is there something I could do to recover?
Thanks.
Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Wait for about 10 seconds when the warning appears. The watch will continue it's boot after 10 secs.
TonySuperPony said:
Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Click to expand...
Click to collapse
I thought I had initially. I hadn't turned the watch on for a while, but decided to get it set up yesterday when I saw news of the 2.0 update hit. It originally had the first firmware on it and wouldn't update to 2.0 (adb would fail to find the watch).
So, I flashed MWF76 from the link in my earlier post. And that worked properly -- the watch booted normally, set up the apps, the right build number was showing, etc.
When that was done I tried to flash the 2.0 update again. And this time the watch was being recognized properly with adb. The flash procedure seemed to go without a hitch, but I got the g.co/ABH error on first boot.
And if you let the watch sit for 10 seconds, it only boots into Fastboot mode. You can't enter recovery. If you try to enter recovery with the vol-down+power button combo, you see recovery for a split second and then it goes right to fastboot.
At the moment it appears the bootloader is locked again.
Still experimenting. Hoping someone with more knowledge may be able to help.
Fastboot oem unlock reports that the bootloader is already unlocked.
Tried flashing all of the IMGs in MFW76 and these flash successfully:
boot
system
recovery
modem
asusfw
But when trying to flash these, the flash fails because it says the bootloader is locked. Trying fastboot oem unlock again reports the bootloader is unlocked, but still can not flash these...
devinfo
factory
misc
modemst1
modemst2
oem
splash
Tried fastboot flashing unlock_critical, and the watch shows part of a message, but I can't see if there's anything to do on...pressing the top or bottom buttons changes the color of the bg.
Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.
yilun said:
Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.
Click to expand...
Click to collapse
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?
re: flashable AW 2.0 zip file
BigWopHH said:
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?
Click to expand...
Click to collapse
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!
Misterjunky said:
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!
Click to expand...
Click to collapse
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"
re: adb sideload
BigWopHH said:
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"
Click to expand...
Click to collapse
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!
Misterjunky said:
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!
Click to expand...
Click to collapse
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.
BigWopHH said:
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.
Click to expand...
Click to collapse
I'd try to get the watch running 1.5 first via fastboot.
See my post in the other thread linked here, specifically my edits.
I did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata"
I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?
re: not booting properly
AndyKir said:
I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?
Click to expand...
Click to collapse
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!
Misterjunky said:
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!
Click to expand...
Click to collapse
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.
AndyKir said:
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.
Click to expand...
Click to collapse
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.
Misterjunky said:
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.
Click to expand...
Click to collapse
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?
re: fastboot bootup
AndyKir said:
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?
Click to expand...
Click to collapse
You must have flashed the wrong boot.img (which is the kernel)
Make 100% sure that you are flashing the correct kernel and
don't issue the command "fastboot format userdata".
All you need is:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
then oem lock bootloader
What was the exact filename of the ziip file
which had the 3 IMG files in it?
Here is the link for the zip file which contains the correct IMG files in it:
https://www.dropbox.com/s/tz9bg5fggpfn2q6/swift_partition_dump_part1_MWG68.zip?dl=1
unlock bootloader, flash the three img files, lock bootloader
and issue this fastboot command: " fastboot reboot "
Don't flash anything else and don't format anything...
Good luck, have a great day!
Misterjunky, thank you for your replies!
I`ve downloaded your files from Dropbox, put it in c:\adb\correct\ folder, and run next commands in PowerShell
PS C:\adb> fastboot oem unlock
...
(bootloader) The bootloader is already unlocked!
OKAY [ 0.006s]
finished. total time: 0.007s
PS C:\adb> fastboot flash boot C:\adb\correct\boot.img
target reported max download size of 262144000 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.038s]
writing 'boot'...
OKAY [ 3.222s]
finished. total time: 4.263s
PS C:\adb> fastboot flash recovery C:\adb\correct\recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.043s]
writing 'recovery'...
OKAY [ 3.150s]
finished. total time: 4.195s
PS C:\adb> fastboot flash system C:\adb\correct\system.img
target reported max download size of 262144000 bytes
erasing 'system'...
OKAY [ 1.134s]
sending sparse 'system' (254201 KB)...
OKAY [ 8.468s]
writing 'system'...
OKAY [ 26.695s]
sending sparse 'system' (149469 KB)...
OKAY [ 5.016s]
writing 'system'...
OKAY [114.570s]
finished. total time: 155.890s
PS C:\adb> fastboot oem lock
...
(bootloader) Locking bootloader...
(bootloader) Device Locked!
(bootloader) Locking bootloader done!
OKAY [ 0.023s]
finished. total time: 0.024s
PS C:\adb> fastboot reboot
rebooting...
finished. total time: 0.008s
PS C:\adb>
After reboot, I still in Fastboot mode - nothing is changed.
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
I need help :'(
I had that.
Phone was completely dead, needed a new board.
chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!
You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.
benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??