Help! Fastboot oem lock wrong kernel... - HTC One X

My girlfriend wanted to go back to Stock firmware but forgot to flash the original boot.img ...
And introduced the fastboot oem lock....
Now is written at the top - locked, and no ability to flash the kernel, or recovery ...
Htc dev unlock does not work .. when the phone is rebooted, everything remains as it was - locked ...
Ruu begins to flash, comes to an end, but nothing happens...
Can't enter recovery...
There are any ideas for unlocking? Or a direct route to the service center?
Blocked kernel - RenovateROM Final 1 - Unofficial build 1
Hboot 1.33.0000
cid_621
sorry for my english))

The first time you unlocked the device the .bin unlock code was send in your mail box, check if its there. If its there you copy it to the fastboot folder (or the folder where you flash from)
Phone in fastboot usb mode and do this command
Fastboot flash unlocktoken unlock_code.bin
This unlocks the bootloader and you can start flashing

Related

[Q] Weird boot problem

Hello,
i got this weird problem when i tried to install clockworkmod from here: knowyourmobile(dot)com/smartphones/htc/onex/onexuserguides/1419609/how_to_root_your_htc_one_x.html
My bootloader is unlocked.I downloaded the file end ran the script.When everything finished my phone got stuck in the boot screen.I tried to erase chase or install stock kernel and recovery (using all ine one tool from this site)but nothing solved it.The only thing that i havent tried yet is to flash a boot.img because i cant find one (i got the phone from europe(paris) and i have the jelly bean update and i cant find the stock boot.img).Any solutions?
Thanks in advance!
If you flash a rom you can find the boot.img inside the rom.zip file ! Flash the boot.img with fastboot commands and do a wipe in recovery and install the rom.zip file from sd card !
And its not a weird boot problem, it's a common user mistake that is done by many....many people
Ow and a kernel = boot.img
Thanks for the reply,Is there another way?Because i dont want to use a custom ROM.I just rooted it in order to install some apps that require root.I said its weird because i flashed the kernel and the problem stays
Do you have a custom recovery at the moment ? And did u do a nandroid backup of the stock rom ?
I think it's weird that you first say that you flashed the kernel and then you say you can't find the boot.img.......
Well i didnt know that kernel=boot.img and i dont know if the all ine one xda program puts the right program for jb.I didnt backup anything,I have clockworkmod recovery
Do you know fastboot and the commands ?
Fastboot oem readcid
and
Fastboot getvar version-main
And post these results here !
I will try it.THis doesnt format anything,right>?
Nope....
You have to enter the recovery from the bootloader - choose hboot and then recovery....if it enters check which version you have (cwm 5.8.4.0 ?)
From there you can go to mounts & storage and then choose at the bottom mount as USB drive
Then you can at least copy everything from the sd to a safe place. I think that the internal data is going to be lost ! Like messages and apps .... Everything that is stored in the cloud is safe anyway
cid:htc__203 OKAY
version-main:3.14.401.27
You can get the ruu with the same number on www.htcruu.com and put the phone in bootloader/fastboot USB
Relock the bootloader with
Fastboot oem lock
And run the ruu.exe with admin rights ...it will put the phone back to 100% stock
This is the one you need
http://www.htcruu.com/download.php?...Radio_5.1204.162.29_release_298897_signed.exe
Nice!Now to reunlock the bootloader i will do the same things i did the first time or there is a command for that?
Yes if you still have the unlock token.bin file you can unlock the bootloader with a fastboot command, the correct command slipped my mind at the moment !
Otherwise you can to the htcdev site again and unlock it there
fastboot flash unlocktoken Unlock_code.bin
Sent from my One V

[Q] Stuck on bootscreen after flash - please help.

