Database Users

Possible working LG one click root tool.

Hey all I don't have an LG G4 but I have a G3 which just got a security update yesterday (trying to block root) which I rooted. I'm thinking that the two phones are pretty similar so it is worth a shot to try the same method on both. Is anyone willing to try my root script on their G4. Worst case scenario it doesn't work. But it won't brick anything. It is based on the LG one click root tool. If anyone is interested you can check out my post in the Sprint LG G3 forum here on xda. link
Thanks for the help.

l33tlinuxh4x0r said:
Hey all I don't have an LG G4 but I have a G3 which just got a security update yesterday (trying to block root) which I rooted. I'm thinking that the two phones are pretty similar so it is worth a shot to try the same method on both. Is anyone willing to try my root script on their G4. Worst case scenario it doesn't work. But it won't brick anything. It is based on the LG one click root tool. If anyone is interested you can check out my post in the Sprint LG G3 forum here on xda. link
Thanks for the help.
Click to expand...
Click to collapse
I tried, doesnt work. Gets to the part where I have to put it in download mode and nothing happens. Thanks for trying though :good:

painedglass said:
I tried, doesnt work. Gets to the part where I have to put it in download mode and nothing happens. Thanks for trying though :good:
Click to expand...
Click to collapse
Did you put your phone in download mode manually? It takes a minute after you enter download mode. Also if you enable daig mode in the dialer ##DIAG# or ##3424# it should automatically put you into download mode when running the script however you may need your SPC/MSL to enable diag mode.

Yeah, exactly as the script told me to. Hold the power button up and plug the usb cable in. Download screen pops up with a progress bar and nothing, all the while the command prompt says waiting (for the download to begin I assume) I left it like that for appx. five minutes so I popped the battery back out. I tried three times and
always the same result. Should I leave it longer?

painedglass said:
Yeah, exactly as the script told me to. Hold the power button up and plug the usb cable in. Download screen pops up with a progress bar and nothing, all the while the command prompt says waiting (for the download to begin I assume) I left it like that for appx. five minutes so I popped the battery back out. I tried three times and
always the same result. Should I leave it longer?
Click to expand...
Click to collapse
No sounds like you did it correctly. You may have to unplug the device once it enters download mode and plug it back in.
Did you check device manager to make sure that your phone is detected and what com port it is on?
If you see your phone in device manager try opening cmd and navigating to the directory where LG Root Script.bat is and run the following replacing the # with your com port number.
Code:
Send_Command.exe \\.\COM#
If it works it should show a # prompt. If that works then we should be able to root it. It is just a matter of playing with what commands we can and cannot run in download mode. When you are done you can type
Code:
LEAVE
and your phone will reboot.
As I mentioned earlier I don't have a G4 so things might be a bit different but not that much.

Its listed under portable devices.....not sure how to figure out the port thing though.
---------- Post added at 11:23 AM ---------- Previous post was at 11:12 AM ----------
Ok, my COM ports are 0004 or 0003 how do I enter the text into the command prompt? I copied and pasted the send command and after I put in lets say 0004 it will throw back "special command: Enter, Leave" and it sends me back to c:\ If you can walk me through this final step, we may get this.

