Got myself in a bit of a mess
Had a S-OFF device with bootloader unlocked (using revone).
Was going to sell on, so put back to S-ON, but this was done before I relocked the bootloader (so bootloader stayed at Unlocked). I've now relocked the bootloader using fastboot oem lock.
However wifi is not working (stuck on turning on), as I appear to have ended up with the wrong kernel.
However, trying to unlock (through htc dev), got by unlock_code.bin, I am running the following command;
fastboot flash unlocktoken Unlock_code.bin
which responds with;
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.142s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.146s
But it is not popping up with anything on the phone, and the bootloader stays at relocked.
Am I stuck, at the bootloader was originally unlocked using revone and now is at status relocked ?
Thanks.
saquib said:
Got myself in a bit of a mess
Had a S-OFF device with bootloader unlocked (using revone).
Was going to sell on, so put back to S-ON, but this was done before I relocked the bootloader (so bootloader stayed at Unlocked). I've now relocked the bootloader using fastboot oem lock.
However wifi is not working (stuck on turning on), as I appear to have ended up with the wrong kernel.
However, trying to unlock (through htc dev), got by unlock_code.bin, I am running the following command;
fastboot flash unlocktoken Unlock_code.bin
which responds with;
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.142s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.146s
But it is not popping up with anything on the phone, and the bootloader stays at relocked
Am I stuck, at the bootloader was originally unlocked using revone and now is at status relocked ?
Thanks.
Click to expand...
Click to collapse
Hi, what boot r u? If you are 1.44 use revone again. The only other thing I can think of is to call fonefunshop to see if they could s-off the device again for you.
I am on HBOOT 1.54 unfortunately.
I don't really want s-off, just the unlocked bootloader.
saquib said:
I am on HBOOT 1.54 unfortunately.
I don't really want s-off, just the unlocked bootloader.
Click to expand...
Click to collapse
Just to cover all bases - after it said complete did you reboot the bootloader using 'fastboot reboot-bootloader'?
I had not, I was expecting the phone screen to display the options to unlock ?
Anyway, I tried that, which gives the following;
fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: loading custom splash failed)
finished. total time: 0.016s
Any ideas? I need to unlock the bootloader as my WiFi is broken. Cannot turn on, I think the reason is that I've ended up with a kernel for a 401.1 Rom but I'm on a 401.8 Rom.
Hi,
if you cid allows try an ruu. If no go then send off to fonefunshop to get s-off. Its got to be worth it to get the phone working again. From personal experience I can say they are fast. Give them a call first to discuss.
It sounds like you possibly went S-on with a custom Hboot. Perhaps the one that removes the red text?
Sent from my One using XDA Premium 4 mobile app
Thanks for the input.
1. I used one of the roms from this thread to return to stock : http://forum.xda-developers.com/showthread.php?t=2471869
2. Comparing the HTC one with the broken wifi to another htc one on 4.2.2, the old difference I can see is in the kernel versions;
- Broken HTC: 3.4.10-g445d072
- Working HTC: 3.4.10-g28df0d6
I don't really want to spend £30 on s-off, if I could unlock the bootloader, I should be able to flash a rom to get wifi working, I think ?
Thanks.
EddyOS said:
Just to cover all bases - after it said complete did you reboot the bootloader using 'fastboot reboot-bootloader'?
Click to expand...
Click to collapse
I had not, I was expecting the phone screen to display the options to unlock ?
Anyway, I tried that, which gives the following;
fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: loading custom splash failed)
finished. total time: 0.016s
Anyone with any ideas ? Is there anything I can do without a RUU and a relocked bootloader to change the kernel to the correct version for the rom ? Thanks!
One thing I've noticed is the the first screen I see when the phone is turned on is a Google logo rather than the HTC logo. Obviously I've got some remnants of a Google Edition Rom left on my phone.
Am I completely lost without s-off ?
Sent from my HTC One using xda app-developers app
Have you fixed this? I have the same problem. Thanks
FIXED!!
I had this exact problem. Android 4.3 is now available via control panel, software updates. I downloaded via mobile data and installed the update and the phone now works fine, including wifi. Hopefully you have a good mobile data plan because the download is >600MB
Related
Hi guys, i performed an all in one update to 4.2 from stock non rooted 4.1, it didnt work properly and now im stuck in fast boot screen with a locked bootloader.
i see the START button with the google icon, i can switch it between power off, recovery mode, restart bootloader. Start does nothing, power off works, restart bootloader works, recovery mode does nothing and says booting failed.
nothing works on the tablet its self, no matter what option i try i cant get out of that part.
I then downloaded WugFresh's all in one toolkit, ADB options are out of the question as that doesn't recognise in this part of the N7. fastboot stuff works, i tried pretty much ever option including the softbrick/bootloop recovery options and they don't even work.
When doing that, the command prompt that starts up spits this out:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.021s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.41
Baseband Version.....: N/A
Serial Number........: 015d2ea4d02c0812
--------------------------------------------
checking product...
OKAY [ 0.029s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4896 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.161s
what do i do? am i screwed?
I think you might want to unlock the boot loader first.
You would need to run the command
fastboot oem unlock
And that will unlock the boot loader which should mean that you can flash the ROM.
And then if you want to lock the boot loader again after flashing the ROM you would need to run
fastboot oem lock
Another example of why toolkits suck. If you can't do it manually don't, otherwise you will struggle with problems like this.
The update failed in some way because you still have the bootloader from 4.1.2. So long as you can get into the bootloader, you are not bricked though. Just got to unlock it and flash manually the update using the fastboot, method and you'll be sweet.
Sent from my Nexus 7 using Tapatalk 2
dr.m0x said:
Another example of why toolkits suck. If you can't do it manually don't, otherwise you will struggle with problems like this.
The update failed in some way because you still have the bootloader from 4.1.2. So long as you can get into the bootloader, you are not bricked though. Just got to unlock it and flash manually the update using the fastboot, method and you'll be sweet.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
This :thumbup:
Sent from my SPH-D710 using Tapatalk 2
If your tablet turns on, it's not bricked.
So many people use that term with no clue as to what it means.
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
pmikec said:
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Click to expand...
Click to collapse
I don't know why it refuses to relock but another question: why do you want it to be relocked? It is adviced to only relock a bootloader when it is absolutely needed (warranty case, resale...)
Face_Plant said:
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
Click to expand...
Click to collapse
This did the trick. I'm not sure why I didn't just try the old command myself before asking. Thanks!
I have a review phone of the P9 (the 09 version). I'm trying to put a nougat beta on it. Bootloader came unlocked- see attached photo. When i go into bootloader fastboot devices sees it no worries. I ran the bat file to check and yes the bootloader is unlocked according to it.
Problem is that when I try to flash TWRP i get:
Code:
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery" (22368 KB)...OKAY [ 0.655s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.667s
I am not a noob to hacking android etc that is for sure but this is doing my head in. Is there an issue with the bootloader unlock? I've sent an email to Huawei support people as well. I had issues getting a bootloader unlock code anyway as being in Australia it doesn't allow be to do anything in Huawei ID, so i cannot get the code. I also tried using the beta app but even when using a VPN it was geoblocked.
ideas on what is going wrong?
thanks
Make sure OEM unlock is enabled in developer settings. If you have an app called "Phone Finder" or any other phone tracker app, disable it. If that doesn't work, you can try restoring phone to factory settings and enable OEM unlock again then try again.
I tried the above stuff mate- unfortunately it did not work. only phone finder is android device manager and it is turned off (phone is basically stock). OEM unlock is enabled correctly etc. even factory reset and did it all over again. oh well. i give up for now. i would love root on this too...
I spent A few hours or so trying to unlock and than root my phone. I have been unable to unlock the bootloader so far, i think.
I ran my IMEI to make sure i was running the right stuff for the right phone.
im getting stuck at the point where you run fastboot to unlock with the token generated by following HTC Dev's bootloader, or really, right after it.
when i do this:
C:\>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.150s
From the various articles ive read, your supposed to get some prompt or option on your phone to unlock the bootloader, but i never see this option on my phone? could it be because my bootloader is unlocked?
Since im new and am not allowed to post external links yet, a screen shot of my bootloader on imgur at /a/JV4eJ
Looking at the image, i think my phone's bootloader is allready unlocked?
Where im hitting a wall is when trying to get the TWRP custombackup to work
I keep getting this error.
C:\>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (20020 KB)...
OKAY [ 2.373s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.400s
I've tried renaming it to twrp.img, and leaving it as twrp-3.1.1-0-hima.img
I have an old hboot on this phone, and read somewhere that i should try an 2.8.7.*.img, so i did aswell, but they all produce the above results.
Any adivce and feedback is much appreciated, and thanks for reading.
The end goal for me is tied into this guide which i have been following
Are you in download mode?
Sent from my HTC One M9 using Tapatalk
lazyguyMC said:
Are you in download mode?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I am not sure. I reboot my phone via adb and it boots to a normal home screen. Ive tried it from there with no luck. IM trying it from the bootloader screen( im assuming this is not the download screen?) If thats the problem, than i am abit confused on how to get to download mode. ive tried adb reboot download, but it just puts be back at the main os screen.
The download mode screen is similar to a stock Android recovery screen. It is black and has many options like show info, show barcodes, reboot to download mode, reboot to bootloader, etc etc. To go in there, shut down your phone, then press and hold volume down and power. Then, you should be able to unlock your bootloader. (Make sure Enable OEM unlock is checked in developer options.)
Sent from my HTC One M9 using Tapatalk
lazyguyMC said:
The download mode screen is similar to a stock Android recovery screen. It is black and has many options like show info, show barcodes, reboot to download mode, reboot to bootloader, etc etc. To go in there, shut down your phone, then press and hold volume down and power. Then, you should be able to unlock your bootloader. (Make sure Enable OEM unlock is checked in developer options.)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe thats one of my issues. Reboot to download mode is not an option when i power down to the bootloader. And also, there was no option for me to enable oem unlock in the dev options.
is it possible the imei number i have is telling me lies?( the reason i ask, is when i run it, it says an m9, but when im in the bootloader it says *** Unlocked *** followed y this line : M7_WLS PVT SHIP S-ON RH
Hmm......You sure that isn't an MY?
Sent from my HTC One M9 using Tapatalk
imei.info tells me its an m9 and swappa tells me its an m7. im so confused. I tried using a key from htc dev for the m7 just abit ago, and it succeeds aswell, but im stil not prompted to unlock the phone.
It's definetely a M7 (the sprint version to be exactly) and not a M9. Those IMEI checks are more than inaccurate. You should always trust the infos in your bootloader. Alternatively, you can take a look at the serial number of the phone. There's a guide written by Llabtoofer (on his website) which explains how to "read" it.
If the bootloader already is unlocked then of course you won't see that prompt. And TWRP fails to flash since you can't flash M9 files on a M7 (at least if your phone isn't S-OFF and if it was you would gain a paperweight by doing so).
I contacted a fellow mod so that the thread will get moved to the correct forum.
OK so i got twrp installed and i attempted to get magisk to install but that failed, so i used SuperSu. I did what i wanted than unrooted and got rid of the twrp custom recovery. The problem is im failing my Safety Net. So after some tedious searching i found a stock rom for my phone, and re-flashed it. Im still failing safetynet with a fresh verified stock rom for my phone. I dunno where to look now in hopes in getting it to pass safety Net. Is it possible SuperSu left something behind? When i installed the Rom via a RUU.exe, wouldn't that have erased all the SuperSu breadcrumbs? i know in my hboot menu it says relocked(not tampered anymore).
brad35309 said:
OK so i got twrp installed and i attempted to get magisk to install but that failed, so i used SuperSu. I did what i wanted than unrooted and got rid of the twrp custom recovery. The problem is im failing my Safety Net. So after some tedious searching i found a stock rom for my phone, and re-flashed it. Im still failing safetynet with a fresh verified stock rom for my phone. I dunno where to look now in hopes in getting it to pass safety Net. Is it possible SuperSu left something behind? When i installed the Rom via a RUU.exe, wouldn't that have erased all the SuperSu breadcrumbs? i know in my hboot menu it says relocked(not tampered anymore).
Click to expand...
Click to collapse
What I would do is run the latest RUU. I've done so on my m7 and it always passes SafetyNet at that point. Make sure you back up anything you want to save first.
I will try reflashing via fastboot with my current rom. If that still fails, I'll try the latest. I'm just hesitant because it comes with the newest security patch, and I need one that's before the March 2017 patch
The last official update for the M7 got distributed in 2015. All RUUs for that Device will be on a security patch that is older than March 2017.
Sent from my HTC One M9 using XDA Labs
i downloaded the latest RUU, and i installed via the executable. it was successful, however i am still failing the safety net check. i attempted again via Fastboot, but i keep getting this error
C:\>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (45578 KB)...
OKAY [ 2.894s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.027s
i got the firmware from the same page as the post mentioned above. Do i have to do something special to get it to take?
brad35309 said:
i downloaded the latest RUU, and i installed via the executable.
Click to expand...
Click to collapse
Did you install version 6.23.651.10 from this thread using the exe? I've reset my phone after running custom ROMs using it and it passed SafetyNet fine afterward.
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?
Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10
Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com