Related
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
same problem here and cant find solution ...
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Flash the latest su and your fine.
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
did that but my adb says no devices or emulators?
jo4mvp24 said:
did that but my adb says no devices or emulators?
Click to expand...
Click to collapse
Make sure your on charging mode and you have adb debug enabled
send the adb reboot recovery command as soon as the twrp connects to the computer. as soon as you hear it connect to the computer it should work if your drivers are working.
charlieb620 said:
Make sure your on charging mode and you have adb debug enabled
Click to expand...
Click to collapse
how do i do that when phone stuck on encryption unsuccessful screen?
exactly my issue
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
This method WORKS!!!! Same situation happened to me. THANK YOU 500x!! you saved my brick!
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
This works 100% thank you so much. Just have patience as it has to be at the right time....WORKS WORKS WORKS!!!!!
Help
Can someone explain the commands and how to do this please thanks in advance
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
epr2175 said:
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
Click to expand...
Click to collapse
What screen are you stuck in? Do you have adb up and running?
Same as before Encryption unsuccessful. I was able to do the trick, got into two and wiped data. Then rebooted to system and it went right back to that screen. I've tried 100 times or so to get back into twrp with no luck. I hear the computer recognize the device when it goes into twrp for 2 seconds after you click reset. Not sure if that means add is up and running or not.
jessiemougeot said:
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
Click to expand...
Click to collapse
Well it booted then got stuck on the lg boot screen again. Adb does not recognize my device, can only boot into Fastboot. Fastboot does see my device, tried lgup, lg bridge, and lg update none see my device, tried relocking bootloader after oem lock bootloader rebooted said my device was corrupted and shut itself off went back into Fastboot unlocked bootloader again and back to the same lg screen help?
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
---------- Post added at 02:06 PM ---------- Previous post was at 01:11 PM ----------
crazyc78 said:
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
Click to expand...
Click to collapse
Now I don't even have the encryption screen it just reboots back to TWRP very frustrating!!
fixed!
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole process step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
This option works!
SyHusky said:
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
jay_h_jacob said:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
Click to expand...
Click to collapse
No problem!! Also I forgot to add I only rooted afterward and didn't try to install a ROM or anything. I would think you risk danger with some ROMs without that decryption thing turned off. So maybe in the short future there will be better fixes.
Hello,
before I get into detail with my current problem at hand, I want to say that I'm extremely new to flashing/rooting my tablet and in most cases am very dependent on guides and how-tos. That being said, I've search through this forum among others in order to get my problem solved but had no success so far. So your expertise is basically my last resort and hope.
I have a Lenovo Yoga 2 1050L, as stated above, and tried to root it yesterday using this guide. Unfortunately, I messed up when it came to the system's image from the custom ROM because I downloaded the original firmware for the 10'' version L instead of the further below mentioned recovery firmware in step 3 (though that link was dead anyway). Moreover, I also included the recovery.img in the custom flash process and not only the system.img and I think the error occurred while flashing the recovery partition.
Long story short, the flashing process failed and I was left with a non-booting tablet.
The status-quo is I can boot into the bootloader mode (power button + volume down) where it'll say "normal boot", "recovery mode" etc. at the top with the android figure lying on the ground with an open stomach.
With the help of the Fastboot Tethered Recovery Launcher I can use the T3 option to change the device status to "fastboot-online". From what I understood I can then enter recovery mode if pressing volume up (so I can do a data/cache wipe) but it says
"could not open sys/devices/virtual/backlight" and I couldn't figure out what that's supposed to mean or how I can solve it.
I also tried to flash it again with the stock rom downloaded from here with the Intel Phone Flash Tool 4.4.4.
But that always failed at the "fastboot -s <device> oem wipe ESP" operation. It failed to execute that command resulting in a timeout only to try it once again. After that second attempt ended in a timeout too, it went on to the next step "fastboot -s <device> oem start_partitioning" but that also failed, ultimately making the whole flash process fail.
The curious thing (for me, anyway) was that I could flash the boot.img, system.img and recovery.img individually (by going to "Custom Flash" in the Phone Flash Tool and then selecting only one of those images) and all three processes succeeded. However, I only got the success message on the Phone Flash Tool, the tablet itself got stuck during the first reboot during or after the flash process.
In fact, every boot/reboot results in the tablet being stuck at the display of the Lenovo Logo. Nothing happens after that, it just stays there.
This happens whenever I try to boot normally or boot straight into recovery mode (Power + Volume Up). The only way I can boot my tablet and actually do something with it is the bootloader mode (Power + Volume Down) but as stated above, from there I didn't manage to get anywhere else so far.
Another thing I have tried is to enter fastboot mode because I read that I can also recover from there. But whenever trying to enter fastboot mode the tablet's display goes black, then a small text says "Fastboot starting..." and that's it. Nothing happens after that, no additional text or new screen.
What I also noticed is that whenever the tablet reboots itself or if I try to boot/reboot it, the tablet is not in the list of available devices anymore if I enter "adb devices" or "fastboot devices" in my command line (with connected tablet). Only when I redo the process with the Fastboot Tethered Recovery Launcher (option T3), can I access the device with those commands again (at first I could access it with "adb devices", later on only with "fastboot devices" and to be honest, I don't know why that is).
I actually just want to wipe the data of the tablet and install the stock ROM again because I think there's just some corrupt data that keeps my tablet from booting normally. But right now I don't even know how to do that because everything I've tried so far didn't work. Not even starting the tablet with the so-called "hard reset" (Power + Volume Down + Volume Up) worked, I only got a black screen in that case.
Because I tried to solve this problem myself all day yesterday, my tablet is now also down to about 20% of battery and I don't know if I can charge it up without a proper ROM installed (probably not). So that's another factor that's hindering me from trying out other steps.
I know this is a lot of text but I still hope there's someone out there who can help me with my problem. I am at my wit's end and would highly appreciate anyone who has knowlegde about this situation with this tablet helping me.
Best regards and thank you in advance
XShunyaX
Hello
I bricked my M3 and tried using Huawei Tool to unbrick it.
I followed all the instructions, and realized that the bootloader needed to be unlocked. I unlocked it and since then, I can't enter Fastboot mode.
I've tried pressing Vol - and power and it's stuck in a loop where it tells me
"Your device has been unlocked...
Your device is booting now"
And then it doesn't move.
Am I screwed?
Thanks a bunch
My device is a BTV-W09
I saw many of the same symptoms and I showed the same symptoms.
At this time, there seems to be no recovery method.
Same symptons as you. I guess the fastboot partition wiped itself after unlocking so there's no way else to get in anymore.
Same here: unlocked bootloader than flashed TWRP (maybe not the right one) and now the TABLET power ups for only 3 seconds with the message "Your device has been unlocked...Your device is booting now" and then it shuts down!!
Anyone could suggest me how can I return to fastboot mode to try to relock the bootloader?
Thank you very much!!!
(I tried VOLDOWN+POWER / VOLUP+POWER with and without USB cable connected with the PC but after 3 seconds of warning message it shuts down!!)
Anyone could help?
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
ETOSoft said:
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
Click to expand...
Click to collapse
Volume up + Hold Power for 3-4 Seconds during the locked boot. When the screen goes blank let go of both and it should go into recovery like it was supposed to. You have to let go though at the right time. I unbricked some op phones doing the same thing but it's been awhile.
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Mate 9
dekraan said:
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Click to expand...
Click to collapse
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Newrooter22 said:
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Click to expand...
Click to collapse
Did not try that! It is at a repairshop at the moment, they feel it is a software problem, but I guess mainly because I dropped the word 'custom rom'.
I've got a couple clues that suggest it might be a fried chip: I get Command not allowed errors when trying several fastboot commands, and I also get a remote:flash write failure when I try to flash a ramdisk.img or system.img.
Hope to hear from the shop today or tomorrow, and will update afterwards!
I have this exact issue on my huawei y6 2018, i can access to the emui recovery mode, and have bootloader unlocked.