Hi.I have two problems !!! First I have HTC one max and i have rooted the phone. but after the root the fingerprint is not working anymore. And my second problem is that when i try to install OTA (lollipop update) the phone download the software but when the phone install it at about 20% it shows error ( red exclamation mark ) and i got the update failed to install.
I have original recovery and i don't know what to do !!
Have to relock boot loader for finger print scanner to work. There's a thread in dev on how to do that. I think you have to be stock to take the ota tho, might have to do an ruu. Should just s-off if possible, install twrp and relock boot loader and get the stock Rom in dev.
Tenounce said:
Have to relock boot loader for finger print scanner to work. There's a thread in dev on how to do that. I think you have to be stock to take the ota tho, might have to do an ruu. Should just s-off if possible, install twrp and relock boot loader and get the stock Rom in dev.
Click to expand...
Click to collapse
I got stock rom with rooted and relocked bootloader
Does your boot loader show "Locked" or "relocked"?
These are the instructions flyhalf posted that I originally used back when I first got the phone and had the same problem with the fingerprint scanner
1.) Fingerprint scanner not working....
Check to make sure your bootloader says "LOCKED" not relocked
if not do this
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
adb reboot bootloader
verify you are now locked
Tenounce said:
Does your boot loader show "Locked" or "relocked"?
These are the instructions flyhalf posted that I originally used back when I first got the phone and had the same problem with the fingerprint scanner
1.) Fingerprint scanner not working....
Check to make sure your bootloader says "LOCKED" not relocked
if not do this
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
adb reboot bootloader
verify you are now locked
Click to expand...
Click to collapse
Any way of doing this through fastboot? My phone is in a boot loop and it wont boot up no matter what I do. It has RELOCKED on it with s-off but maybe unlocking it or locking it could help me finally boot it up.
I don't think it can be done in fastboot but I could be wrong. I read your op. Since you say everything seems to flash fine have you tried flashing different firmware?
Tenounce said:
Does your boot loader show "Locked" or "relocked"?
These are the instructions flyhalf posted that I originally used back when I first got the phone and had the same problem with the fingerprint scanner
1.) Fingerprint scanner not working....
Check to make sure your bootloader says "LOCKED" not relocked
if not do this
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
adb reboot bootloader
verify you are now locked
Click to expand...
Click to collapse
Will this work with S-ON ????? Because i have S-ON and it didn't work with me
kareim1 said:
Will this work with S-ON ????? Because i have S-ON and it didn't work with me
Click to expand...
Click to collapse
It should but you need to unlock again first
Tenounce said:
It should but you need to unlock again first
Click to expand...
Click to collapse
Well it didn't work.... Is there any other solution ??
Related
Just curious what exactly is going on during that 30 minutes required to unlock the bootloader on P769. What is it that has to take place within the phone/radio to allow it to be unlocked?
Also, say you wait an hour, then pass the oem-unlock command only to have the phone simply reboot, do you then have to wait an additional 30+ to even have a chance of it unlocking?
I have been able to unlock it once, but the bastard refuses to do anything but reboot when I try now. Just seeking more info as to what exactly is going on in that 30 minutes so I can make sure I am doing everything possible.
socalledsin said:
Just curious what exactly is going on during that 30 minutes required to unlock the bootloader on P769. What is it that has to take place within the phone/radio to allow it to be unlocked?
Also, say you wait an hour, then pass the oem-unlock command only to have the phone simply reboot, do you then have to wait an additional 30+ to even have a chance of it unlocking?
I have been able to unlock it once, but the bastard refuses to do anything but reboot when I try now. Just seeking more info as to what exactly is going on in that 30 minutes so I can make sure I am doing everything possible.
Click to expand...
Click to collapse
Are you talking about one device ? What did you do after you unlocked the bootloader ?
Lelus said:
Are you talking about one device ? What did you do after you unlocked the bootloader ?
Click to expand...
Click to collapse
Yeah same device. I flashed CM10 before the bugs were fixxed, then went back to V20D which appears to have relocked the bootloader.
socalledsin said:
Yeah same device. I flashed CM10 before the bugs were fixxed, then went back to V20D which appears to have relocked the bootloader.
Click to expand...
Click to collapse
Since you've unlocked it already ,you just need xloader and uboot from jb p760, use ones from this post
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
or use fastboot option 6
Lelus said:
Since you've unlocked it already ,you just need xloader and uboot from jb p760, use ones from this post
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
or use fastboot option 6
Click to expand...
Click to collapse
Awesome, I will give that a shot. Thanks a ton man.
So after doing that, I can then just push CWM and reflash CM10?
socalledsin said:
Awesome, I will give that a shot. Thanks a ton man.
So after doing that, I can then just push CWM and reflash CM10?
Click to expand...
Click to collapse
sure , you can even flash recovery x and u at the same time
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery_file of=/dev/block/mmcblk0p4
Lelus said:
sure , you can even flash recovery x and u at the same time
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery_file of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
OMG It worked! Thank you so much. I feel like such an idiot now lol. Let the flashing commence!
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
hurrrtin said:
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
Click to expand...
Click to collapse
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
PhantomApollyon said:
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
Click to expand...
Click to collapse
fastboot oem writecid xxxxxxxxx if you have issues with revone, try typing "su" before ./revone -p in shell so it runs as root (if you have root obviously)
Also omitting the "-p" switch might help.
fr4nk1yn said:
Also omitting the "-p" switch might help.
Click to expand...
Click to collapse
Even though this is marked solved in the op, im going to leave this tidbit here as it most likely would have applied here.
adb install dnashellroot.apk
[16:40] <@beaups> then
[16:40] <@beaups> adb shell
[16:40] <@beaups> am start -n c.fyf/.MainActivity
[16:41] <@beaups> wait 10 seconds, then
[16:41] <@beaups> /dev/sh
[16:41] <@beaups> let me know if $ turns into #
[16:41] <maxiixam> k
[16:42] <maxiixam> hah, helps if im not in fastboot =P
[16:43] <@beaups> indeed
[16:43] <maxiixam> don't worry this aint my first rodeo
[16:43] <@beaups> says the guy who went s-on...
[16:44] <Nick> lmfao
[16:44] <maxiixam> every dog has his day.
[16:44] <maxiixam> also next, we got #
[16:45] <@beaups> cool
[16:45] <@beaups> echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
[16:45] <@beaups> ^copy/paste that
[16:45] <@beaups> do NOT screw it up
[16:45] <maxiixam> done
[16:46] <@beaups> ok
[16:46] <@beaups> exit
[16:46] <@beaups> exit
[16:46] <@beaups> adb reboot bootloader
[16:46] <@beaups> fastboot getvar cid
[16:46] == Bowsakirby [[email protected]/web/freenode/ip.69.92.52.209] has quit [Ping timeout: 250 seconds]
[16:46] <maxiixam> all 2222222's just procede to htcdev?
[16:47] <@beaups> yep
[16:47] <@beaups> then use facepalm for s-off
Run this from an elevated cmd prompt where you have un zipped moonshine.
*I am not responsible for what may happen to your phone*
rumrunner s-off is now available for select htc one's, including those that have been previously unexploitable.
brought to you by beaups and fuses
www.rumrunner.us
note:
you MUST be htc dev unlocked or rooted
you MUST have working drivers (windows)
you MUST meet all of the prerequisites
support is available at #rumrunners on freenode and andirc
do NOT clutter support channels with unsupported configurations
updated version for 2.24.401.8 posted. If you are on this firmware and have been having issues, please remove ALL old versions and download again from rumrunner.us. Sorry for the issues.
Rumrunner custom hboot. Enjoy.
No portion of it may be redistributed, repacked, rehosted, or oneclicked!
S-OFF device is required!!
Features:
Full set of fastboot flash commands
Full set of fastboot erase commands
Full set of fastboot oem commands (eng-hboot command set)
Removes red banner
Removes tampered text
Download here
How to flash:
1) Put your phone in fastboot mode
2) Type the following commands into terminal
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rumrunner_2.24_401.8_hboot.zip
fastboot reboot-bootloader
If you like our work, please donate at rumrunner.us
thread opened.
Just sent a request for Sprint support
Hmmm, so I carefully ensured that I met the requirements and had the right package for my model 224113, I restored a stock TMO twrp backup, and ran rumrunner.
All seemed well until suddenly I encountered the following error during test 3
FATAL: **** IT
Now it's been printing periods in the cmd window for about 15 minutes.
The device is in bootloader.
What is safe for me to do?
S-OFFed yesterday. Thank you for this!
S-OFFed successfully, thank you very much
any way to remove "tampered" flag?
Will you be releasing Custom Hboot for different variants?
zorbakun said:
Will you be releasing Custom Hboot for different variants?
Click to expand...
Click to collapse
+1..
Will this support Hboot 1.55?
I'm unfortunately stuck on that HBoot...
hypocritelecteur said:
Hmmm, so I carefully ensured that I met the requirements and had the right package for my model 224113, I restored a stock TMO twrp backup, and ran rumrunner.
All seemed well until suddenly I encountered the following error during test 3
FATAL: **** IT
Now it's been printing periods in the cmd window for about 15 minutes.
The device is in bootloader.
What is safe for me to do?
Click to expand...
Click to collapse
Disable antivirus/firewall/Windows Defender etc etc. Retry.
Tabtoub said:
S-OFFed successfully, thank you very much
any way to remove "tampered" flag?
Click to expand...
Click to collapse
You can use revone to remote TAMPERED : http://forum.xda-developers.com/showthread.php?t=2314582
You should do BOLD steps:
Instructions
Use any operating system you like, you only need adb.
1. Download revone and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and: => command : adb shell
* cd /data/local/tmp
* chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Click to expand...
Click to collapse
Does it works on Viper 2.7.0 sense based Custom ROM with build 2.24.401.1? Becase I lost my nandroid backup for last OTA 4.2.2 update
My HTC One Is International version
Asia WWE Version
Unlocked via HTCDev.com
Sent from my HTC One using xda premium
@acank46.mh I S-OFF'd with ViperOne 2.6.0, so 2.7.0 should be fine.
---------- Post added at 12:33 PM ---------- Previous post was at 12:33 PM ----------
@balla786 It will work on 1.55.
acank46.mh said:
Does it works on Viper 2.7.0 sense based Custom ROM with build 2.24.401.1? Becase I lost my nandroid backup for last OTA 4.2.2 update
My HTC One Is International version
Asia WWE Version
Unlocked via HTCDev.com
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thank's Sir
Sent from my HTC One using xda premium
To remove 'Tampered' banner after S-OFF'ing, put this is in terminal emulator
Code:
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
Just copy and paste it into terminal to ensure no errors
Credits @scotty1223
Maybe @beaups can put this in the OP to prevent repeat questions?
Got S-Off this AM. Good start to a Monday! Thank you!
Sent from my HTC One using Tapatalk
Got my HTC one s-offed last friday. I was tring to make it work on windows 8.1 but it was impossible to get the fastboot drivers to work. finaly I tried on a different computer with windows 8 and all worked perfectly.
thank you for the hard work.
polys_a said:
Got my HTC one s-offed last friday. I was tring to make it work on windows 8.1 but it was impossible to get the fastboot drivers to work. finaly I tried on a different computer with windows 8 and all worked perfectly.
thank you for the hard work.
Click to expand...
Click to collapse
Ah, so it doesn't work on windows 8.1. Thanks for the tip, I've been trying for two days on 8.1 with no luck so I will try on Windows 8. Thanks.:good:
My DNA was previously S-off and unlocked before the latest kitkat OTA, when the new OTA came out I fastboot flashed the latest HBOOT and Radio before I started using a custom sense 6 rom. It seems that with the HBOOT update, my bootloader became locked and the tempered sign is gone as well, I tried using firewater, but since my phone is S-Off the application just say there's not anything it can do and closes. What can I do to unlock my bootloader? Or do I have to return everything to S-On and run firewater?
Just downgrade the hboot and install again 3.06.605.4 and later unlock your bootloader and keep it s-off!! and later if you want update again to kitkat but use the first ota zip and second one too!!
I would flash the 3.06 hboot first before this, but it probably won't make a difference.
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
Click to expand...
Click to collapse
quoted from this thread http://forum.xda-developers.com/showthread.php?p=47769994
Change CID, htcdev -> unlock
Sent from my Nexus 5 using XDA Free mobile app
.torrented said:
I would flash the 3.06 hboot first before this, but it probably won't make a difference.
quoted from this thread http://forum.xda-developers.com/showthread.php?p=47769994
Click to expand...
Click to collapse
worked perfectly!! Thanks so much
hi all
i restore my htc one max (international) & returned the original recovery but how i can remove the warning?
Please help!!!
bumet3eb said:
hi all
i restore my htc one max (international) & returned the original recovery but how i can remove the warning?
Please help!!!
Click to expand...
Click to collapse
I believe you need to be S-OFF then go here: http://forum.xda-developers.com/showthread.php?t=2540004
JBS976 said:
I believe you need to be S-OFF then go here: http://forum.xda-developers.com/showthread.php?t=2540004
Click to expand...
Click to collapse
Please Advice
bumet3eb said:
hi all
i restore my htc one max (international) & returned the original recovery but how i can remove the warning?
Please help!!!
Click to expand...
Click to collapse
you need soff. use firewater.. this will remove the tampered banner.
then you can unlock and lock(not relock) using scotty123's method.
all info is on this site, already been talked about.
scotty123's method:
soff and at least an unsecured kernel are needed
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked