Hi Everyone,
First I apologize if this isn't the right place to post this, please move it to the correct forum if it's not.
I have a Asus TF700 (running the latest Asus firmware) the, warranty just ran out so I figured it was time to unlock and play with some custom roms.
I got it unlocked using the Asus bootloader tool, I went to install CWM using fastboot and it seemed to go OK but then when I went to reboot the bootloader it failed giving me a write failure. Now when I try to boot up recovery it briefly shows the android guy in working mode then goes to the error with the android laying on his back.
Here is my commands with fastboot:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (6688 KB)...
OKAY [ 2.483s]
writing 'recovery'...
OKAY [ 2.409s]
finished. total time: 4.893s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\adb>adb reboot bootloader
error: device not found
And that's it, I'm a bit stumped not sure how to fix it so I can move onto installing the roms, any help would be greatly appreciated.
Anyone?
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
packyy said:
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
Click to expand...
Click to collapse
Yes, if I hadn't then I wouldnt have been able to use fastboot or install CWM.
No one? I thought this was the android super stars forum.
Can someone at lease suggest another forum with people willing to help?
Not a single person willing to help me out? Wow, thanks.
this is the first time i have owned an LG phone. I have the bootloaded unlocked and usb debugging enabled. I have read just about every guide i could find but i still cant manage to flash twrp.
i am trying to flash the latest twrp-3.2.1-0-h830.img
i am showing build number NRD90U and software version H83020a.
i am getting this error message trying to flash thru either adb or minimal adb and fastboot programs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (18700 KB)...
OKAY [ 0.511s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.531s
any suggestions would be appreciated. thanks
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496 this should show you how
tensux said:
this is the first time i have owned an LG phone. I have the bootloaded unlocked and usb debugging enabled. I have read just about every guide i could find but i still cant manage to flash twrp.
i am trying to flash the latest twrp-3.2.1-0-h830.img
i am showing build number NRD90U and software version H83020a.
i am getting this error message trying to flash thru either adb or minimal adb and fastboot programs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (18700 KB)...
OKAY [ 0.511s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.531s
any suggestions would be appreciated. thanks
Click to expand...
Click to collapse
If you already have TWRP before just use the app.
If its the first time you flash twrp using the Recowvery method, make sure you have a copy of the recovery.img on your internal memory. :good:
rflores said:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496 this should show you how
Click to expand...
Click to collapse
cheeze.keyk said:
If you already have TWRP before just use the app.
If its the first time you flash twrp using the Recowvery method, make sure you have a copy of the recovery.img on your internal memory. :good:
Click to expand...
Click to collapse
Hi thanks for the replies.
I finally got it to work after a couple days of a soft brick at lg firmware update. i used Easyrecowery and and for some reason needled to toglle between file transfer and phot transfer while getting stuck while the scripts were processing
https://forum.xda-developers.com/tmobile-lg-g5/how-to/guide-root-twrp-lg-g5-using-t3580264
now to flash lineageos
So I just followed the steps to unlock the bootloader for my Mate 10 pro and wanted to continue installing TWRP and then Magisc, but after I unlocked it, it refuses to show up in my adb devices. Any suggestions? I also tried to list the device on Ubuntu with no success When I try to run the fastboot flash recovery_ramdisk twrp.img this msg come up:
target reported max download size of 471859200 bytes
sending 'recovery_ramsik' (8622 KB)...
OKAY [ 0.188s]
writing 'recovery_ramsik'...
FAILED (remote: partition length get error)
finished. total time: 0.203s
Try reinstalling the drivers
Bowserman16162 said:
Try reinstalling the drivers
Click to expand...
Click to collapse
I did it several times without success.
Bowserman16162 said:
Try reinstalling the drivers
Click to expand...
Click to collapse
Its listed as an Android Bootloader Interface if that helps...
Then maybe try using fastboot instead of adb you can install stuff from that.
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
cAnArdtichAud said:
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
Click to expand...
Click to collapse
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
You should update your platform tools and you'll need to format data to go back to the November factory image.
Tulsadiver said:
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
Click to expand...
Click to collapse
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Edmontonchef said:
You should update your platform tools and you'll need to format data to go back to the November factory image.
Click to expand...
Click to collapse
Yeah thanks I updated them after I had the issue and retried without working.
cAnArdtichAud said:
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Click to expand...
Click to collapse
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Tulsadiver said:
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Click to expand...
Click to collapse
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
Yeah but I've already flashed back recovery and radio the OS part is failing
V0latyle said:
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
Click to expand...
Click to collapse
thx. I tried several images but will retry on another port, another cable same PC (only one...)
I have 31.03 command tools
funkin' love you guys: ensuring I was on a powered usb port, changing cable made me flash the data/os files
funkin' pixel 6 reverted back to the entire previous rom
funkin Xmas to you guys , #heartWithFingers!
vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
You can't go back without a full wipe.
Tulsadiver said:
You can't go back without a full wipe.
Click to expand...
Click to collapse
Because when you unlock the bootloader prior to flashing, the phone is wiped.
cAnArdtichAud said:
Because when you unlock the bootloader prior to flashing, the phone is wiped.
Click to expand...
Click to collapse
Even if your bootloader is already unlocked.
sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
That is just the radio.....not the system.
vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Tulsadiver said:
That is just the radio.....not the system.
Click to expand...
Click to collapse
Yes ,just the radio image from November on top of the complete December image.
What I did;
Flash-all (December factory image with the -w removed for no data wipe)
Next, I extracted the November radio image from the November factory image.
Than , fastboot flash radio radio.img.
I know it sounds confusing. Lol..
sniff1 said:
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Click to expand...
Click to collapse
Fastboot flash radio yourradio.img
Yes the radio command needs to be there after the flash command and before your radio.img.
Very similar to to flashing a boot image,
Example, fastboot flash boot boot.img
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help!
A working TWRP has not been ported to this device.
You can convert your device to STOCK OEM and root with my guides and this will also bring you up to C_17.
Thanks! In fact, yesterday I used your "Full Convert Tmobile...dummies" to prepare an old Windows-7 partition to do this but I have been working up the courage to make the attempt. It is reassuring to hear that I am on the right track.
katooom said:
Thanks! In fact, yesterday I used your "Full Convert Tmobile...dummies" to prepare an old Windows-7 partition to do this but I have been working up the courage to make the attempt. It is reassuring to hear that I am on the right track.
Click to expand...
Click to collapse
Make sure you install .net v4.5 on there before you install Fastboot Enhance
scanman0 said:
Make sure you install .net v4.5 on there before you install Fastboot Enhance
Click to expand...
Click to collapse
Thanks! By chance, it seems that I already had .net 4.8 installed from 2019. However, during setup I did have to setup the Visual Studio 2015 redistributable package.
katooom said:
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help
Click to expand...
Click to collapse
here is a working .IMG file for the Nord N200 DE2118. for some reason it won't let me upload it
Working TWRP for OnePlus Nord N200 .img file why won't it let me upload it
The problem is that's for Android 11, your running android 12. Best case scenario you brick your device
I know this from personal experience lol
katooom said:
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help!
Click to expand...
Click to collapse
If your trying to root, use magisk.