painedglass said:
Its listed under portable devices.....not sure how to figure out the port thing though.
Click to expand...
Click to collapse
It should be listed under "Ports (COM & LPT)" If it isn't then your computer isn't detecting your phone correctly hence it getting stuck in download mode and not rooting.
OK just got your updated post. Use COM4 in the command not COM0004
Should look like
Code:
Send_Command.exe \\.\COM4
If that works do a ctrl+C to kill the command and run the following.
Code:
Send_Command.exe \\.\COM4 < installRoot
You should see about 4 or 5 hashs (#####) and then just wait about a minute or two, it will say a bunch of things and then tell you to reboot.

I also added enter after the COM#0004 then it threw up the "Enter/leave" as well as "USAGE: SEND_COMMAND.EXE [PORT]"

painedglass said:
I also added enter after the COM#0004 then it threw up the "Enter/leave" as well as "USAGE: SEND_COMMAND.EXE [PORT]"
Click to expand...
Click to collapse
get rid of the # and the 0's should look like this
Code:
Send_Command.exe \\.\COM4 < installRoot

This is a bit too advanced for me. I'm running windows 10 and I'm spinning my wheels here because there are no ports listed in my device manager. I keep copying and pasting but it does nothing. I'm Not sure what to do now. Maybe someone else with a bit more experience can help.

are we ok to post here think it worked
http://imageshack.com/a/img908/9774/V8jIv2.jpg
http://imageshack.com/a/img537/2502/XYIm5B.jpg

What does root checker say?
Poslano sa mog LG-D802 koristeći Tapatalk

l33tlinuxh4x0r said:
Hey all I don't have an LG G4 but I have a G3 which just got a security update yesterday (trying to block root) which I rooted. I'm thinking that the two phones are pretty similar so it is worth a shot to try the same method on both. Is anyone willing to try my root script on their G4. Worst case scenario it doesn't work. But it won't brick anything. It is based on the LG one click root tool. If anyone is interested you can check out my post in the Sprint LG G3 forum here on xda. link
Thanks for the help.
Click to expand...
Click to collapse
You now have your own thread here in the LG-G4 General section

looks like lg_root.sh not starting to work
somything wrong with rights?

gavo84 said:
are we ok to post here think it worked
http://imageshack.com/a/img908/9774/V8jIv2.jpg
http://imageshack.com/a/img537/2502/XYIm5B.jpg
Click to expand...
Click to collapse
What was verdict?? What carrier r u on
Sent from my VS986 using Tapatalk

Syrop said:
looks like lg_root.sh not starting to work
somything wrong with rights?
Click to expand...
Click to collapse
Yup, write protection is on just like the Note4 and other devices on lollipop.

The one click method adds viruses and Trojans to ur pc. Good luck
BAD ASS NOTE 4 & LG G4

Oh lord, please let this work. ?
Sent from my G4 whilst wishing for root

Windows 10 DOES NOT recognize LG devices properly in DL mode. I was just restoring a G2 to stock with LG Flash tool, it wouldn't recognize properly in 10. Went to 8 and worked beautifully. =

BACARDILIMON said:
The one click method adds viruses and Trojans to ur pc. Good luck
BAD ASS NOTE 4 & LG G4
Click to expand...
Click to collapse
Before you spout off, explain your comments. Show proof of the issue.

LeEco Pro 3 X727 stuck in fastboot

I'm banging my head and have been working on this for a few days now. I have an X727 that all of a sudden went into the death boot loop, and all I can get to is the fastboot screen. I can connect via fastboot and push flash files etc, but I cannot connect via adb no matter what I try. Device drivers are correctly recognized (Win10 x64) and all fastboot functions work. I successfully unlocked and rooted it after this happened (in order to push new images). This thing was bone stock beforehand.
I've tried flashing every version of recovery I can find and nothing works - I always either end up back in the loop (stock recovery) or in a screen with distortion (twrp). I've attached an image of what the screen looks like with the latest twrp recovery flashed.
I'm hoping anyone can help here, I'm just about out of ideas. Thanks in advance for your expertise!

Well I finally got the phone to be recognized in qfil mode and tried to force the factory ROM back onto it. The process, using FlashOne, appears to work, but the phone remains in an endless boot loop.
Anyone have any ideas? Really stuck here...
Thanks!

CltFlyBoy said:
Well I finally got the phone to be recognized in qfil mode and tried to force the factory ROM back onto it. The process, using FlashOne, appears to work, but the phone remains in an endless boot loop.
Anyone have any ideas? Really stuck here...
Thanks!
Click to expand...
Click to collapse
Before you had it only going fastboot what did you flash.
Sent from my SM-A730F using xda premium

mchlbenner said:
Before you had it only going fastboot what did you flash.
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Nothing - The phone was bone stock and started going into a boot loop, recovery did not work (when entering recovery mode it would exit after a few seconds and reboot). The only thing I can get to is fastboot. adb does not recognize the device at all, but fastboot does, as does the low level qfil drivers.
BUT - no matter what I push to the device it remains in the exact same boot loop. I cannot even get the (supported) TWRP to boot after I successfully flash it (either via fastboot, the Tool All In One util, etc). The boot loader is unlocked (I did that first before trying to TWRP it).
Any ideas at all before I buy another phone? REALLY appreciate the help!

I have same problem

Bumping, hoping for any traction here. I'm willing to try anything to get this phone working again (it's now a matter of principle).
I thought that the Qualcomm chipset was supposedly "unbrickable". If that's the case then I would love to understand where the failure point is...

