Hello everyone. Today, I was updating the edxposed magisk module, then rebooted the device and now I cannot use it because it asks for a password. I am on Lineage OS 17, using latest Predator Kernel with latest magisk. I have Orange Fox recovery installed, but the thing is that I cannot boot into recovery mode to format data. I powered off the device, pushed volume up and power button but it was booting in the os, again asking for a password. I tried booting an image of twrp from fastboot and it didn't work, the phone either booted into the os asking for password or just powered off. Now I am trying to flash stock miui latest global with miflash tool and when i click the refresh button a box appears saying "Invalid class". I have all the necessary drivers installed. This error does not make sense to me since I have flashed stock firmware in the past on lavender using miflash tool. I searched on the internet and found no solution and very little information about this error. I cannot believe it, all of that because of a freaking magisk module update, I regret so much the moment I tried to update that edxposed module!
Anyway, I really am desperate at this point, I don't have much experience and I have no idea what to do. If anybody knows of a way to fix these problems, please reply as soon as you can, as this is my main device! Any help will be greatly appreciated.
If you have a backup of the boot partition, you can simply install the image via fastboot using "fastboot flash boot boot.img" and that should fix it.
user0u said:
If you have a backup of the boot partition, you can simply install the image via fastboot using "fastboot flash boot boot.img" and that should fix it.
Click to expand...
Click to collapse
Hello, thanks for the reply. I tried flashing my boot image but it didn't work, it was still asking for password. I also tried "fastboot boot boot.img" and same result. What I want to do at this point is to make MiFlash tool work so that I can flash the stock rom. For some odd reason on my computer it showed that "Invalid class" error. But now I tried using MiFlash tool on my dad's old laptop, and everything seems to be working here, no errors. At the moment of writing this the stock rom is being flashed. Let's hope I will be able to boot into it.
Good luck
FilippPAOK said:
Hello, thanks for the reply. I tried flashing my boot image but it didn't work, it was still asking for password. I also tried "fastboot boot boot.img" and same result. What I want to do at this point is to make MiFlash tool work so that I can flash the stock rom. For some odd reason on my computer it showed that "Invalid class" error. But now I tried using MiFlash tool on my dad's old laptop, and everything seems to be working here, no errors. At the moment of writing this the stock rom is being flashed. Let's hope I will be able to boot into it.
Click to expand...
Click to collapse
FilippPAOK said:
Hi, did you solved the problem with invalid class? i have the same issue
Click to expand...
Click to collapse
Hello, I never found a solution to this weird error, but I didn't need to because I now use a different computer. I don't really know how to help you. I remember that back then it used to work fine but suddenly one day this error showed up out of nowhere. I don't know what caused it and there isn't much information about it on the internet. Maybe try putting the mi flash tool folder to different directories on your computer and see if that helps, try deleting it and redownloading it or check the log on the mi flash tool log folder. I remember that it didn't help me back then but maybe it helps you.
Elaborate a bit on the issue. What is your device? What did you do before the error started showing up? Try being a bit more specific and maybe someone else will help you.
If you have access to another computer, use that one as a temporary solution to flash your device.
Hi, thanks for the reply
I tried everything: Update windows, reinstall Net Framework, Reinstall MiFlash, use older or newer versions, Reinstall Drivers, use in different locations
I'm 99% sure the problem is not MiFlash but any component in Windows 10
Because I had other problems with other application with similar error
I have no idea, I don't want to format my computer...
My device is Dell E7240
DoMimik said:
Hi, thanks for the reply
I tried everything: Update windows, reinstall Net Framework, Reinstall MiFlash, use older or newer versions, Reinstall Drivers, use in different locations
I'm 99% sure the problem is not MiFlash but any component in Windows 10
Because I had other problems with other application with similar error
I have no idea, I don't want to format my computer...
My device is Dell E7240
Click to expand...
Click to collapse
Hello, sorry for the late reply. Unfortunately, I don't know how to help you. If you find a solution, please post it so that people who might have the same issue in the future know how to solve it.
Please, I also found this kind of problem on my desktop, invalid class when refreshing in the miflash tool. I am very sad
Related
So this is what happened, I was on I MedroM v3, so I was there was a firmware in beta (the 7.0 update) so I've done it and now I'm stuck in a bootloop
, I flashed the Nougat recovery so it locked my bootloader
and removed TWRP so I can't even go to flash the old rom
again. I also can't get the product id now cause I don't have an OS installed, there's no way to pull it without it an OS. I have tried every existing method possible and nothing (including the sd
card method with update.app and bla bla bla)
So I can't flash files through fastboot It says " Command not allowed"
Can somebody please help me, I have experience with flashing and everything but I in my entire life have not seen that a phone company so big doesn't have a ******** flashtool
or some other way of recovering hard bricked devices instead of buying a new motherboard or something..
If somebody could help me I would be so grateful! Please excuse my language I'm very mad and frustrated, I need my phone for work and now I'm offline..
- Fastboot is available but the bootloader is locked
- No TWRP
- No OS Installed
Download a firmware you want, extract the update.app and put it in sd card folder. From the phone completely shutdown, press vol +, vol - and power at the same time hold it until the updater with percentage progress moving appears.. you should be fine after that.. ? i believe. Maybe try it. That's what i did on my case
No, It says "Software Install failed! Incompatability with current software version"
When I go to eRecovery t says that it cant connect to WIFI.
As I said i tried every known method and I can't get it to work. Spent my whole day trying to fix it, I'm out of ideas
akseon said:
So this is what happened, I was on I MedroM v3, so I was there was a firmware in beta (the 7.0 update) so I've done it and now I'm stuck in a bootloop
, I flashed the Nougat recovery so it locked my bootloader
and removed TWRP so I can't even go to flash the old rom
again. I also can't get the product id now cause I don't have an OS installed, there's no way to pull it without it an OS. I have tried every existing method possible and nothing (including the sd
card method with update.app and bla bla bla)
So I can't flash files through fastboot It says " Command not allowed"
Can somebody please help me, I have experience with flashing and everything but I in my entire life have not seen that a phone company so big doesn't have a ******** flashtool
or some other way of recovering hard bricked devices instead of buying a new motherboard or something..
If somebody could help me I would be so grateful! Please excuse my language I'm very mad and frustrated, I need my phone for work and now I'm offline..
- Fastboot is available but the bootloader is locked
- I can't boot into TWRP
- No OS Installed
Click to expand...
Click to collapse
I had the same problem, but with the L31.
First try to use https://www.xda-developers.com/how-to-install-twrp/
Then with the file i send you attached (MAF32)
- Fastboot flash boot boot.img
- Fastboot flash system system.img
- Fastboot flash cust cust.img
- and finally TWRP
After that i puted the first exctrated uppdate.pp in my memory card and with the "3 buttons" process i flashed it. Then i repeated the same process with the second one (http://forum.xda-developers.com/hua...droid-nougat-dev-build-huawei-t3488360/page33). After this finished, again with the 3 buttons i made a factory reset.
5 minutes later, it was working.
i don't understand how to boot to fastboot ? and where to get these img files i am really stuck here pleaase
You don't understand, In order to unlock the bootloader i need the product ID which you get by typing some number combination in the dialer. I cant get to the dialer cause I dont have any OS installed, cause the old was dirty flashed. So thats why i cant flash TWRP etc..
hello, i'm using Huawei P9 Lite VNS-L21. i tried to flash the stock nougat Firmware Which i actually did and it worked flawless! but there was a little problem because there wasn't any Software update option in there, so after that i wanted to downgrade to stock MM. IDK what happened wrong while installing that, my phone got BRICKED. i don't have the Erecovery and twrp either. i cant flash firmware via DLOAD Method. the only thing i have is FASTBOOT mode..
i tried literally everything.. but nothing working..
I sent it to HUAWEI CUSTOMER CARE and they returned it back after a couple of days...
im really very worried because ive been using this phone for like 2 months ... and now im helplesss, If anybody is reading this please help/ assist me out of this.. i'd be really greatfull if anybody's going to help me out..
hash26 said:
hello, i'm using Huawei P9 Lite VNS-L21. i tried to flash the stock nougat Firmware Which i actually did and it worked flawless! but there was a little problem because there wasn't any Software update option in there, so after that i wanted to downgrade to stock MM. IDK what happened wrong while installing that, my phone got BRICKED. i don't have the Erecovery and twrp either. i cant flash firmware via DLOAD Method. the only thing i have is FASTBOOT mode..
i tried literally everything.. but nothing working..
I sent it to HUAWEI CUSTOMER CARE and they returned it back after a couple of days...
im really very worried because ive been using this phone for like 2 months ... and now im helplesss, If anybody is reading this please help/ assist me out of this.. i'd be really greatfull if anybody's going to help me out..
Click to expand...
Click to collapse
Why don't you flash TWRP in fastboot mode?
fasboot flash recovery recovery.img
PS: You need to start your own thread, really, rather than hijack someone else's
StrangerWeather said:
Why don't you flash TWRP in fastboot mode?
fasboot flash recovery recovery.img
PS: You need to start your own thread, really, rather than hijack someone else's
Click to expand...
Click to collapse
I'm new to this forum, if i did something that i shoud not I'm sorry about that and thanks for replying..
Ive tried many times to flash twrp recovery through fastboot it says installed but when i try to go to recovery there isnt any recovery...
i have a post with a same problem but with frp active, any sugestions?
hash26 said:
I'm new to this forum, if i did something that i shoud not I'm sorry about that and thanks for replying..
Ive tried many times to flash twrp recovery through fastboot it says installed but when i try to go to recovery there isnt any recovery...
Click to expand...
Click to collapse
What happens when you type : adb reboot recovery?
StrangerWeather said:
What happens when you type : adb reboot recovery?
Click to expand...
Click to collapse
Nothing happens it just reboots itself again n again but recovery doesn't open itself
hash26 said:
Nothing happens it just reboots itself again n again but recovery doesn't open itself
Click to expand...
Click to collapse
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
StrangerWeather said:
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
Click to expand...
Click to collapse
I'm about to do this! Thanks you
StrangerWeather said:
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
Click to expand...
Click to collapse
thank you so much for replying but there is something i want to ask you about..
the tool you told me about "SuperR's Kitchen" works on Linux.. and i'm a windows user is there any other software that runs on Windows and works as same as super'R ..
Waiting for your reply!!
hash26 said:
thank you so much for replying but there is something i want to ask you about..
the tool you told me about "SuperR's Kitchen" works on Linux.. and i'm a windows user is there any other software that runs on Windows and works as same as super'R ..
Waiting for your reply!!
Click to expand...
Click to collapse
Hi!
There is this but I haven't tested it: https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Let us know how it goes!
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
TWRP: https://dl.twrp.me/karate/twrp-3.1.1-1-karate.img
Gapps: http://opengapps.org/ (ARM64)
J.D.M said:
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
Click to expand...
Click to collapse
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Crolys said:
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Click to expand...
Click to collapse
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem. Remembering that in the site https://dl.twrp.me/karate/ has two versions of TWRP, the version twrp-3.1.1-0-karate.img is 32bits and the version twrp-3.1.1-1-karate. img is 64bit.
J.D.M said:
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem.
Click to expand...
Click to collapse
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Crolys said:
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Click to expand...
Click to collapse
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Crolys said:
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Click to expand...
Click to collapse
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
got same 255 error,just now i reflashed stock rom and issue resolved
vasu009 said:
got same 255 error,just now i reflashed stock rom and issue resolved
Click to expand...
Click to collapse
how did you reflashed the stock rom, please reply cause im stuck with the twrp and unable to do it. my phone doesn't have an os now
what s the password of the trwp
J.D.M said:
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
Click to expand...
Click to collapse
Can install this ROM on any Lenovo K6 Power device ??
dushd95 said:
Can install this ROM on any Lenovo K6 Power device ??
Click to expand...
Click to collapse
Yeah
J.D.M said:
Yeah
Click to expand...
Click to collapse
It says device not supported why??
Dont forget to reboot again into twrp - after flashing 64bit twrp . This is a step that is very important if you will not reboot your phone into twrp after flashing 64 bit twrp then , it will keep showin you the error 255.
So check that .
wacccim said:
what s the password of the trwp
Click to expand...
Click to collapse
Go for 3.2.1.0 it is better then 3.1.1.1 in 64 bits it ain't ask password i use it to flash all roms
Tere 3.1.1-1 asking for password to encrypt data
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Erase the data
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
Use erase the data from wipe option then you will be able to install rom and g-apps.
Every time you will need password, I don't know why but after erasing data you install all files otherwise you need to erase data again and again
Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
I Faced same problem. It's ok that your phone is in weird state for time now. And also possible to recover.
Hopefully you have adb-tool, custom-rom & gapp, twrp.img on your PC.
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
fastboot oem reboot-recovery
3)Wait for mobile to boot in to recovery mode with TWRP
Now need to flash custom-rom followed by gapps installion.
I) You can use pendrive with otg to flash custom-rom followed by gapps
OR
II)You can use phone storage/SD card to flash the custom-rom followed by gapps
OR
III)adb sideload command as fallow
a)In TWRP recovery on mobile, goto Adavanced->ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify custom rom path inside ""
adb sideload "C:\adb\images\MyCustomROM.zip"
Have a patience to complete the operation.
Click back for Adavanced Menu again.
b) Select ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify Gapp path inside ""
adb sideload "C:\adb\images\open_gapps-arm-7.1-pico-20180611.zip"
c)Have a patience to complete the operation.
Once complete go to TWRP Screen.
d)Now go back TWRP main menu & select wipe->format Data.
Go to Reboot->system.
How to install TWRP if no OS there
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
a) To check the device is connected to PC or not
fastboot oem device-info
b) To flash the recovery. Give twrp path inside the ""
fastboot flash recovery "C:\adb\images\twrp.img"
c) To boot into recovery mode
fastboot oem reboot-recovery
---------- Post added at 10:03 PM ---------- Previous post was at 09:57 PM ----------
[/COLOR]
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
In my case, It worked with PIN.
Alright so where i'm at now is basically the aftermath of a failed attempt to install a cyanogen unofficial rom for my phone.
I have a p9 lite VNS-L23 dual sim and well basically, i unlocked the bootloader and i rooted it with twrp and installed superuser using the srk tool. Everything worked fine up to this point until i booted into recovery, cleared cache and data etc to do a clean install and the install failed with an error code 7.
I thought doing a twrp backup before the flash was effective but because it didnt take any length of time, i sort of thought it definitely wasnt a full backup but i didnt pay it any attention and tried to flash it anyway since iv'e never had probs flashing anything with other of the phones ive had before which was my main mistake.
Usb debugging was enabled before trying to flash. I thought it failed because i didnt change my file system but i had no idea how to do that so i avoided it and tried to install a newer version of twrp to see if the rom would work with the updated version instead. When flashing the twrp img file, it asked where i wanted to install and i think i selected bootloader instead of boot cause there were only 2 options.
After than finished and i chose to restart in recovery, recovery never loaded. I was getting erecovery but that couldnt help me either. I was just stuck with no os and a phone stuck on the bootscreen. I tried to unbrick my phone by installing the update file for the international version firmware which i downloaded which was the only one not to fail after trying 2 others before it before realizing the error i was making. I read online that it would restore my phone back to ofw and that was great considering i had no os installed. Now, after the update, i think i reached like 100% then it went blank. I tried to wait a couple seconds to see if it was rebooting but nothing happened. tried all button combinations with and without the charger for varying lengths of time but no luck. I hear a sound when its connected to my laptop tho so idk if that matters. Its a bit frustrating right now and i have no clue how to fix this problem and i havent even had the phone for a long time. If someone. anyone can help me, id more than appreciate it
So far, nothing is responding to anything. No lights, no vibrations and i dont see anything when it conencts to my laptop, my laptop just makes the connected sound. I see Fastboot 2.0 detected but the srk tool cannot detect any emulators or devices :/ im so depressed at this point. More or less just bought the ****.
Sounds bad, try using the dload method and if that doesn't work you are ******.
What is the output of "fastboot devices"
vidra said:
Sounds bad, try using the dload method and if that doesn't work you are ******.
What is the output of "fastboot devices"
Click to expand...
Click to collapse
its the dload method that has me in this mess. It didnt reboot from the upgrade and since then i think ive been in fastboot mode. I get a response with the fastboot devices cmd and i manage to flash the boot, recovery and system of the stock firmware but still no luck. Think my only option is to use dc phoenix but i cant buy credits for that
bessonster said:
its the dload method that has me in this mess. It didnt reboot from the upgrade and since then i think ive been in fastboot mode. I get a response with the fastboot devices cmd and i manage to flash the boot, recovery and system of the stock firmware but still no luck. Think my only option is to use dc phoenix but i cant buy credits for that
Click to expand...
Click to collapse
Have you tried flashing MM with dload?
vidra said:
Have you tried flashing MM with dload?
Click to expand...
Click to collapse
not getting to the upgrade screen with dload, the phone restarts but nothing on screen. I can use fastboot only to flash and unlock bootloader, check specifications but thats it. I flashed the stock image which is mm thru fastboot but no luck. I read that i might wait for my battery to drain since my battery isnt rly made to be removable. Can i still use dload without any on screen response?
Have you also tried flashing vendor, cust ... partitions ?
vidra said:
Have you also tried flashing vendor, cust ... partitions ?
Click to expand...
Click to collapse
Fastboot doesnt flash certain img's such as xloader etc, no vendor img included inside the update but i doubt i'd be able to flash it anyway, but i flashed everything i was allowed to incl. cust, boot, recovery, system, cache, . Everything else is giving error: command not allowed. I've hit a brick wall so far til my battery drains or i take it to a repair shop which is i guess, last resort. Can't seem to find help anywhere on the internet, nothing returns anything to the screen.
Looks like a hard brick, take it to an official repair shop. But remember: unlocking the bootlader does NOT void the warranty.
Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!
You should just be able to install matiek form my understanding
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.
peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.
holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!
I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW