Related
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Plz any developers help him
Sent from my Lenovo A6000 using Tapatalk
Find how to flash device with qfil in google
Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
Im on rr 5.7.3
- first i wipe data,dalvik,cache and system in twrp
- flash L2KK.zip
- reboot recovery and stuck at boot (lenovo powered by android)
i know i have to flash twrp for kitkat right? but i end up flashing something about partition because i wasnt giving attention. not my phone cannot go into recovery or fastboot. just a red notification light. i know this is my fault.
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
sasukay said:
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
Click to expand...
Click to collapse
nope
Irwan Fauzi said:
nope
Click to expand...
Click to collapse
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
sasukay said:
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
Click to expand...
Click to collapse
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Sloved
i have sent my device to service center.. thanks to everyone who trying to help me..
Irwan Fauzi said:
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
Click to expand...
Click to collapse
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
bvsbrk said:
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Click to expand...
Click to collapse
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
sasukay said:
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
Click to expand...
Click to collapse
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
bvsbrk said:
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
Click to expand...
Click to collapse
I can understand who you are talking about
No problem
I never considered myself above anyone so something
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
I would not suggest flashing a6000 s ROM on your new phone or you may end up like your a6000
Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
Don't you ever try to flash custom ROM that not supported for your phone
Hello everyone.
First of all i was on the beta program for android 10 until like Q4 but since i was't able to play DFFOO i decided to downgrade the OS back to the last official build, and that was the android 9 june/july build.
I followed everything on the essential website in order to downgrade and i got it right, sort of. Everything was working fine except for the fact that the phone just wouldn't update at all. it'd just throw me an error, not big deal i though, until android 10 came out and since i wasn't getting it on my phone on it's own i decided to sideload it and here we are
I also folllowed everyhting on the Essential's website except for the fact of using the last Pie build i thought it was not big deal (idk if that mattered) so everything went fine until the installation reached 94% and then it said: Installation complete (i thought it was weird but not much else) next thing i do is select reboot now and boom.
All i get now is the sound of windows if i connect it to my computer and the "Qualcomm HS-USB QDloader 9008" under the ports section in device manager, no ammount of holding and pressing buttons will make it come back to life, so i come here for help, worst case scenario i'll have to buy a new one (they're pretty cheap second hand)
I'm sorry to say this to you, but you are out of luck... The QDL mode is because of 2 reasons:
-Joined D- and GND on a stripped cable
-Bootloader corrupted.
The most common thing is the Bootloader was corrupted because of 2 files: hyp.mbn and rpm.mbn. Either was downloaded bad or was flashed but have issues on those 2...
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
In a post I made on Reddit I explain something about this issue, and what causes it. But without the Programmer and the Firehose, you can't recover the device.
Why would Andy Rubin not put out the Firehose when Essential is supposed to be a developer friendly phone!?!? Makes no sense.
IngJulian_RVLX said:
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
.
Click to expand...
Click to collapse
Do you think there is a possibility they will release them in the future eg when new model comes out or when support for PH-1 ends? Or are other manufacturers always leaked & not "official" leak? Suppose most leaks for other phones are from service centres, vice kinda answers my own question.
IngJulian_RVLX said:
I'm sorry to say this to you, but you are out of luck... The QDL mode is because of 2 reasons:
-Joined D- and GND on a stripped cable
-Bootloader corrupted.
The most common thing is the Bootloader was corrupted because of 2 files: hyp.mbn and rpm.mbn. Either was downloaded bad or was flashed but have issues on those 2...
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
In a post I made on Reddit I explain something about this issue, and what causes it. But without the Programmer and the Firehose, you can't recover the device.
Click to expand...
Click to collapse
Thanks for the quick reply, oh well, at least i didn't buy it at its 700 dollars lauch price.
i'd like to read that post though, mind sharing the link?
Noct1070 said:
Thanks for the quick reply, oh well, at least i didn't buy it at its 700 dollars lauch price.
i'd like to read that post though, mind sharing the link?
Click to expand...
Click to collapse
https://www.reddit.com/r/essential/comments/cku745/my_ph1_bricked_by_may_ota_qdledl_9008_and_its/
I did the same thing, and ended up in the same situation, so this is definitely a reproducible problem. Contacting Essential support in hopes that they're willing to fix... but from what I'm reading around the web it's not likely. ?
Just adding my two cents. I had this exact same issue and Essential reached out to me. Told me I could ship my phone to them and they would fix it. Low and behold, they did. At the cost of only shipping, we'll worth the wait to get the phone back.
I guess depending on warranty age and registering, retail vs eBay used purchase, etc
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Brotinger said:
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Click to expand...
Click to collapse
If you download the lmsa tool, plug in the tablet and go to recovery it will download the full stock firmware. Then you can find it c/program data/LMSA/downloads.
I did that then downloads magisk manager. Extract the boot.img from firmware and put in storage of tablet. Then used magisk manager and patch the boot.img it will tell where it is stored. Extract from tablet and put it in same folder as adb/fast boot. Then put tablet in fastboot and fastboot flash boot magisk-patched.img. then fastboot reboot. The will be rooted with magisk
I forgot. You must unlock bootloader to do this.
Dear 11mackey11,
thank you so very much for caring enough to share your knowledge with me!
So the guide I mentioned earlier is pretty much applicable for the newer model as well? What a relief!
I am also grateful for the hint on how to obtain the stock firmware. For all the dirty things I did to my devices in the past, it never became necessary to put the LMS-Assistant to use, but I will gladly change that now.
As soon as my device arrives, I will try to root it as you suggested and will report back how I fared.
Again, many thanks!
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Brotinger said:
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Click to expand...
Click to collapse
Hi. I just purchased the same tablet. I would appreciate it if you could write up a guide on this forum. It would be a help for everyone.
I'm not even sure how you unlock the bootloader on this thing!
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Tutorial
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I want to apply it to my device, have you tried this method?
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
b4nd0ler0 said:
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
Click to expand...
Click to collapse
thanks, I'm waiting for news from you. The tablet is sold very much in our country. like this in the world. I'm sure the developers will do something about this device.
b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I rooted my device with this method
this method doesn't work
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
This method is working!
Use the Official Lenovo website to access your original "rom" file and get the "boot.img" file.
Program: Lenovo Rescue And Smart Assistant https://lnv.gy/3d8FHLi
For an article on how to download the Rom file via the program, see here. (Step 3)
https://bit.ly/2yE1nQf
Good Luck!
adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
You did not enable Magisk Hide
mingkee said:
You did not enable Magisk Hide
Click to expand...
Click to collapse
That was it! Thanks! You're smarter & more helpful than Google!!! ))
Hi.
After i root the tablet, i tried to delete youtube and gdrive. Then i restart the tablet but it stuck in fastboot mode. Not booting.
i couldn't install stock rom. What i must do
I did this..
i patched the boot img from the lenovo program. and i like to shut down my devices when i dont use them and now i cant make it boot. im stuck in a bootloop and its says orange alert when i boot the device. i can only get into the fastboot menu. when i try to boot with vol + and power nothing happens and when i release it starts up again in a bootloop. i cant shut it down either. it just loops and loops. cant do the rescue thing with the program either.. anybody that knows how i can fix this?
I have an out of topic question regarding this tablet.
Can The Lenovo M10 Plus (2nd Gen) 10.3" TB-X606F Output Display via HDMI to TV ???
I tried using a powered USB-C to HDMI adapter to output/mirror the tablet to a TV, but it didn't work.
Brotinger said:
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Click to expand...
Click to collapse
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
unlock not possible
CMX939 said:
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
Click to expand...
Click to collapse
I have the same issue, "waiting for device" and adb dies.
I assume, the latest lenovo updates (Android 9) block unlocking.
The current! LMSA tool does not allow to restore an old separately downloaded firmware
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.
Howdy. Tried to root my OnePlus 8 Pro. First time trying such a thing... Having now bricked my phone into a boot loop, I'm pretty sure that the guide I followed missed an important step. It said to download the latest patch, extract it, then use magisk to patch it and flash it. I'm pretty sure that the part I missed was actually updating to that patch before flashing. So I have whatever latest patch that I didn't have the foresight to write down, but my original build was IN2025_11_C.33 . Am I boned completely and thoroughly or is there any hope of recovering? Thanks either way.
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
SomeRandomGuy said:
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
Click to expand...
Click to collapse
thanks!
dimlu said:
thanks!
Click to expand...
Click to collapse
In case you haven't sorted it yet - this is a great MSM guide which also links to the Windows drivers you need and the MSM tools for your device.
Good luck