Database Info

Cannot enter Recovery mode

Hi... i tried to flash CWM and enter recovery mode a couple of times and not once am i successful. I keep getting a white HTC screen with red text "This build is for development purposes only, not to be distributed.. etc etc"
No matter which CWM i tried it just would not work... i noticed some people have this problem but no solution? Does the latest One S have some kind of block or something that does not let us run these images?

Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?

First person I have heard of not being able to flash recovery. Unlock bootloader. Then go to appstore and download goomanager. Download and flash TWRP thru goomanager.....done
Sent from my HTC VLE_U using XDA Premium HD app

Moved To Q&A​
Please post questions in the Q&A section​

azzledazzle said:
Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?
Click to expand...
Click to collapse
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right

onlinechi said:
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right
Click to expand...
Click to collapse
Yes, If it says unlocked then it is unlocked did YOU unlock it ?
Are the recovery images flashing successfully ? without any errors ? you could try and use adb to reboot in to recovery.
If that fails, You could try and fastboot boot recovery, You can flash almost anything this way

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get.... yes I did unlock it. Yes I did successfully flash. Its just when I reboot and enter bootloader and choose recovery... I keep getting that despite trying multiple images ... what is the meaning of that screen anyway... if we know what it does perhaps we can know what is wrong

--duplicate post--

That writing you see is normal, It happens as soon as you put non official software on the device. I cant figure out why it wont boot into recovery.
You could try to flash stock recovery,
Then fastboot erase cache.
Then reflash CWM and hope for the best.
Dont give up, Ill have a look around for some kinda fix for you !
EDIT: Also try Hasoons All In One Tool until i figure this out

when I click recovery in the bootloader... it shows that and just stays there.... may I know where the link is to a stock recovery as I did not back up mine...

https://dl.dropbox.com/u/69014495/stock recovery.zip
Does the phone boot ?
Did you try fastboot erase cache ?

Hi.. i tried flashing the stock recovery with Hasoons tool... I still get to the screen which shows... "this build is for development purposes only. Do not distribute.. etc etc..." Thats so strange. Logically it should should just show that for awhile then go on to the recovery isnt it? Why does it just stay there?
By the way.. how do i erase cache? Is it possible to be done without entering recovery?