Hi.
I flashed Android Revolution HD 18.4 on to my phone and now it's just get stuck on bootscreen.
And I can't get to my sd card via computer when in fastboot.
If anyone have any suggestions on what I can do, please help me.
Thanks.
Enter the bootloader and go to recovery from there. Mount the sdcard as a diskdrive/mass storage device with the option witin the recovery !
What hboot do you have ?
What recovery do you have ?
thanks.
i mounted it now and flashed boot.img and then flashed the rom but now it's getting stucked on the htc-one-beatsaudio-screen.
any thoughts on what to do?
What recovery ?
What hboot number ?
hboot 1.12.0000
recovery CWM v6.0.2.7
To e able to run JB roms you need to update the hboot first !
in this thread - http://forum.xda-developers.com/showthread.php?t=1920060 - it says "IF YOU HAVE NO CID NUMBER LISTED ABOVE, STOP NOW!"
my cid is H3G_G04. should I go back to ics or is there a way for me to have jb?
(thanks very much for you help by the way)
You can check this thread
http://forum.xda-developers.com/showthread.php?t=1927048
i did these steps exept no. 5 cos' i don't have a unlock_code.bin file.
1) go into fastboot and enter "fastboot oem lock" - the device will reboot
2) go into fastboot again and enter "fastboot oem rebootRUU" - there will be a black screen with a silverish HTC logo
3) enter "fastboot flash zip firmware.zip" (you need the firmware.zip from page 1 for this)
3a) enter the same again, the green bar under the logo should go to 100% (either after the first or second time)
4) enter "fastboot reboot-bootloader" to go back to your fastboot
5) unlock your device again with the unlock code ("fastboot flash unlocktoken Unlock_code.bin")
6) Restore your old boot.img (fastboot flash boot name_of_boot_file.img) and recovery (fastboot flash recovery name_of_recovery_file.img), make sure you copied them from the nandroid backup folder we created earlier into the folder that contains the fastboot.exe you're using.
(7) Reboot and you should now have Hboot 1.39 with your old boot and recovery.
now i have hboot 1.39 but... now when i go in to recovery it isn't cwm anymore. it's just a logo of a phone with a red varning-sign over it. then i get in to som sort of android screen but when i unlock it the screen turns white with green htc logo. any thoughts?
You need to unlock the bootloader and flash a custom recovery
Go to the htcdev site and get a new unlock code.bin file
Now it's working, Thanks so very much man! You're awesome! =)
Thank you very much ! and good you got it solved ! :good:
CASE CLOSED !

[Q] Htc one Bricked Need help

