Related
I'd like to update my RAZR i to JB by flashing one of the "Homemade Fastboots", but I can't get the unlock status of this device and so I am a bit afraid the flash process might fail halfway in and the device becoming unusable. I have never played around with things like unlocking or rooting before.
The command found on page 9 of "Unlock the Bootloader on Your RAZR i" is not recognized (see below). The adt-bundle I used was just downloaded today.
C:\RAZR\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot oem getvar all
...
(bootloader) unrecognized oem command
(bootloader) List of oem commands:
(bootloader) system
(bootloader) showtext
(bootloader) partitions
(bootloader) partition
(bootloader) md5
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) blank
(bootloader) build-signature
(bootloader) help
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) pull
(bootloader) push
(bootloader) dump
(bootloader) bosconsole
(bootloader) prod_fuse
(bootloader) nvm
(bootloader) config
(bootloader) dnx_timeout
(bootloader) proxy
FAILED (remote failure)
finished. total time: 0.240s
Btw, I did get an unlock key through the Motorola website, but the unlock command also doesn't work.
C:\RAZR\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot oem unlock ............
...
(bootloader) Not supported on engineer phone!
FAILED (remote failure)
finished. total time: 0.186s
Does anyone know if the Homemade Fastboots can be loaded on this RAZR i without "bricking" it?
Ok, if unsure about flashing the homemade fastboots, is there any other reasonably safe way to flash a regular JB firmware on this RAZR i that currently has obviously a non-standard firmware?
I am somewhat worried to get another "not supported on this phone" or other error message in the middle of the process of loading another firmware, when I've already gotten beyond the point of no return, and then being stuck with a non-working phone.
Iridium8 said:
(bootloader) Not supported on engineer phone!
Click to expand...
Click to collapse
This mean that your phone is a prototype for test purposes, not a retail phone. (Hope you didn't pay for it...)
A have one of this too. Have you manage to update your phone?
Thanks a lot!
evilinheaven said:
This mean that your phone is a prototype for test purposes, not a retail phone. (Hope you didn't pay for it...)
A have one of this too. Have you manage to update your phone?
Thanks a lot!
Click to expand...
Click to collapse
Hi,
Sorry for the late reply, I didn't check back here recently.
Apparently mine is some kind of retail phone, but with a specially built software version. Since I wanted this phone so badly (and I still believe this it the one phone on the market that suits me best), but I didn't have a chance to go to Europe at the time, I bought this from a store in China that had imported it to there. However, to be able to sell this phone in China they are putting these "specially made" software versions with added Chinese UI language on the phone. Since I couldn't get any useful advise in this forum I later contacted those who sold me this phone and they told me I should be able to put any official 4.0.4 version on it (which would then be upgradable OTA), but also warned me that I could then end up with a sim-locked/net-locked RAZR i. So I didn't pursue this any further. I might try it once I've got my next smartphone, but at the moment I am still very happy with my RAZR i.
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)
Q&A for |TOOL| HTC One Toolkit [M7] • v3.2.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for |TOOL| HTC One Toolkit [M7] • v3.2.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
McCovican said:
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
Click to expand...
Click to collapse
Were both files (firewater and temproot) in the same adb/fastboot folder?
4304
majmoz said:
Were both files (firewater and temproot) in the same adb/fastboot folder?
Click to expand...
Click to collapse
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need S-OFF to root. You just need a unlocked bootloader, custom recovery and SuperSU. Here are the instructions.
Also, I would use the raw adb and fastboot commands without the toolkit. I would recommend the Minimal ADB & Fastboot Tool. Most Dev's and OPs will give the commands for how to do certain things so you could just copy and paste. It also gives you more control on what is happening to your phone.
McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need s-off to root the phone. But with s-on you will be limited to flashing Roms, Recovery and Kernels. Firmware updates are possible but must be Signed firmware and can only be flashed with a 're-locked bootloader.
Just flash TWRP Recovery 2.6.3.3 boot to TWRP then reboot system from TWRP. You will be prompted to root the device Select yes. You may need to update binaries but that's it your done.
Better still just flash a prerooted Rom with TWRP. :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Bricked phone using tool
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(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.041s
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
???????????? fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
redlupine said:
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(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.041s
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
????????????fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
Click to expand...
Click to collapse
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu. http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu.
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
redlupine said:
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
Click to expand...
Click to collapse
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
I would however like to bring this to the attention of @nkk71 let's wait to see what he has to say on this subject
I've never seen a getvar so messed up so let's hope nkk71 has some idea :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
Click to expand...
Click to collapse
You are right, I'm posting this to the bricked help phone thread:
[Unbrick Service] Bricked Phone? Need Help? Look Here.
Lollipop
Hey,
I have a UK M7 (locked to H3G if that matters) currently running Android Revolution w/ Sense (rooted).
I have set my CID to 11111111 , I have S-OFF, HBOOT-1.56.0000 and I am looking load the OTA for the Google Play Edition (Lollipop 5.0.1) on to it using your tool. And then I will re-root.
Really I just wondered if anyone thinks that this is a bad idea for any reason.
htc one stock
I lost my stock back-up for warranty CID- VZW__001
OS- 1.10.605.10
I d like to return to full s-on stock for warranty make a new back-up
Then use tool kit to return to s-Off TWRP CAN you please help
help..
hello there OP , thankyou for the time you have put into this tool, im a noob with smartphones, and once tried 'windroid' one-click/aio type device from xda forums, it ended up with me unlocking the token thingy, but then it would not go frther, it actually put a cross X over the pic of a HDD or looked it, i quickly hit power off/one and it booted automatically into a factory install/reset kind of environment.. since then ive been to scared to even try rooting again... but your kit and hansoon one seem O.K , but my problem is, how do i find what version exactly of phone that i have, the thing lookes like the htc one x, i recall updating the rom couple of times now, so it is on kernel v3.* , but again, i need to somehow find this info and then try again using a app that actually works..i getting good reviews on your thread so i guess im hoping for some magic here, i know the questions ive asked are very nooby, but trust me i thought i had killed it, i remember unlocking the token id, i recall pasting this in and then it showed up as unlocked.. i have kept my .bin file handy if ever i re-needed it.. so i guess that part is done.. i would LOVE to run something wich doesnt kill the battery, as im experincing now is 1day lasting full charged..without many apps :S
i am sorry for the length of this question, its just i had a bad experience once, dont want that again.. but im hanging to try again... feel free to respond, or not respond, i know what im askingshould be here somewhere, although the model, if it is a one or one-x i guess is the only thing i am curious of..is how would i know because a couple of models looked very similar.. i THINK im running android 4.2.2 ,kernel 3.* , i beleive there is a couple.
i know there is a new exploit out for v3 kernel. would this not help make the tool 1000% proof.?? one wich i was told is now being used for android v5 wich apprently roots every device upto v5, so thats all v3/4 and 5 in one exploit...i have 'heard' that xda do have it and are using it for newer phones.. but what an oppurtunity,if this was added into your tool,it would be 100% proof on everything android.. just a thought but, you seem like a happpy go lucky cool op, so im just saying, if i was working on a tool, id work alot more on exploitation of the device/making sure there is no residual pains, and simply adding ballon like tips around the app kinda cool touch... i like your tools look, and i wish to use it.. but i dont want to endup being locked in phone..
i have htc one x , 32g, i believe :S it LOOKS exact same as the htc one-x,it was given to me as a one-x (sold to me),and at that stage,it was on ebay prettymuch on par with the other htc one-x,so it would be one-x im about 99% sure, i just now wonder about the updates i allowed the phone to perform,wich then changed android version/kernel.
I dont know if you have the answer i need, or answers if you wish to answer the entire post,because your going to get it,and really its you i want to ask anyhow, so its fine if it stays private, although since it is noobish, i guess you could go either way... i do raise some issues for some people to scared to get 'bricked' .. my phone uses vodaphones manager,wich i have uninstalled everytime it installs,now it has embedded itself though,and it only deletes down to un updated vodafone manager, i deleted every other voda app on there... so its basiocaallly a question of, do i go ahead with this version, or do i wait for something thats 100%.. im sure alot of people are like me, alittle hesitant to root..or had bad experiences.. ive rooted my samsung duo young fine, but the htc, well.. its got me sofar..i see all the one touch tools,i grabbed them, but wich one will actually work right.. remembeing i have used one wich was labelled windroid from xda ,it only made me paranoid as hell to use a working one, and then, i also think of exploitation, and i seriously wonder if your app can rooot an updated one-x on 4.2.2,and it does not go higher, it seems like two updates to get to this version,no updates now for about 6-12months,so i am looking here at a handful of exploits wich DO work and will root, ie; futex ; or asking you, if you think that would make your app even nicer,and erhaps a cleaner root process is achieved with something new, i know the one mentioned in UG came to xda,so,why is there no updated packs :?
i would hope that things got updated,maybe just me,but if theyre updating theyre firmware, then surely you must update your end to handle this... so is MY phone going to be o.k with this app, or do i wait and hope there is a newer expoloitation achieved ?
its a long post,, but i hope im getting through to some dev, theres alot to be done with these packs,specially with things like google play pad coming out, id like to buy one of those,but again,how do i trust apps wich have not been updated in ages...yet my phone has updated.. it just blurs the mind as to how you would get around kernel patches..i know android has many exploits,but not clean ones like the current one in use.. i will look in on this thread and hopefully someone will explain to me how to get the exact phone info, and alittle more info on how things getting rooted, ie; exploitation , and kernel images/links to GOOD working kernels already tested.. noobs like me dont want to test 5 types, we want one GOOD one
im sorry to write alot,but this is good topic ive been walking around for to long. i even have a spare iphone sitting here just for when i root the one-xx.i am confdent that if anyone will help me on this,its going to be xda forums, simple as that... i dont even bother reading many other blogs nomore,everything android is here..its a great little place,and i love it sofar.. exploring the roms,reading,wanting :[.. i will await some feedback. again, apologies for long post,but i trying to be thorough as i can on each issue. cheers.
dru
---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------
apologies for the long post... ofc i dont expect it to go public BUT it does raise some issues..i dont see all of xda forum yet, but every search sofar has yielded results..only areas i find lacking is the rooting devices actually explaining wich root method is being used, its not a necessity,but some root methods leave memory leaks/other bugs wich can be phone specific, ome wich dont do anything atall because they bypass aprotections properly.
IF there is a thread on exploiting, i will join there..someone has to be sharing the exploits,and so they should, but alittle more info could be given to public,i guess not all people care,they just want one-click, well, i care about what i stick in my phone, so flashing a custom rom, kernel to me is a big deal i expect done right once..
i look forward to some feedback on my htc issues.
Sense Rom for S-off?
Do I have to install a sense-based rom before i go on s-off with Firewater?
Greez philipp
s-off htc one x
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Griffmiester said:
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Click to expand...
Click to collapse
You are not at the right place, this is the HTC One forum (M7) not the One X (Endeavor or Evita)
If you have an Endeavor One X (Tegra 3 cpu variant) , S-OFF is not possible
If you have an Evita One X (XL) (Qualcom cpu variant), head to this forum: http://forum.xda-developers.com/one-x-att
will i be able to use the toolkit with this phone...
Click to expand...
Click to collapse
No this is not for the One X, anyway better to learn how to use ADB and Fastboot .
Do this toolkit work with last android update?
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
LucaBalzano said:
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
Click to expand...
Click to collapse
Then I would suggest spend a few days to learn. Even if it does work and something goes wrong you won't know how to fix it. Do the proper research and learn to do things the right way instead of using a tool kit.
HTC ONE X+
***LOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
HBOOT
SERIAL: FA2ASW105934
CANNOT GET OUT OF HBOOT SCREEN OR UE ADB FASTBOOT
So when i entered the fastboot getvar all command in adb
Heres what i got
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-sizeKB: 100000
(bootloader) partition-typeKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0xaXXXXXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.180s
Im wondering if the unlock code can be used to unlock it or its just the binary data on true or false.
@sd_shadow Your thoughts on this?
This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi
Ugh wish i had another kindle fire
sd_shadow said:
This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi
Click to expand...
Click to collapse
Apparently I just tried this with the one Getvar gave me it didnt work. gave me an unlock code error
I bought this fire for my son. The hdx unlock worked until 3.2.4 firmware and is based on a bug on image verification. Probably we can't unlock any more the bootloader..both on newer HDx and on this cheap fire.
@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?
rjmxtech said:
@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?
Click to expand...
Click to collapse
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...
ldeveraux said:
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...
Click to expand...
Click to collapse
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.
rjmxtech said:
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.
Click to expand...
Click to collapse
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens
ldeveraux said:
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens
Click to expand...
Click to collapse
That one I posted in the wrong place I changed to "nvm" when I realized I posted in the wrong place but I get what you're saying.
well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.
jwalb89 said:
well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.
Click to expand...
Click to collapse
What are the symptoms of your brick? Can you get to fastboot?
Drax TD said:
What are the symptoms of your brick? Can you get to fastboot?
Click to expand...
Click to collapse
I do have access to fastboot, but not to recovery as stated so no adb commands for me... on normal boot it goes to the cm12 boot logo, and continues attempting to boot.
Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk
Franzferdinan51 said:
Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk
sd_shadow said:
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk
Franzferdinan51 said:
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Ahh well good luck can't wait too see what you come up with would love to have a real recovery instead of flash fire
Sent from my KFFOWI using Tapatalk
jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Any luck getting a update.zip that can restore stock using fastboot?
Thanks
I know I have another post like this up but I don't know how to delete the other one, sorry!
I don't know what I'm doing or how I bricked it. I keep trying to flash different things but always give errors. I don't think there's an OS on it anymore. I don't know if I'm making it better or worst, all the tutorials and solutions I've found online always seem to complicated or I do it and nothing happens. Please if you could help give detailed explanations on how to fix it
I'm missing gpt.bin I think? But I don't know how to get it
Lots of these errors:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
variant: owens XT1776
Boost Mobile
PLEASE ITS ONLY BEEN A DAY AND I'M LOSING MY MIND WITHOUT MY PHONE.... HELP ME