I have the Idol 3 6039K (Dual SIM) model with latest firmware, Rooted and with TWRP Recovery 2.8.7.0 flashed on the phone.
Everything is working fine, only I have noticed that "Reboot to Recovery" via a software command is not working. Instead of rebooting into recovery my phone does a normal system reboot. Not a big issue but I wonder if others have the same problem.
Details:
- Phone: Idol 3 model 6039K with latest firmware 5.0.2 build 01006
- Fastboot commands restored following instructions in this thread and rooted by booting the TWRP recovery image using fastboot and installing UPDATE-SuperSU-v2.46.zip file using TWRP.
Following commands are working from android terminal after entering "su" or from windows command prompt using adb:
- "reboot" => Phone reboots system as expected => OK
- "reboot bootloader" => Phone reboots in bootloader => OK.
- When phone has booted into bootloader the fastboot commands are working as expected => OK.
Booting into TWRP Recovery is working by turning OFF the phone and pressing Volume UP + Power buttons at the same time.
Reboot to Recovery from inside TWRP is also working.
Only the following is not working from android terminal or from windows using adb:
- "reboot recovery" => Phone does not reboot in TWRP Recovery but does a normal system reboot as if only "reboot" is entered.
- Also Reboot to Recovery using applications like Titanium Backup or Quick Boot app results in a normal system reboot instead of reboot to recovery.
Questions that I have:
- Can somebody let me know if the "reboot recovery" command is working on his/her phone?
- Has anybody an idea what could be the reason that reboot to recovery is not working on my phone? Could it be related to the firmware version that I use or could there be another cause?
Thanks in advance for any feedback or ideas.
Maybe my opening post was too long?
Could somebody with a rooted Idol 3 phone tell me what happens after typing the following 2 commands in a command line shell:
su
reboot recovery
The phone should reboot into recovery mode, but my phone does a normal reboot.
Hey Ho...
My Idol 3 also boots up in system by "fastboot recovery".
To go into recovery with stock firmware , rootet, i used the "ndr utils" from Playstore.
Now i´m on CM12.1 .... and have the "recovery boot" option in pomermenu
neutrinobox said:
My Idol 3 also boots up in system by "fastboot recovery".
To go into recovery with stock firmware , rootet, i used the "ndr utils" from Playstore.
Now i´m on CM12.1 .... and have the "recovery boot" option in pomermenu
Click to expand...
Click to collapse
Thanks for your reply. Btw, as far as I can see "fastboot recovery" is not a valid command.
Command "adb reboot recovery" from windows command prompt works for 2 other Android devices that I have (Samsung Galaxy Gio and Asus TF303K tablet both reboot in recovery mode), but my Idol 3 6039K reboots in system.
Some more experiments that I did:
- Went back to the original Stock firmware 5.0.2 build 01006 including stock recovery => reboot recovery command results in reboot in system
- Installed NDRutils from Playstore and selected "Reboot to Primary Recovery" => reboot recovery command results in reboot in system
I suspect that Android apps simply make use of the /system/bin/reboot binary that is included in the stock firmware. If this binary does not support reboot in recovery mode, Android apps can also not initialize a reboot to recovery mode. It looks to me that "reboot recovery" is simply not supported by the reboot binary that comes with the stock firmware. Maybe it has worked with earlier firmware, but the reboot binary that comes with the latest firmware does not seem to support it.
Is there anybody out there with an Idol 3 phone for who "reboot recovery" is working? If so, please let us know!
Hello CornelisJ,
which file did you use to restore the fastboot commands? The 6039S?
Gesendet von meinem 6039K mit Hilfe von XDA Forums
Maulschelle said:
Hello CornelisJ,
which file did you use to restore the fastboot commands? The 6039S?
Click to expand...
Click to collapse
Indeed for restoring the fastboot commands on my 6039K with firmware 5.0.2 build 01006 I have used the files for the 6039S.
(see opening post of this thread for the download link).
Related
I want to update my nexus 5 version 4.4 to 4.4.2 however i have a big problem when using TWRP to make a backup of my system, my current system is:
From fastboot mode
Name: hammerhead
Variant: hammerhead D821
HW Version: rev_11
Bootloader version: HHZ10X
Baseband version: M8974A-1.0.25.0.17
Kernel version: 3.4.0-g9ab14ba
KRT16M
If I press BACKUP from TWRP the phone will restart with a message: No commands
Here if i press the power and volume up buttons there appear few options: reboot system now, apply update from ADB, wipe data/factory reset, wipe cache partition (NOTHING related to TWRP i supose).
If from the (power + volume up + volume down) menu I select Recovery mode, again the phone restarts and i get same screen, "NO COMMANDS".
The device is rooted and working properly but on version 4.4 i also have SuperSU Pro v1.85 installed.
For flashing i used this: theunlockr.com/2013/11/06/root-nexus-5-cf-auto-root-method-video/
The applications that i "consider" that could give any problems are: Xposed installer, ROM Manager, Titanium Backup, Greenify.
Is there any solution to this "No commands" thing?
PS: i woudnt like to flash stock again to lose all my data + apps. Anyway, if i had to flash stock again, how would i keep all apps and data i currently have ? Could Titanium backup do that ?
You're on stock recovery that's why. Not sure how it came back but it did. Will need to flash it again to backup your rom
Sent from my Nexus 10 using Tapatalk 4
y2whisper said:
You're on stock recovery that's why. Not sure how it came back but it did. Will need to flash it again to backup your rom
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Lol how can it still be in stock recovery if i am root user... damn...
kenjyholy said:
Lol how can it still be in stock recovery if i am root user... damn...
Click to expand...
Click to collapse
Root and custom recovery are two different things. If you want to upgrade to 4.4.2 just fastboot flash the system and boot image from the 4.4.2 factory image. If you want to get twrp back, fastboot flash the twrp image.
jd1639 said:
Root and custom recovery are two different things. If you want to upgrade to 4.4.2 just fastboot flash the system and boot image from the 4.4.2 factory image. If you want to get twrp back, fastboot flash the twrp image.
Click to expand...
Click to collapse
I was following this forum.xda-developers.com/showthread.php?t=2557523 [ROM] [STOCK] Android 4.4.2 KOT49H - Rooted/Busybox/Odexed (12/10/13)
But i stopped in Instruction 1 since i wanted to backup everything i had in case of fail. I think i can install 4.2.2 following that guide WITHOUT doing a backup of my system, but question: If i install 4.2.2 successfully will bootloader be unlocked so i can backup my system with TWRP, AFTER i install 4.2.2 ?
The main issue is that i want to upgrade to 4.2.2 but i dont wanna risk on breaking the system and ending up into an endless "No command" loop... Thats why i want to do a backup first.
kenjyholy said:
I was following this forum.xda-developers.com/showthread.php?t=2557523 [ROM] [STOCK] Android 4.4.2 KOT49H - Rooted/Busybox/Odexed (12/10/13)
But i stopped in Instruction 1 since i wanted to backup everything i had in case of fail. I think i can install 4.2.2 following that guide WITHOUT doing a backup of my system, but question: If i install 4.2.2 successfully will bootloader be unlocked so i can backup my system with TWRP, AFTER i install 4.2.2 ?
Click to expand...
Click to collapse
Bootloader will be unlocked if it is now. But if you don't have twrp installed now you'll have to install it first to flash that rom
And rfbrow
jd1639 said:
Bootloader will be unlocked if it is now. But if you don't have twrp installed now you'll have to install it first to flash that rom
Click to expand...
Click to collapse
I have twrp installed but when I want to do a backup of my atm rom I get the no command error :s now I am even doubting if the bootloader is flashed properly
kenjyholy said:
I have twrp installed but when I want to do a backup of my atm rom I get the no command error :s now I am even doubting if the bootloader is flashed properly
Click to expand...
Click to collapse
If I were you I'd fastboot flash the twrp image again. See if that gets your recovery back
jd1639 said:
If I were you I'd fastboot flash the twrp image again. See if that gets your recovery back
Click to expand...
Click to collapse
OK, how do I do that? Is there any guide around?
kenjyholy said:
OK, how do I do that? Is there any guide around?
Click to expand...
Click to collapse
Assuming you don't have the path to ADB defined, just browse to the folder where you have adb installed.
Copy and paste the recovery image here (latest I think is openrecovery-twrp-2.6.3.4-hammerhead.img).
Then hold the "Shift" key and right click inside the folder. You should see an "Open command window here" - click that.
Once the command prompt opens, restart your phone in fastboot, connect it to your computer and type "fastboot devices". This should return something like "List of devices" and a number underneath that will not make any sense to you - but it's telling that you have the fastboot drivers correctly installed and your phone is detected.
You can now start flashing the recovery image. You do that by typing "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" and hitting enter. You should see some progress going on, and then telling you that it finished.
Still on the command prompt, type "fastboot reboot-bootloader". This should restart your phone in fastboot mode, and your new recovery should now be active. You can open it now using the volume and power keys.
morphvale said:
Assuming you don't have the path to ADB defined, just browse to the folder where you have adb installed.
Copy and paste the recovery image here (latest I think is openrecovery-twrp-2.6.3.4-hammerhead.img).
Then hold the "Shift" key and right click inside the folder. You should see an "Open command window here" - click that.
Once the command prompt opens, restart your phone in fastboot, connect it to your computer and type "fastboot devices". This should return something like "List of devices" and a number underneath that will not make any sense to you - but it's telling that you have the fastboot drivers correctly installed and your phone is detected.
You can now start flashing the recovery image. You do that by typing "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" and hitting enter. You should see some progress going on, and then telling you that it finished.
Still on the command prompt, type "fastboot reboot-bootloader". This should restart your phone in fastboot mode, and your new recovery should now be active. You can open it now using the volume and power keys.
Click to expand...
Click to collapse
Thanks dude this solved my issue, i could successfully do my backup, gona try to flash 4.4.2 next days.
Solve command recovery problem
It is not an error at all. When you are in the recovery screen with "no commands", while holding power button press volume up once. Then you'll get the recovery options. Hope it helps, I found that solution on official google support forums
kenjyholy said:
I want to update my nexus 5 version 4.4 to 4.4.2 however i have a big problem when using TWRP to make a backup of my system, my current system is:
From fastboot mode
Name: hammerhead
Variant: hammerhead D821
HW Version: rev_11
Bootloader version: HHZ10X
Baseband version: M8974A-1.0.25.0.17
Kernel version: 3.4.0-g9ab14ba
KRT16M
If I press BACKUP from TWRP the phone will restart with a message: No commands
Here if i press the power and volume up buttons there appear few options: reboot system now, apply update from ADB, wipe data/factory reset, wipe cache partition (NOTHING related to TWRP i supose).
If from the (power + volume up + volume down) menu I select Recovery mode, again the phone restarts and i get same screen, "NO COMMANDS".
The device is rooted and working properly but on version 4.4 i also have SuperSU Pro v1.85 installed.
For flashing i used this: theunlockr.com/2013/11/06/root-nexus-5-cf-auto-root-method-video/
The applications that i "consider" that could give any problems are: Xposed installer, ROM Manager, Titanium Backup, Greenify.
Is there any solution to this "No commands" thing?
PS: i woudnt like to flash stock again to lose all my data + apps. Anyway, if i had to flash stock again, how would i keep all apps and data i currently have ? Could Titanium backup do that ?
Click to expand...
Click to collapse
ok guyz
I have this phone (with CM11S updated) since a month and finally, only from yesterday, I managed to get access to the fastboot command.
Via windows 7-64 there was no way do do this.
I've installed a windows 8 virtual machine and it works fine.
Installed adb+fastboot
downloaded bacon image (renamed twrp.img)
installed universal naked drivers
downloaded supersu zip
I followed the classic procedure to root the phone and
http:
//s29.postimg.org/nwypa3lfr/Catturaz.png
as per the screenshot, the result seams to be "OKAY", but when I reboot on recovery, I have already the original and unrooted "simple recovery"; then I cannot install supersu
why the hell !!!
Settings > About phone > Tap on Build number 7 times to enable Developer options.
Then go back to Settings > Developer options > disable Update recovery with system updates
Holy Cow!!!1!!
I think i've solved
I think just have solved, by a simple trick:
No needed to flash the recovery; simply when in fastboot, do not flash the recovery but reboot loading the new (and temporary) recovery. Whit this simple trick you are able to install the supersu.
then summing up:
enter on the command line adb reboot bootloader
(wait for a second and on the phone screen appears ###fastboot...)
enter on the command line fastboot boot twrp.img
(wait 5 to 10 seconds and appears the teamwin bacon recovery)
press install and load the supersu zip previously loaded on the phone
reboot
enter on the supersu app and DEselect "Respect CM’s root Policy"
et voilà
Of course the teamwin recovery is NOT installed on the phone and you already have the OLD simple recovery , but the phone is rooted and YOU HAVE THE POWEEEER!!!1!
luasso said:
Holy Cow!!!1!!
I think i've solved
I think just have solved, by a simple trick:
No needed to flash the recovery; simply when in fastboot, do not flash the recovery but reboot loading the new (and temporary) recovery. Whit this simple trick you are able to install the supersu.
then summing up:
enter on the command line adb reboot bootloader
(wait for a second and on the phone screen appears ###fastboot...)
enter on the command line fastboot boot twrp.img
(wait 5 to 10 seconds and appears the teamwin bacon recovery)
press install and load the supersu zip previously loaded on the phone
reboot
enter on the supersu app and DEselect "Respect CM’s root Policy"
et voilà
Of course the teamwin recovery is NOT installed on the phone and you already have the OLD simple recovery , but the phone is rooted and YOU HAVE THE POWEEEER!!!1!
Click to expand...
Click to collapse
that won't keep the custom recovery forever though mate. you need to fastboot flash recovery recovery.img
Artem said in another thread that you have to go into developer settings and uncheck the update recovery one. then you can flash the recovery and it will stick permanently.
BTW: it works on windows 7 64bit for me. i have the full sdk installed though.
MontAlbert said:
that won't keep the custom recovery forever though mate. you need to fastboot flash recovery recovery.img
Artem said in another thread that you have to go into developer settings and uncheck the update recovery one. then you can flash the recovery and it will stick permanently.
BTW: it works on windows 7 64bit for me. i have the full sdk installed though.
Click to expand...
Click to collapse
That's an option I unchecked before doing everything. That's why I have not replied to Chromium.
And i've tried also with the SDK complete installed on Win7.64.
It doesn't work for me; I dont know why (yet), but by now with this workaround i'm satisfied.
By the way, the OnePlus One is a very goooood phone
I flashed the cos13 signed full ROM thru twrp 3.0.2-3 by tugapower. After successfully flashing it, I noticed that my recovery goes back to cos recovery, twrp was gone and also rot access. Halp halp halp. :crying:
Hi,
I suggest you to do this :
- Boot your phone to the OS => Settings => Developer options.
- untick "Update Cyanogen recovery", tick "Advanced reboot"
- long press on the power button, the boot menu will appear and then, press reboot => reboot to bootloader.
- the phone will enter in fastboot mode
- download an official TWRP image (prefer the latest one) => https://dl.twrp.me/bacon/
- put the downloaded file in a adb or minimal adb folder and than flash it to your phone though fastboot commands
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
After fastboot flashing TWRP, type the command below.
adb reboot recovery
Sent from my SM-S767VL using Tapatalk
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
JR44 said:
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
Click to expand...
Click to collapse
After flashing TWRP, you can't let the device boot to any other mode, you have to boot directly to recovery. If you allow the device to boot into any mode other than recovery, it will revert back to stock recovery. The only way to keep TWRP is to boot directly into TWRP immediately after flashing.
Try this, flash the TWRP file using the fastboot flash recovery (name of file) command. Then, after it flashes, try using this command:
fastboot boot recovery (name of your specific file)
This may allow you to boot into TWRP and keep TWRP recovery so that you can boot into it at any time after that.
Sent from my SM-S767VL using Tapatalk
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
JR44 said:
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
Click to expand...
Click to collapse
I don't know, I'll keep looking, if I find anything useful, I'll post it.
Sent from my SM-S767VL using Tapatalk
Still not working
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
JR44 said:
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
Click to expand...
Click to collapse
Odin is for Samsung devices only. You can't use Odin on your device.
Sent from my SM-S767VL using Tapatalk
I was able to get the device rooted with the magisk boot image patch method, but I was seeing if I can get twrp?
turboperson123 said:
I was able to get the device rooted with the magisk boot image patch method, but I was seeing if I can get twrp?
Click to expand...
Click to collapse
Could you link me to the method you used for root please?
Sent from my God Mode 8
Hi
I'm highly interested too. Could you share the method please?
Do you manage to install twrp?
Thanks!
Hello,
How do you do to unlock bootloader.I was able to download and patch with magisk the last ROM but I can't flash it !
Please would you tell us how you do that ?
Thanks
here is the link https://forum.xda-developers.com/ge...agisk-root-t3992477/post80692227#post80692227
Thank you !
go to settings and enable developer options, then go to developer options / enable usb debugging and enable oem unlock
then on pc if you have adb and fastboot installed then type adb reboot bootloader
then once the tablet is in fastboot type fastboot oem unlock-go to unlock the bootloader
TWRP 3.3.1-0 TB-X605F Lenovo Smart Tab M10
i used the twrp port from stock recovery method here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
"warning this will wipe data, bootloader needs to be unlocked, computer has adb and fastboot installed"
1. download twrp from here http://www.mediafire.com/file/tn7csi4gzm91w7v/twrp-3.3.1-0-X605F.img/file
2. then on the tablet go to settings / Developer mode / usb debugging
3. connect the tablet to pc with usb cable then on the tablet you will see usb debugging authorizations, click on allow always to make the device debuggable
4. on pc launch command prompt then type "adb reboot bootloader" to reboot into bootloader
5. once in bootloader type "fastboot flash recovery "the directory of the twrp-recovery.img" once flashed then type "fastboot reboot"
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here http://www.mediafire.com/file/ndhe4ewlzlffdur/Disable-dm-verity-forceencryption.zip/file then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Working fine from my side
Turbo, many Thanks!
It works perfectly ! ?
turboperson123 said:
i used the twrp port from stock recovery method here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
"warning this will wipe data, bootloader needs to be unlocked, computer has adb and fastboot installed"
1. download twrp from here http://www.mediafire.com/file/tn7csi4gzm91w7v/twrp-3.3.1-0-X605F.img/file
2. then on the tablet go to settings / Developer mode / usb debugging
3. connect the tablet to pc with usb cable then on the tablet you will see usb debugging authorizations, click on allow always to make the device debuggable
4. on pc launch command prompt then type "adb reboot bootloader" to reboot into bootloader
5. once in bootloader type "fastboot flash recovery "the directory of the twrp-recovery.img" once flashed then type "fastboot reboot"
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here http://www.mediafire.com/file/ndhe4ewlzlffdur/Disable-dm-verity-forceencryption.zip/file then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Click to expand...
Click to collapse
Good job, @turboperson123 ! @Monpseud0 pointed me over here.
I've got some time this week & I'm going to start on a version that will handle encryption. You can find the device tree and code here. I've included a link to this thread.
I bricked my device. Rebooting the system from TWRP only gets me back into TWRP.
Am afraid I will have to flash a new rom.
Does anyone know where to download a working rom for TB-X065F
Help much appreciated.
stefankkl said:
I bricked my device. Rebooting the system from TWRP only gets me back into TWRP.
Am afraid I will have to flash a new rom.
Does anyone know where to download a working rom for TB-X065F
Help much appreciated.
Click to expand...
Click to collapse
Easiest thing to do is use LMSA. It's available on Lenovo's support page: https://pcsupport.lenovo.com/au/en/...r-list/component?name=Software and Utilities.
Still unable to re-flash stock ROM
Yahoo Mike said:
Easiest thing to do is use LMSA. It's available on Lenovo's support page:
Click to expand...
Click to collapse
I can download the ROM through LMSA, but not flash it.
Trying to do so yields a "complete" message from LMSA after only a few seconds, but then rebooting the device only gets me back into TWRP.
I also tried to flash all system_xx.img from the ROM using fastboot flash system system_xx.img ,
and to flash all vendor_xx.img from the ROM using fastboot flash vendor vendor_xx.img.
Fastboot performs this operation, but then rebooting gets me back into TWRP again.
Trying to reboot the system from TWRP yields the message "no system installed"
Help much appreciated.
stefankkl said:
I can download the ROM through LMSA, but not flash it.
Trying to do so yields a "complete" message from LMSA after only a few seconds, but then rebooting the device only gets me back into TWRP.
I also tried to flash all system_xx.img from the ROM using fastboot flash system system_xx.img ,
and to flash all vendor_xx.img from the ROM using fastboot flash vendor vendor_xx.img.
Fastboot performs this operation, but then rebooting gets me back into TWRP again.
Trying to reboot the system from TWRP yields the message "no system installed"
Help much appreciated.
Click to expand...
Click to collapse
Tough one! Try this. It will wipe your data partition, though.
If it will let you, power down the tablet for about 10mins. Then boot into TWRP. Go to "Wipe" and swipe for Data/Factory Reset. Reboot.
If the M10 still won't boot, in TWRP re-format Data (by typing 'yes' under Wipe->Format Data), and wipe cache and Dalvik Cache. I think dalvik is under Wipe->Advanced. Factory reset again. Reboot.
As an absolute last resort, you might try fixing permissions in TWRP under "Advanced". But I don't think that's going to do much, because you haven't booted the ROM successfully yet.
Hope one of these works for you. Let us know what worked for you. If nothing works, PM me and we'll try some other things.
Lenovo Logo THEN black screen -- DEAD
turboperson123 said:
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Click to expand...
Click to collapse
I followed the instructions but on the last step of rebooting to system the device restarts, shows the Lenovo logo then it goes to a black / blanks screen. It appears to have shut down. I must hold the power button for several seconds before it wakes up (or restarts?) and does this all over again -- shows the Lenovo logo then black screen.
For the record the device was already rooted with Magisk. I was just trying to do a TWRP backup but found /data mounting errors so tried following steps 6 & 7. At the moment the device refuses to boot up. I am unable to get back into Recovery Mode. The ONLY thing i can do is get into FASTBOOT mode and issue commands from CLI.
The following hardware key combos produce the same results -- tablet turns on to show the Lenovo logo, after a few seconds the screen goes black (the device appears to have turned off):
x Power key
x Power Key + Volume Down
x Power Key + Volume Up
x Power Key + Volume Up + Volume Down
** Release of keys is done once Lenovo logo appears
Any ideas?
UPDATE
I went ahead and performed: fastboot flash boot boot.img << the boot.img was the earlier patched magisk image i used to get the rooted working tablet.
After performing the above the tablet turned on and is now showing the Lenovo logo however it does nothing else --- it remains on the logo forever. I am able to get into TWRP recovery. I went ahead and wiped Dalvik, Cache, and Data. Rebooted to System but still it is stuck on the Lenovo Logo.
The device if fully charged.
crosis99 said:
I followed the instructions but on the last step of rebooting to system the device restarts, shows the Lenovo logo then it goes to a black / blanks screen. It appears to have shut down. I must hold the power button for several seconds before it wakes up (or restarts?) and does this all over again -- shows the Lenovo logo then black screen.
Any ideas?
Click to expand...
Click to collapse
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.
Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.
Yahoo Mike said:
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.
Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.
Click to expand...
Click to collapse
Thanks for the response. Yes mine has the Snapdragon 450. I will investigate the LMSA. Been messing around all day but made no progress -- not even QPST is working out.