Wish this reply was to help you, but I'm experiencing the exact same problem. Phone was acting a little laggy this morning. Turned it off and turned it back on. It shows LeEco, vibrates twice, and then loops again. Pressing Vol-Up brings it to a LeEco - RECOVERY screen, but it only sits for 2-3 seconds before rebooting again. Pressing Vol-Down brings it to fastboot, and that's about it.
I haven't gone so far as to install TWRP or anything, but this is a completely stock phone updated to 20S.
What the hell happened to our phones??
Is there any way to recover any of the data?

I hear you dude - thanks for the post anyway, there is something to be said for shared misery. FWIW, I never got the dang thing to respond. I let the battery fully drain (I left it in recovery mode then the low level mode as long as it would stay on, then let it sit for two weeks after that). Same thing - I can hit it with fastboot but NOT ADB, I can write flash files to it, it looks like I'm pushing TWRP correctly, but when I try to reboot into recovery - NADA. Just goes back into it's normal boot loop, never hits recovery.
I'm starting to wonder if there is a mechanical problem with the phones. Maybe a flex cable that eventually wiggles just loose enough to do this.
What I'd REALLY love is to find *any* answer - I can't stand a problem like this that never gets explained. So with that said, does *anyone* have *any* other ideas? I'm an electronics guy, I have rebuilt too many phones to count, etc - I can try whatever *valid* suggestions y'all might have.
Thanks for letting me rant, I LOVED this phone (and it's sister, bought exactly the same time, is still rock solid).
</soapbox>

CltFlyBoy said:
I hear you dude - thanks for the post anyway, there is something to be said for shared misery. FWIW, I never got the dang thing to respond. I let the battery fully drain (I left it in recovery mode then the low level mode as long as it would stay on, then let it sit for two weeks after that). Same thing - I can hit it with fastboot but NOT ADB, I can write flash files to it, it looks like I'm pushing TWRP correctly, but when I try to reboot into recovery - NADA. Just goes back into it's normal boot loop, never hits recovery.
I'm starting to wonder if there is a mechanical problem with the phones. Maybe a flex cable that eventually wiggles just loose enough to do this.
What I'd REALLY love is to find *any* answer - I can't stand a problem like this that never gets explained. So with that said, does *anyone* have *any* other ideas? I'm an electronics guy, I have rebuilt too many phones to count, etc - I can try whatever *valid* suggestions y'all might have.
Thanks for letting me rant, I LOVED this phone (and it's sister, bought exactly the same time, is still rock solid).
</soapbox>
Click to expand...
Click to collapse
Welp, I tried using FlashOne2.0 and QFIL to flash when I got the phone to Qualcomm 9008 mode. After trying it a few times, I got it to flash successfully. Same problem. Didn't help it one bit, FYI.
What I did notice was that the phone was a little laggy and warm so I decided to restart it. Do you think it's a heat issue causing solder to come loose from a chip? It's happened to a laptop before -- it could be causing our issues? Did your phone run hot? I have a dual layer case on mine so it did run hot sometimes...just spitballing some ideas.

That would definitely be a possibility - heat cycling causing an already suspect solder joint to fail is common. Granted, not as common with SMD devices or BGAs like the processors, but still, it happens. That would make a lot of sense too. I'd love to tear into it and look for physical problems - I just dread taking the dang screen off just to get to the insides, I can see me snapping the thing now...
I'm trying to repro the entire thing on a completely different computer - fresh drivers/everything. Will update if I see any success.

Well crap, no joy. Got very excited as QFIL looked like it worked (pushed le_zl1_qfil_ufs_fix), pulled the phone off the computer, booted, back into the same boot loop. Dangit.
I need to learn how to give up sometimes.

CltFlyBoy said:
I need to learn how to give up sometimes.
Click to expand...
Click to collapse
You and me, both. I tried every version of the qfil files I could find. No dice on any of them.
Not sure what else we can do at this point in time. The kicker is that I've had this phone less than a year but I can't find any way to contact LeEco USA. None of their numbers work and they haven't replied to any e-mails I've sent.

ME TOO
epikfone said:
you and me, both. I tried every version of the qfil files i could find. No dice on any of them.
Not sure what else we can do at this point in time. The kicker is that i've had this phone less than a year but i can't find any way to contact leeco usa. None of their numbers work and they haven't replied to any e-mails i've sent.
Click to expand...
Click to collapse
x727
i have the same problem
and it's a good phone to be losse
it happened with the phone after i make an update for android 9
if i have some novelty tell me, every day i have try doing something, and nothing works
flashone 2.0 almost all roms
fastboot i did not try yet ...
if have any news share please
grateful

I have the same problem to

Was anyone able to fix the problem? I got the exact same problem yesterday in the night. Out of nowhere it started vibrating twice and now it's stuck in this loop and with a "broken" white/black screen sometimes. No idea what to do.
On another note, is there anyway to access my files via fastboot?

I have the same problem last week and did same as everybody. Endless boot cycle even after QFIL and flashpro. I am certain it is a hardware issue.
I was using Lineage 16 and it ran hot so I put it on extreme battery saver and this helped the issue. I was just bout to change roms but been putting it off. I had it in the car next to car vent with heat blowing and google maps on. I noticed it was hot, not burn hot though. 4 hours later was using it and it had same graphical glitch problem. I'm sure it has to be disassembled and inspected, and maybe heatgun on a BGA chip or some flash memory.

That sucks! Well, I am pretty sure I am not going to be able to fix my phone, but do you know if there is a way to recover my files, using only fastboot and my pc?
Thanks!
ricecrispi28 said:
I have the same problem last week and did same as everybody. Endless boot cycle even after QFIL and flashpro. I am certain it is a hardware issue.
I was using Lineage 16 and it ran hot so I put it on extreme battery saver and this helped the issue. I was just bout to change roms but been putting it off. I had it in the car next to car vent with heat blowing and google maps on. I noticed it was hot, not burn hot though. 4 hours later was using it and it had same graphical glitch problem. I'm sure it has to be disassembled and inspected, and maybe heatgun on a BGA chip or some flash memory.
Click to expand...
Click to collapse

Count me in. Same issue. Have tried every QFIL. Every adb, fastboot, recovery, rom possible. All in one tools etc etc. There is something missing from the 727 for sure that no one has access to.

ampped101 said:
Count me in. Same issue. Have tried every QFIL. Every adb, fastboot, recovery, rom possible. All in one tools etc etc. There is something missing from the 727 for sure that no one has access to.
Click to expand...
Click to collapse
If you create a TauBao account ( free) you can have the phone repaired in China. The turn around time is 6 weeks. But apparently you pay $10 down and if the repair is simple resoldering ( most likely) it will cost $30 https://item.taobao.com/item.htm?sp...OXhfJ&id=559560190173&ns=1&abbucket=17#detail
No doubt it seems risky, but may be worth the risk, they seem legit to me and have a lot of positive feedback
Good Luck
PS Use Google translate

the same problem
interesante, exactamente me sucedio lo mismo, estaba utilizando lineage os 16 oficial y recibi una actualizacion, como no tenia bateria suficiente pospuse el reinicio y se apago por falta de carga, al encender me quedo en bootloop, el telefono entra a fastboot y se mantiene encendido, igual funciona con qfid y flashone 2.0, flash todos los archivos pero al reiniciar sucede el mismo bucle... algo me hace pensar que las tablas de particiones en la memoria flash estan corruptas y por eso a pesar de flash con exito, la particion boot o firmware esta dañado
CltFlyBoy said:
I'm banging my head and have been working on this for a few days now. I have an X727 that all of a sudden went into the death boot loop, and all I can get to is the fastboot screen. I can connect via fastboot and push flash files etc, but I cannot connect via adb no matter what I try. Device drivers are correctly recognized (Win10 x64) and all fastboot functions work. I successfully unlocked and rooted it after this happened (in order to push new images). This thing was bone stock beforehand.
I've tried flashing every version of recovery I can find and nothing works - I always either end up back in the loop (stock recovery) or in a screen with distortion (twrp). I've attached an image of what the screen looks like with the latest twrp recovery flashed.
I'm hoping anyone can help here, I'm just about out of ideas. Thanks in advance for your expertise!
Click to expand...
Click to collapse

Redmi Note 6 Pro Suddenly Bricked - Needs operation authorization ? ...

Somehow the phone went fully bricked.
No led wants to light up nothing is recognizing it except device manager as Qualcomm HS-USB QDLoader 9008 (COM3).
Click to expand...
Click to collapse
Only way i was able to get it to run into another boot loop was by fully charging it and attempting to press power on ... happened on occasions but software is damaged, so i can enter it into fastboot mode max.
It has some security system inside not letting me Flash it without an authorized account.
Click to expand...
Click to collapse
I tried to use everything i have found including Firehose , sadly in such a mode it is ineffective ...
My phone is not rooted, not flashed, i didnt try any hardware manipulation yet.
Are there any recommendation ?

Is your phone's bootloader unlocked? If yes and you are able to boot into fastboot mode than you can flash the factory ROM. If your bootloader is not unlocked you cannot flash any ROM. So, you have to bruteforce flash the factory ROM through 'EDL'. Good luck!

Nitin Rai said:
Is your phone's bootloader unlocked? If yes and you are able to boot into fastboot mode than you can flash the factory ROM. If your bootloader is not unlocked you cannot flash any ROM. So, you have to bruteforce flash the factory ROM through 'EDL'. Good luck!
Click to expand...
Click to collapse
Id need to glash it through EDL since my bootloader is locked.
I cant find any tutorial for it, other than being an authorized xiaomi user to fix it...

xer094 said:
Id need to glash it through EDL since my bootloader is locked.
I cant find any tutorial for it, other than being an authorized xiaomi user to fix it...
Click to expand...
Click to collapse
There are plenty of YouTube videos out there. You can search like this - " Redmi note 6 pro Test point edl flashing "

Nitin Rai said:
There are plenty of YouTube videos out there. You can search like this - " Redmi note 6 pro Test point edl flashing "
Click to expand...
Click to collapse
Okay, ill check it out, thanks :good:

xer094 said:
Okay, ill check it out, thanks :good:
Click to expand...
Click to collapse
Good luck! Don't forget to hit that thanks button if I helped you ?

Hello, I 'm facing the same issue, mine got bricked while I was installing the stock firmware. Now I'm getting following error.
https://ibb.co/nMpvcfL
Kindly update here when you'll find the solution. Thanks

Nitin Rai said:
Good luck! Don't forget to hit that thanks button if I helped you ?
Click to expand...
Click to collapse
Sadly, im still facing the same issue, i cant find any correct site/video where i could fix the phone ... im in EDL Mode but requires authentication to work ...
No Source ive found works without an authorized login

Problem solved....!
xer094 said:
Sadly, im still facing the same issue, i cant find any correct site/video where i could fix the phone ... im in EDL Mode but requires authentication to work ...
No Source ive found works without an authorized login
Click to expand...
Click to collapse
I removed the back cover and disconnect the battery. Under the battery ribbon there are three points. You have to short circuit two points while connecting the data cable. than press flash button and here you go. Problem solved. It will take 10-12 mins. watch following video
https://www.youtube.com/watch?v=dJ7EDizk5N0

forevrknight45 said:
I removed the back cover and disconnect the battery. Under the battery ribbon there are three points. You have to short circuit two points while connecting the data cable. than press flash button and here you go. Problem solved. It will take 10-12 mins. watch following video
https://www.youtube.com/watch?v=dJ7EDizk5N0
Click to expand...
Click to collapse
Yep, this is what I was talking about

forevrknight45 said:
I removed the back cover and disconnect the battery. Under the battery ribbon there are three points. You have to short circuit two points while connecting the data cable. than press flash button and here you go. Problem solved. It will take 10-12 mins. watch following video
https://www.youtube.com/watch?v=dJ7EDizk5N0
Click to expand...
Click to collapse
For me this process doesnt work, i get storsec.mbn error as it is flashing...
One of the suggestions from the video comments is written to try QPST, sadly this one isnt working with me ... or could be i havent found a good source for it.

Still not solved, getting storsec.mbn error

I had the same problem, need an authorized account to flash, so, before giving up, i contacted a russian guy who flashed my phone via teamviewer for 20 USD. Better than nothing I guess.

xer094 said:
Still not solved, getting storsec.mbn error
Click to expand...
Click to collapse
That means one of your phone's partition is corrupted
So you can try using a flash tool called "Qfil Fash Tool"
If qfil also doesn't work then try "EMMC DL Tool"
(With shorting the pins in the motherboard)
In these two tools you will get different modes of flashing. Try them out. Good luck!

felipetnk said:
Tive o mesmo problema, preciso de uma conta autorizada para fazer o flash, então, antes de desistir, entrei em contato com um cara russo que fez o flash do meu telefone via teamviewer por 20 dólares. Melhor do que nada, eu
Click to expand...
Click to collapse
RSOLVEU?

Lenovo Tab M10 FHD Plus (X606f) won't power on after flashing older ROM

I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again ?

I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.

ldeveraux said:
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
Click to expand...
Click to collapse
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.

python_rocks said:
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
Click to expand...
Click to collapse
assuming windows, check that your drivers are detecting the recovery module

ldeveraux said:
assuming windows, check that your drivers are detecting the recovery module
Click to expand...
Click to collapse
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?

python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch)...
Click to expand...
Click to collapse
Cool. Are you doing a Halium port for this device?

Yahoo Mike said:
Cool. Are you doing a Halium port for this device?
Click to expand...
Click to collapse
I'm not a Halium dev but I'm trying to flash the device. Me and another member of the community have our tablets dead after flushing it with supposedly Android 9 ROM. Not even Lenovo's Rescue Tool is helping now.

python_rocks said:
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
Click to expand...
Click to collapse
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.

ldeveraux said:
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
Click to expand...
Click to collapse
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.

python_rocks said:
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
Click to expand...
Click to collapse
Oh i misunderstood completely! That is worse, i have no clue how to fix it...

python_rocks said:
The tablet won't power on at all.
Click to expand...
Click to collapse
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.

Yahoo Mike said:
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Click to expand...
Click to collapse
Yeah, I've ordered opening kit. I'm going in. Quite a few people got their devices working by disconnecting the battery and connecting it back. I've noticed that no matter how long the
tablet is on charger the LED stays red, it doesn't change to orange or green.
This same problem has happen to two more members of the community. Same tablet.
We had to flag that ROM as it bricks the tablet.

python_rocks said:
We had to flag that ROM as it bricks the tablet.
Click to expand...
Click to collapse
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.

Yahoo Mike said:
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Click to expand...
Click to collapse
Thank you for trying to help.
The flash tool doesn't do anything when I click Download and plugging in the tablet while holding the volume down button. Dropdown option was set to "firmware upgrade" as advised.
The guide suggests that it's for people who can at least power on the device. It says "switch off the phone ..." which I don't need to do since I can't even switch it on

python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again
Click to expand...
Click to collapse
Did you mange to fix it?

A. Alaska said:
Did you mange to fix it?
Click to expand...
Click to collapse
You need to use a rework station heat gun or maybe a hair blow dryer might work to heat the sides of the screen to remove it.
I recommend cutting a water bottle in a square or rectangle shape then using the corner to slowly pry the screen off. After that remove the battery ribbon and hold the power bottom for 20-60 seconds to fully drain the charge.
Then recconect it and turn it on 100 percent works.
Just remember you must have the flash tool app and firmware ready in upgrade or download mode while holding down vol. It will reflash the tablet and bam will unbrick.

Just to note down my experiences here as well. I now also got into the same trouble. I tried
TB-X606F_S100015_191127_BMP.zip and also TB-X606F_S300091_201215_BMP.zip
It turns out that with these two you cannot start up the device anymore. Just as the thread-creator described. In my case pluging out and in again seems to give the SP FalshTool the chance to flash again (put it in "Download"-Mode before). So the latest firmware by today - TB-X606F_S300429_21110_BMP.zip - helped me to revive it again.
For me this is nice, but I also wanted to put Ubuntu touch on it just as described here: https://gitlab.com/ubports/community-ports/android9/lenovo-tab-m10-fhd-plus/lenovo-x606 ... unfortunately I am blocked now due to not being able to bring Android 9 on it. btw: There is no proposal on the site which firmware-version is even Android 9. I just guessed from the date.

55S434 Tcl android tv

I messed up my TV soft resets not bringing the screen back.
I set Secondary Display to 4k and it black screened now stuck in reboot mode.
It starts up and after Android tv logo it reboots a couple times then just suts black screened
There is not manual reset button.
Is there a recovery file that i can load onto a USB drive and use the Physical power button to boot the usb drive and recovery my tv or is it jacked?

Figured it out flashed to v662

Hypertext1 said:
I messed up my TV soft resets not bringing the screen back.
I set Secondary Display to 4k and it black screened now stuck in reboot mode.
It starts up and after Android tv logo it reboots a couple times then just suts black screened
There is not manual reset button.
Is there a recovery file that i can load onto a USB drive and use the Physical power button to boot the usb drive and recovery my tv or is it jacked?
Click to expand...
Click to collapse
where did you find firmware, could you share with me?
I think I got same model: 55S434
current version: v8-r851t02-lf1v458.018656
I am facing frame drop on 4k-60 fps, youtube or any other software so I think there may be bug with my version so I would like to rollback on some stable version.

Did you ever find this V662 firmware that works for the S434?

Hypertext1 said:
Figured it out flashed to v662
Click to expand...
Click to collapse
I'm glad you figured it out. Can you share details as to what you did? I've the same TV that won't boot, it's stuck on Android tv loading screen. What's the method to restore os via USB? Thanks

q-killer said:
I'm glad you figured it out. Can you share details as to what you did? I've the same TV that won't boot, it's stuck on Android tv loading screen. What's the method to restore os via USB? Thanks
Click to expand...
Click to collapse
yeah i had to download a flash to a thumb drive then plug it into the tvs usb port then hold the power button under the bottom middle while plugging in the tv and it goes into flash mode.
Just search the forums and you will find the info buried here and there they also have a Telegram chat channel which is helpful.

key words to search andriod tv google tv V662
telegram

Hypertext1 said:
key words to search andriod tv google tv V662
telegram
Click to expand...
Click to collapse
This site is more dev less how to i assume most members figure if you are not smart enough to read the forums and search it and figure it out on your own you have no business flashing your devices.
Notice no one responded to my ask for help i just figured it all out on my own in about 6 hours of research and then got a thumbs up.
REMEMBER you can brick your devices

Hypertext1 said:
yeah i had to download a flash to a thumb drive then plug it into the tvs usb port then hold the power button under the bottom middle while plugging in the tv and it goes into flash mode.
Just search the forums and you will find the info buried here and there they also have a Telegram chat channel which is helpful.
Click to expand...
Click to collapse
Awesome! Thank you so much for the reply! I found the telegram channel and obtained the update zip. TCL support wouldn't provide the steps to update, so thanks so much for the info! I actually accidentally hit the Netflix button which strangely got me out of the boot loop so I didn't have to restore after all. So glad it's working now!

q-killer said:
Awesome! Thank you so much for the reply! I found the telegram channel and obtained the update zip. TCL support wouldn't provide the steps to update, so thanks so much for the info! I actually accidentally hit the Netflix button which strangely got me out of the boot loop so I didn't have to restore after all. So glad it's working now!
Click to expand...
Click to collapse
awesome man glad ya didn't have to flash it but hey might as well mod it now!!!!

Anyone can post the before(if you still have) and after pics from the TV's 'Product Information'. The info required for us are:
-TCL Model Number: XXS434-XX
-Software Version:
-TV+ OS Version:
-PQ Version:
-Project ID:
-Model Code:
-Client Type:
-Kernel Version:
Thank you in advance, we all value your efforts here.