Related
I am having trouble finding a root method for this phone
, Or even just some news about development. Anyone point the way?
i have the same question. Anyone have any information?
It's kinda like a bum deal right now. I got two ZTE devices no root. Upset I can't disable all these google apps
Sent from my Z971 using Tapatalk
Same. Waiting for ZTE 971 root.
What is needed to get the process started to Root the ZTE Blade Spark z971
CharmedWhovian said:
What is needed to get the process started to Root the ZTE Blade Spark z971
Click to expand...
Click to collapse
Nobody knows yet
Sent from my ZTE Z971 using XDA Labs
Anybody has ROM or smth else for this phone?
Frp for blade spark?
I have had now about 4 or 5 newer ZTE phones. What I have come across is that none were able to be rooted. I posted a few requests, no one here took on the task. I don't know if it is that they can't be rooted or its just to hard for someone to do. Either way I have gotten away from buying ZTE phones for this reason.
Did anyone try to unlock the bootloader?
Code:
adb reboot bootloader
fastboot oem unlock
AT&T shows that there have been multiple OTA updates for this phone, and the last one early Jan 2018 was over 500mb. It should not be hard to port TWRP if we have an unlocked bootloader.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1217955?make=ZTE&model=ZTEZ971
sparkie420 said:
I am having trouble finding a root method for this phone
, Or even just some news about development. Anyone point the way?
Click to expand...
Click to collapse
Nope, fastboot is removed on ZTE Nougat devices
It looks like they figured out ways around this for the Axon7, using EDL mode, but I tried a few things (including axon7tool, and the flashable zip to enable fastboot) without any luck.
I'll keep digging but it doesn't look too promising.
ZTE has our kernel sources at http://opensource.ztedevice.com [ZTE Z971 Nougat(7.1.1) Kernel(3.18.31)]
Won't do us much good without an unlocked bootloader though..
Anyone know if you can use MiFlash to flash in EDL mode without an unlocked bootloader?
aslezak said:
Did anyone try to unlock the bootloader?
Code:
adb reboot bootloader
fastboot oem unlock
AT&T shows that there have been multiple OTA updates for this phone, and the last one early Jan 2018 was over 500mb. It should not be hard to port TWRP if we have an unlocked bootloader.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1217955?make=ZTE&model=ZTEZ971
Click to expand...
Click to collapse
TWRP for ZTE 791
Here is a Z971 TWRP I compiled for our device.
Any brave soul want to flash it using QPST or using one of the other methods in this post? Unbrick All Qualcomm
You'll need to rename it to recovery.img first. If you have to choose a firehose, choose prog_emmc_firehose_8917_ddr.mbn
Supposedly you can flash even with a locked bootloader :good:
aslezak said:
Here is a Z971 TWRP I compiled for our device.
Any brave soul want to flash it using QPST or using one of the other methods in this post? Unbrick All Qualcomm
You'll need to rename it to recovery.img first. If you have to choose a firehose, choose prog_emmc_firehose_8917_ddr.mbn
Supposedly you can flash even with a locked bootloader :good:
Click to expand...
Click to collapse
I'll do it man just message me details on how to
I was going to try & backup all the partitions using QPST, but it seems you need to get the phone into 9006 mode. We can only get into 9008 mode [Qualcomm HS-USB QDLoader 9008] with "adb reboot edl" (emergency download mode). Holding down Vol+/Vol-/Power from EDL will get you into yet another mode, ZTE Handset Diagnostic (DFU) mode, but I couldn't figure out how to do anything from here with QPST.
The only way to get the phone into 9006 mode is to brick the bootloader, which I'm not willing to do at the moment. Supposedly you can use the "axon7tool -d" and it will try to write to your bootloader & boot, but it just crashed when I tried to do it.
The other way to get into 9006 mode is to flash an mbn and another file, but I believe those are device specific, and we don't have those..
Anyway, does anyone have a phone that wasn't updated to the latest Z971V1.0.0B20 firmware? It would be nice if we could get that from the /update folder so if we brick, we have something we might be able to flash to recover.
JonnyGrench said:
I'll do it man just message me details on how to
Click to expand...
Click to collapse
I figured out if you put the AT&T SIM card in, then Settings / AT&T Software Update, you will see the Z971V2.0 update & it will download.
I wasn't able to see the update until I put the AT&T SIM card in.
Unfortunately, I was unable to grab the OTA update.
If someone hasn't already updated to the latest software version, if you could "adb logcat -d -f /sdcard/Download/ota.txt" once the download starts, we can probably get the url of the OTA update, then work from there on building a flashable firmware... :good:
aslezak said:
I was going to try & backup all the partitions using QPST, but it seems you need to get the phone into 9006 mode. We can only get into 9008 mode [Qualcomm HS-USB QDLoader 9008] with "adb reboot edl" (emergency download mode). Holding down Vol+/Vol-/Power from EDL will get you into yet another mode, ZTE Handset Diagnostic (DFU) mode, but I couldn't figure out how to do anything from here with QPST.
The only way to get the phone into 9006 mode is to brick the bootloader, which I'm not willing to do at the moment. Supposedly you can use the "axon7tool -d" and it will try to write to your bootloader & boot, but it just crashed when I tried to do it.
The other way to get into 9006 mode is to flash an mbn and another file, but I believe those are device specific, and we don't have those..
Anyway, does anyone have a phone that wasn't updated to the latest Z971V1.0.0B20 firmware? It would be nice if we could get that from the /update folder so if we brick, we have something we might be able to flash to recover.
Click to expand...
Click to collapse
Greetings, i have ZTE blade spark too, as i see, this thread looks like it died very quick. well, i am not a developer but i'll try contacting some developers to check if we can do something. Maybe since they know a lot about it, they can help us to unlock bootloader, etc. I JUST HOPE that this thread doesnt die like the Huawei Ascend XT forums did and the phone couldnt have any custom ROM. The best thing is we have source code (the XT didnt had a good source code or no source code at all) and we can start from that. But we need a good dev to help us, try to contact as many devs as possible too.
Not to discourage you, but the fastboot is "disabled" on all ZTE U.S. devices. You would need to flash using QPST which requires having the correct vendor signed firehose programmer (which isn't available). You could try modifying the ota zip update, if you received one on your phone. You would need to download this OTA update manually before rebooting the phone (to have it installed), otherwise the link will be rolled off the logcat logs.
Good luck.
ensol52 said:
Greetings, i have ZTE blade spark too, as i see, this thread looks like it died very quick. well, i am not a developer but i'll try contacting some developers to check if we can do something. Maybe since they know a lot about it, they can help us to unlock bootloader, etc. I JUST HOPE that this thread doesnt die like the Huawei Ascend XT forums did and the phone couldnt have any custom ROM. The best thing is we have source code (the XT didnt had a good source code or no source code at all) and we can start from that. But we need a good dev to help us, try to contact as many devs as possible too.
Click to expand...
Click to collapse
So I just got this phone and wanted to root and all that like I did my S4. Came here for some help because I am most definitely not educated enough for this. I did have a question though. I see a lot about a locked bootloader but under the developer settings I see "OEM Unlocking Allow the bootloader to be unlocked." The default is off, and I have left it so. Is this anything or am I missing something?
aslezak said:
I figured out if you put the AT&T SIM card in, then Settings / AT&T Software Update, you will see the Z971V2.0 update & it will download.
I wasn't able to see the update until I put the AT&T SIM card in.
Unfortunately, I was unable to grab the OTA update.
If someone hasn't already updated to the latest software version, if you could "adb logcat -d -f /sdcard/Download/ota.txt" once the download starts, we can probably get the url of the OTA update, then work from there on building a flashable firmware... :good:
Click to expand...
Click to collapse
Just got the phone, going to do this. Edit: Total skid here btw. Is it safe to post that file here?
Foggofed said:
Just got the phone, going to do this. Edit: Total skid here btw. Is it safe to post that file here?
Click to expand...
Click to collapse
Hello ? Lol, yeah! Upload it to a good site like Android dev, I'm a lil behind the loop but I'm sure sharing your findings are what's going to lead us into a possibility of getting some Dev love...
Sent from my Z971 using Tapatalk
Hello, Ya all... hope you're doing fine.
I searched for days to find a serious guide to root moto c, xt1754, and wasnt successful. Now, am an older guy and I sure cant dive as deep as you do into that area Had me a fine Moto G and rooted it with XDA know how pretty good. Unfortunately this device got stolen a few weeks ago. Since am not a rich man and that I needed a new device, I got the Moto C. I can see for myself thats a pretty simple piece... but till am able to get a better Moto - I'd like to root XT1754 either. So, is anyone willing to help me? Could I use the files I once successful used for Moto E and G, logically updated?
Is Moto C another kind Moto E?
Hope I'd describe my case well enough for you. I also truly hope someone might have mercy with me and can let me know what I've to do.
Wish you all a Good Time at All.
Tyd27
In short, no, you cannot use the same files as on previous gen Moto's. The reason behind it... quite simple: they have absolutely nothing in common. This Moto C sports an MTK processor, to begin the long list of differences.
What you can try is this:
1. Unlock your bootloader. Either via Motorola Developer Website, or via fastboot oem unlock.
adb reboot bootloader
fastboot oem unlock
OR
fastboot oem unlock UNLOCK_CODE_FROM MOTOROLA
Once you're done with that, re-enable USB Debugging and OEM UNLOCK ( if you need to turn it back on ).
Then install the latest Magisk app from www.tiny.cc/latestmanager
At this stage, you will need your original boot image ( from here: https://www.needrom.com/download/moto-c-4g-xt1754-nrd90m-054-row-official-rom/). You will need to register there, and wait basically until forever for that firmware file to finish downloading. Open that up with 7zip and extract it. Find the file called boot-signed.img.
Patch it using Magisk.
move that patched_boot.img in your ADB directory.
adb reboot bootloader.
fastboot flash boot patched_boot.img
At this point, 2 options:
a. It will flash, in which case you will do fastboot reboot
b. it will not flash, in which case you will get an error ( boot image not signed etc)
If the first option occurs, you might get a "corrupt" error screen upon reboot. Follow the steps and let the phone do a factory reset. If it reboots properly, re-install Magisk and enjoy root.
if it does not want to reboot properly... you'll congratulate yourself on having the firmware handy
So, thanx alot for this answer. Am happy that someone took care now coz i really dont like unrooted devices. Well, the other side is am 58 now and not a professional at phones. Rooted a few motos with xda help and all went good. Unfortunately my last moto g got stolen and fir what reason ever else i chose to get moto c. Probably it was realky damn ****n stupid. Until i can afford another moto i going to try everything to root moto c. I'll read your reply now before i start doing it. Too bad that there is no way rooting it like moto g. Does it mean i wont have twrp neither?
Have a Good Day.
Tyd27
Definitely no TWRP on it, until someone with the knowledge will port it. That's just how it goes with MTK Devices and their closed source, I'm afraid.
Hi can u make a custom recovery for moto c xt1754
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-1-0-moto-c-t3703184
______________________________________________
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.
Oculus go is built by MI and using the same chipset as MI5S.
MI5S can be Deep Flashed using Deep Flash cable.
So I was wondering if same method can be applied with Bricked Oculus Go to revive or unbrick
Alternately Oculus Go does show up as Qualcomm HS-USB QDLoader 9008 device in pc.
Now if we can have the flashable image, we might be able to recover it.
I wondered the same thing for a while now...
Here is the problems I see so far:
1. We have no usable firmware, or even just the bootloader to use the Qualcom tools.
2. Once hardbricked the big question is what happened to he hardware data like MAC address and serial numbers.
Unless they are stored securely or can be retrieved we have a big problem.
3. The probem would not exists if Oculus would provide properly working firmwares and devices.
With point three I see the biggest issue as I doubt we will get our hands on a firmware.
From what I can see the standard recovery mode is disabled, so OTA or Fastboot only here for starters.
And if I take the reactions of other closed source system as a guide then I assume trying to enter fastboot mode will cause a softbrick.
Only if the thing would accept block based firware updates we could have a chance using a dump from a clean device.
We still would need ADB access on the faulty device though or a way to convert a dump into something usable for the Qualcom tools.
I strongly tend to say that only the bootloader part is stuffed when the red light problem happens.
But I have not tested for any available backdoors to gain root access.
Downunder35m said:
I wondered the same thing for a while now...
Here is the problems I see so far:
1. We have no usable firmware, or even just the bootloader to use the Qualcom tools.
Click to expand...
Click to collapse
I am try to look at MI5S or MI VR standone firmwares.
Also there is recent firmware update thats been pushed over ota, trying to source the same.
Downunder35m said:
I wondered the same thing for a while now...
2. Once hardbricked the big question is what happened to he hardware data like MAC address and serial numbers.
Unless they are stored securely or can be retrieved we have a big problem.
Click to expand...
Click to collapse
Not such a big issue.
Downunder35m said:
I wondered the same thing for a while now...
3. The probem would not exists if Oculus would provide properly working firmwares and devices.
With point three I see the biggest issue as I doubt we will get our hands on a firmware.
From what I can see the standard recovery mode is disabled, so OTA or Fastboot only here for starters.
Click to expand...
Click to collapse
Trying to get hands on firmware update 3.49 or 3.51
And if I take the reactions of other closed source system as a guide then I assume trying to enter fastboot mode will cause a softbrick.
This is an interesting article
https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
Finally I got the OTA updates. It looks like its a delta update.
Update has changes to following partitions.
aboot
keymaster
pmic
xbl
boot
system
cmnlib64
rpm
hyp
tz
cmnlib
ovrtz
devcfg
modem
Does anyone knows how to extract payload.bin for A/B type ota
Its based on Android 7.1.2 Release 36 or N2G48H
And when phone goes into standby mode, it gets deteceded is Qualacom USB QLoader 9008
@Downunder35m Would you be interested in playing with the OTA zip
Just wondering.. Where is the Ota stored on the device? Do you think it installs if you put it on the storage in the according folder by hand? Otherwise it would be interesting to find out how the oculus go retrieves the updates online, then there might be the option to "intercept" that
Maybe you find a solution to flash the kernel, provided by facebook again: https://github.com/facebookincubator/oculus-go-kernel
Did you find any solution?
Would a full device backup from the headset work as a deep flash rom? I really don't know too much about MI hardware/software.
Is this do-able with out unlock.bin??
I've tried using adb/fastboot. ADB reports the device OK; fastboot can't see the device.
I've tried all manner of drivers to load........ I know there are separate drivers for adb and fastboot.
This is driving me nuts.
Finally, are there different SUB-variants of the 996?? One generic and one US Sprint??
Thanks
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
ROMSG said:
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
Click to expand...
Click to collapse
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Graf_Eberstein said:
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Click to expand...
Click to collapse
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. I did some fairly general "looking" for that ROM elsewhere, found a couple of articles when Google-searching, but haven't had a chance to check those out (that will have to wait until tomorrow). If it turns out that there is no alternate link to the ROM, are there any other ways of getting it, short of looping @Tilde88 in?
Graf_Eberstein said:
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. Since I haven't gotten past the first post yet, I'm going to see if I can find that elsewhere and report back.
Click to expand...
Click to collapse
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Darnrain1 said:
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Click to expand...
Click to collapse
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Graf_Eberstein said:
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Click to expand...
Click to collapse
Your welcome,
Stock Oreo Rom, flash in order But there are a lot more roms for the Lgv20 you can look around if you want.
LG V20 ROMs, Kernels, Recoveries, & Other Developm
US996 DIrtysanta Rom
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Graf_Eberstein said:
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Click to expand...
Click to collapse
Your phone is rooted great.
DUMP backup with LGUP. Might not be to late. Just hold vol up and plug in usb to phone and computer. Go into LGUP and choose DUMP all files. You don't need to dump system or cache. This will save all the files on your computer. Back the files up like google drive or something.
Take battery out and put back in. Then you want to boot into twrp and do a format.
Then your ready to install an OS on your phone. Why don't you check out my rom I made it's stock Oreo debloated. There are some good guides on there also you can follow. link
If you need any more help just ask. I don't mind.
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Graf_Eberstein said:
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Click to expand...
Click to collapse
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Darnrain1 said:
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Click to expand...
Click to collapse
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Graf_Eberstein said:
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Click to expand...
Click to collapse
Not a problem. Because I only have an H910 I didn't get all the bloatware on other lgv20 phones. But that Mobile Services Manager is a huge bloatware that installs more bloatware. So I thought I would try and find it and remove it in the latest version. You can update Auto_Debloat and it should get rid of that Mobile Services Manager for you. All you have to do is just flash the new version in twrp and reboot.