Related
Hi, first of all, may thanks to jerpelea for http://forum.xda-developers.com/showthread.php?t=1126358.
I have try to upgrade my arc from 2.3.2 (unlocked bootloader) to 2.3.3 using the phone and I have brick the phone, now is with 2.3.3 running very well.
Now i'am looking for a way to root the phone, and i do not find anyware the way, but in few posts, some people talk about it, I do not know if it would be with locked bootloader.
If this question is on the forum, i don't find it.
Thanks
Flash a rooted .img if you are on unlocked device or flash a generic .181 ftf and root + OTA to get 2.3.3. Got it?
Its all in the forum under Android Dev section. Lookie lookie!
datagubben said:
or flash a generic .181 ftf and root + OTA to get 2.3.3.
Click to expand...
Click to collapse
Bad idea mate, with the unlocked bootloader
hi, but if a do a downgrade to rom 2.3.2 (rooted), and update to 2.3.3 using OTA, my phone will brick, and i will need to make a flash using the http://forum.xda-developers.com/showthread.php?t=1126358, won't i ?
Yes, so it is advisable not to try the OTA updates AT ALL!
Like datagubben said, just flash an already rooted ROM.
Cheers!
xtacy! said:
Bad idea mate, with the unlocked bootloader
Click to expand...
Click to collapse
Yes, I forgot to write: .................... if you are on bootlocked device.
My bad
Sent from my LT15i using XDA Premium App
Hi, if i relocked the bootloader again, i do an downgrade to 2.3.2, root the phone, upgrade using OTA my phone get's 2.3.3 rooted with any problem, am I right?
smokada said:
Hi, if i relocked the bootloader again, i do an downgrade to 2.3.2, root the phone, upgrade using OTA my phone get's 2.3.3 rooted with any problem, am I right?
Click to expand...
Click to collapse
Currently is not possible to re-lock your unlocked phone.
here is the quot from website:
"Please note that there is no turning back when unlocking the boot loader. You will not be able to revert the phone to a locked or original state if you unlock it. Also, if you brick the phone, it is your own responsibility."
See it more at this link:
http://unlockbootloader.sonyericsson.com/#13123381016851&if_height=1159
silverwind said:
Currently is not possible to re-lock your unlocked phone.
here is the quot from website:
"Please note that there is no turning back when unlocking the boot loader. You will not be able to revert the phone to a locked or original state if you unlock it. Also, if you brick the phone, it is your own responsibility."
See it more at this link:
http://unlockbootloader.sonyericsson.com/#13123381016851&if_height=1159
Click to expand...
Click to collapse
Incorrect.
[TUTORIAL] Re-lock bootloader: http://forum.xda-developers.com/showthread.php?t=1134335
smokada said:
If this question is on the forum, i don't find it.
Thanks
Click to expand...
Click to collapse
Then I would have a read of every section of the Arc forum.
smokada said:
Hi, first of all, may thanks to jerpelea for http://forum.xda-developers.com/showthread.php?t=1126358.
I have try to upgrade my arc from 2.3.2 (unlocked bootloader) to 2.3.3 using the phone and I have brick the phone, now is with 2.3.3 running very well.
Now i'am looking for a way to root the phone, and i do not find anyware the way, but in few posts, some people talk about it, I do not know if it would be with locked bootloader.
If this question is on the forum, i don't find it.
Thanks
Click to expand...
Click to collapse
if ur already having ur 2.3.3, just flashing recovery kernel made by either doomlord or bin4ry to have access to recovery mode, then, you can flash superuser package (aka root) to have ur fone completely rooted.
here's link of bin4ry recovery image (ps: this is just a live boot, so do exactly as what it said)
http://forum.xda-developers.com/showthread.php?p=13340438#post13340438
@smokada,
I'm not sure if an OTA update will work for you even if you relock your bootloader (after flashing 2.3.2) as the DRM files have been wiped but it's possible to update via SEUS, which would make you lose your root.
@silverwind,
You're a bit behind the times mate. We've been able to lock the bootloader for quite some time now i.e. from the end of June. You can follow that thread here.
[The DRM files which were wiped while unlocking the bootloader can't be retrieved by locking the bootloader again.]
EDIT: LOL! I didn't realise that so many people posted before me with the answer.
Hey guys, I force updated to jellybean however I kept superSU and my phone's boot loader is still unlocked is there anyway to unroot and re lock my bootloader.
Root and a unlocked bootloader should not give problems to update (did it myself)......
Does the update fail ?
MarcelHofs said:
Root and a unlocked bootloader should not give problems to update (did it myself)......
Does the update fail ?
Click to expand...
Click to collapse
Don't matter now just need to re install clockwork recovery any tutorials
AH I understood it wrong i guess.....
So you are on JB now, and you want stock recovery and lock the bootloader
1 : if you did the update to JB you should already be on stock recovery (otherwise the update would have failed)
2 : you can re-lock the bootloader with a fastboot command
3 : if you want to unroot just delete the SU app
Fastboot OEM lock
Hope this answers your questions
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
Sir,
I have rooted HTC desire 816 w..
I want to install the new update but i failed to do this.
I un-rooted the device and uninstalled su and flashed the stock recover which i took from update files but when i tried to update it starts updating then stopping and give me black screen with red signal, please help .....
Did you remember to Relock the bootloader after installation of stock recovery.img
Why I need to re-lock?
mbwambo said:
Did you remember to Relock the bootloader after installation of stock recovery.img
Click to expand...
Click to collapse
mbwambo said:
Did you remember to Relock the bootloader after installation of stock recovery.img
Click to expand...
Click to collapse
There is no need to relock the bootloader.
I used a .exe RUU to get my phone 100% stock!
If you have a locked bootloader, use the command "fastboot oem lock" via Fastboot.
If you have "stuck on sending 1/8" issues, try to use the .exe on another computer! It worked for me.
Big thanks to ckpv5 and Mr Hofs for the help !
Hi guys..
So a long time ago I rooted my phone, installed a custom recovery and a custom ROM on my HTC. But then I came back to a stock ROM, stock recovery but still rooted.
Today I had an OTA official update (security fix). I installed it, but then my phone is stuck on the HTC One logo! I don't have any backups..
I don't know if I can use ADB or everything since i don't know if I can power off.
I don't know if I'm really rooted. When I wanted to unroot the phone it didn't worked, so I desactivated supersu, and automatically set supersu to "reject requests" (to root access)
S-ON
Stock recovery
Stock rom (this one: http://www.forum-generationmobiles....lection-de-roms-officielles-en-zip-htc-one-m8 )
CID= HTC_203
Unlocked bootloader
Rooter-or not
I don't know what to do, help :'( I don't want to waste 500€...
Flash a custom recovery and flash a custom rom. Then start looking for a backup with at least a working phone. There is a dedicated firmware/backup thread in the general section. Have a read there .... it's stickied so can't mis it !
That's what I wanted to do too! Okay. But thats kinda strange, I mean I installed a stock rom with a stock recovery but I can't install OTA update
LowPoly said:
That's what I wanted to do too! Okay. But thats kinda strange, I mean I installed a stock rom with a stock recovery but I can't install OTA update
Click to expand...
Click to collapse
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
ckpv5 said:
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
Click to expand...
Click to collapse
Okay, thats good to know.
Before I do anything, can I also re-lock the bootloader and install a RUU (exe) instead ? Will it work ? I'm probably wrong, but I think it's better since its a pure stock new ROM and not a backup..
LowPoly said:
Okay, thats good to know.
Before I do anything, can I also re-lock the bootloader and install a RUU (exe) instead ? Will it work ? I'm probably wrong, but I think it's better since its a pure stock new ROM and not a backup..
Click to expand...
Click to collapse
Yeah .. you can use RUU.exe (relock bootloader because S-On and make backup of your internal storage important data as this will wipe everything)
Some prefer to use pure stock TWRP backup because of the hassle to relock and later to re-unlock as these process will wipe data. Some prefer to keep their data intact and there is no need to relock bootloader when using a backup
ckpv5 said:
[...] because of the hassle to relock and later to re-unlock
Click to expand...
Click to collapse
By the way, if I want to re-unlock my bootloader, will I have to do this method again
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
with HTCdev etc ? Or is there a "fastboot" method as fastboot oem lock ?
LowPoly said:
By the way, if I want to re-unlock my bootloader, will I have to do this method again
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
with HTCdev etc ? Or is there a "fastboot" method as fastboot oem lock ?
Click to expand...
Click to collapse
Yes ... you can use the unlock_code.bin that you already have. If that doesn't work, you need to reapply to HTCDev as there is no fastboot command to unlock bootloader unless your device is S-Off.
ckpv5 said:
Yes ... you can use the unlock_code.bin that you already have. If that doesn't work, you need to reapply to HTCDev as there is no fastboot command to unlock bootloader unless your device is S-Off.
Click to expand...
Click to collapse
Okay! Thank you very much
Hi again,
I thought of something. A long time ago, white installing an Aroma-install stock ROM (link in first post), I had this problem: http://forum.xda-developers.com/htc-one-m8/help/problem-write-internal-storage-5-0-1-t3085187 . But to solve it, I need root, and for an unknown reason I couldn't uninstall root.
So since i'm not very comfortable with english, and IN CASE i have the same problem with a RUU:
if Aroma stock rom:
-> Stock rom
-> Stock recovery
-> Rooted (i can choose if i root it or not)
-> SD card problem
-> Need root to solve (terminal emulator)
-> Solve
-> No OTA update because can't uninstall root
If RUU
-> Stock rom
-> Stock recovery
-> Not rooted
-> SD Card problem
-> Need root to solve
-> Install root and solve
-> No OTA update because can't uninstall root
What will I have to do ?
Since now your current firmware is a lollipop and you need to do another OTA, don't think that problem will happen again.
But if that still happen, you only need to reunlock the bootloader and install TWRP (the latest) and reflash SuperSU.zip then follow that instructions to correct that SD problem.
(assuming you're using RUU to get back to stock)
If you want to use a backup ... read my thread on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and all the files needed are there.
ckpv5 said:
Since now your current firmware is a lollipop and you need to do another OTA, don't think that problem will happen again.
But if that still happen, you only need to reunlock the bootloader and install TWRP (the latest) and reflash SuperSU.zip then follow that instructions to correct that SD problem.
(assuming you're using RUU to get back to stock)
If you want to use a backup ... read my thread on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and all the files needed are there.
Click to expand...
Click to collapse
Thank you very much for all your quick answers. I did the fastboot oem lock command to lock the bootloader, but it appeared it failed:
C:\Fastboot>fastboot oem lock
... INFO[PGFS] partition_update_pgfs: pg1fs_securi
ty
INFOTZ_HTC_SVC_ENC ret = 0
INFO[PGFS] partition_update_pgfs: pg2fs_sec_recovery
INFOLock successfully...
INFOdeinit_lcd
INFOmipi display off
INFOmdp_clock_off
INFOturn off fd8c2308 failed 1 times. Try again...
INFOdisable_mmss_clk done
INFOpll1_disable done
INFOTZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
INFO[CRITICAL] SPMI write command failure: cmd_id = 0, erro
r
INFO= 4
INFO[CRITICAL] SPMI write command failure: cmd_id = 0, erro
r
INFO= 4
INFO[ERR] Cannot halt SPMI arbiter!!
INFO[INFO] Rebooting device
FAILED (status read failed (Unknown error))
finished. total time: 1.190s
but the bootloader is showing "RELOCKED" anyway. So I launched the RUU, but for more than 30min it was stuck on "1/8". The program said it was supposed to take only 10min, so I unplugged the phone and powered-it off.
For now my bootloader says "RELOCKED" and OS "4.16.401.13 (4.16.401.10)".
So I don't really know on which os version I am.
What I want to do now is:
Unlock my bootloader again;
Flash a 4.16.401.10 firmware
Install latest twrp recovery
Install a backup
Is it correct, or is there another way to fix all this ?
I hope no partition is corrupted when unplugged phone while RUU still running.
OS "4.16.401.13 (4.16.401.10) means incomplete process.
You can try those steps.
ckpv5 said:
I hope no partition is corrupted when unplugged phone while RUU still running.
OS "4.16.401.13 (4.16.401.10) means incomplete process.
You can try those steps.
Click to expand...
Click to collapse
Or I still can try another ruu exe, and wait longer, like 1 hour ?
LowPoly said:
Or I still can try another ruu exe, and wait longer, like 1 hour ?
Click to expand...
Click to collapse
You can try again to run the RUU but it should not take more than 20 mins.
You need to use USB 2.0 to avoid problem and if possible to run it on Win7 pc as some reported problem on Win8 and Win10 (personally I don't have problem on any windows version but USB 2.0)
ckpv5 said:
You can try again to run the RUU but it should not take more than 20 mins.
You need to use USB 2.0 to avoid problem and if possible to run it on Win7 pc as some reported problem on Win8 and Win10 (personally I don't have problem on any windows version but USB 2.0)
Click to expand...
Click to collapse
Some people said that they solved the problem by re-running the RUU.. Btw it was stuck on "sending". Anyway I'm gonna re-run the same RUU. If it's still stuck i'm gonna try to re-run the ruu by using a usb 2.0. And if it's still stuck I'm gonna try to flash the .10 firmware, twrp etc...
I'll keep you up to date
EDIT: or maybe the RUU isn't working because fastboot oem lock said FAILED ?
LowPoly said:
Some people said that they solved the problem by re-running the RUU.. Btw it was stuck on "sending". Anyway I'm gonna re-run the same RUU. If it's still stuck i'm gonna try to re-run the ruu by using a usb 2.0. And if it's still stuck I'm gonna try to flash the .10 firmware, twrp etc...
I'll keep you up to date
EDIT: or maybe the RUU isn't working because fastboot oem lock said FAILED ?
Click to expand...
Click to collapse
No .. not that. It's the USB connection usually.
You also can try fastboot flash RUU.zip - http://forum.xda-developers.com/showthread.php?t=2735235
but you need to use htc_fastboot.exe instead of normal google fastboot.exe
You can have all the needed files RUU.zip and htc_fastboot.exe there
Okay here's what I'm gonna do.
- Trying the exe RUU on another computer (with windows 8, but there I'm sure there's no usb problem).
- If not working, trying flashing the zip RUU you gave me on this same computer
- If not working, trying again the exe RUU but waiting a longer time (~3hours, it worked for someone).
- If not working, trying flashing a new firmware, twrp, and using a backup.
If all these steps don't work I'm gonna be sure that there's no more solution and that my phone is officialy dead uhh
EDIT: I'm definitely sure that this is an USB problem. On my first computer (with windows 7), I can't read some USB keys for no reason. They're not detected.
LowPoly said:
If all these steps don't work I'm gonna be sure that there's no more solution and that my phone is officialy dead uhh
Click to expand...
Click to collapse
There are many ways to update the phone... don't give up.
Try all the steps that you mentioned. They should work. If still not working, I'll tell you the other way that I have in mind i.e. flashing firmware and ROM without a need of PC.
Okay! I finish to install all the drivers and start to try the steps. I'll keep you updated. Thank you again by the way. Right now you're my last and only hope