I tried flashing the stock recovery. Locking the bootloader... then unlocking it all over again. Then flashing the CWM recovery... then boot to recovery.. still.... the same. :-(

so the phone does never boot ??
If i was you i'd run an RUU and start all over again

Oh no... the phone is perfectly fine.. its just the Recovery in to which its stuck. The normal operation of the phone is totally OK. I read something.. if i had flashed a recovery image... it should show my phone as "tampered" in the bootloader. Mine does not show that.. it just shows "Unlocked".. Is there something i missed?

Btw... i do not know if it matters.. but my phone is from Singapore.

it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.

I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.

jayelbird said:
I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.
Click to expand...
Click to collapse
How did you use Rom Manager when you dont have root?

azzledazzle said:
it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.
Click to expand...
Click to collapse
MMM.... Does not work.. I tried this
Boot into boot loader.. did the erase cache. Was ok. Did a reboot.
Reboot in to bootloader.. install recovery.. reboot
Reboot then attempted enter recovery.. still the same... Stuck at the red text
I then tried this
Boot into boot loader... did the erase cache.. was ok.. no reboot
Flash the recovery.. no reboot
Enter recovery.. still the same.. stuck at red text
Reboot.. enter recovery.. also the same.. stuck at red text...
:-( I have had HTCs.. Samsungs... and rooted all of em.. this is the first time i have been unsucessful.. heck i even rooted a China Device before....

Urgent Help, time constraint - to Stock for return

I've been at this for like 8 hours going in circles. I have about 12 hours to figure this out. I am scheduled to go back to TMO to return this phone. Please help me.
While trying to revert back to stock, upon boot, at first there is a green icon, then it turns red w/ an exclamation point and just hangs there. It seems to have booted into the recovery because where it hangs, if i touch the "home" button, it disappears and shows me the cwm recovery main menu with a few errors relating to unable to mount SD. Its a very gimpy CWM with more than half of the commands/functions missing. (see pics below)
This is what I am currently getting in order....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Boots to image 01
- Then to 02, here its trying to load/mount stuff, notice the SD icon and load bar near the bottom
- In 03 it looks like it ran into an error and hangs there
- Not sure why but I realized it boots straight into recovery. From 03, if i touch the home button I get 04. Notice all the stuff missing from cwm options
- 05 is what my HBoot / Bootloader looks like
-------------------------------
I am able to get back into HBoot / bootloader screen and can confirm that while in that mode the PC does recognize the device. But everything I flash does not work. When I run RUUs they seem to begin a process, but once that is done ( which isnt long), I would reboot but see nothing has changed. I tried to undo that stock recovery to access to NAND backups and start the process again but that Recovery doesn't have options for backups (strange?). Anyways, but can not flash another CWM successfully.
This is what I currently see when flashing a CWM now
c:\android-sdk\tools>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-vi
lle.img
sending 'recovery' (6616 KB)...
OKAY [ 0.969s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.210s
c:\android-sdk\tools>fastboot reboot
rebooting...
I am completely out of options now. I looked at all the stickies around here and other places but can not find anything that will work. I did my best to be as thorough as I can. Please let me know if there are more info that would help. Thanks ahead of time.

This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium

Chris Boyer said:
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.

enzyme said:
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
Click to expand...
Click to collapse
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium

These are the steps I took that led me here.....
1. flashed ville_recovery_signed.img via Fastboot from here
2. re-locked the bootloader with in fastboot
3. ran RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed from here that was from this thread.

http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app

Moved To Q&A​
Do not open question threads in the development section, thats what Q&A is for.​

Chris Boyer said:
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Yeah i have full control of Fastboot, just not always getting the desired final results. Yes I have the AIO pack and have tried to flash those recoveries w/o results. I mean from the log it looks like that did the trick but nothing changes after reboot, I can't get rid of the current Recovery.

stealthnoodle said:
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Click to expand...
Click to collapse
Steath! Now we are getting somewhere!
As I was going through the steps, I got the CWM from the AIO. That was before I had a chance to flash the 2nd time (step3), before I could get to the rest of the steps I allowed the phone to boot normal instead of HBoot, then it reverted back to the other recovery. But as of right now I did flash via AIO, cleared storage, factory defaulted, flashed via AIO again and now I am on step 5.
I am still sitting in the AIO CWM right now. The guide says to flash the UTB rom, which I am unfamiliar with and it appears like a custom rom. So what should I flash and what method should I use? Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty. Should I .....
- flash one of the RUUs via fastboot?
-rename the RUU and push it to the SD via ADB and flash via CWM (like in the guide)?
(not sure if that method works with customRom only or RUUs as well.

enzyme said:
Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty.
Click to expand...
Click to collapse
If you can mount your sdcard partition in recovery, you can then adb push a rom to it and flash it.
On your PC:
adb push yournewrom.zip /sdcard/
Then on your phone, in recovery:
Format system, data, cache
Flash zip from sdcard -> choose zip -> /sdcard/yournewrom.zip
Before you boot into the new rom, flash the boot.img (extract it from the zip) in fastboot.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot

Steath's advice led me to the guide and got me on the right track. Even with detailed instructions, I went in circles for awhile, but in the end I got it. I'm so relieved, its been a stressful 12hrs.
So now I just have one last question. Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice who knows, I'm still very new to much of it.

enzyme said:
Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice...
Click to expand...
Click to collapse
It is safe and common practice (and in many cases required to prevent bootloops) to extract the boot image from the rom you flash, and flash this boot image through fastboot.
Custom roms do not come with their own recovery (only their own boot.img). The only reason to extract a recovery from a RUU or OTA and flash it, is when you need to go back complete stock.
Edit: But if you want to switch to a different custom recovery, then yes, flashing it through recovery is safe and the proper way. (You just don't 'extract' it from anything.)

I'm really stuck getting recovery installed - please help?

Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch - don't get the 'amber LED' which various guides tell me to press Vol Down at.
I'm using
Code:
fastboot boot recovery.img
to boot the phone into recovery and
Code:
fastboot flash recovery recovery.img
to flash it, which hasn't worked at all. All of theTWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys

[snip]

TimTams said:
Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch. I'm using
Code:
fastboot flash boot boot.img
to write the boot images and
Code:
fastboot boot recovery.img
to boot the phone into recovery. All of the other TWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
Click to expand...
Click to collapse
I don't think your bootloader is unlocked because:
1: your device won't boot after flashing an image.
2: your rooting status says: bootloader unlock allowed.
(if unlocked, it says rooting status: bootloader unlocked)
Yes means it can be unlocked.
Unless you unlocked already and use drm fix because then it still shows yes but Im pretty sure your bootloader isn't unlocked.
BTW this thread belongs in Q&A section.
You can request a movement by hitting the small "!" triangle button underneath your post when viewing this page in a browser.
Sent from my E6653 using XDA-Developers mobile app

Thanks heaps - that sounds like it might be the issue, I'll have a play and post back here. It would explain why I've had so much trouble with what seems like a simple task
langeveld024 said:
I don't think your bootloader is unlocked
...
Click to expand...
Click to collapse
EDIT:
It looks like this was done correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure I want to go and have another crack at flashing a recovery... I couldn't seem to get any of them to work.

I've just followed this guide to installing recovery and it hasn't worked... I still just get stuck at the sony logo. Any ideas why? How do I know the recovery image linked is correct for my phone?
http://www.digitbin.com/unlock-bootloader-flash-twrp-root-sony-xperia-z5/

OK, I got recovery installed! Thanks to this guy: http://forum.xda-developers.com/xperia-z5/help/boot-flashmode-fastboot-t3457818
mentions what no other guide mentions...
I need to have a custom kernel before I can flash recovery (first mention of this I've seen)
The kernel I flash needs to match the firmware I have installed
With that, I had instant success.
EDIT:
And now I have managed to get a custom ROM installed at last My procedure was, for anyone that be stuck in a similar way:
If your phone already won't boot:
Download Flashtool and install it. I have mirrored it here as all the sources I found were very slow: http://noobs.wtf/uploads/flashtool-0.9.22.3-windows.exe
Go to the 'drivers' folder inside your Flashtool install directory (default C:\Flashtool\drivers) and follow the instructions to install the "flashmode" driver
Select XperiFirm within Flashtool and download the correct firmware for your phone - mine was "Xperia Z5 > Sumire > E6653 > Australia > Telstra AU > 32.2.A.0.253 / R5C"
Turn off your phone and boot it in flashmode - Insert USB while holding vol down until the LED is green
Once Flashtool has finished downloading your firmware, go back to the main screen and click the 'lightning' button to flash your phone with the new firmware that should show up in the list - leave all the options unticked. Wait for it to say 'complete - un plug your phone'
Your phone should now boot successfully
To install a custom ROM:
I was not able to access my SD card in any version of TWRP - so copy your ROM to the internal storage of your phone. I used v1.5.0 of THIS ROM successfully.
Copy v36 (or newer) of THIS KERNEL .zip file to your internal storage as well. (v32 and higher are in the google docs link) NOTE this must match the firmware version - v36 was the one I used because, as above, I re-flashed my phone with 32.2.A.0.253 from Flashtool. The appropriate versions are listed on that link
[*]Also download TWP-3.0.2-2-E6653.img (or newer equivalent) from that same link.
[*]Follow the instructions HERE to unlock your bootloader (and make sure your fastboot drivers are installed correctly)
[*]Reboot your phone and re-enter fastboot mode (vol-up while plugging in USB) you can issue the command 'fastboot oem unlock' and it will return 'already rooted' if it has been done correctly
[*]Now with your phone in fastboot mode, issue the commands "fastboot flash recovery TWP-3.0.2-2-E6653.img" then "fastboot boot TWP-3.0.2-2-E6653.img" to install and then boot into TWRP recovery
[*]Once in TWRP, go to "Install" and install first the Kernel, then install the ROM, making sure to do the wipes
For me, this completed the process of installing a custom ROM I was stuck on the lack of info around installing the kernal and whatnot.

TimTams said:
I was stuck on the lack of info around installing the kernal and whatnot.
Click to expand...
Click to collapse
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app

langeveld024 said:
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.

TimTams said:
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
Click to expand...
Click to collapse
Hmm maybe u should suggest the OP of those threads to add this information then.
I personally never read those guides lol[emoji14](not anymore at least, at some point I was learning about this like you as well, we all had to learn)
Sent from my E6653 using XDA-Developers mobile app

[Recovery] TWRP 3.2.1-0 for GPD XD Plus / XD+ Handheld MT8176

Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img

My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.

I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.

Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.

I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.

"fastboot reboot" worked perfectly for me!

Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64

So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..

LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/

Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings

Contact me in discord.

Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.

Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks

Lenovo TB-X605F Magisk Root

"warning this will wipe your data"
"warning make sure that the tablet matches the firmware TB_X605F_USR_S200065_1905280020_Q00332_ROW
1. download adb setup https://forum.xda-developers.com/showthread.php?t=2588979
and install it
2. download the TB-X605F firmware http://www.mediafire.com/file/1uo5eu6iuzx39cd/TB_X605F_USR_S200065_1905280020_Q00332_ROW.zip/file
3. on the tablet go to settings and enable developer options
4. enable oem unlock and usb debugging
5. plug the tablet into the computer with usb cable and check the box on the tablet that allows usb debugging
6. reboot into fastboot using "adb reboot bootloader"
7. once fastboot has loaded type "fastboot oem unlock-go" to unlock the bootloader
8. then on computer extract the zip file and look for boot image "boot.img"
"make sure you have usb debugging enabled in developer options"
9. once your tablet is set up, on the android system prompt click "Charging this device via usb"
then click "Media device MTP" to access tablet storage on computer
10. download the magisk.apk file http://www.mediafire.com/file/vinf7xswbir90yi/magisk.apk/file
11. once downloaded drag the "boot.img" in firmware folder to internal storage
12. open command prompt and type adb install "the directory of the magisk apk file"
13. once magisk is installed launch the app and go to install / install / Select and Patch a File and look for the location of the boot.img
14. magisk will patch the boot image and put it in the download directory
15. go into download directory and you will see magisk_patched.img
16. on computer drag the magisk_patched.img on tablet storage to the directory where you want it to be
17. open cmd on computer type adb reboot bootloader
18. type fastboot flash boot "the directory of the magisk_patched.img"
19. once flashed type fastboot reboot
20. once booted go into magisk if it asks to update manager then update it, once the updated magisk manager is installed go to install / install / Direct Install to update root

Hi,
great job!
Do you know if it is possible to flash a recovery?
Thanks

Bootloop when trying magisk root
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...

justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
What error did LMSA give you? The vol-up + USB-in combo is really touchy. Maybe give it a few more tries with LMSA.
Someone else had probs like this, but was able to boot into recovery using Pwr+VolUp+VolDown combo. If that works, see if you can factory reset.

justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
Did you try power+vol up+vol down, 10 seconds long? It reinitialize the tab.
Good luck, neighbour

Hello,
thanks a lot for you help, LMSA stuck a 67% with error "fail to rescue".
The good solution was from my french neighbour with "power+vol up+vol down" for more than 10s. I then got acces to recovery and go to fasboot mode to flash original boot.img.
I've been then able to use LMSA to rescue my TAB and it's back to life !
I just wonder why magisk's boot generated was wrong... I'll make some other try in the weekend to root my tab.
Thanks a lot.
Merci du Var !

justalone said:
Thanks a lot.
Merci du Var !
Click to expand...
Click to collapse
De rien / you're welcome.
I had the same issue at 67% with LSMA.
Before I rooted the Tab, I upgraded it to Android 9 in Settings/System. Then everything worked fine.
I hope your house is safe despite this crazy rain.

This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.

KrazyKlutt said:
This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.
Click to expand...
Click to collapse
There's a magisk_patched.img for that build over on this thread.

Yahoo Mike said:
There's a magisk_patched.img for that build over on this thread.
Click to expand...
Click to collapse
Thanks a million Mike! You’re the best ?
XDA can be a jungle sometimes, I though I did research but I missed both the root thread and the TWRP thread for 605F.
That would have saved my lots of time a headache haha , but I didn’t get a heart attack so it’s all good.
Anyway, the patched Magisk worked perfectly, and all is good , finally a working YouTube Vanced since my previous Xperia 2 tablet.
The only weird thing was the link issue from Lenovo’s recovery for the latest firmware, the full one, not the ota updates.
???

twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix, which i was trying to look for an official tree, but i mean we already have one and when you compile it, it produced a faulty recovery image and lenovo hasn't released a kernel source or device tree yet, but i hope i can get a fully working one

turboperson123 said:
twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix...
Click to expand...
Click to collapse
Try this TWRP for X605F. I've been using the "update" function with no problems.
turboperson123 said:
... lenovo hasn't released a kernel source or device tree yet...
Click to expand...
Click to collapse
Have a look at this post.
There are so many hardware variants of the M10 now, it's probably impossible for Lenovo to release reliable kernel source. There's now even an M10 that uses SDM429 (rather than SDM450). ...and the second gen M10 FHD Plus (X606F) will use the MediaTek Helio P22T.

hello i have a problem i do the adb install command but it say "Missing APK file" plz help me