Database Users

Problems unlocking bootloader

Hello all, hope you're all doing well. I've come across some problems when trying to unlock the bootloader on the Nexus 6P. Whenever I execute
Code:
fastboot flashing unlock
in the bootloader, my command prompt stays at
Code:
< waiting for device >
and never seems to progress after that. I have also tried
Code:
fastboot oem unlock
, but it still stays on
Code:
< waiting for device >
. I have already done some research on this problem and I have tried to troubleshoot by checking if I have the latest SDK update, and I do, but still no luck. My main purpose of doing this is to install the official 7.1.1 factory image. How can I fix this problem?

Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device

I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?

Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said

Thanks for reaching out and taking time to try and help out everyone.
dontbeweakvato said:
Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device
Click to expand...
Click to collapse
I've forgot to mention that when I run
Code:
adb devices
when the operating system is up, ADB recognizes it. However, when I'm in bootloader, like you mentioned, it doesn't see it. I've tried switching off and on the "OEM unlocking" and "USB debugging" in the "Developer options", however the problem persists.
tropical cactus said:
I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?
Click to expand...
Click to collapse
Doubt minimal adb will fix this, but worth a try. I'll also try running ADB on a different computer if that might help. Also, the reason why I want the official 7.1.1 release is because my device is currently running the developer's version. In addition I tried checking for update; no use.
dontbeweakvato said:
Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said
Click to expand...
Click to collapse
Yup. I did mention that my SDK tools are the latest release in my first post.
Edit: Never mind everyone I've found the solution! For some reason the device didn't have the Google USB drivers installed when the device is in the bootloader screen. After days of researching and trial and errors, here is the article that helped me:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Note: If you're experiencing this similar problem with the "< waiting for device >" message in the command line, you must acquire the Google USB driver .zip file.
Thanks to everyone that offered help!

Yep driver issues. Classic.

Nothing Works for installing TWRP, unlocking bootloader

