Related
Hey guys,
I might be wrong here but this is my last hope.
Rooted my One X yesterday, tried to install a .zip so that annoying menu bar would go away.
Didn't word out well, got in a 'bootloop', decided to install the stock RUU, but im getting this ERROR 120 30% massage.. i already tried different stuff but nothing seems to work.
Then things got worse, decided to let it charge for a while, but now i can't even get in recovery mode, it redirects it to fastboot.
Thnx in advance
You will need to relock the bootloader to flash the stock ROM
From fastboot do "fastboot oem lock" then try again. Try flashing from Fastboot and if that doesn't work try bootloader.
Alternatively, flash custom recovery and try flashing over original versions of the whatever files you replaced with your modification.
Electronic Punk said:
You will need to relock the bootloader to flash the stock ROM
From fastboot do "fastboot oem lock" then try again. Try flashing from Fastboot and if that doesn't work try bootloader.
Alternatively, flash custom recovery and try flashing over original versions of the whatever files you replaced with your modification.
Click to expand...
Click to collapse
Already relocked the bootloader, installing RUU rom in bootloader, got same ERROR 120 massage.
Though i had a custom recovery, apparently i dont (im a noob), but i cant even get in the recovery mode.
Already reinstalled stock recovery...
TheNetherTukkers said:
Already relocked the bootloader, installing RUU rom in bootloader, got same ERROR 120 massage.
Though i had a custom recovery, apparently i dont (im a noob), but i cant even get in the recovery mode.
Already reinstalled stock recovery...
Click to expand...
Click to collapse
Corrupt RUU?, try downloading it again...
Are you sure you downloaded the correct RUU for the region of your device?
Tony Tan said:
Are you sure you downloaded the correct RUU for the region of your device?
Click to expand...
Click to collapse
If you are certain your ruu is for your region and not corrupted then from http://forums.androidcentral.com/ge...o-get-error-120-battery-less-than-30-a-2.html
Try this
Running Windows 7:
Make sure battery is over 30% (but that's why we're here, isn't it? It IS over 30%) Turn phone off Take battery out for a minute, then replace the battery DO NOT turn phone back on Plug into USB Hold VOL DOWN button and press the power button for 5 Seconds but don't let go of VOL button Make sure the choice FASTBOOT is highlighted and press the power button to select it You should see FASTBOOTUSB up top Stay on this screen while you go to your computer Exit HTC Sync if it's running, wait a minute, then open HTC Sync again, see if it connects (Mine didn't connect to sync, but I left the window open in the bkgrd) Open the updater and go through the steps. Update should begin without error message.
Hope this works for you guys. I tired countless ways to do it before breaking down and calling in. This way worked the first time for me.
Sent from my HTC One X using xda premium
If you relocked you also need to flash boot.img in fastboot from the stock rom you want to use.
Extract the ruu.exe and take the boot.img out, flash it using the adb tools and fastboot.
TheNetherTukkers said:
Already relocked the bootloader, installing RUU rom in bootloader, got same ERROR 120 massage.
Though i had a custom recovery, apparently i dont (im a noob), but i cant even get in the recovery mode.
Already reinstalled stock recovery...
Click to expand...
Click to collapse
Laurentius26 said:
If you relocked you also need to flash boot.img in fastboot from the stock rom you want to use.
Extract the ruu.exe and take the boot.img out, flash it using the adb tools and fastboot.
Click to expand...
Click to collapse
Where can i find my radio version? And cant find any boot.img in my RUU file.
It's called 'boot_signed.img'
The radio I don't know.
TheNetherTukkers said:
Where can i find my radio version? And cant find any boot.img in my RUU file.
Click to expand...
Click to collapse
Laurentius26 said:
It's called 'boot_signed.img'
The radio I don't know.
Click to expand...
Click to collapse
Can't find it, but i cannot go into recovery mode, wich makes me think there is something seriously wrong..
TheNetherTukkers said:
Already relocked the bootloader, installing RUU rom in bootloader, got same ERROR 120 massage.
Though i had a custom recovery, apparently i dont (im a noob), but i cant even get in the recovery mode.
Already reinstalled stock recovery...
Click to expand...
Click to collapse
Perhaps ur battery is less than 30%.
Sent from my HTC One X
TheNetherTukkers said:
Can't find it, but i cannot go into recovery mode, wich makes me think there is something seriously wrong..
Click to expand...
Click to collapse
To extract contents from an RUU, do this.
Run the desired RUU
Go to search and type in '%temp%' (without the quotes)
A folder named 'temp' will appear, open that, and search in it for 'rom.zip'
Open the zip, and extract what u jeed from there.
And hit thanks!
Sent from my HTC One X
@TheNetherTukkers, extract the boot_signed.img as theDroidfanatic beautiful explains.
Attached I have the adbtools, extract and put the folder on your desktop's c:\ together with boot_signed.img
So you have c:\adbtools\
adb.exe
AdbWinApi.dll
fastboot.exe
boot_signed.img
Now put your device in fastboot mode and connect to your pc.
In start\search on your pc type 'cmd' without the quotes and hit enter.
In the command window that pops up browse to c:\adbtools and type the following:
fastboot flash boot boot_signed.img [hit enter]
fastboot erase cache [hit enter]
After this you go into fastboot again and flash the ruu.
got this,
c:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)...
OKAY [ 0.563s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.766s
Got everything adb java etc already installed..
waz675 said:
Try this
turn phone off Take battery out for a minute, then replace the battery
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
are you sure?
Are you sure your phone is relocked?
Which ruu are you trying to flash?
TheNetherTukkers said:
got this,
c:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)...
OKAY [ 0.563s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.766s
Got everything adb java etc already installed..
Click to expand...
Click to collapse
Laurentius26 said:
Are you sure your phone is relocked?
Click to expand...
Click to collapse
Pretty sure, it says ***** RELOCKED ****** in bootloader..
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed, is the RUU im trying to flash.
Hmmm, that's strange.
You have a branded HTC One X?
And which rom are you trying to flash?
Try >> THIS link, it's the 1.29.401.11 version, credits to Football for the RUU.
TheNetherTukkers said:
Pretty sure, it says ***** RELOCKED ****** in bootloader..
Click to expand...
Click to collapse
Laurentius26 said:
Hmmm, that's strange.
You have a branded HTC One X?
And which rom are you trying to flash?
Try >> THIS link, it's the 1.29.401.11 version, credits to Football for the RUU.
Click to expand...
Click to collapse
I dont think its branded.. i mean i got it from Vodafone (holland) but i dont see a special RUU for that anywhere so i figured i had the genereal european version.
You must be sure about that because there do exist Vodafone updates.
Have a look HERE at the bottum, Vodafone roms for several countries. No Dutch dho.
Did you buy the phone straight from Vodafone or did you use a retailer?
Maybe you could check with them?
TheNetherTukkers said:
I dont think its branded.. i mean i got it from Vodafone (holland) but i dont see a special RUU for that anywhere so i figured i had the genereal european version.
Click to expand...
Click to collapse
Okay, so i was just scrolling through my apps, then my phone randomly restarts, and wont go past the HTC Beats screen, and when it does, the screen is just black.
So i restart into bootloader, and it says "Locked" at the top, so it appears its relocked itself?
WHAT DO I DO? WAS rooted and running Revolution HD-9.8 ROM.
Thanks
Edit: Tried unlocking the bootloader again, no result, got error message "FAILED (status read failed (Too many links))
finished. total time: 6.219s"
Edit: Battery is 3970mv, and i cannot get into recovery (i flash RUU HELP PLEASE.)
my friend Mr Hofs said to me your bootloader may unlock and only show locked !
i try to install CWM recovery !
C:\adb-Fastboot>fastboot flash recovery CWM.img
sending 'recovery' (5742 KB)...
OKAY [ 0.754s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.960s
i run CMD in ADMINISTRATOR
hey when i flash RUU phone reboot and go to bootloader and i try to reboot (not anything happend only after 3sec show HTC logo and go to bootloader (recovery and factory rest like this)
The most important thing you didn't tell is that the RUU flashed successfully, and that the phone didn't boot up. And that your bootloader goes from unlocked to LOCKED instead of relocked as it should......
The failed status error is normal, its confirmed everywhere on xda
Mr Hofs said:
The most important thing you didn't tell is that the RUU flashed successfully, and that the phone didn't boot up. And that your bootloader goes from unlocked to LOCKED instead of relocked as it should......
The failed status error is normal, its confirmed everywhere on xda
Click to expand...
Click to collapse
my phone after (rom crash and ..) unlocked ==> locked
i don't see relocked status in my life !!
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed
now it's running (RUU)
wait........
"Fingers crossed and burning a candle"
and when it ends up successful you plug out the cable before you reboot !
ERORR [159]:IMAGE ERROR
The rom update utility canot update your android phone.
please get the correct rom update utility and try again
now try ICS ruu
And are you sure the fastboot command
Fastboot getvar version-main
Gave the the 2.17.707 number and not the 2.14.707 number ?
View attachment 1672111
Mr Hofs said:
And are you sure the fastboot command
Fastboot getvar version-main
Gave the the 2.17.707 number and not the 2.14.707 number ?
Click to expand...
Click to collapse
sorry ! screen shot in zip file
Seen the picture .. its freakin bizar ! Ruu matches and the bootloader is locked, ruu runs succesfull but the phone does not boot up..... Unlocking the bootloader is succesfull but the bootloader remains locked !
:banghead: i cant seem to understand this !
Is your recovery CWM or stock? If you were running ARHD I suppose you had a custom recovery aswell?
As far as i know RUU won't work until you flash stock recovery.
Hope this helps
basd43 said:
Is your recovery CWM or stock? If you were running ARHD I suppose you had a custom recovery aswell?
As far as i know RUU won't work until you flash stock recovery.
Hope this helps
Click to expand...
Click to collapse
Yes that's an option, but i tested a ruu once with custom recovery,kernel and rom and it worked flawlessly ! The main problem at this moment is that he flashes the .bin code and that the bootloader remain locked ! The commands are correct, but it refuses to unlock ......
Mr Hofs said:
Yes that's an option, but i tested a ruu once with custom recovery,kernel and rom and it worked flawlessly ! The main problem at this moment is that he flashes the .bin code and that the bootloader remain locked ! The commands are correct, but it refuses to unlock ......
Click to expand...
Click to collapse
Did he try to flash a custom rom despite the fact the boorloader says locked? Maybe it just says locked but is actually unlocked? Happend to me once and after rebooting into bootloader after flashing it said unlocked... dont ask why, just happened...
Yes i believe he tried that too, got faile attempt remote not allowed error.....he rebooted the bootloader a couple of times and it said unlocked indeed, maybe that's the solution....keep rebooting the bootloader untill it says unlocked and then start flashing directly
Its giving me a headache ..... Been thinking about this for 2 days already
basd43 said:
Is your recovery CWM or stock? If you were running ARHD I suppose you had a custom recovery aswell?
As far as i know RUU won't work until you flash stock recovery.
Hope this helps
Click to expand...
Click to collapse
You don't need to flash anything to use an ruu. The only thing that you need is a locked bootloader.
As the other user said. It may be reporting status wrongly. If you're going to try the ruu again. I suggest running fastboot OEM lock first just to make sure
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
You don't need to flash anything to use an ruu. The only thing that you need is a locked bootloader.
As the other user said. It may be reporting status wrongly. If you're going to try the ruu again. I suggest running fastboot OEM lock first just to make sure
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes .... But can you tell me why the ruu ended up as successful ? I just dont seem to get that ?
Another thing ! If you bootloader says LOCKED you should also have full warranty !! If nothing else helps its best to go to the htc service center
I have an HTC One, that was a replacement for another phone. It came pre-installed with 3.11.605.1 update, and s-off via Firewater (running the Firewater hboot). I need help returning back to complete stock, with a locked bootloader, and s-on. since I need to send it back in for Warranty. Please and thank you.
Shriggly said:
I have an HTC One, that was a replacement for another phone. It came pre-installed with 3.11.605.1 update, and s-off via Firewater (running the Firewater hboot). I need help returning back to complete stock, with a locked bootloader, and s-on. since I need to send it back in for Warranty. Please and thank you.
Click to expand...
Click to collapse
follow this guide:
http://forum.xda-developers.com/showthread.php?t=2475216
synisterwolf said:
follow this guide:
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
I currently have the 1.10.605.08 RUU from an older HTC One, Do you think I'm able to use that RUU on this phone, even if it came with 3.11.605.1 pre-installed from Verizon?
Shriggly said:
I currently have the 1.10.605.08 RUU from an older HTC One, Do you think I'm able to use that RUU on this phone, even if it came with 3.11.605.1 pre-installed from Verizon?
Click to expand...
Click to collapse
as long as you are s-off you can use any of the RUU. But if you do use the older ones, you will need to update OTA to the latest or VZW will know.
you can however download the latest one here:
http://forum.xda-developers.com/showthread.php?t=2765784
synisterwolf said:
as long as you are s-off you can use any of the RUU. But if you do use the older ones, you will need to update OTA to the latest or VZW will know.
you can however download the latest one here:
http://forum.xda-developers.com/showthread.php?t=2765784
Click to expand...
Click to collapse
Alright, Thanks!
synisterwolf said:
as long as you are s-off you can use any of the RUU. But if you do use the older ones, you will need to update OTA to the latest or VZW will know.
you can however download the latest one here:
http://forum.xda-developers.com/showthread.php?t=2765784
Click to expand...
Click to collapse
As I try to flash the RUU, this is what i get.
./fastboot flash zip Rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 53.287s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (No such file or directory))
finished. total time: 60.874s
Shriggly said:
As I try to flash the RUU, this is what i get.
./fastboot flash zip Rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 53.287s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (No such file or directory))
finished. total time: 60.874s
Click to expand...
Click to collapse
Are you in RUU mode?
Code:
fastboot oem rebootRUU
To be honest, they won't even check if you're rooted or running a custom ROM. They will immediately RUU and see if the phone is usable.
synisterwolf said:
Are you in RUU mode?
Code:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Yeah, I rebooted into RUU.
Cares said:
To be honest, they won't even check if you're rooted or running a custom ROM. They will immediately RUU and see if the phone is usable.
Click to expand...
Click to collapse
Yeah, but i'm not trying to take a risk of paying 600$
synisterwolf said:
Are you in RUU mode?
Code:
fastboot oem rebootRUU
Click to expand...
Click to collapse
The only zip it was able to flash was Santod's 3.11.605.1 Firmware without a boot.img, I used it to get the bootloader back.
Shriggly said:
The only zip it was able to flash was Santod's 3.11.605.1 Firmware without a boot.img, I used it to get the bootloader back.
Click to expand...
Click to collapse
if you are already on the firmware.
flash a stock OTA build and then flash stock recovery then just lock bootloader then s-off. they wont know a difference.
synisterwolf said:
if you are already on the firmware.
flash a stock OTA build and then flash stock recovery then just lock bootloader then s-off. they wont know a difference.
Click to expand...
Click to collapse
I've tried doing that, but the thing is that I forgot that the Bootloader is relocked, so I have no way to flash the recovery. I'm rying to find a way to bypass it, but so far, no luck.
synisterwolf said:
if you are already on the firmware.
flash a stock OTA build and then flash stock recovery then just lock bootloader then s-off. they wont know a difference.
Click to expand...
Click to collapse
Success! I've unlocked the bootloader, and flashed all the stock files! Thank you for your help!
Shriggly said:
Success! I've unlocked the bootloader, and flashed all the stock files! Thank you for your help!
Click to expand...
Click to collapse
oh man, i miss read your OP. Said "locked" bootloader. i thought unlocked.
i am so sorry for that but glad you got it.
synisterwolf said:
oh man, i miss read your OP. Said "locked" bootloader. i thought unlocked.
i am so sorry for that but glad you got it.
Click to expand...
Click to collapse
Now we ran into another problem. As I locked the bootloader, and put back s-on. Now the phone only boots up into the bootloader, it says
*** TAMPERED ***
*** LOCKED***
*** Security Warning***
I'm basically stuck here since it wont boot up into the rom. I'm guessing that we'll have to RUU it to 4.10.505.3?
Shriggly said:
Now we ran into another problem. As I locked the bootloader, and put back s-on. Now the phone only boots up into the bootloader, it says
*** TAMPERED ***
*** LOCKED***
*** Security Warning***
I'm basically stuck here since it wont boot up into the rom. I'm guessing that we'll have to RUU it to 4.10.505.3?
Click to expand...
Click to collapse
try a factory reset from inside the hboot.
synisterwolf said:
try a factory reset from inside the hboot.
Click to expand...
Click to collapse
Can you I've me the button combination for the stock recovery to factory reset it?
Shriggly said:
Can you I've me the button combination for the stock recovery to factory reset it?
Click to expand...
Click to collapse
should be an option in hboot. on the main screen:
Fastboot
Recovery
Factory Reset <----this option.
Simlock
Check SmartSD
Image CRC
Show Barcode
it will boot into stock recovery and take a little bit.
synisterwolf said:
should be an option in hboot. on the main screen:
Fastboot
Recovery
Factory Reset <----this option.
Simlock
Check SmartSD
Image CRC
Show Barcode
it will boot into stock recovery and take a little bit.
Click to expand...
Click to collapse
Still stuck in the bootloader..
I'm in a situation with my HTC One m7 4.4.3 Verizon where:
- I'm S-OFF
- Bootloader is locked
- Stock Recovery
- su no longer available due to OTA upgrade
Does anyone know how I can once again unlock my bootloader?
I have tried following methods but none of them worked:
1. reset lock status. It doesn't work because I don't have su anymore and I don't know how I can install it with stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475914
2. flash custom recovery TWRP using fastboot, but I'm getting FAILED (remote: not allowed) error, probably due to I'm still in locked bootloader.
3. tried running Sunshine, but it thinks that I'm already rooted and is looking for su.
http://forum.xda-developers.com/showthread.php?t=2792487
so, the challenge is: how do I get my unlock bootloader back while on S-OFF without su installed?
Any help is much appreciated.
smallwei said:
I'm in a situation with my HTC One m7 4.4.3 Verizon where:
- I'm S-OFF
- Bootloader is locked
- Stock Recovery
- su no longer available due to OTA upgrade
Does anyone know how I can once again unlock my bootloader?
I have tried following methods but none of them worked:
1. reset lock status. It doesn't work because I don't have su anymore and I don't know how I can install it with stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475914
2. flash custom recovery TWRP using fastboot, but I'm getting FAILED (remote: not allowed) error, probably due to I'm still in locked bootloader.
3. tried running Sunshine, but it thinks that I'm already rooted and is looking for su.
http://forum.xda-developers.com/showthread.php?t=2792487
so, the challenge is: how do I get my unlock bootloader back while on S-OFF without su installed?
Any help is much appreciated.
Click to expand...
Click to collapse
s-off > unlocked bootloader. you dont need the bootloader unlocked to flash recovery. If you are s-off you have full control of phone.
what command are you using to flash recovery? when you do "fastboot devices" in bootloader what does it say?
Hi, thanks for the quick response. Here is the command and output:
fastboot flash recovery openrecovery-twrp-2.7.1.1-m7wlv.img
C:\temp\Android_Root\htc_one>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7wlv.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.276s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.311s
Here is the fastboot devices output:
C:\temp\Android_Root\htc_one>fastboot devices
FA37TS911824 fastboot
What's the output when you type "fast boot devices"
Sent from my iPhone 6 using Tapatalk
Here is the fastboot devices output:
C:\temp\Android_Root\htc_one>fastboot devices
FA37TS911824 fastboot
smallwei said:
Here is the fastboot devices output:
C:\temp\Android_Root\htc_one>fastboot devices
FA37TS911824 fastboot
Click to expand...
Click to collapse
cool so fastboot is seeing the phone.
follow this post and see if you can flash recovery via RUU:
http://forum.xda-developers.com/showpost.php?p=52987867&postcount=2
Thanks much.
If I understand it correctly, flash RUU will wipe out the phone completely, is it true?
I'm holding this method off as the last resort to try after I exhaust all other options.
smallwei said:
Thanks much.
If I understand it correctly, flash RUU will wipe out the phone completely, is it true?
I'm holding this method off as the last resort to try after I exhaust all other options.
Click to expand...
Click to collapse
if you do a full firmware it will wipe. this should be JUST recovery. But i would recommend backing up internal storage. I have not tried this method.
Gotcha. Thanks again. I'll give it a shot.
It works! Thanks so much synisterwolf! You're genius!
I used the Recovery RUU from the following link:
http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
smallwei said:
It works! Thanks so much synisterwolf! You're genius!
I used the Recovery RUU from the following link:
http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
Click to expand...
Click to collapse
now i wonder if you can do the "fastboot flash recovery" way.
anyways, you can now unlock bootloader if you chose too by following the original guide you posted. Let me know if you need anymore help.
:victory:
synisterwolf said:
now i wonder if you can do the "fastboot flash recovery" way.
anyways, you can now unlock bootloader if you chose too by following the original guide you posted. Let me know if you need anymore help.
:victory:
Click to expand...
Click to collapse
Yes, fastboot flash recovery also works after I changed bootloader to unlocked.
smallwei said:
Yes, fastboot flash recovery also works after I changed bootloader to unlocked.
Click to expand...
Click to collapse
I think you're correct on having hboot unlocked. I'm used to engineering hboots from the past. Where it was required to unlock before flashing recovery. With the standard hboot, I guess you need to flash the insecure boot IMG, so you write to system then install su to unlock. Glad you got it working though.
Happy flashing.
Sent from my iPhone 6 using Tapatalk
The other way that I have success by using temp root Towelroot. After rooted I use scooty menthod to lock/unlock bootloader without htcdev. From ADB with code from Scooty I can get unlock bootloader. From this step I can flash TWRP and SuperSU. Zip
Okay guys i think i really ****ed up this time...
A few weeks ago I got so excited about the release of lollipop I installed a port the first day it was available... It went well and I got everything working on first try even battery was good on this one...
Now to the problem: I wanted to update today by installing cm12 on my HTC (international), after downloading it I went full chuck Norris and made a full while without making a Nandroid backup... So i go to install from SD and select the cm12 zip and an error occurs: you need bootloader 3.18.00 or so...
OK I thought just install the old room that worked.. ****... I deleted it a while ago when reseting my PC and I don't know which one it was... Tried 4 different rooms now and every one tells me to update my bootloader..
Does anyone know how to update the bootloader under cm 12 and with s-on?? Tried installing a sense rom but they don't work (no WiFi, no data nothing) I think it's because of the partitions under cm11 and 12...
I searched everywhere but can't find anything that works.. Pleaaase help me
Thx
Austrian Atheist
Witch recovery version ?
You could fastboot flash a different recovery like Philz touch recovery put a backup from @Mr Hofs thread on your external sdcard and restore from it.or using a different recovery try a stock ROM
jball said:
Witch recovery version ?
Click to expand...
Click to collapse
3.16...
jball said:
You could fastboot flash a different recovery like Philz touch recovery put a backup from @Mr Hofs thread on your external sdcard and restore from it.or using a different recovery try a stock ROM
Click to expand...
Click to collapse
I tried a stock rom (Revolution) but nothing worked because the partitions were wrong (i think)...
Do you think installing a backup through Philz will work?
[Edit] can't find mentioned backup, do you have a link maybe? [Edit]
[Edit 2] Do you think one of those will work? http://forum.xda-developers.com/showthread.php?t=2701376 [Edit]
@AustrianAtheist
Your trying to use a stock recovery to flash a ROM?
Twrp is 2.8.4.0 right now,if your having partition issues than try a GPE ROM using a custom recovery
jball said:
@AustrianAtheist
Your trying to use a stock recovery to flash a ROM?
Twrp is 2.8.4.0 right now,if your having partition issues than try a GPE ROM using a custom recovery
Click to expand...
Click to collapse
no in had PhilZ installed... i think i really ****ed up..
so here's my problem:
I managed to install a newer firmware version through RUUs even tho I'm S-on, but after installing it i went to bootloader and it's still relocked (had to do it) but now, i can't unlock it anymore because it says:
c:\miniadb_m7>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830612992 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.114s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.125s
please help me... i can't install a rom without unlocking the bootloader and nothing is installed on my phone so i can't boot into anything except bootloader
AustrianAtheist said:
no in had PhilZ installed... i think i really ****ed up..
so here's my problem:
I managed to install a newer firmware version through RUUs even tho I'm S-on, but after installing it i went to bootloader and it's still relocked (had to do it) but now, i can't unlock it anymore because it says:
c:\miniadb_m7>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830612992 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.114s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.125s
please help me... i can't install a rom without unlocking the bootloader and nothing is installed on my phone so i can't boot into anything except bootloader
Click to expand...
Click to collapse
Are you using the original unlock.bin file or have you tried going through HTC website again.
I know you want it fixed ASAP but I need the information
I'm an idiot...
Des i downloaded the .bin file again but I didn't move the file to the adb directory... God... I'm so embarrassed right now
I made it through the unlock process again and installed twrp again and now that I'm on 3.18 hboot I managed to install cm12
But sadly I can't install a 4.4 sense ROM because there's no RUU for my cid (austria) so I can't update further, but at least I got cm12 running
Thx dude
:good:
AustrianAtheist said:
I'm an idiot...
Des i downloaded the .bin file again but I didn't move the file to the adb directory... God... I'm so embarrassed right now
I made it through the unlock process again and installed twrp again and now that I'm on 3.18 hboot I managed to install cm12
But sadly I can't install a 4.4 sense ROM because there's no RUU for my cid (austria) so I can't update further, but at least I got cm12 running
Thx dude
:good:
Click to expand...
Click to collapse
Well just wait till Sunshine is updated and you can S-OFF to do whatever you want. Am glad you figured it out though