So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.
First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.
Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.
So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.
Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.
Im just very confused were do i go from here.
Model number LM-v4059N (jydypn)
SKT_KR (Korean version)
Android 10
Device State - Unlocked
Also i know my IMEI if that helps
Cookies_crumbly said:
So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.
First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.
Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.
So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.
Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.
Im just very confused were do i go from here.
Model number LM-v4059N (jydypn)
SKT_KR (Korean version)
Android 10
Device State - Unlocked
Also i know my IMEI if that helps
Click to expand...
Click to collapse
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.
But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.
The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.
If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.
cheers
AsItLies said:
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.
But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.
The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.
If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.
cheers
Click to expand...
Click to collapse
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.
I managed to install v35 eng abl back.
Also, can you sideload download mode from Bootloader?
Cookies_crumbly said:
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.
I managed to install v35 eng abl back.
Also, can you sideload download mode from Bootloader?
Click to expand...
Click to collapse
ahhh good, then follow this link and you'll find the boot+twrp image you need.
So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.
follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.
this is abl attached.
AsItLies said:
ahhh good, then follow this link and you'll find the boot+twrp image you need.
So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.
follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.
this is abl attached.
Click to expand...
Click to collapse
Okay so im trying to understand
First i fastboot flash abl_b kor_30f (im on b part)
Then i fastboot boot twrp
Them Resart into TWRP using power down + volume down
Then go from here?
Because i get error like this should i also flash to abl_b only?
I renamed abl_b to new, and twrp to boot for easier usage
Cookies_crumbly said:
Okay so im trying to understand
First i fastboot flash abl_b kor_30f (im on b part)
Then i fastboot boot twrp
Them Resart into TWRP using power down + volume down
Then go from here?
Because i get error like this should i also flash to abl_b only?
I renamed abl_b to new, and twrp to boot for easier usage
Click to expand...
Click to collapse
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.
any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.
I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.
cheers
AsItLies said:
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.
any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.
I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.
cheers
Click to expand...
Click to collapse
I first tried loading 30f abl and got this (My active abl was in b):
C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (1024 KB)...
OKAY [ 0.024s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 0.027s
then i tried with twrp and got the same error:
C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (65536 KB)...
OKAY [ 1.384s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 1.386s
im new to this, i really need help
Cookies_crumbly said:
I first tried loading 30f abl and got this (My active abl was in b):
C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (1024 KB)...
OKAY [ 0.024s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 0.027s
then i tried with twrp and got the same error:
C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (65536 KB)...
OKAY [ 1.384s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 1.386s
im new to this, i really need help
Click to expand...
Click to collapse
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!
You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!
I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.
So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.
cheers
AsItLies said:
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!
You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!
I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.
So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.
cheers
Click to expand...
Click to collapse
Okay my goal is installing TWRP + CUSTOM ROM
Only thing working now is v35 bootloader, and download mode shows "no command" dialog.
I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.
please help me, step by step
greatly appreciated
Cookies_crumbly said:
Okay my goal is installing TWRP + CUSTOM ROM
Only thing working now is v35 bootloader, and download mode shows "no command" dialog.
I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.
please help me, step by step
greatly appreciated
Click to expand...
Click to collapse
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.
To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.
And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).
They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.
Do that, and we'll go from there. cheers
AsItLies said:
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.
To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.
And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).
They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.
Do that, and we'll go from there. cheers
Click to expand...
Click to collapse
They files you shared is for 30c, mine is 30f (Korean version).
Is it okay to use it?
Also is there a certain order do i have to go through? like boot first etc?
cheers for the helps
Cookies_crumbly said:
They files you shared is for 30c, mine is 30f (Korean version).
Is it okay to use it?
Also is there a certain order do i have to go through? like boot first etc?
cheers for the helps
Click to expand...
Click to collapse
yes, I know they are not what you currently have. But it will work to get to lgup, not to boot the device, only to get to lgup.
there's no order, I would have told you an order if there was one.
just re-read what I said. This allows you to go directly from qfil to lgup, use the key combo I mentioned.
It's at that point you can re-flash kor 30f, and start fresh.
Im still getting the same error.
C:\adb>fastboot flash abl abl_30c.img
target reported max download size of 805306368 bytes
sending 'abl' (1024 KB)...
OKAY [ 0.031s]
writing 'abl'...
FAILED (remote: unknown command)
finished. total time: 0.031s
Cookies_crumbly said:
Im still getting the same error.
C:\adb>fastboot flash abl abl_30c.img
target reported max download size of 805306368 bytes
sending 'abl' (1024 KB)...
OKAY [ 0.031s]
writing 'abl'...
FAILED (remote: unknown command)
finished. total time: 0.031s
Click to expand...
Click to collapse
you're suppose to be using qfil, not fastboot.
But how would i enter QFIL if i cannot enter 9008 mode?
why are u unable to enter 9008 mode?
AsItLies said:
why are u unable to enter 9008 mode?
Click to expand...
Click to collapse
I did now, thank you
I was just having problem clicking volume up down button so i thought it was only possible if the phone is booted.
Successfully installed the recovery files and booted into download mode.
Downloading original kdz and hopefully do all this all over again, this time backing up the files
Thank you for all your troubles, you single handedly helped me save my phone.
AsItLies said:
why are u unable to enter 9008 mode?
Click to expand...
Click to collapse
Another surprise, when i tried to install kdz on the phone, it says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la
Both refurbish and upgrade options show same result.
This is the same version that i successfully flashed before
edit: shoot, i downloaded the wrong version
Cookies_crumbly said:
Another surprise, when i tried to install kdz on the phone, it says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la
Both refurbish and upgrade options show same result
Click to expand...
Click to collapse
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
AsItLies said:
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
Click to expand...
Click to collapse
Great news, i flashed kdz using patched LGUP with custom cmd line. Now its working as intended, it shows OEM already unlocked in dev options. i patched abl_a to get magisk working ( i think my active slot is A now).
So i got root and magisk, but my goal is still have TWRP and install custom ROM.
So from what i gathered, i install v35 on abl_a, boot into fastboot, flash twrp to boot and flash orignal abl back and restard bootloader.
Or can i just flash twrp into boot_a in QFIL?
cheers
Related
I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.
Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.
Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]
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.
So basically I was installing TWRP onto my Mi A2. I installed twrp on slot b using fastboot flash boot_b twrp.img When then trying to boot into the b slot using fastboot set_active b That command wasn't recognized. I tried installing JDK and SDK manager to get the latest syntax etc. of adb/fastboot. I tried everything again and accidently typed fastboot flash boot twrp.img . This made me flash twrp to my a slot too. The new adb/fastboot syntax still didn't recognize the set_active command. So now I'm simply stuck with twrp on both my slots. I tried installing havoc-OS v2.0 for GSI. downloading the img.xz file. Extracting it and tried flashing it on slot a. But it kind of failed. This was the code:
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot flash system_b havoca2.img
target reported max download size of 536870912 bytes
sending sparse 'system_b' (524284 KB)...
OKAY [ 17.596s]
writing 'system_b'...
OKAY [ 0.001s]
sending sparse 'system_b' (524284 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 18.764s
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot reboot
rebooting...
finished. total time: 0.001s
I would appreciate some help
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Stop using minimal adb, use this
https://developer.android.com/studio/releases/platform-tools
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
If all that results in is you staying in TWRP, look at twrp and hopefully it's one of the newer versions that allows you to set the 'active slot'. Hopefully choosing the other slot and then indicating reboot in twrp will cause the device to boot normally.
AsItLies said:
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Click to expand...
Click to collapse
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Nebrassy said:
Stop using minimal adb, use this
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
Click to expand...
Click to collapse
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
ncse said:
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Click to expand...
Click to collapse
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
AsItLies said:
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
Click to expand...
Click to collapse
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
ncse said:
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
Click to expand...
Click to collapse
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
AsItLies said:
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
Click to expand...
Click to collapse
Now i get bootloops. Should I flash system.img too? Apprently all this fault is because you have to type .\fastboot.exe instead of fastboot in powershell.
EDIT: I flashed system.img too. It works again. Thanks for all the help!
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
Fastboot flashing unlock_critical
I managed to brick a moto G7 plus to the point of not being able to recover from it (locked bootloader, no twrp, boots to fastboot)
I wanted to go back to 100% stock but failed badly.
My device is odd one. RETLA stream with XT1965-T hardware. Lenovo Rescue apparently don't work on these devices.
1) I flashed stock RETLA latest rom from Lolinet using a flash.bat I made
2) worked and booted fine.....twrp was still intact
3) I did factory reset when booted in.
4) To relock I flashed boot.img and sent lock command a few times
5) Bootloader is now locked but only boots to fastboot and get (YOUR DEVICE HAS LOADED A DIFFERENT OPERATING SYSTEM.
6) I cannot unlock with code because adb says says I need developer option etc.
To repeat: this is BOOTLOADER LOCKED, JUST BOOTS TO FASTBOOT and gives "your device loaded a different operating system) which is not the issue and I expected that.
Bankflash didn't do anything. I mostly get oermission denied with mostly flashing anythiine else.
Any suggestions on how to just get this thing at least bootable again to use?
Thanks.
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Anrito Kun said:
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Click to expand...
Click to collapse
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Anrito Kun said:
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Click to expand...
Click to collapse
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207
Having trouble installing TWRP.
I can fastboot and attempt:
`fastboot boot TWRP.img`
But it either fails or "succeeds" and then just hangs on the LG Logo.
`fastboot flash recovery TWRP.img`
-returns an error that recovery_a doesn't exist.
`fastboot flash abl_a TWRP.img`
-returns "Volume is Full"
Any ideas what I may be doing wrong?
Device is an ATT LG V40 with the V35 Engineering Bootloader if that helps.
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
The only thing about using fastboot is you want to save the original boot_a image first. At&t doesn't make their kdz available and if u want /need to go back to stock u need to save it first.
After flashing it (either way), you need to immediately go to recovery, don't boot the device, u have to format data and reboot to recovery and then flash magisk and no verity zip. Otherwise a backup of your data won't work as it will be encrypted.
just one point, don't every flash something to a partition when yer not sure what yer doing. The abl partition is only about 1 meg in size, it's the 'android boot loader'. You could, if unlucky, flash something wrong for that partition and end up overwriting the partitions that are next to it, and essentially (just about) brick the device.
cheers
AsItLies said:
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Click to expand...
Click to collapse
Sorry! It's Pie.
AsItLies said:
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
Click to expand...
Click to collapse
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
sharpienation said:
Sorry! It's Pie.
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
Click to expand...
Click to collapse
Wow, so I don't think you understood some things. First, stop trying to flash an image to the wrong partition then what it's for. It is NOT for abl_a, and it is NOT for recovery (there is no recovery partition on a treble phone). STOP DOING THAT.
and second, because that boot_a (ONLY!!!) partition is for Q, as I said, you need one for Pie, and shouldn't even be trying to use it anyway.
and third, you can't fastboot boot these boot/twrp images, they have to be flashed to the partition and then you have to boot to recovery immediately after (don't try to boot the phone).
So if you can't flash the image with fastboot then the only option would be to use qfil, again, be sure to back up the original image first.
I'll look around and see if I can find one for Pie. We may have to create one if it's not around.
cheers
Just checking, but u do know how to use qfil yes? And, how did u get fastboot on the device? Using qfil I'm guessing? and you deleted laf_a? or the engineering abl?
This info is important because 1) the fastboot you get when simply erasing the laf_a is not as powerful and full featured as the engineering abl. The actual capabilities of the (laf_a erased) fastboot varies by OS variant, but some of them are basically worthless.
2) you'll have to be able to use qfil to get this accomplished.
let me know and we'll go from there.