Hey guys,
I can't install TWRP anymore on my unlocked "P8 lite" after the last Stock ROM Update. I've done the installation many times before without problems using Minimal ADB and fastboot and even the Universal Fastboot and ADB tool. When I try to flash I get no failed command, but nothing happens on my phone. I've tried with the newest grace .img (for "P8") and with an older .img that I've used in the past successfully. Commands "adb devices" and "adb reboot bootloader" work fine.
Any solution?
thx
CMD commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26226 KB)...
OKAY [ 1.437s]
writing 'recovery'...
OKAY [ 1.172s]
finished. total time: 2.625s
Related
looks like yet another ota update for the hd6 was released today
kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
if you havent already disabled ota updates i suggest doing so now
thanks for the info
can anyone confirm whether or not the latest KingRoot works with v4.5.4 as well?
HamishAhern said:
can anyone confirm whether or not the latest KingRoot works with v4.5.4 as well?
Click to expand...
Click to collapse
You need to unlock your bootloader & flash twrp and boot in to it, then reboot to system and it says Flash SuperSu?
Root Voila.
meganoahj said:
You need to unlock your bootloader & flash twrp and boot in to it, then reboot to system and it says Flash SuperSu?
Root Voila.
Click to expand...
Click to collapse
And how do you flash twrp without root ? You need to be in 5.4.3 where you have root, and can proceed further.
bibikalka said:
And how do you flash twrp without root ? You need to be in 5.4.3 where you have root, and can proceed further.
Click to expand...
Click to collapse
Sorry i forgot that you need root for flashing recovery
i think that you need to downgrade to 4.5.3 (Later available)
or reboot to bootloader (adb reboot-bootloader) and
try (After Bootloader Unlock): fastboot flash recovery recovery.img
or when its not work try: fastboot -i 0x1949 flash recovery recovery.img
meganoahj said:
or reboot to bootloader (adb reboot-bootloader) and
try (After Bootloader Unlock): fastboot flash recovery recovery.img
or when its not work try: fastboot -i 0x1949 flash recovery recovery.img
Click to expand...
Click to collapse
I tried your commands but they both fail: FAILED (remote: flashing not allowed for locked hw)
devicer said:
I tried your commands but they both fail: FAILED (remote: flashing not allowed for locked hw)
Click to expand...
Click to collapse
You need to unlock your bootloader
meganoahj said:
You need to unlock your bootloader
Click to expand...
Click to collapse
Well, I did it, or I think so:
Code:
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/manfid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0x0000XX
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/serial
0xSSSSSSSS
[[email protected] /tmp]$ python2 cublock.py XX SSSSSSSS
Your unlock code is in 'unlock.img'.
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot -i 0x1949 flash unlock unlock.img
target reported max download size of 52429824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.036s]
writing 'unlock'...
OKAY [ 0.089s]
finished. total time: 0.125s
[[email protected] /tmp]$ fastboot reboot
rebooting...
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.295s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.318s
[[email protected] /tmp]$ fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.297s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.321s
[[email protected] /tmp]$ fastboot reboot
rebooting...
devicer said:
Well, I did it, or I think so:
Code:
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/manfid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0x0000XX
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/serial
0xSSSSSSSS
[[email protected] /tmp]$ python2 cublock.py XX SSSSSSSS
Your unlock code is in 'unlock.img'.
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot -i 0x1949 flash unlock unlock.img
target reported max download size of 52429824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.036s]
writing 'unlock'...
OKAY [ 0.089s]
finished. total time: 0.125s
[[email protected] /tmp]$ fastboot reboot
rebooting...
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.295s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.318s
[[email protected] /tmp]$ fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.297s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.321s
[[email protected] /tmp]$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
Ok i think you need to downgrade, ask amazon for rollback like “my device have problems with fire os 4.5.4“, or wait for method for downgrade
Or try fastboot boot recovery.img then flash your recovery with twrp
devicer said:
Well, I did it, or I think so:
Code:
[[email protected] /tmp]$
[[email protected] /tmp]$ fastboot flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.295s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.318s
[[email protected] /tmp]$ fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.297s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.321s
[[email protected] /tmp]$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
How about you run the command to check if you have unlocked your bootloader :
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
bibikalka said:
How about you run the command to check if you have unlocked your bootloader :
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Click to expand...
Click to collapse
Maybe you missed the part when I say that the Fire is at version 4.5.4, un-rooted...
devicer said:
Maybe you missed the part when I say that the Fire is at version 4.5.4, un-rooted...
Click to expand...
Click to collapse
Yes, looks like you are SOL !
Between 4.5.3 (Feb) and 4.5.4 (May) Amazon prob fixed the issue of the bootloader unlock, as well as the root exploit.
Call Amazon and beg them to downgrade you to 4.5.3 !
On the other hand, with rooted and unlocked 4.5.3 one should be able to update to 4.5.4, and keep root and unlock (after the update file is patched properly !).
bibikalka said:
On the other hand, with rooted and unlocked 4.5.3 one should be able to update to 4.5.4, and keep root and unlock (after the update file is patched properly !).
Click to expand...
Click to collapse
Bibikalka--Can you elaborate on patching the file and updating to 4.5.4? You haven't tried this yet? thx
DoLooper said:
Bibikalka--Can you elaborate on patching the file and updating to 4.5.4? You haven't tried this yet? thx
Click to expand...
Click to collapse
No, I have not tried this. I started looking at the upHDX script from here :
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
But then real work and life got in the way Basically, in the update script one should disable writing to 3 places, recovery, UBOOT, and TEE1, and also delete those images (just to be sure).
$ grep by-name 20-4.5.3/META-INF/com/google/android/updater-script
...
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/UBOOT");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/TEE1");
upHDX covers most of this, but not all. Also, upHDX updates kernel for HDX and signs it. For now I want to extract the existing boot.img for 4.5.3, compare to the one from the update, create a package to write 4.5.3 kernel via TWRP, and make sure that I can recover to a working kernel. Then I'll play with the actual updating.
I have a Redmi Note 1GB ram, 2 sims ( model HM NOTE 1S CT ) running ANDROID 4.4.4 MIUI 8.6.7.28 beta.
I'm trying to install TWRP onto it but keep getting the same error as shown below:
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (13408 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.563s]
finished. total time: 0.989s
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.425s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.534s
I've tried many different twrp versions but always the same error. Anyone help ?
Why you need to flash twrp.img to boot? When I did this part, it was done already.
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (13408 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.563s]
finished. total time: 0.989s
Click to expand...
Click to collapse
That,s just to check it. It should reboot the phone into twrp, but standard recovery is still there.
Even if I try to boot into twrp using the volume down/power button, standard recovery comes up.
Can anyone help ?
blankers said:
Can anyone help ?
Click to expand...
Click to collapse
What ROM are you on? If you are on a Custom ROM already, you can try to use TWRP manager to install.
Another option would be you flash another recovery, like PhilzTouch, and then a Custom ROM, then TWRP manager...
the 2nd command should work "fastboot flash recovery twrp.img"
in my case.its always working.i already try many times
1.flash stock miui rom using MIUI flash tool
2. flash twrp using fastboot "fastboot flash recovery twrp.img"
3. reboot
note : after flashing twp you need to execute "fastboot reboot" and miui/custom rom should boot normally
then reboot to recovery
i used twrp3.0.2
So I'm in a bit of a pickle regarding the encryption on my OP2. The problem is this, I rooted and installed a custom rom which I went on to encrypt using androids native encryption. I've since this installed a new rom but the encryption is still active when booting to recovery and my lock screen pin is required to get the phone to start, even when its a fresh rom install and full data wipe? I've eve tried replacing the recovery to the latest version of twrp through adb but just get the following:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (22032 KB)...
OKAY [ 0.576s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.600s"
Any thoughts?
Unlock bootloader
Sent from my ONE A2005 using Tapatalk
As a happy new owner of the Le Pro 3 AI Edition (x651?) I'm trying to install TWRP on this phone, but can't get the TWRP's for X720 to work.
Is someone working on a TWRP for the AI Edition, or is there perhaps another TWRP I might be able to get working?
Tried with Minimal ADB as well as Mauronofrio's tool.
Error from Minimal ADB:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery_twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (47052 KB)...
OKAY [ 2.002s]
writing 'recovery'...
(bootloader) Fastboot oem devices is unlock
FAILED (remote: size too large)
finished. total time: 2.032s
Don't flash anything from here on AI edition because it's on mediatek hardware and x720/727 is qcom, you will most likely break your phone.
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
akinkoff85 said:
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
Click to expand...
Click to collapse
Did you unlock the bootloader again? Or was it just a wipe
Is usb debugging turned on?
Perhaps revoke it and cycle it then test ADB again.
If so run ADB kill-server
Then run ADB reboot bootloader should work then.
Also did you get the prompt when you did ADB devices on your phone to allow connections to that device?
Seems like driver issue.
Search for
ualcomm-hs-usb-qdloader-9008-driver-64-bit
akinkoff85 said:
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
Click to expand...
Click to collapse
Hey I'm having the same issue. Did you get this resolved?
It’s 100% a driver issue
If you're using Windows 7 there's a known issue with drivers, use Windows 10
I tried for hours to unlock on windows 10. I could access the device in adb while the phone was on and as soon booted into fastboot, Windows 10 says there was no driver.
Disabled verified drivers in Win 10 and was able to install the drivers, but fastboot still couldn't recognize the oneplus.
ymDroid said:
I tried for hours to unlock on windows 10. I could access the device in adb while the phone was on and as soon booted into fastboot, Windows 10 says there was no driver.
Disabled verified drivers in Win 10 and was able to install the drivers, but fastboot still couldn't recognize the oneplus.
Click to expand...
Click to collapse
Quite strange that.
From a completely fresh win 10 installation I just plugged in my phone, install the OnePlus drivers, then activated USB debugging, allowed all drivers to be installed.
Added necessary ADB and fastboot files in a folder to C: and then typed ADB devices via powershell in that folder, got prompted to accept the device.
From that point fastboot worked and always has.
try this solution https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
-
This did the job for me.
Hi everybody.
I have same problem.
(The story):
Unfortunately default Lenovo TAB M8 8505x OS have multiuser and many unwanted def app. So I was not success to limit my girl's tablet. Then I tried on custom rom and used fastboot mode ( by keep DOWN+POWER keys ). after this command (fastboot reboot fastboot)my fastboot mode was disabled and I can not connect to my tablet . now this show the logo for a few seconds and then restart again. I searched on the web to how to enable fastboot mode again and not found anything. One person prefer to wait for recharge battery completely and then charge but it does not work. to So I need help immediately.
This is my list of commands I used :
D:\LENOVO TAB M8\platform-tools>fastboot devices
HGT6FPQP fastboot
D:\LENOVO TAB M8\platform-tools>fastboot getvar version-bootloader
version-bootloader: akita_row_call-622276bd-20220223142906-20220706021818
Finished. Total time: 0.003s
D:\LENOVO TAB M8\platform-tools>fastboot flashing unlock
(bootloader) Start unlock flow
D:\LENOVO TAB M8\platform-tools>fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 1.219s]
Writing 'boot' OKAY [ 0.470s]
Finished. Total time: 1.867s
D:\LENOVO TAB M8\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/24 (130096 KB) OKAY [ 5.518s]
Writing 'system' OKAY [ 1.905s]
Sending sparse 'system' 2/24 (128056 KB) OKAY [ 5.592s]
Writing 'system' OKAY [ 1.865s]
......
Sending sparse 'system' 24/24 (31296 KB) OKAY [ 1.241s]
Writing 'system' OKAY [ 0.482s]
Finished. Total time: 198.984s
D:\LENOVO TAB M8\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB) OKAY [ 1.271s]
Writing 'recovery' OKAY [ 0.472s]
Finished. Total time: 1.907s
D:\LENOVO TAB M8\platform-tools>fastboot flash cache cache.img
Sending 'cache' (128 KB) OKAY [ 0.016s]
Writing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.062s
D:\LENOVO TAB M8\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D:\LENOVO TAB M8\platform-tools>fastboot flash recovery twrp34.img
Sending 'recovery' (4562 KB) OKAY [ 0.163s]
Writing 'recovery' OKAY [ 0.069s]
Finished. Total time: 0.254s
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>fastboot reboot
< waiting for any device >
^C
As you can see , fastboot reboot fastboot was the last command I used and then my tablet restarted and fastboot mode disabled for ever. So turning off and then keeping Down+Power keys for going to fastboot not working
How can I enable fastboot mode again ?
M323 said:
Hi everybody.
I have same problem.
(The story):
Unfortunately default Lenovo TAB M8 8505x OS have multiuser and many unwanted def app. So I was not success to limit my girl's tablet. Then I tried on custom rom and used fastboot mode ( by keep DOWN+POWER keys ). after this command (fastboot reboot fastboot)my fastboot mode was disabled and I can not connect to my tablet . now this show the logo for a few seconds and then restart again. I searched on the web to how to enable fastboot mode again and not found anything. One person prefer to wait for recharge battery completely and then charge but it does not work. to So I need help immediately.
...
Click to expand...
Click to collapse
I am fairly certain you'd be better off asking in your Lenovo Tab forum, not here in the Oneplus 8 one.
Thank you Nimueh for your reply. I think the issue is not just for a model of cell phone.
Did you ever test this command in fastboot mode? : fastboot reboot fastboot
Why this command disabled fastboot mode ?
M323 said:
Thank you Nimueh for your reply. I think the issue is not just for a model of cell phone.
Did you ever test this command in fastboot mode? : fastboot reboot fastboot
Why this command disabled fastboot mode ?
Click to expand...
Click to collapse
No, that's not a command I've ever used, only JUST fastboot reboot
NO idea, sorry.
Romyo717 said:
This did the job for me.
Click to expand...
Click to collapse
Had this issue on my LG V30 unlocking the bootloader and this worked for me. Looks like a scam, and I'd uninstall it thoroughly after using it, but it did work! I also had to swap to a usb-2.0 hub to get the process I was doing to work so that might be useful.
Did you ever get it fixed?