Related
hi guys, i have the X722, i can use ROMs of X727 and X720?
No the x722 has no custom ROMs. You'll soft brick the phone if you try to load any ROMs from other variants onto it, to my knowledge.
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
I also soft bricked my Le Eco Pro 3
vsrocha said:
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
Click to expand...
Click to collapse
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
For anyone else reading this post : don't trust every comment here. Some people will give incorrect or incomplete info, such as advice to wipe the system to get around encryption.
* That's what I did and after successfully unlocking the boot-loader, I find that my system was somehow encrypted.. I did not encrypt my phone so I am not sure how this happened. In my haste, I did not create a recovery, I thought that is what the official Leeco twrp was for?
Options?
I too read about the Qfil tool, at the time I was having trouble downloading the files so I attempted to wing it... and failed.
I see now that I did not spend enough time on this complex option.
Update:
here is the exact instructions for using the Qfil method. ( this link provides step by step, and is tedious, but appears to work.
Sigh! I attempted to post a link and could not, due to being new on this site.
No doubt, I found the best instructions that I have seen yet on the Qfil Process.
Its on the unoffical Leeco Repair site : tora33 #comment-15320 this post is much more extensive than some other posts by Tora33 linked from XDA
Again, I can't post the actual link here! Just search for : unoffical Leeco Repair site : tora33 #comment-15320
Potential other options
J tag brick repair service website : brickedmyphone they charge $45 to repair a bricked phone.[/U
[*] This video seems very promising! Unfortunately, I wasn't able to find this video before now.
Since I am new here I am not allowed to help you by posting links!
search YouTube for How to unbrick any bricked letv phone without loosing data ( easiest way ) in Hindi.
Yes its in Hindi, but you will still understand because he used some English and it seems that he has built a fairly useful tool. Although, its still easy to get the gist of what he is telling us and he apparently built a program to repair a bricked Leeco phones, and he has other videos
[*] Finally Google : LeEco X820 Max 2 Super Unbrick Guide ( gizmochina. website) seems to be another complete solution.
I hope this helps you!
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
https://www.youtube.com/watch?v=m0o4QtNXljg
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
tsongming said:
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
Click to expand...
Click to collapse
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
sk8223 said:
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
Click to expand...
Click to collapse
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
tsongming said:
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
Click to expand...
Click to collapse
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
sk8223 said:
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
Click to expand...
Click to collapse
Thank you for you very good detailed advice. Its truly appreciated.
I was decrying the shop ROM a lot but it's okay. I thought it'd be a lot worse than it is, but at least it lets me play the games I want to play on it without issue (so far...). I'm debloating it soon. Gonna remove all the LeEco apps. I hope kernel sources get released for the x722 but I ain't holding my breath.
Ok guys, new here and I've done a bit of reading on this already. From what I gather, the S7 Edge is difficult if not impossible to unlock without a factory reset. Here's the issue.
This phone belongs to my friend's husband who was severely injured in an accident at work. He's in a coma and probably won't survive. He was severely burned over 90% of his body with chemicals and he has no fingerprints to unlock the fingerprint scanner. In addition, his wife doesn't know his password, so I figured I'd see if I could do anything for her. I tried the Dr. Fone program, but it's apparently incompatible with the S7 Edge. He keeps getting texts and messages and we can't check them. The phone is also set for a daily alarm at 1:30 AM, and apparently you can't power it down without the lock code either. Ideally, I'd like to either gain access for her or at least extract what data we can from the thing before factory resetting it. It would also be nice to power it down so that it doesn't keep putting out an alarm every night in the middle of the night. All his contacts with his family are inconveniently stored in the phone as well. It's kind of a worst case scenario.
Any assistance or recommendations for a course of action for this situation would be fantastic. I don't have any other information on the device itself other than that it's running on Freedom Mobile's network in Ontario, Canada. They've said they can factory reset it for her, but we were trying to avoid that and get any contacts or messages from his phone if possible.
Thanks in advance for any help! I know it's a long shot!
Edit: I managed to power down the phone with the Power Button/Volume Down trick after about 9 tries, so at least the alarm won't go off. Other than that, no luck.
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
UnNaMeD__ said:
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Click to expand...
Click to collapse
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Use odin 3.13 the latest
Then download twrp recovery 3.2.2.0 tar file for hero2lte the latest.
Boot your phone into odin mode by restarting your phone while holding power home button and vol down. When your reach the confirmation screen press OK.
Open odin and put the tar file in the ap slot and click the ap box and hit start to begin flashing.
Now restart ur phone by holding power home and vol down then immediately hold power home vol up to reach custom recovery.
Edit I just tested this myself
Flash the zip file from this thread no need to go looking for files in system.
https://forum.xda-developers.com/showthread.php?t=2780696
Should remove password pin or pattern.
To check if it's network locked just look at the back of your phone if it says 935u or Verizon wireless or 935W8 then the phone is unlocked for different networks.
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
UnNaMeD__ said:
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
Click to expand...
Click to collapse
maxlords said:
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
Click to expand...
Click to collapse
Hey alright no problem.
Download TWRP for G935W8 from official TWRP website:
https://teamw.in/samsung/samsunggalaxys7edge.html
You can follow some instructions from this thread regarding flashing:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Flashing TWRP might cause your phone to not boot. You will need to download dm-verity disabler from the thread above.
So download TWRP, Aroma file manager, dm-verity bypass, and zip file to disable pass that the other user posted: https://forum.xda-developers.com/showthread.php?t=2780696
Download all these files and put aroma file manager, dm-verity bypass and that password zip file bypass on your SD.
Make sure auto reboot is disabled in odin, follow instruction in thread about how to install twrp. If the auto reboot is disabled, phone will just remain at the same screen, so after the flashing is done from odin. You need to force reboot on your phone (volume down + power button for few seconds), just when the screen goes off, you need to immediately press recovery button combination (vol up + home + power). Here once you enter TWRP recovery see if you can enable MTP and trasnfer data to PC, if not, goto install zip and try password bypass zip file. If it works file then ok and proceed to install dm-verity bypass file and reboot your phone. If that zip doesn't works. You need to go to same install zip file option and now install aroma file manager. From there delete the password files that I told you about earlier, flash dm-verity and reboot again.
Thats it, if get confused about a step, tell me.
Well, I attempted to install TWRP through the latest version of Odin, but it didn't work. The error message I got in Recovery/Download mode was:
"Custom Binary (RECOVERY) Blocked By FRP Lock."
I looked that up online and apparently to install TWRP, I need to remove the FRP lock. I found a program called RealTerm which can supposedly bypass the FRP lock, but it doesn't seem to be connecting to the locked phone and it's not exactly user friendly.
Am I missing something here? Or is there no way to bypass the FRP lock on the unit?
______________________________________________
REPAIR HTC U11 - CORRUPT - RELOCKED - S_ON
______________________________________________
I run a phone repair shop,
Customer brought a HTC U11 in to repair,
was soft bricked with an attempted custom rom installation then relocked the bootloader without flashing a working OS to it,
The os version was there but when the device booted a message appeared the device is corrupt cannot be trusted and will not boot,
this tutorial is how I managed to revive the dead device please read below.
Device specs on this model were :
______________________________________________
Fastboot oem readmid
2PZC10000
Fastboot oem readcid
htc_039
______________________________________________
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
_____________________________________________
Bootloader displayed killswitch enabled please disable,
Killswitch/frp
Killswitch/oem unlock
Killswitch/bootloader
when trying to unlock with provided original unlock_code.bin that was provided with the phone & returns not allowed on production build in bootloader, could not flash any stock recoveries or TWRP back to the device, also couldn't receive the unlock code
_____________________________________________
I used tried the following programs to flash :
•htc_fastboot.exe
•minimal adb and fastboot 1.7msi
•power shell on windows 8.1
•minimal adb & fastboot
•fastboot binaries from htc_dev.com
couldn't get anything to flash to the customers phone with any of these so dont bother.
____________________________________________
NOTE
I downloaded the OTA's & firmware from the google spreadsheet it had no file for the 2.33.710.9 section there the page it went to was 404 so I just downloaded all of the files with the same CID htc_039 in this case, so just download all relevant files with your matching CID main version shouldn't be an issue as it wasnt for me.
_____________________________________________
REPAIRING THE HTC U11
NOTE
☆Links are at the bottom of tutorial☆
#1 Go through the files in spreadsheet then download all with the same CID as you have even though the main versions might be different,
#2 try to flash them all with normal fastboot to see what is a signed or close to signed zip and what isnt, (you will know by the RUU errors you face anything but RUU security fail zip from USB command or RUU main version fail ) means it probably won't work but try anyway,
NOTE
I narrowed it down to a few but the one that did end up working was main version 1.11.710.5, but this main Verision was 2.33.710.9 ??? Dont ask me how it worked twice as it needed to be flushed first time it said but it did,
#4 Now the only flash tool that works for downloading to the device in RUU mode is the HTC 10 batch tool.
#5 Place the .zip into the "com" folder which is located where ever the batch tool is installed, in my case was C://Android/com
#6 Open the batch tool with administrator privledges,
select option 3 to open fastboot terminal with the purple screen
NOTE
when entered location of the terminal should be "example" C://android/com on the screen this is where you placed your RUU.zip file.
#7 boot U11 to download mode, with device off hold,
•Power
•Volume down
NOTE
plug the device into the computer & make sure drivers are installed properly and working.
#8 Type into the terminal "fastboot oem rebootRUU",
phone will reboot to RUU mode.
#9 type into terminal "fastboot flash zip <file_name.zip>
NOTE
do not add " " or < > into the command syntax simply drag and drop the file if you do not wish to type the entire filename out.
it flashed all 28 zips twice in my case as it needed to be flushed the first time, these same files would not work on any other fastboot terminal I would only ever receive RUU error zip from USB command or RUU error main version fail,
so there you go this helped me and now I hope it can help you all out with your broken U11 fix please enjoy and if this tutorial has helped you please dont forget to hit the thanks button
_____________________________________________
NOTES
when using the HTC 10 batch tool fastboot terminal you can use either standard "fastboot" syntax or the "htc_fastboot" syntax both work.
WINDOWS 10 USERS :
you MUST disable driver signature verification or you will not be able to install any drivers for your U11.
_____________________________________________
FASTBOOT COMMAND SYNTAX
_____________________________________________
STANDARD SYNTAX
fastboot oem rebootRUU
fastboot flash zip "<example.zip>"
HTC SYNTAX
htc_fastboot oem rebootRUU
htc_fastboot flash zip "<example.zip>"
_____________________________________________
LINKS
_____________________________________________
HTC 10 batch tool (credits to sneakyghost ),
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
_____________________________________________
Google spreadsheet for your RUU (credits to 5m4r7ph0n36uru),
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
_____________________________________________
HTC drivers for your U11 (fastboot adb & mtp)
http://gsmusbdriverzone.xyz/download-htc-u11-usb-drivers-official.html
____________________________________________
☆☆☆EDIT☆☆☆
I have noticed in download mode OS VERSION is 2.33.710.9 still,
But in the OS system settings in about phone & also HTC sync manager the OS VERSION is 1.03.710.7,
BUT it can also receive and install OTA updates up until 1.29.710.9 version before it will not install any higher updates,
So may be best to unlock the bootloader & flash a newer RUU version to your device to OTA update.
Very strange indeed but just thought I'd better add it.
Thanks
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Sent from my coconut frond hut using Tapatalk
mauiblue said:
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Click to expand...
Click to collapse
Hey mate,
No problem at all
Firstly though I would strongly suggest to flash the Unlock_code.bin you got from HTC dev to unlock your bootloader while you have a functional OS,
enable OEM unlock in developer settings then flash unlock code via bootloader or download mode, will save you the big headache of what I was going through when the bootloader is re locked only signed firmware can be flashed but if unlocked can flash unsigned firmware to the device,
I'd say HTC has not repaired the device correctly at all, I'd be pursuing reimbursement for any money you have paid to them,
not even I have had re corruption or anything works like brand new just my OS version in download mode is 2.33.710.9 but zip I flashed in RUU mode was 1.03.710.7 but let me OTA all the way up to 1.29.710.9 before it stopped installing them it downloads it just wont install it,
I'd switch OEM unlock on, flash unlock_code.bin to get unlocked bootloader will stop you from getting the corruption error, I'd also change the OS also just to see if HTC havent flushed something out of the device properly.
Just please whatever you do do not lock the bootloader without a functional OS
Hope this helps mate, if you need any more help dont hesitate
Thanks
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
korom42 said:
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
Click to expand...
Click to collapse
No problem mate ,
I'm not sure why,
but the customer locked his bootloader before having a workable OS, he had a viper rom with TWRP on it & from what he told me he wanted the oreo bootloader and modem so tried to flash a firmware package that did not flash, but did not take a nandroid backup prior with TWRP then locked the bootloader allowing only signed firmware to be flashed, dont asky me why lol, as even re locking the bootloader it stills shows as modified in bootloader mode, possibly he thought that it would go away if he re locked it I cant be certain he wasnt to sure what he did,
I also had to re lock the bootloader after unlocking it to receive the OTA Updates from 1.03 - 1.29 as they wouldnt install they would download but not install as soon as I re locked it again I could OTA all the way up to 1.29.710.9 before the same would download but not install,
But in my personal reference to everyone you would be better of keeping the BL unlocked your device wont corrupt
As for the re lock of the bootloader snd the exact ruu version as mentioned in the post OS this was corrupted and would not boot, had no recovery only fastboot, download & RUU , could not flash token or receive unlock code, main version on device was showing version 2.33.710.9 as oreo firmware but ruu that I got to successfully flash with the HTC 10 batch tool was nougat 1.03.710.5, which was also giving me RUU error main version in normal and HTC fastboot but same file worked in the batch tool fastboot with or without htc-fastboot syntax I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would , main versions and SDK were both diff and it definitely works I recreated and flashed the device over and over again just to be sure before originally posting
mauiblue said:
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
Click to expand...
Click to collapse
Have to use fastboot to flash device, or sd card,
Fastboot is diff from adb, but glad everything is working well now for you mate and you shouldn't hopefully have anymore problems with it
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
mauiblue said:
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
Haha patience probably not lol I'm surprised the phone ever started working again after some of the things it got called , no I'm just persistent in everything I do if I cant repair it I make it my goal to repair it ,
That's what I explained to the customer also never lock a bootloader when they system doesn't function as it should only bad things can happen,
I kept getting the OTA notification pop up to but you cant turn it off on HTC like you can with Samsung
I just flashed oreo and kept BL unlocked and no problems again so far
But it does pay off to read that is very true, I learnt the hard way when I first started out with mobiles I had a brand new S3 when they just came out and ended up flashing an S2 kernel to it and literally burnt the touch controller out on the board and made the touch non functional, I've always read up on everything ever since before attempting repair modification or customisation and havent gone wrong since pretty much,
Speaking of HTC did they charge you a fee to supposedly "repair" your device, as I could tell just from what you mentioned something wasnt flushed right in it, which makes you entitled to a refund, I'd file a dispute with them for the work order and reimbursement on the postage and what not as to be honest I've even been all over HTC websites in aus and America and spoken to they're tech support also (usless might i add) even they state that sometimes they cannot even fix this exact issue, and they charge more for the fact the bootloader is modified to repair them,
Click to expand...
Click to collapse
Aloha M. Fortunately HTC has didn't charge me anything. The frustrating thing is that they didn't include with my phone documentation on what they supposedly had done to the phone. Obviously they were able to get the phone to boot up at least once. But it seems like they didn't even test the phone so that it would consistently boot up. Flashing the latest OS update wouldn't have taken much time. I really like HTC phones and their GUI but their customer service SUCKS donkey balls.
Aloha!
Sent from my HTC U11 using Tapatalk
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
mauiblue said:
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
Click to expand...
Click to collapse
That's great mate, glad it didnt cost you anything then, apart from the 5 week wait though that must have been terrible,
I would have thought they would package it up a bit better but then again they have never been good for service,
Anyhow everything must still be working well then and all issues seem to be gone, , I'm yet to receive a U12 into my work for repair but I do agree battery is pretty good on the U11 I can charge it and it last me 2 days almost before I have to charge it again, but then again I've had it open aswell and the battery takes up 3/4 of the phone under the hood it's a very big battery even in actual size,
Anymore problems with U11 or any other makes and models feel free to contact me through pm or post if you need help and I'll get back as soon as I can
Thanks Matty. All the best!
Sent from my HTC U11 using Tapatalk
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas or advice would be appreciated.
RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
Hey mate,
Yeah somethings going wrong with your OS
What version of android is it using ? 7.0 or 8.0,
As the bootloader is unlocked please KEEP it unlocked dont relock it under any circumstances if relocked only a very specific version of firmware can be reflashed and if flash fail the device will be bricked completely until the correct RUU is flashed
S-ON shouldnt be a problem when BL is unlocked and you can flash most firmwares that match your HTC u11 MID & CID
Recovery should boot without an SD card so if say recovery is corrupted aswell as part of the system is also,
What you need to do is plug it into the PC and using fastboot type the command,
fastboot getvar mid
fastboot getvar cid
with the device in download mode if you can,
If it wont boot to download mode with the button combination
Turn USB debugging on & connect to pc now your going to be using adb
Type this command to try and reboot to download mode to use the fastboot command to obtain your device info
adb oem reboot-download
Or adb reboot-download
It should reboot you to download mode now where you can obtain the necessary info with the fastboot getvar command,
Once you have that info head over to the google spread sheet and download the firmwares that match your MID & CID and then use the tutorial one page 1 to flash the phone,
Remember do not lock BL under any circumstances bad things will happen if the flash goes wrong.
RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
I had an nearly similar problem with my SD Card it always was seen corrupt from the system even after formating the SD Card. Then I did a factory reset, that did the trick for me.
It may take some time to set up the phone again, but for me it was the only way to make it reusable again.
Try to use different hardkey combinations, there are more then one to get into bootloader or downloadmode and even with the ADB commands you can treat your device to do what you want!
I hope this will help you.
So the links that I posted don't work because I don't have enough posts. I have factory reset the phone a few times in an attempt to get things working properly again. Here's the info since I can't put up the screenshots:
Android version:
8.0.0
Security level:
June 1, 2018
Software:
Bad Boyz US unlocked U11 v3.8 (I have a feeling I may have used the wrong one here)
Kernel:
3.3.78-perf-gbd700a6
[email protected] #1
SMP PREEMPT
Baseband:
8998-002772-1712182056
Build:
2.42.617.7 9.0_g CL1011554
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
kajfux said:
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Click to expand...
Click to collapse
Have you tried the htc_fastboot command syntax mentioned in the tutorial also with the batch tool ? If so and its still not working Its 100% to do with the zip your trying to flash id say it contains header errors,
Has it given you an error somewhere along the lines of "
a terrible mishap happened with the original ret lens 0" thats another common error to receive to indicate that your .zip is no good,
Try another .zip that matches your PID & CID dont worry about the main version the htc batch tool fastboot command promt for bypasses bootloader security to allow rollback of the bootloader,
I successfully took mine back to nougat from oreo with a locked bootloader which couldnt be re unlocked due to all killswitches being on & S-ON, no recovery or working OS, only download, bootloader & RUU mode,
Deffo the .zip trust me sorry for the late reply aswell didnt get notification but i hope this helps you out a bit.
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
RedSkull23 said:
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
Click to expand...
Click to collapse
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
turboxav said:
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Click to expand...
Click to collapse
What you mean by "unlock".
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
With my p10 lite with emui 8 it worked. So why not
0
yes
I Have unlock my phone yesterday with dc unlocker
Seppppx said:
You can downgrade (idk if it is possible from emui 8 I don't even own this phone) and then you can follow this tutorial to unlock your bootloader (FOR FREE) https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Edit : found this guide with HiSuite it may work https://youtu.be/xFCLpgGZEJM
Click to expand...
Click to collapse
Yeah, but not for Huawei P8 Lite 2017 version... I found this to be possible just for older phones (like the original P8 lite) which can be downgraded to Android 5. Newer ones can't be flashed with unsigned firmware (= firmware which is not straight from damn Huawei who decided not to provide the bootloader codes in the first place) so the only way apparently is to use paid software like DC-Unlocker as stated in this official XDA thread --> https://www.xda-developers.com/huawei-honor-unlock-bootloader-fee/
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
Unlocked the bootloader yesterday! I have Huawei P8 Lite 2017 PRA-LX1 and had latest Emui 8 build on it... Bought the code for 4€ from DC-Unlocker, and required around 2 minutes for unlocking. You can follow this guide --> https://www.youtube.com/watch?v=4xYybHAlWaQ
I tried so hard to get the code for free, and I know modding should not cost people money. But at the end of the day, I think those 4 euros were worth it
Yeah,4 Euros is ok and the only method!!!
-CALIBAN666- said:
Yeah,4 Euros is ok and the only method!!!
Click to expand...
Click to collapse
And also worth it if we consider fact that our phone is now EMUI free. ?
DunoCZ said:
And also worth it if we consider fact that our phone is now EMUI free.
Click to expand...
Click to collapse
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
af1985 said:
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
Click to expand...
Click to collapse
Did you after fastboot oem unlock leave phone format yourself right?
DunoCZ said:
Did you after fastboot oem unlock leave phone format yourself right?
Click to expand...
Click to collapse
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget ???
Momin8454 said:
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget
Click to expand...
Click to collapse
Lol you are dumb...
DunoCZ said:
Lol you are dumb...
Click to expand...
Click to collapse
Well, I didn't had any knowledge of it. Turns out my EMUI version was more recent one that's why I had more issues with TWRP.
And I was just sharing my experience with Honor 8 lite.
DunoCZ said:
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
Click to expand...
Click to collapse
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Some advice from a beginner
af1985 said:
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Click to expand...
Click to collapse
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Jujub said:
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Click to expand...
Click to collapse
Check out my SPECTRUM profile I wrote even simple tut how to flash kernel and enable adoptable storage
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
yurtal said:
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
Click to expand...
Click to collapse
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
zgfg said:
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
Click to expand...
Click to collapse
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
yurtal said:
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
Click to expand...
Click to collapse
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Oh ok. Yes I'll read up on it. Thanks for your help.
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Hey, just to follow up. I managed to get it back up and running from someone with EDL support.