Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.
My main problem came with that my HBOOT version was 1.57.0000 and "S-On".
I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)
If someone please, has any fix to this problem, I would be greatly appreciated.
If there is any information you need to know please ask!
Jimmyy9 said:
Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.
My main problem came with that my HBOOT version was 1.57.0000 and "S-On".
I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)
If someone please, has any fix to this problem, I would be greatly appreciated.
If there is any information you need to know please ask!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2739126
alray said:
http://forum.xda-developers.com/showthread.php?t=2739126
Click to expand...
Click to collapse
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.
Jimmyy9 said:
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.
Click to expand...
Click to collapse
then you'll probably need to send your phone for a motherboard replacement.
alray said:
then you'll probably need to send your phone for a motherboard replacement.
Click to expand...
Click to collapse
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?
The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.
Jimmyy9 said:
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?
The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.
Click to expand...
Click to collapse
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.
alray said:
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.
Click to expand...
Click to collapse
Thank you for your swift replies.
This further question goes beyond my knowledge of android development. Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking? I can see this can be perceived as quite a bad thing to do morally, but I can see the coming quote from HTC for them to fix the motherboard as being quite high in price!
Jimmyy9 said:
Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking?
Click to expand...
Click to collapse
With S-ON and not able to boot in recovery, I don't know how.
alray said:
With S-ON and not able to boot in recovery, I don't know how.
Click to expand...
Click to collapse
Thank you very much for your replies and help
I did see in this thread http://forum.xda-developers.com/showthread.php?t=2781953 that @nkk71 was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem!
Jimmyy9 said:
Thank you very much for your replies and help
I did see in this thread http://forum.xda-developers.com/showthread.php?t=2781953 that @nkk71 was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem!
Click to expand...
Click to collapse
Hi Jimmyy9,
unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).
in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.
i've tried the same (and a lot more) a couple of days ago, but without any success
it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer
unless you can get to a custom recovery (even a rooted ROM), i honestly can't help
just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.
sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas
nkk71 said:
Hi Jimmyy9,
unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).
in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.
i've tried the same (and a lot more) a couple of days ago, but without any success
it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer
unless you can get to a custom recovery (even a rooted ROM), i honestly can't help
just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.
sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas
Click to expand...
Click to collapse
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,
Or
Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a RUU h-boot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.
Jimmyy9 said:
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,
Or
Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a hboot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.
Click to expand...
Click to collapse
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:
* a booted rooted ROM with USB debugging enabled
or
* a custom recovery
unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.
as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success
maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure
if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.
nkk71 said:
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:
* a booted rooted ROM with USB debugging enabled
or
* a custom recovery
unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.
as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success
maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure
if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.
Click to expand...
Click to collapse
I appreciate you offering your free time to help with my problem but if you think it will produce the same results as your previous tests then I wouldn't want you to waste your time. I have heard about this JTag process and it looks very convincing @ www.funphoneshop.com.
I see 2 paths.
The first would be to go with the JTag process and hope that it works (since m7 is not listed on their model list)
or
Seeing as my phone is still under HTC warranty until 2016, I could attempt to further brick the phone (hard-brick not turning on at all) and go through the repair process to get a replacement phone. If I did do this I would need to do something that gives no proof that this phone was ever rooted/unlocked.
In your knowledge would a simple flash of a ROM from another model or device corrupt hboot/bootloader?
Hello again, I've done some more research about what other users did when they had unfortunately hard-bricked their phone and I came across this thread that you had also posted in a few weeks ago (http://forum.xda-developers.com/htc-one/help/htc-one-m7-hard-brick-t2876273).
According to your post flashing this recovery will corrupt one of the main partitions and therefore make the device unable to switch on and then cause it to appear as "QUALCOMM HS6USB QDLOADER 9008".
My question is that are HTC able to see any proof of tampering once the device is in Qualcomm mode?
Jimmyy9 said:
I appreciate you offering your free time to help with my problem but if you think it will produce the same results as your previous tests then I wouldn't want you to waste your time. I have heard about this JTag process and it looks very convincing @ www.funphoneshop.com.
I see 2 paths.
The first would be to go with the JTag process and hope that it works (since m7 is not listed on their model list)
Click to expand...
Click to collapse
you should give them a call, with the proper hardware they can S-OFF your device and a lot more, so since you know what the problem is it should be easy to fix for them.
even if they only s-off the phone, that would be enough to continue the software solution (downgrade hboot and use the noBCB recovery)
Related
:crying::crying:
And the steps have ruined my phone. I can still use the phone, but I can no longer access TWRP. I can get in to the bootloader, and select "Recovery", but it just reboots the bootloader. I'm not getting anywhere trying to flash the stock boot image. I keep getting file signature errors. adb is worthless, it never has recognized any device I've every tried to use with it. ANd yes, I've tried it on multiple computer's running multiple OS's with multiple phones. I'm not a dev, so it sucks....period.
Now, again, I cannot even revert my phone back to it's factory condition. I relocked the bootloader as I was following the tutorials from MANY different high level forum posters. I cannot unlock the bootloader again which is going to make flashing TWRP again impossible. I don't know what to do. I was doing this because when that OTA update came about I had accidentally told it to install. Well, it couldn't, it would go straight to TWRP and fail immediately. But when that happened a couple of days ago my friends and colleagues have only been able to receive the last part of any SMS message I send. The first two parts disappear.
This is what I get running "fastboot getvar all"....obviously. Lol!
C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34BS901308
(bootloader) imei: 990001465704088
(bootloader) meid: 99000146570408
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.194s
Click to expand...
Click to collapse
Anyway, the devs here are the best and I know here is a way to get my phone back to proper working order again. As far as I can tell, without being able to unlock the bootloader, I'll never be able to flash another custom recovery therefore I will never be able to restore from a NANDROID.
I don't want to sound like every n00b or whatever who comes to these forums but I need some serious help. My requests for help in the forum threads have largely gone unanswered. So until someone on here has the time to help me I'm screwed. I mean damn, maybe I'll just sell the phone and get one of the 64GB models. I don't know what I'm going to do.
I need serious help until then... I've got to recovery my bootloader and must "re-unlock" my bootloader. If I could do that I'm pretty sure I could flash TWRP again and restore from one of my NANDROIDS. But until then... Well, all I can do is beg for someone who knows more than I do about this device to help me. I would be forever grateful.
Please, any advice, techniques, snippets of code, adb commands (if it will recognize my device), fastboot commands (fastboot always recognizes my device) or anything to get my phone back to normal, working order.
I mean I don't give a damn about root access, custom ROM's or Kernel's any longer. I just want my phone back that I paid so very much for and waited for weeks and possibly months on the waiting list just so I could pre-order.
If it's ruined then there's not much I can do about that. But it isn't bricked and I can still use the phone for the most part. But the bootloader is what has been destroyed basically.
Help, help, help!!!! :crying:
PAinguINx said:
:crying::crying:
And the steps have ruined my phone. I can still use the phone, but I can no longer access TWRP. I can get in to the bootloader, and select "Recovery", but it just reboots the bootloader. I'm not getting anywhere trying to flash the stock boot image. I keep getting file signature errors. adb is worthless, it never has recognized any device I've every tried to use with it. ANd yes, I've tried it on multiple computer's running multiple OS's with multiple phones. I'm not a dev, so it sucks....period.
Now, again, I cannot even revert my phone back to it's factory condition. I relocked the bootloader as I was following the tutorials from MANY different high level forum posters. I cannot unlock the bootloader again which is going to make flashing TWRP again impossible. I don't know what to do. I was doing this because when that OTA update came about I had accidentally told it to install. Well, it couldn't, it would go straight to TWRP and fail immediately. But when that happened a couple of days ago my friends and colleagues have only been able to receive the last part of any SMS message I send. The first two parts disappear.
This is what I get running "fastboot getvar all"....obviously. Lol!
Anyway, the devs here are the best and I know here is a way to get my phone back to proper working order again. As far as I can tell, without being able to unlock the bootloader, I'll never be able to flash another custom recovery therefore I will never be able to restore from a NANDROID.
I don't want to sound like every n00b or whatever who comes to these forums but I need some serious help. My requests for help in the forum threads have largely gone unanswered. So until someone on here has the time to help me I'm screwed. I mean damn, maybe I'll just sell the phone and get one of the 64GB models. I don't know what I'm going to do.
I need serious help until then... I've got to recovery my bootloader and must "re-unlock" my bootloader. If I could do that I'm pretty sure I could flash TWRP again and restore from one of my NANDROIDS. But until then... Well, all I can do is beg for someone who knows more than I do about this device to help me. I would be forever grateful.
Please, any advice, techniques, snippets of code, adb commands (if it will recognize my device), fastboot commands (fastboot always recognizes my device) or anything to get my phone back to normal, working order.
I mean I don't give a damn about root access, custom ROM's or Kernel's any longer. I just want my phone back that I paid so very much for and waited for weeks and possibly months on the waiting list just so I could pre-order.
If it's ruined then there's not much I can do about that. But it isn't bricked and I can still use the phone for the most part. But the bootloader is what has been destroyed basically.
Help, help, help!!!! :crying:
Click to expand...
Click to collapse
so basically if i understood you, you want to unlock bootloader and flash customer recovery twrp
first go to htcdev to do the unlocking of your bootloader then after that you will be able to flash twrp
adb do not run if your One is on fastboot mode
adb will recognize your device only on recovery or open rom
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
and also, after successfully doing the flashing
try to do s-off before you return to stock and update to 4.3
PAinguINx said:
:crying::crying:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
Help, help, help!!!! :crying:
Click to expand...
Click to collapse
Hey, careful there!!! You have a SPRINT variant, this forum is mostly for GSM version of the HTC One (M7_U and M7_UL). Head over to the Sprint HTC One forum, I'm sure someone will help you out.
http://forum.xda-developers.com/sprint-htc-one
nkk71 said:
Hey, careful there!!! You have a SPRINT variant, this forum is mostly for GSM version of the HTC One (M7_U and M7_UL). Head over to the Sprint HTC One forum, I'm sure someone will help you out.
http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
Uh oh, I've wandered in to strange territory here. Lol!
I'll head over to the other forums.
I have made some progress though. I've unlocked the bootloader once again. TWRP is still in tact, thus indicating the structural integrity of my partition table remains stable and consistent with what it should be after I rooted my device.
Thank you guys for responding. I still need to return to stock. My main issue is that when I send texts messages only 1/x are being received. Usually the last part of a long message will be received.
Quick question though, why are their such significant differences between the Sprint M7 and AT&T's or any other carriers?
[email protected] said:
so basically if i understood you, you want to unlock bootloader and flash customer recovery twrp
first go to htcdev to do the unlocking of your bootloader then after that you will be able to flash twrp
adb do not run if your One is on fastboot mode
adb will recognize your device only on recovery or open rom
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
and also, after successfully doing the flashing
try to do s-off before you return to stock and update to 4.3
Click to expand...
Click to collapse
So I need to S-Off before going back to stock. I'm assuming that I will be unable to do so after flashing? I tried pushing revone earlier yesterday but I had no luck. Also, why has the HTC One AIO tool from Samsoon been removed? Not only has it been removed, but I cannot find any "legit" downloads on the internet for it either...
Thanks!
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Enion said:
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Click to expand...
Click to collapse
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
kibmikey1 said:
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Enion said:
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Click to expand...
Click to collapse
Blinking is good, just hold POWER + VOLDOWN with the phone sensors under a bright light (not kidding!!), it should reboot after 30sec to 2 minute. If it doesn't reboot, let go and try again; the bright light is important!!
Once it reboots, keep holding VOLDOWN so it reboots to bootloader.
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to
flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Enion said:
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Click to expand...
Click to collapse
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
nkk71 said:
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
Click to expand...
Click to collapse
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!
Enion said:
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and s/n we don't need to see those.
can you confirm your hboot is dated before June 2013. I'll post your options after that
Hi, thanks for noticing, I removed it, please dit your post aswell
If you're talking about the date at the top of the bootloader, it says May 3
Enion said:
Hi, thanks for noticing, I removed it, please dit your post aswell
Click to expand...
Click to collapse
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
Enion said:
If you're talking about the date at the top of the bootloader, it says May 3
Click to expand...
Click to collapse
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
nkk71 said:
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
Click to expand...
Click to collapse
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Enion said:
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Click to expand...
Click to collapse
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
nkk71 said:
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
Click to expand...
Click to collapse
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
No problem mate, remember for revone to work your firmware is good ((bootloader) version-main: 1.29.161.16), but you will need a ROM based on 4.1.2 preferably (I have one - which worked for me and two others) in case you can't find one.
Also read here: http://forum.xda-developers.com/showthread.php?t=2431515
here: http://forum.xda-developers.com/showthread.php?t=2365506
and of course: http://forum.xda-developers.com/showthread.php?t=2314582
Let me know if you need any more help.
Once you are S-Off, you can easily upgrade/downgrade firmware in @vomer's guide (same as before, but down in the firmware section): http://forum.xda-developers.com/showthread.php?t=2365506
Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
Hey @Enion, you all good now?
nkk71 said:
Hey @Enion, you all good now?
Click to expand...
Click to collapse
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Enion said:
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Click to expand...
Click to collapse
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
nkk71 said:
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
Click to expand...
Click to collapse
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Enion said:
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Click to expand...
Click to collapse
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
nkk71 said:
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
Click to expand...
Click to collapse
Thank you sir!
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.708.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Oops
(bootloader) imei: nothing to see here
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-14eb688c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks for taking the time to read this, any pointers would be very much appreciated
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
kelvov said:
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
Thanks for taking the time to read this, any pointers would be very much appreciated
Click to expand...
Click to collapse
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
hp79 said:
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:...
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
Click to expand...
Click to collapse
Thanks for the info, will have to try it tomorrow after buying a cable
alray said:
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
Click to expand...
Click to collapse
Unfortunately no, I wrongly assumed a simple backup would have sufficed in the event anything went wrong. Never again. Oops, that for the heads up on that
You should be able to push ARHD 31.6 and be ok
sent from my mobile device
Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:
BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?
Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.
BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?
crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier
I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.
BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.
Fastboot, on the phone side, isn't connecting to my computer.
crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?
BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.
crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?
BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct
crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"
crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.
Hello Folks
My bootloader of my Desire 510 is unlocked and i want it back locked, but dont know how to do it
i hope someone can help me
Regards Marco
Addicted2Bass said:
Hello Folks
My bootloader of my Desire 510 is unlocked and i want it back locked, but dont know how to do it
i hope someone can help me
Regards Marco
Click to expand...
Click to collapse
Hello Marco,
Here is how to relock your bootloader:
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button until you get into the bootloader
3. Release "Down" and "Power" button
A different way to do it other than steps 1 - 3 is follow steps 6 - 8 and type in a command prompt
Code:
adb reboot bootloader
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background
5. Connect your USB cable and it will say "FASTBOOT USB"
6. Navigate to the folder you have your adb.exe, fastboot.exe stuff from Android Studio or wherever you obtained it from (Mine is in C:\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like: "HT42PXU99475 fastboot" if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Type
Code:
fastboot oem lock
in the command window
You should see something like:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 596539196 (0x1FFFFD6C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 9
(bootloader) [INFO] Reset reason in IMEM is 0x77665800
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
Your phone will automatically reboot and your bootloader will be locked
You can check by booting into the bootloader and it should say *** RELOCKED *** at the top in white letters and purple background
Thanks Dude!
Its locked indeed!!
Do i need to use this step in order to return to stock? and what are the steps to return to stock,i have stock image?
is there a certain kernal to flash along with stock image,if someone could provide steps to return to stock,id be grateful! thanks
donthateme702 said:
Do i need to use this step in order to return to stock? and what are the steps to return to stock,i have stock image?
is there a certain kernal to flash along with stock image,if someone could provide steps to return to stock,id be grateful! thanks
Click to expand...
Click to collapse
You only need to follow those steps if you plan to use the RUU from here.
If you have a stock recovery, you can use TWRP. If you have the file boot.emmc.win in the recovery folder, that is the stock kernel. Just put the stock image on your sdcard and Restore it in TWRP.
It worked... A little too well.
blaqueknight said:
You only need to follow those steps if you plan to use the RUU from "I can't post links yet, but you get the idea..."
If you have a stock recovery, you can use TWRP. If you have the file boot.emmc.win in the recovery folder, that is the stock kernel. Just put the stock image on your sdcard and Restore it in TWRP.
Click to expand...
Click to collapse
I had been bricked, or at least I'm pretty sure I was. However... Upon trying to unlock the bootloader via the WinDroid deal offered here in xda, the bootloader now won't re-unlock.
The word *RELOCKED* has been frickin' glaring at me for over 3 hours now, and I can't seem to find the answer or help anywhere. :crying:
MN-StormChaser said:
I had been bricked, or at least I'm pretty sure I was. However... Upon trying to unlock the bootloader via the WinDroid deal offered here in xda, the bootloader now won't re-unlock.
The word *RELOCKED* has been frickin' glaring at me for over 3 hours now, and I can't seem to find the answer or help anywhere. :crying:
Click to expand...
Click to collapse
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
MrMike2182 said:
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
Click to expand...
Click to collapse
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
MN-StormChaser said:
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
Click to expand...
Click to collapse
WinDroid is a great tool. The only problem with it comes when you have adb installed already and you install the drivers that come with WinDroid. They cause a conflict.
I hope the manual method of unlocking works for you. It has always worked for me, unless I made a mistake. When I correct the mistake, it goes off without a hitch.
You can find the RUU here for your respective carrier.
MN-StormChaser said:
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
Click to expand...
Click to collapse
If you need help with manually unlocking it let us know because it's really easy.
More details...
I may need some more help, pertaining the specific step-by-step stuff... Downloading the stock ... Rom/RUU?... from the HTC website. I'll be up all night trying to get this fixed, mainly due to needing my phone for my new job early this week. My end goal through all of this is to get a rom/kernel, or whatever else is needed, installed on it and either have it with write-protection removed or just completely blank so I don't have to worry about Boost hacking my phone and installing a bunch of crap and changing my screen setup. I really appreciate your help, guys. I will admit that, yes, I am slow to catch on to this stuff, but once I completely get the hang of this I want to be a big contributor to XDA and start helping others and developing/testing roms, etc.
Unlocking
MN-StormChaser said:
I may need some more help, pertaining the specific step-by-step stuff... Downloading the stock ... Rom/RUU?... from the HTC website. I'll be up all night trying to get this fixed, mainly due to needing my phone for my new job early this week. My end goal through all of this is to get a rom/kernel, or whatever else is needed, installed on it and either have it with write-protection removed or just completely blank so I don't have to worry about Boost hacking my phone and installing a bunch of crap and changing my screen setup. I really appreciate your help, guys. I will admit that, yes, I am slow to catch on to this stuff, but once I completely get the hang of this I want to be a big contributor to XDA and start helping others and developing/testing roms, etc.
Click to expand...
Click to collapse
If you go to http://www.htcdev.com/bootloader/ create an account, then they will walk you right through the method to unlock, and it is exactly the same method used to reunlock.
Hey do u know how to find which carrier the mobile is ??
Bcoz when i bought it,,the cover is of boostmobile...so is my carrier boost??
deepak oli said:
Hey do u know how to find which carrier the mobile is ??
Bcoz when i bought it,,the cover is of boostmobile...so is my carrier boost??
Click to expand...
Click to collapse
If that's what the cover says then that's what it is.. Boost Mobile. Where did you buy this phone from?
My relatives bought it from u.s!
deepak oli said:
My relatives bought it from u.s!
Click to expand...
Click to collapse
I'm pretty sure I can fix the phone now, since I finally have all the information I've needed for the last week!
Do you have a Boost Mobile over there in your Country? If not it's going to be pretty hard to use the phone since it's locked to Boost..
Hey, yooo hooo @deepak oli Answer me!!
---------- Post added at 10:09 PM ---------- Previous post was at 09:37 PM ----------
Fine don't answer me then, do it when you want to..
Ok here we go, you need to flash twrp from right here ---> twrp-2.8.7.0-a11.img This is going to be flashed after you unlock your boot loader so go use your unlock token and unlock the boot and then from a computer flash the twrp by doing fastboot flash recovery twrp-2.8.7.0-a11.img after you flash that go to the HBoot and tell it to reboot to recovery and while you're in recovery tap backup to make a backup because it needs to be done to move certain files/folders... Then go to the XDA thread and download the modded cm11 by me and follow the directions on which file to put it in and after this your phone will boot... CM11 Modded on XDA
Will this work and will i be able to use my phone again???
If yes then thhhaaaannnnkkkk uuuuuu!!!!!!
deepak oli said:
Will this work and will i be able to use my phone again???
If yes then thhhaaaannnnkkkk uuuuuu!!!!!!
Click to expand...
Click to collapse
It should have worked already if you did what I told you.
RUU for htc desire 510
MrMike2182 said:
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
Click to expand...
Click to collapse
hey can you by any chance get a RUU for me. I have been searching for days (literally).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
Thats the phone info. i NEED it because i cant use my phones mobile data
Dopekyd said:
hey can you by any chance get a RUU for me. I have been searching for days (literally).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
Thats the phone info. i NEED it because i cant use my phones mobile data
Click to expand...
Click to collapse
Is your carrier Cricket or something else?