Database Info

D2303 Bricked. Fastboot works, FlashTool doesn't

I have bricked M2 D2303. I don't know how it was bricked for the first time(it's not mine), but yesterday I temporarily resurected it by flashtool. It booted and worked few minutes on any system(i dont remember what it was) After trying to put customrecovery it started to bootloop.
Now Flashtool doesn't see this device anymore, but fastboot is stil alive. I flashed CM12.1 boot.img - it showed sony logo, android logo and then bootanimation(blue waves). After few more tries of flashing different images it doesn't start to boot, screen remains black. I searched for boot, system and userdata IMG packets, but I've found only this one: http://forum.xda-developers.com/xperia-m2/general/aosp-5-0-2-d2303-progress-t3073842
After flashing nothing happens. Fastboot still works, but flashtool doesn't.
I don't have any idea how to resurect it now...
I've never had any sony android device... My only ones were nexuses and Oneplus One.

Try repairing using Sony PC Companion...This may solve your problem

Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
{
"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"
}

Download the TWRP recovery and OmniROM or any other flashable ROM.
Flash the recovery through fastboot.
Reboot into the recovery, allow /system modification and install the ROM; reboot to system.
Then re-flash stock if needed.

Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.

wefhy said:
Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.
Click to expand...
Click to collapse
If the bootloader is locked you shouldn't be able to flash any .img file. It it isn't unlocked in order to flash a recovery the phone must have a kernel (Sony made them for KK) that supports the recovery in a separate partition. Stock Xperia phones don't. Flashing any random .img file I won't be surprise if the phone gets bricked, it isn't like in many other phones.
Anyway, to fix it you must be able to flash via flash mode. Flashtool when connecting a phone reports in the log which mode is enabled (if the phone gets recognized at all). So you can use it to see if anything is alive. If the flash mode is dead for any reason but fastboot still works you must a kernel for Xperia M2 flashable via fastboot, if any is available. That may reopen the flash mode and from there do a phone repair from PC Companion.
Oh, and as usual if you are in Windows be sure all USB drivers are correctly installed..