I tried doing a manual ota update, only getting to flashing the firmware.So when I tried to flash the ota I was unable to due do it relocking my phone and wiping everything.I still have s-off but I cant do anything in fastboot since its not unlocked and my custom recovery was deleted leaving me with stock.Is my htc bricked? If so is there any way to get it to boot? Thanks
RubberThunder said:
I tried doing a manual ota update, only getting to flashing the firmware.So when I tried to flash the ota I was unable to due do it relocking my phone and wiping everything.I still have s-off but I cant do anything in fastboot since its not unlocked and my custom recovery was deleted leaving me with stock.Is my htc bricked? If so is there any way to get it to boot? Thanks
Click to expand...
Click to collapse
Not at all, you are fine. Since you are s-off, you can flash a stock RUU and start fresh.
Download this RUU - http://goo.gl/JEkyCk
Then follow this instruction -
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip rom.zip (rename file to rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip rom.zip
That will leave you in stock 4.3 android, then you can just use a command line to unlock bootloader since you are s-off.
Hope I helped!

[GUIDE] How to revert back to stock Android. VERY EASY!

For the last two days I tried to revert my HTC One V back to stock android. As in, the way I got it when I first booted it up. I experienced that this progress was pretty difficult. Maybe this was because I was used to the AOSP niceness of Google's LG NExus 4 or because HTC made it very hard to say the least to downgrade/upgrade to their own stock ROM.
I may not have the original sources for all files because I deleted some original .zip files and only have the extracted files.
First off, I wouldn't do any of this if you have important files on your device, I wiped everything from my phone a dozen of times in the process and it didn't care because I didn't had any important files on their.
Alright, so what we want to achieve is to get to the latest version of HTC's RUU version "2.22.401.7". The RUU I could find was "2.22.401.1" so we're gonna have to d/l some OTA's later on via our device if everything is set up.
So obviously everyone who is trying to revert back has somewhere unlocked their bootloader by doing
fastboot oem get_identifier_token
and
fastboot flash unlocktoken Unlock_code.bin
Please remember this: ANY RUU will fail every single time if your device is LOCKED. It will ONLY work if it's unlocked or relocked.
So first off what we gonna have to do is relock/unlock our device. You can relock your device by going into fastboot[1] mode and running the following command:
fastboot oem lock
Myself have expierenced an error that told me it "FAILED". Please reboot your bootload:
fastboot reboot-bootloader
And check the locked status at the top. If it says "RELOCKED", succes! If it didn't, retry the command above.
Next, we're relocked so we can run the RUU. Please look at the text file at the RUU source [2] for the download links. In this .zip file are the files inside the RUU wizard. You can run the wizard by executing "ARUWizard.exe" and you can view the contents of the actual ROM in "rom.zip extracted" and you can find the original ROM in "rom.zip". Since these are the files the wizard will be using (except rom.zip extracted folder) please do not touch them.
Alright, so we've got the extracted files of the RUU and we're ready to update. Please boot your phone in fastboot mode and connect it to your computer via USB. Now run the "ARUWizard.exe" file and let it update. I couldn't think of a situation where this could go wrong, so please ask below if you face any problems.
The wizard will flash stock radio, recovery andsystem.img (the actual ROM you all know) so by doing this you lose your custom revovery.
When your phone boots up you've gotta go through 3-4 updates till it's on "2.22.401.7".
I recommend not flashing a custom recovery right away because when you install/download OTA updates it isn't able to flash it right. In the meantime if you want root[3] use this command:
adb install -s supersu.apk
When you're on the latest version you have to unlock your bootloader, otherwise you cannot flash a custom recovery or kernel or whatever. You can do this via HTC[4]. I think there are enough guides on how to do this, but in short:
- create an account with an legitimate email address
- Select "all other supported devices" from the list
- follow on screen instructions.
Seriously everything is on there, HTC made it really easy.
If you want to install a custom recovery I recommend using TWRP[5]. Please flash TWRP by booting into fastboot and running the following command:
fastboot flash recovery twrp_recovery.img
Troubleshooting
There isn't really a lot that can go wrong if you do this. But when you're stuck on a screen or you think your device is "bricked" or stuck in a bootloop do these things:
- First off, hold the power and volume down button till the device goes down. If it's down, release the buttons and then hold the same buttons again till you're in bootloader
If that doesn't work do either of these commands (make sure your device is connected via USB, hehe)
Make sure fastboot and/or adb is working first:
fastboot devices
adb devices
If fastboot is working:
fastboot reboot-bootloader
If ADB is working:
adb reboot bootloader
adb reboot recovery
If you have any questions, please ask me. I did a dozen of things these two days, I may forgotten something because I did a crapload of things all at once.
Cheers!
Sources:
[1] http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930
[2] http://rg.to/file/aaca8c0c03e655d6df78242b4cea931b/hov.zip.html
http://ul.to/dfmg5dnw
https://mega.co.nz/#!wBcUiIxD!uIkyqZLgFErSItBTu3K7RY3eyUmXVUg60rcB-B-QRWE
Please request other providers below.
[3] http://download.chainfire.eu/supersu
[4] http://www.htcdev.com/bootloader
[5] http://techerrata.com/browse/twrp2/primou
tl;dr
unlock bootloader -> run RUU -> done
This is great and all, but is this for the PRIMO-C or U? US version? etc... etc..

ROOT Elephone S7 4gb on Windows 10x64 at last!

For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)

Categories

Resources