I normally lurk around to get the information I need to root most of my devices and get root only applications. I recently got the Axon 7 (A2017U B29 Android 6.0.1) and I've perused many of the guides for rooting, TWRP, and bootloading unlocking. I have been unable to get even a single method to work at all.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
This thread flatly did not work and I found out it was because the B29 model does not unlock out of the box.
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I have not been able to get the axon7root.exe to work at all. I keep getting a message saying failed to say hello to the device. (the only one I could get was the zip file in the thread, the links do not work as many go to a host where the file size and download are not the same and the actual thing downloaded seems to be a random exe installer that isn't the actual file. If anyone actually has these files, I would appreciate it). I installed the qualcomm drivers, but I can't figure out which port number is correct. I see this in my device manager: QUSB_BULK with this in the properties: Port_#0001.Hub_#0003 and it isn't what is shown in those pictures. I was able to get the axon7tool to work with edl previously but I cannot get this to work no matter what I put in. It always fails to connect.
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Tried this as well but MiFlash could not see my phone in EDL mode.
There was another thread that used axon7tool and tried to use it to flash the recovery, but that last step never worked no matter which recovery image I attempted to use.
At this point, I am at a loss for what is actually the issue and what needs to be done. Even driver reinstalls have not changed anything (Windows 8.1 if that's relevant).

You could try the tool kit.

lafester said:
You could try the tool kit.
Click to expand...
Click to collapse
Edit: NVM, I found it. I will try this out next.

ruser453 said:
Edit: NVM, I found it. I will try this out next.
Click to expand...
Click to collapse
No, the tool kit in dev released today.
Also you need to flash signed twrp per the guide in order to unlock using your method.

lafester said:
No, the tool kit in dev released today.
Also you need to flash signed twrp per the guide in order to unlock using your method.
Click to expand...
Click to collapse
The toolkit found is exactly that one in that case. The unlock procedure from the getgo is not working as MiFlash still isn't recognizing my device and the Qualcomm drivers refuse to show up as the COM 9008 drivers like the guides are saying. The TWRP flash option on that one also explicitly says an unlocked bootloader is required. I can't see this toolkit helping much if the main tools outright refuse to work. I also DID see one of the guides mention a signed TWRP, but the link for it has been taken down and I've not seen a signed image anywhere else. I can try this on another computer I own some other time, but I can't put my finger on what isn't working.

ruser453 said:
The toolkit found is exactly that one in that case. The unlock procedure from the getgo is not working as MiFlash still isn't recognizing my device and the Qualcomm drivers refuse to show up as the COM 9008 drivers like the guides are saying. The TWRP flash option on that one also explicitly says an unlocked bootloader is required. I can't see this toolkit helping much if the main tools outright refuse to work. I also DID see one of the guides mention a signed TWRP, but the link for it has been taken down and I've not seen a signed image anywhere else. I can try this on another computer I own some other time, but I can't put my finger on what isn't working.
Click to expand...
Click to collapse
https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!dVMjmayY
---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------
You installed tenear driver so you would need to switch it back to use miflash.

Do not use that signed TWRP if you find it somewhere.
If you read the thread to the end, those users found serious problems with their IMEI restoring with that.
Most interested in the results of this thread. Is NOT clear, neither well documented (at least for me, sorry for my clumsiness)
1.- If it is necessary or not to unlock bootloader to let a normal TWRP for Axon 7 install
2.- EDL, fastboot, adb, axon7tool, axon7root.... Which method is best to flash the "good" Twrp. Why flasing TWRP in recovery requires so many operations?
3.- Are those methods (and zips, and other) equally usable for any model? and for any running firmware version?
Regards (and thank you in any case. This is not a lame claim. I do appreciate a lot all the effort that people doing tools and methods devote to help others. A lot.

lafester said:
https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!dVMjmayY
---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------
You installed tenear driver so you would need to switch it back to use miflash.
Click to expand...
Click to collapse
Thank you so much for the links. I didn't notice your post on the signed TWRP sadly. I have removed it. I did not get to peruse those threads in that much detail sadly and I did not notice the warning.

ruser, pls...
document your achievements...
And install other TWRP now you have installed the signed TWRP. At least, read that thread and do not restore a backup done with tht TWRP.
Regards

He used tenear method.

jrotaetxe said:
ruser, pls...
document your achievements...
And install other TWRP now you have installed the signed TWRP. At least, read that thread!!!
Regards
Click to expand...
Click to collapse
I will get to it when there is more time. I've already removed the signed one and installer TWRP proper. I've rooted successfully and backed things up. Xposed and moving my stuff over is all that remains. Nothing out of the ordinary so far, but I won't be using this for calls for a few days at least.

Makes sense. EDL method seems to be easy to do...
Wonder which TWRP he flashed. When receiving mine, I will try to put one "guide for lef-handed and chinese model" to stay in Marshmallow and root...
Thank you

FIX HTC-U11☆corrupt☆relocked☆s-on☆

______________________________________________
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.

Sooo... I screwed up BIG TIME...

First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye

the_darkest_knight said:
First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye
Click to expand...
Click to collapse
You must sign in google account

leap_ahead said:
You must sign in google account
Click to expand...
Click to collapse
Did that already...

Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/

redultra82 said:
Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/
Click to expand...
Click to collapse
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).

..

the_darkest_knight said:
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).
Click to expand...
Click to collapse
I thought that was the be all of recovery, its never let me now

Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help

redultra82 said:
I thought that was the be all of recovery, its never let me now
Click to expand...
Click to collapse
I don't know why it doesn't work...
ilyes9999 said:
Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help
Click to expand...
Click to collapse
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work

the_darkest_knight said:
I don't know why it doesn't work...
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work
Click to expand...
Click to collapse
I don't know what you mean . All i know by my experience if you can access the eRecovery you can fix it even with locked bootloader
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
And by the way when looking for a firmware for your device . You should use older versions and it should be the full ota update

HELP: Rooting Essential PH-1 on android 9

Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.

Can someone please help me? I don't know what more to do. Please.

Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?

goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9

I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...

kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.

I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.

Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!