wefhy said:
Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
Click to expand...
Click to collapse
To repair your phone by using PC Companion you have to go to Support Zone: 1
Then follow the steps (sorry for the language i can't change it) : 2
3
I hope it will help you

Hope your Xperia will fixed bro,
Keep your spirit

@Miche1asso
Fastboot mode works, I'm able to flash any boot image.
Windows drivers are installed correctly because flashtool repaired this phone few days ago.
Wchich kernel to flash? Recovey-friendly one? It's for 4.4.4, but last installed system was lollipop. I am able to flash system via recovery on bricked sony device? On my Oneplus One it's impossible.
Or rather any original kernel to revive flashtool?
Unfortunately most of download links are dead :/
@tromine It would be better if my PC companion worked the same... Support zone shows nothing.
Edit: I flashed this kernel: http://www.android.gs/install-cwm-recovery-on-sony-xperia-m2-lte/ It's a progress - its shows sony logo again I tried few times to boot into recovery bu every time it stucked on sony logo. I pressed power off button (next to sim/sd) and left it for few minutes on c harger and... It booted into recovery (without any volume hotkey)
It looks like stock recovery on my oneplus or zenfone:
I am able to flash system using it? Only stock one or any?
O rather i should flash any other recovery?
Push zip file via ADB or any other way to tho this?
Or one question for everything: What's the fastest way to flash CM12.1 from there?
Edit: Nearer than farther Now I have CWM v6 on it But it still can't flash any system image
It says installation aborted; error in storage(...).zip; can't partition non mmbcblk device: /devices/msm_sdcc.2/mmc_host

Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.

wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
Wich flashtool do you use?

wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
A couple of things: Did you update PC Companion to the last release? It must have the option to repair the phone somewhere. I can't help much on that because I use the OS X version, but the option is there on one of the top menu.
Anyway, since you managed to flash a working kernel (with CWM) the phone isn't bricked. From there (the CWM) I would flash a full custom ROM which includes a kernel with CWM, obviously wiping everything (cache and data). The kernel must belong to the ROM to avoid further troubles. At that point hopefully the flash mode is restored. But even if it isn't from there with the last PC Companion repair the phone.
PS: I realize I messed up a bit writing in English in my previous post. But it seems you've got what I meant anyway.

I use the newest flashtool and PC companion downloaded from sony page. I updated them.
I searched few times, but my pc companioj just hadn't got repair option.
CWM wasn't able to flash anything(alwatys the same error)
Anyway... I installed flashtool on Linux Mint. It detected device immediately. As linux version is hardly outdated, it couldn't flash anything on this device(device list stopped on Xperia T/S - no M/M2) but somehow it unlocked my xperia.
When I next time tried to use flashtool on windows it just detected it and flashed stock.
Now I'm on 5.1.1 and everything works fine Thanks!

[RECOVERY][TWRP]TWRP 3.0.2-0 for HUAWEI TAG-L01 (P8 lite smart/GR3/Enjoy 5S)

{
"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"
}
Hi everyone, i've started developing for this device, don't worry about his name(he has different name in different country), if your device model numer is "HUAWEI TAG-L01" you can use this recovery
You can also if you have TAG-Lxx but if you install a zip that check device it will found a TAG-L01
Remember, first you have to unlock the bootloader or it won't boot!! see this thread
DOWNLOAD
INSTALL INSTRUCTIONS
-reboot into bootloader(you can using "adb reboot bootloader" or by pressing volume down and power and selecting fastboot mode)
-type "fastboot flash recovery recoveryimage" (i suggest to drag and drop your image to the console so you don't have to worry about folders)
-presso volume up and power for some seconds and select recovery mode, allow twrp to write system(to prevent stock rom to re-flash stock recovery)
Thanks to:
androidlover5842 for his help
SOURCES
device tree
vendor tree

V2
deleted boot partition from wipe menu(no need)
Changed device name to the real one(HWTAG-L6753)
Download is in the first post

twrp now root is must easy

can you port twrp for phicomm e653 4g

here your thing
View attachment build.zip

mac12m99 said:
Hi everyone, i've started developing for this device, don't worry about his name(he has different name in different country), if your device model numer is "HUAWEI TAG-L01" you can use this recovery
You can also if you have TAG-Lxx but if you install a zip that check device it will found a TAG-L01
Remember, first you have to unlock the bootloader or it won't boot!! see this thread
DOWNLOAD
INSTALL INSTRUCTIONS
-reboot into bootloader(you can using "adb reboot bootloader" or by pressing volume down and power and selecting fastboot mode)
-type "fastboot flash recovery recoveryimage" (i suggest to drag and drop your image to the console so you don't have to worry about folders)
-presso volume up and power for some seconds and select recovery mode, allow twrp to write system(to prevent stock rom to re-flash stock recovery)
Thanks to:
androidlover5842 for his help
SOURCES
device tree
vendor tree
Click to expand...
Click to collapse
Works excellent on Huawei GR3 TAG-L23

Hello guys dose this support GR 3 2017 model number PAR-LA1 ?

Aaron Turkman said:
Hello guys dose this support GR 3 2017 model number PAR-LA1 ?
Click to expand...
Click to collapse
No, it has a different cpu

mac12m99 said:
No, it has a different cpu
Click to expand...
Click to collapse
So bro where I can find a thread for my device I search XDA without result

Aaron Turkman said:
So bro where I can find a thread for my device I search XDA without result
Click to expand...
Click to collapse
Sorry but don't exist, no developer has created one

mac12m99 said:
Sorry but don't exist, no developer has created one
Click to expand...
Click to collapse
Thanks bro

Help!
Some recovery for the TAG-L13? The one in this post does not work for me on my device. Any suggestions?

EnriqueGlezMata said:
Some recovery for the TAG-L13? The one in this post does not work for me on my device. Any suggestions?
Click to expand...
Click to collapse
Have you unlocked bootloader first?

please help me
my phone p8 lite tag-L01 is dead total
my pc detect MTK USB PORT

mac12m99 said:
No, it has a different cpu
Click to expand...
Click to collapse
Hello guys dose this support GR 3 model number TAG-L32 ?

Diskiedinya said:
Hello guys dose this support GR 3 model number TAG-L32 ?
Click to expand...
Click to collapse
Yes, is the same phone.
Please tell me if not

mac12m99 said:
Yes, is the same phone.
Please tell me if not
Click to expand...
Click to collapse
can you tell me how to get into fastboot mode huawei gr3 tag-l32 ? pleaseee

I am having a problem and cannot find the source.
I have the L22 and have the correct code for unlocking and the phone reports "Unlock pass", factory resets and then reboots.
When I boot back into the bootloader and type "fastboot oem get-bootinfo", it reports "(bootloader) unlocked, not unlocked:yes. Once booted, developer options reports it is still unlocked.
I have attempted to flash a couple of versions of TWRP, they copy and all is reported fine, yet the phone remains on stock recovery.
Any ideas?
Thanks for any help, I'm stumped.
Found a solution: Do not reboot the phone via adb/fastboot, instead after flashing, hold down the power button to restart. Then you may enter TWRP/recovery in the normal manner. For some reason when you reboot via fastboot it does not work.

Hi ..sorry for late question..is this work for tag AL00??

Does it work on Huawei gr3 tag-l21

[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

My LG Q Stylo plus bricked, Please help save

Hi All,
Yesterday my LG Q Stylo plus was gone into black screen, and could not soft reset or hard reset. When I put it on charging, it vibrated again and again every few minutes, still with black screen. Then I opened the back cover, unplugged the battery to force it power off. Then I tried to factory reset it, but failed to start. Today I tried to flash it, but the PC could not detect the device even though I already downloaded LG driver. In this case, I can not flash it. And it showed on the screen said " FASTBOOT MODE.........". Please see attached picture. Anyone who know how to fix it please help me. Thanks a lot!
{
"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"
}

Can you get into recovery? If so, reset it in recovery or flash a new stock (or custom) rom onto it. In fastboot mode you may be able to directly boot into a custom recovery or flash a custom recovery if you need to.

I tried to flash a new stock rom on it. But PC could not detect the device, even though I already installed the driver. I tried to hold the power button with volume down key to reset it, it didn't work and the screen showed nothing but black. Only after the battery drained out, I plugged the charger on, the screen will be lit and showed the message like above picture showed. Is there any other way to let PC detect the device so that I can flash it?

If you're using Windows, maybe boot into a Linux Live USB (like linux mint for e.g.) and download adb and fastboot. Linux usually works all the time for me with fastboot, so try that and see if it can detect your phone. If detected you might have to run
Code:
fastboot oem unlock
which WILL erase your data, but you can't flash anything without doing so.

I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?

auroraguy123 said:
I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?
Click to expand...
Click to collapse
No. LOCK STATUS on Fastboot likely means the bootloader is locked to not allow custom images to be loaded. This is purely for security and can be unlocked by running the Fastboot oem unlock command I wrote about above. This wipes your data so that, no thief can steal your phone, unlock the bootloader, and browse your files with a custom recovery, as your data will be wiped. I'm not 100% sure but across the few phones in my life that use Fastboot, it has always meant the oem lock to prevent custom images for security reasons.
Any slowdowns occur either because battery saving scheme, full RAM, many processes running, malware, etc. Its not to do with Fastboot.
You should be able to see the device in Fastboot on Linux. Try and flash a custom recovery first, but it might not work because it's locked. In that case you'll need to unlock the Fastboot (which will erase your user data) and then flash a custom recovery, from which you can flash a new rom. Or flash stock recovery and load your official ROM zip if it's supported
Good luck, let us know if you have any issues.

as
quickishfm
said just connect your phone to computer and type
fastboot devices
if device is connected it will be shown on screen
after it just use command adb oem unlock
to unlock bootloader.
if you dont want to unlock bootloader then you will have to erase data partition by using command fastboot erase data

I downloaded adb and fastboot on Linux. But when I typed adb device, still can not see the device. What should I do?

You must type fastboot devices (or fastboot device, I can't remember ) when your screen is in that FASTBOOT MODE.
Once it's in there you just have to flash a custom recovery, or, unlock the bootloader first as we discussed before. This will wipe user data remember. After unlocking bootloader you can flash a custom recovery or stock recovery, and then a new ROM in recovery.

When the device is power off, after I plug it to pc usb, it will show charging sign on the screen and then go the fastboot mode as showed in the picture above. I checked the device manager it was connected as android bootlock inferface. But if I use adb device, there is no device is found.

Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?

auroraguy123 said:
Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?
Click to expand...
Click to collapse
There's no way to do that. It would not be secure if you could overwrite recovery if data is not deleted - then anyone could steal your phone, put a custom recovery and read data partition if not encrypted.
Maybe you can reflash a stock recovery zip (if you can find and if it let's you to flash) through fastboot, then go into recovery and sideload stock rom to your device. Most likely in this case the data will not be deleted.

Thanks. Why it showed unknowed command when I typed fastboot oem unlock?

Hmm, not sure, might have to look on Google. Does anything come up with
Code:
fastboot oem get_unlock_data
?

same when I typed fastboot oem get_unlock_data showed unknown command. Is there a way to let pc force the device to go to download moade because it stuck in the fastboot mode?

AFAIK the download mode is only a thing for Samsung, most other Android phones use fastboot as the download mode which flashes recovery etc.
Perhaps look online on ways to fix the unknown command issue... How did you install fastboot for the Linux?

Cn you run fastboot oem help, and fastboot --version please
Post the output here, thanks

I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.

auroraguy123 said:
I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.View attachment 5204225View attachment 5204225
Click to expand...
Click to collapse
That's useful, thanks. It seems the syntax has changed. Try
fastboot flashing unlock
to unlock the bootloader, and then you should be able to flash a custom recovery.
There's also update to directly flash an update.zip if you can find one, which might not need unlock boorloader. But this will likely have to be a stock update.zip signed by LG so no custom recovery or anything. I don't know if this will erase data.

I also run fastboot -w, it started wiping, but then failed as shown unknown command.