Related
How do I get the bootloader to relock?I tried fastboot oem lock but it tells me to use fastboot oem lock begin first so I do that and then it says to flash signed image first so I do and then the process starts all over again.I want to relock so I can return the phone but I can't get it to lock,keep getting the run around by my computer
What image are you flashing?
Have you tried Shawn's return to stock tool, in the development section? It doesn't state that it re-locks the bootloader, but it can't hurt to try.
Verified Shawn's return to stock tool does NOT re-lock the bootloader. Just used it cause I soft bricked my device jacking around with Xposed modules.
Has anyone tried the factory XMLs from here (http://forum.xda-developers.com/moto-x-style/development/stock-stock-firmware-t3201459)?
Even if you lock the bootloader again it will show "relocked" not locked so it's still visible that it was unlocked at some point.
I figured it out,instead of running the .bat file you have to flash 1 by 1 using fastboot.The .bat file will automatically reboot the phone and the locking process can't happen.it doesn't say relocked,just locked status code 2 but the people at Motorola will know the difference but those at best buy won't, I just need to exchange it for another,the volume rocker sticks.I thank all for the replies and the help
kinglove1211 said:
I figured it out,instead of running the .bat file you have to flash 1 by 1 using fastboot.The .bat file will automatically reboot the phone and the locking process can't happen.it doesn't say relocked,just locked status code 2 but the people at Motorola will know the difference but those at best buy won't, I just need to exchange it for another,the volume rocker sticks.I thank all for the replies and the help
Click to expand...
Click to collapse
What files need to be manually ran?
I am running into the same issues you were.
I can't get any of the files to flash though.
Thanks
The files a couple posts up will get you back to stock but first you have to type in fastboot OEM lock begin.Then flash all files inside the zip one by one starting with gpt..bin,then boot loader,then the boot.IMG,followed by the rest one by one until you get all of them flashed.Then type fastboot oem lock and it'll give you conformation that it was successful. It'll wipe your data so if you have photos or music you don't want to lose then back it all up.you'll be relocked afterwards.if you need further help p.m. me and I'll be glad to give a hand.Oh,make sure your adb and fastboot is up to date
Thanks for the rundown, ended up getting it. I was running into computer problems seemed to lose connection to my phone. Lots of tries but eventually got it to work.
Sent from my Nexus 6 using Tapatalk
Does it take away the start up splash screen with re-locking it?
xdame said:
Does it take away the start up splash screen with re-locking it?
Click to expand...
Click to collapse
No you need to flash the fixed logo for that.
Misterxtc said:
No you need to flash the fixed logo for that.
Click to expand...
Click to collapse
Exactly what i needed, thank you!
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
http://www.xda-developers.com/xiaomi-locks-bootloader-on-recent-devices/
What the hell, Xiaomi?
I don't know if the Redmi Note 2 is affacted yet as it's not on the list but I aborted the update download.
Looks like it will be locked in the future anyway, so watch out!!!
Yes, and I know some of people that haven't been noticed this kind of change and their phones have been bricked ...
So the only way to unbrick their phone - reboot to fastboot mode and use line flash to recover their system.
For those who have flashed non stock's MIUI ROM => Please don't flash 6.1.14 ROM. ( But only Xiaomi Mi Note Pro/Redmi Note3/Xiaomi 4C will be suffered.)
You can flash the weekly Roms by xiaomi.eu with unlocked bootloader
It sucks but it's kinda understandable... My note 2 came from the seller with a custom rom and bucket load of bloatware... They even removed the miui browser and installed a really suspicious browser.
I flashed a new rom as soon as I could but the average user might not have the knowledge or perception of what's going on so there's a real risk here and damages the brand.
Locking the Bootloader is a necessary evil for Xiaomi, upsets the geek/dev community but protects the wider (average) consumer.
If the unlock process works as they say it shouldn't be an issue for us.
I don't like the oficial MIUI roms (bloatware, suspicious system apps, etc.). So this is a new reason to avoid official roms.
dablado said:
I don't like the oficial MIUI roms (bloatware, suspicious system apps, etc.). So this is a new reason to avoid official roms.
Click to expand...
Click to collapse
these aren't official roms
rally200 said:
It sucks but it's kinda understandable... My note 2 came from the seller with a custom rom and bucket load of bloatware... They even removed the miui browser and installed a really suspicious browser.
I flashed a new rom as soon as I could but the average user might not have the knowledge or perception of what's going on so there's a real risk here and damages the brand.
Locking the Bootloader is a necessary evil for Xiaomi, upsets the geek/dev community but protects the wider (average) consumer.
If the unlock process works as they say it shouldn't be an issue for us.
Click to expand...
Click to collapse
Hi!
My rn2 also came in the same state - custom rom and bloatware. I dont know what kind of a user I am but Im probably closer to average than anything else. I am trying for 'advanced' title though: ). The problem I have is not exactly flashing the new rom, at least not yet. First I want to backup the one it came with. The thing is in case of warranty claim my service center wants it returned in the state I received it in. Ive used Flashify and Partitions Backup apps first, then I wanted to boot twrp and do another backup. But it seems there is something wrong with the bootloader. >fastboot boot twrp.img works for everyone but me. It returns: failed unknown command. Do you maybe have an idea what could be wrong? Bootloader custom too? What would you suggest I do to backup my phone? I would really appreciate it.
Thank you
m
While I understand their motivation for locking the bootloader, and I am willing to accept it, it's the unlock procedure that is nuts. If you brick your phone, and then need to wait 1-3 weeks to get an unlock code, that is crazy. Granted a lot of people would have no use for an unlocked bootloader, and heck, don't even know what it is. But for the folks that do, and want to experiment with non-official roms or recover from a brick/bootloop, this is a real drag.
Why does the unlock procedure have to be so potentially lengthy? If you have gone to the effort to contact them about unlocking it, what's the sense in making you wait several days to several weeks to actually get the necessary unlock code? The only issue this solves is of vendors loading junky firmware--it would be discouraging for them to have to wait 3-21 days for each phone they want to infect with a junkware rom. But the collateral damage is for the end user who needs it unlocked quickly--he/she will have to suck up the 3-21 day wait. Probably a good piece of advice for anyone interested would be to immediately request a bootloader unlock code from Xiaomi after receiving a device, and then it would be available in the future when needed.
bopy said:
Hi!
My rn2 also came in the same state - custom rom and bloatware. I dont know what kind of a user I am but Im probably closer to average than anything else. I am trying for 'advanced' title though: ). The problem I have is not exactly flashing the new rom, at least not yet. First I want to backup the one it came with. The thing is in case of warranty claim my service center wants it returned in the state I received it in. Ive used Flashify and Partitions Backup apps first, then I wanted to boot twrp and do another backup. But it seems there is something wrong with the bootloader. >fastboot boot twrp.img works for everyone but me. It returns: failed unknown command. Do you maybe have an idea what could be wrong? Bootloader custom too? What would you suggest I do to backup my phone? I would really appreciate it.
Thank you
m
Click to expand...
Click to collapse
Lol Your doing it wrong buddy it's :
fastboot flash recovery recovery.img
If your recovery is named twrp.img than it should be
Fastboot flash recovery twrp.img otherwise rename the .img file and use the first command
dissidius said:
Lol Your doing it wrong buddy it's :
fastboot flash recovery recovery.img
If your recovery is named twrp.img than it should be
Fastboot flash recovery twrp.img otherwise rename the .img file and use the first command
Click to expand...
Click to collapse
Thank you for your reply.
Actually its listed as command "boot <kernel> [ <ramdisk> ]" and on RN2: hxxp://en.miui.com/thread-207290-1-1.html
Havent tried flash yet and I wont until I figure out whats going on.
Lock the bootloader, i have no problem. But at least they should have given an easier and faster way to get it unlocked.
What about china dev rom 6.1.21?still lock bootloader?
Sent from my Redmi Note 2 using Tapatalk
harizamzi said:
What about china dev rom 6.1.21?still lock bootloader?
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
RN2 is still not affected, still unlock on 6.1.21
I also think that Xiaomi should not do this...
BUT the only thing that concerns me about locking the bootloader is,how I am going to root my device.. The only solution would be to have a zip that contains an SU binary,properly signed so it can be flashed with Mi Recovery.
When I had the Mi3, I flashed the Global Stable,then flashed a homemade (signed) update.zip that had SU inside and I was rooted. I had my phone "stock" but rooted and could do anything..
tonydeli7 said:
I also think that Xiaomi should not do this...
BUT the only thing that concerns me about locking the bootloader is,how I am going to root my device.. The only solution would be to have a zip that contains an SU binary,properly signed so it can be flashed with Mi Recovery.
When I had the Mi3, I flashed the Global Stable,then flashed a homemade (signed) update.zip that had SU inside and I was rooted. I had my phone "stock" but rooted and could do anything..
Click to expand...
Click to collapse
I agree on this. I don't need custom recovery but I need root access. So stock rom (or with lock bootloader) with root access is enough for me.
So is boot loader for RN2 still unlocked in all official roms?
I have been using custom roms for last couple of months now, so I did not really keep tab on this.
TIA
yea, but just to be safe, avoid the official roms and use the xiaomi.eu roms, they are modded for international users and have the bootload lock cleared out.
My redmi note 2 pro was using the latest 6.5.27global dev rom, and I had flashed cn dev rom 6.5.27, bootloader were not locked on both rom, but since 6.5.24 there removed the native root on cn dev rom but you like the native root, just goto security app > root permission and it will let you downloaded the root package. Since then, when ever i flashed a latest rom, also flashed superSU.zip in one go by twrp.
Sent from my 2014817 using XDA-Developers mobile app
My redmi 2 enhanced with cn latest miui8 rom, the bootloader still unlocked. What info will you got from.
Sent from my Redmi Note 3 using XDA-Developers mobile app
hi all my first post im wanting to relock 5x bootloader has i unlocked the boot loader unofficial way as my fingerprint scanner is not working so prob needs to go back also it wont update
i tried this via adb fastboot oem lock and it said FAILED ( remote invalid command) plus on the phone in fastbbot red its got PHONE unlocked and FRP UNLOCK
hope someone can help would be appriciated and im running b130 firmware
I dont think you can relock it its unlockable for a reason. Offtopic// how is warranty in europe when unlocked?
hmm,
well ive relocked bootloader just will not update and fingerprint not working not even in menu
Maybe you should walk us through what exactly you did up until the point where your FP scanner stopped working. It seems strange that it stopped working as a result to unlocking the bootloader (they are not related).
this is what i did
right i tried installing cm13 installed twrp and then the rom did not work kept crashing
so i reinstalled stock recovery via adb
then installed b130 rom for l21 device
ive even tried the dload update app route to reinstall stock rom and when i connect it to my charger and do the key combo i keeep getting software installed failed and it goes to quick to get the error message
i cannot update and im stuck on b130
when i do goto uopdate via handset it says your system was altered and full update is needed and then fails
zulu1875 said:
right i tried installing cm13 installed twrp and then the rom did not work kept crashing
so i reinstalled stock recovery via adb
then installed b130 rom for l21 device
ive even tried the dload update app route to reinstall stock rom and when i connect it to my charger and do the key combo i keeep getting software installed failed and it goes to quick to get the error message
i cannot update and im stuck on b130
when i do goto uopdate via handset it says your system was altered and full update is needed and then fails
Click to expand...
Click to collapse
A custom rom doesnt support fp. to go back to stock here is the link https://www.androidfilehost.com/?fid=24411628330025756 (props to deadman96385). First of all. dont flash a rom if you havent done the research.
jimandroidnerd said:
A custom rom doesnt support fp. to go back to stock here is the link https://www.androidfilehost.com/?fid=24411628330025756 (props to deadman96385). First of all. dont flash a rom if you havent done the research.
Click to expand...
Click to collapse
yes i flashed that rom above and now back on stock an fp not working !! i cant even update anything on phone this is what im getting when i type in fastboot maybe this the prob ???
etecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : W6HDU16127002395
Firmware : KIW-L21C432B130
FB LockState: LOCKED
widevine LockState: RELOCKED
*******************************************
Bootloader Lock State: RELOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: need to verify
Boot image need to be verified
Recovery image need to be verified
Bootloader Version: 001.001.000
*******************************************
Battery state: 4275mv
zulu1875 said:
yes i flashed that rom above and now back on stock an fp not working !! i cant even update anything on phone this is what im getting when i type in fastboot maybe this the prob ???
etecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : W6HDU16127002395
Firmware : KIW-L21C432B130
FB LockState: LOCKED
widevine LockState: RELOCKED
*******************************************
Bootloader Lock State: RELOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: need to verify
Boot image need to be verified
Recovery image need to be verified
Bootloader Version: 001.001.000
*******************************************
Battery state: 4275mv
Click to expand...
Click to collapse
Thats not the error. You cant update the phone after you rooted it/ after the bootloader is unlocked.
Did you clean flash it or dirty?
jimandroidnerd said:
Thats not the error. You cant update the phone after you rooted it/ after the bootloader is unlocked.
Did you clean flash it or dirty?
Click to expand...
Click to collapse
cleanan flashed it i cant understand why its showing root as it supposed to be unrooted
zulu1875 said:
cleanan flashed it i cant understand why its showing root as it supposed to be unrooted
Click to expand...
Click to collapse
What recovery do you use? It might be the recovery that flashes root back to the phone
i really can't fig out why this phone is messed up i aint got tarp no more it supposed to be stock
and won't update tried the load update.app procedure just fails more or less straight away
the fp aint working I've had enough lol and i can't even take it back to service centre as i think they would say boot loader as been unlocked no warranty
I'm giving up on this phone if anyone wants it for 120 quid
let me know to much of a headache
zulu1875 said:
cleanan flashed it i cant understand why its showing root as it supposed to be unrooted
Click to expand...
Click to collapse
flashed that and i get software install failed went so quick couldn't see why it failed
tried installing b130 stock from paul obrien link still software install fails from what i could see as it went quick was crc check or something
zulu1875 said:
tried installing b130 stock from paul obrien link still software install fails from what i could see as it went quick was crc check or something
Click to expand...
Click to collapse
i gunna give up on the phone gunna chuck it out of window in a min
zulu1875 said:
i gunna give up on the phone gunna chuck it out of window in a min
Click to expand...
Click to collapse
@Zulu:
Is your issue that the fingerprint setup menu item does not even show up in the settings menue even when you re-flash stock rom and EMUI 3.1?
I have that exact issue. I have been trying every possible way to go back to stock, am at EMUI 3.1 now with original Recovery. But still the fingerprint menu item still does not show up in the setup menue screen.
Now I am hoping that EMUI 4 will solve that issue.
Did you find a solution by chance?
philip00026 said:
@Zulu:
Is your issue that the fingerprint setup menu item does not even show up in the settings menue even when you re-flash stock rom and EMUI 3.1?
I have that exact issue. I have been trying every possible way to go back to stock, am at EMUI 3.1 now with original Recovery. But still the fingerprint menu item still does not show up in the setup menue screen.
Now I am hoping that EMUI 4 will solve that issue.
Did you find a solution by chance?
Click to expand...
Click to collapse
hi yes same issue i couldn't get phone to update to b140 or anything so I've just reflashed cm13 this time which went without any issues this time round. when i went back to stock the fingerprint was not even in menu same as you
i will not buy a cheap budget phone anymore this is way to much aggro lol and I've flashed loads of phones before and never had these issues on this scale I'm going to be buying another phone in a couple of months
the only reason i wanted to flash in first place as i thought stock was laggy
let me know if you get your issues sorted and then give me a step by step guide please when you have done this
also i did unlock my boot loader via dc client software as huawei site for unlocking boot loader never worked for me
:silly:
u can relock the bootloader. i did it. just go to the bootloader with fastboot oem relock ****** command. **** is your 16 digit unlock code. but 1st flash the stock recovery then lock the bootloader.
zulu1875 said:
hi all my first post im wanting to relock 5x bootloader has i unlocked the boot loader unofficial way as my fingerprint scanner is not working so prob needs to go back also it wont update
i tried this via adb fastboot oem lock and it said FAILED ( remote invalid command) plus on the phone in fastbbot red its got PHONE unlocked and FRP UNLOCK
hope someone can help would be appriciated and im running b130 firmware
Click to expand...
Click to collapse
Hello zulu1875, if you are interested you can now contact our support team at 1-844-524-6667 for more information as we now offer an RMA process to re-flash the device back to factory settings. Please keep in mind that re-flashing the device will wipe the memory of the device clean.
HonorUSA_Ashley said:
Hello zulu1875, if you are interested you can now contact our support team at 1-844-524-6667 for more information as we now offer an RMA process to re-flash the device back to factory settings. Please keep in mind that re-flashing the device will wipe the memory of the device clean.
Click to expand...
Click to collapse
Hi thanks for message I'm based in uk does honour uk offer this service as I desp need to back to stock
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.
Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.
Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.
OK will give that a shot tomorrow thanks
If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.