I have found that revone s-off originally for the HTC One/Droid DNA works on the One S. You MUST be rooted for this to work. Super CID is NOT required. I do NOT take any credit for this, I just want to bring it to your atention. All the credit goes to @ieftm who made this tool.
HTC One revone s-off link: http://forum.xda-developers.com/showthread.php?t=2314582
HTC Droid DNA revone s-off link: http://forum.xda-developers.com/showthread.php?t=2314706
NOTE
Please do not ask me if this works on any other firmware other than 3.16.401.8/9. Unfortunately I cannot tell you or test it with your firmware. Please try it at least and if it WORKED, comment below and I will add it to the list below.
CONFIRMED working on:
3.16.401.8/9 WWE
If you are not rooted or on stock rom you can root by downloading Kingo Android Root from here. You need a Windows PC or a Mac/Linux running Wine Windows Program Loader
Instructions
1. Download revone here.
2. Connect your phone with USB Debugging On and open a Command/Terminal window.
3. cd to the folder containing revone.
4. Type in the following:
Code:
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 755 revone
5. Prepare your phone by typing:
Code:
./revone -P
6. If you get a message saying "success" then proceed to step 7.
**If your phone reboots then wait 2 minutes and try again from step 3.
**If you are told to reboot then do so and try again from step 3.
**If you get an error and your phone does not reboot or if you are not told to reboot then you can try step 7 but not guaranteed to work.
7. To s-off using revone type in:
Code:
./revone -s 0 -u
8. If it reported success type in:
Code:
exit
adb reboot bootloader
9. You should now see s-off. If not try again.
10. Here are some OPTIONAL commands:
Code:
./revone -u (Unlocks the bootloader)
./revone -l (Locks the bootloader with locked message)(Important for warranty reasons)
./revone -r (Relocks the bootloader with relocked message)
./revone -t (Removes the tampered message)
Please hit the thanks button here and here if this helped.
Good to have a another option
Sent from my One S using Tapatalk
at least now we can unlock bootloader without htcdev or losing data, i've tested all of the commands myself and can confirm they all work
Does this work with 3.16.401.9?
it should, i tried it with 3.16.401.8 and please tell me if it does work
is superCID required for this?
dd98 said:
at least now we can unlock bootloader without htcdev or losing data, i've tested all of the commands myself and can confirm they all work
Click to expand...
Click to collapse
I may have missed something out but, how can you be root (to use revone s-off) without htcdev?
@twist3d0n3 its not
@Bricolo_fr i added program called kingo android root which supports the htc one s and doesnt require a bootloader unlock
i get 'unable to open revone: permission denied' when doing the chmod 755 revone command... what do?
after adb shell type su and try again
aye that gets past it, thanks.
when i run ./revone -P it says failed (code 1).
i carried on based on what the OP says, says successful but still won't s-off on reboot. tried 4 times now and still the same
twist3d0n3 said:
i get 'unable to open revone: permission denied' when doing the chmod 755 revone command... what do?
Click to expand...
Click to collapse
I assume you're doing it straight from the phone, so try the "su" command before you start all the other commands (which is done by simply typing in "su".)
I have aquestion of my own also... On the "./revone -P" command, I get a "revone failed (error code = 1)". What do I do about this? I'm trying to do it straight from the terminal emulator by he way.
Speeder975 said:
I assume you're doing it straight from the phone, so try the "su" command before you start all the other commands (which is done by simply typing in "su".)
I have aquestion of my own also... On the "./revone -P" command, I get a "revone failed (error code = 1)". What do I do about this? I'm trying to do it straight from the terminal emulator by he way.
Click to expand...
Click to collapse
You haven't read too much from those links in OP aren't you? If you have done that, you've noticed that the same error was discussed there as well. Shortly, you are either on the wrong ROM to try revone or you should reboot till it works. If after rebooting several times you got the same error, then you might need to flash first a ROM as close to stock as possible... Viper could be an option but I'm not sure cause I didn't try
Sent from nowhere over the air...
Rapier said:
You haven't read too much from those links in OP aren't you? If you have done that, you've noticed that the same error was discussed there as well. Shortly, you are either on the wrong ROM to try revone or you should reboot till it works. If after rebooting several times you got the same error, then you might need to flash first a ROM as close to stock as possible... Viper could be an option but I'm not sure cause I didn't try
Sent from nowhere over the air...
Click to expand...
Click to collapse
I DID read those links. Tried about 4 different ROMS, two of which were Sense-based. Oddly enough, Viper is a ROM I haven't tried yet... I'll do that
Speeder975 said:
I DID read those links. Tried about 4 different ROMS, two of which were Sense-based. Oddly enough, Viper is a ROM I haven't tried yet... I'll do that
Click to expand...
Click to collapse
OK, sorry I presumed wrongly...try Viper also. I remember in the first days of the S-Off "thing",, it was one of the ROMs of choice for starting this. I was never trying S-Off since I don't needed but I've read alot about it and the ways of achieving it.
This looks like the perfect solution to get S-OFF without losing all my data. But I can't even get root with Kingo. It tells me "Root Failed! The current status of your device is S-ON, please go to "Tools"=>"HTC UnlockBootloader" to unlock it to S-OFF and try again." I know this is the wrong thread for Kingo questions, but maybe someone on his way to S-OFF has solved the problem? Btw: Where is this "Tools" menu?
I'm stuck in an endless loop here
tried this a few times on my stock (rooted) backup and still no go... says failed at both bits that start ./revone
FraBle said:
Does this work with 3.16.401.9?
Click to expand...
Click to collapse
Read OP
hi i got this message after step 5
Gaining root access (thanks to Dan's motochopper)...Segmentation fault
139|[email protected]:/data/local/tmp $
whats the problem.
Related
I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0
Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...
chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all
When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".
I do not see # sign when i type adb shell..
Means I have to root again ?
What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S
Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.
Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.
Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?
It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?
Originally posted in here
Click to expand...
Click to collapse
Okay, I tried the taco root exploit as suggested here.
Since I'm new to Android, the process was a little vague for me. Finally managed to get it done properly after reading through I really don't know how many pages here on this forum and google searches. Didn't wanna risk a brick, lol.
I've just written down the step by step procedure if someone like me needs the help.
1st off, my device is a Sensation running 2.3.4 OTA stock, unrooted/ untouched and Revolutionary fails to S-off this phone.
Edit: Just got a brand new Sensation Xe where I faced the same problem, no OTA etc (I unpacked the phone), but Revolutionary S-OFFstill fails. Tried the same methode below and it is S-OFF now. Screenshot of the new phone below:
DISCLAIMER
Using the following method might void your warranty.
I am not responsible if following this method results in bricking your phone.
Whatever you do is at your own risk
You'll need the tacoroot.bin file (I got mine from the htcsupertool v3 zip)
ADB set up.
HTC drivers. I used the HTC v 3.0.0.007 drivers.
Copy/move the tacoroot.bin file to a folder and open a command window from there or move it to the Android SDK/ tools folder (my set up) and navigate there from a command window depending on how you have ADB setup.
Run the following adb commands.
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –-undo
Done. Go ahead with custom recovery etc. I did not install any custom recovery with Revolutionary as I didn't want to risk anything. Someone better equipped folks might be able to say if that would disrupt the whole process.
I've installed ARHD 6.5.1 XE on this Sensation now, no issues. It's a friend's phone, my own XE is running the same without all this drama )
Note: Shamelessly copied bits and parts from all over the forum and the net. Thanks to everyone here and no offense if something has been taken from someone without acknowledgement.
Warnings and Disclaimers
TacoRoot may void your warranty. This is not an s-off/unlock, but a temporary root method – and an unstable one at that (note, however, that it’s technically a “quasi-perm” root in that your phone will stay rooted after you pull the battery). Your phone will be unstable until the undo parameter is used, and may not fully boot. ADB, however, will come up as root.
If your phone breaks as a result of this exploit, neither Android Police nor Justin Case can be held liable.
Edit: I corrected the command line to undo tacoroot, thanks to mathrania's post below.
Thanks for the guide... just a comment:
Instead of : adb shell /data/local/tacoroot.bin –undo
it should be: adb shell /data/local/tacoroot.bin ––undo
I just died trying the first command
thanks..
now i see.. it must be double dash..
i didnt know that. i will try to root again..
can i install clockwork after s-off?
will this work for hboot 1.27 S-on?
bestmodel03 said:
will this work for hboot 1.27 S-on?
Click to expand...
Click to collapse
No cus u cant run revolution on 1.27
1st off, my device is a Sensation running 2.3.4 OTA stock
Click to expand...
Click to collapse
fuel3100 said:
now i see.. it must be double dash..
i didnt know that. i will try to root again..
can i install clockwork after s-off?
Click to expand...
Click to collapse
Sure, you can. I'm using 4EXT Touch Recovery though.
Brilliant Baba! kewl method... Salute Forever_n00b
ty so much....
was suffering A LOT!!!!
Awesome
Works perfectly for HTC SEnsation XE with Hboot1.18...
Thanks mate... Tacoroot ROCKZ...!!
Installing ROM now..
Success
Successfully S-Off using Tacoroot on my Sensation HBoot 1.18.0000
Thank you very much Forevernoob!
Phollux said:
Successfully S-Off using Tacoroot on my Sensation HBoot 1.18.0000
Thank you very much Forevernoob!
Click to expand...
Click to collapse
Same for me, worked great.
after adb shell /data/local/tacoroot.bin --root command, my phone now boot loop on bootanimation i don't know what should i do...
echbel said:
after adb shell /data/local/tacoroot.bin --root command, my phone now boot loop on bootanimation i don't know what should i do...
Click to expand...
Click to collapse
Mee too, how is it going?
drcrazy91 said:
Mee too, how is it going?
Click to expand...
Click to collapse
while on boot loop, i've connected phone to pc and started revolutionary tool, it completed the command succesfully
echbel said:
while on boot loop, i've connected phone to pc and started revolutionary tool, it completed the command succesfully
Click to expand...
Click to collapse
I also ran revolutionary while on boot loop and it completed successfully. However after that im now stuck in boot loop and am unable to run the --undo command. I've tried running the --undo command while in boot loop but it dosnt seem to help.
Sometimes it will make it to the wallpaper for a few seconds then just reboot again..... Anyone know how i can fix this?
just some additional info: revolutionary definately worked. It shows S-OFF in fastboot on Hboot 1.17.1111
I dont think im not bricked but i just need some assistance getting things back on track!
jez151 said:
I also ran revolutionary while on boot loop and it completed successfully. However after that im now stuck in boot loop and am unable to run the --undo command. I've tried running the --undo command while in boot loop but it dosnt seem to help.
Sometimes it will make it to the wallpaper for a few seconds then just reboot again..... Anyone know how i can fix this?
just some additional info: revolutionary definately worked. It shows S-OFF in fastboot on Hboot 1.17.1111
I dont think im not bricked but i just need some assistance getting things back on track!
Click to expand...
Click to collapse
Let the phone reboot and in the mean time run the adb from pc and do the undo command
(you can verify the phone is connected or not using "adb devices")
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
Let the phone reboot and in the mean time run the adb from pc and do the undo command
(you can verify the phone is connected or not using "adb devices")
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Yeah I've done this now so i assume it has worked. It Unfortunately hasnt fixed the problem.
Any other ideas?
EDIT: ok i mangaed to get clockwork on the phone and I'm rocking insert coin no worries. Thanks for your reply.
hello. i have a problem here which is after i doing Juopunut Bear, i cannot boot my handphone. i already follow a instruction from a
http://forum.xda-developers.com/showthread.php?t=1614617
http://www.flow-wolf.net/2012/09/how-to-s-off-htc-sensation-xe-4g.html
http://www.youtube.com/watch?v=pCwEbh_JsI8
i already made the last step about 30 times but i still didnt get the s-off
i try to reboot phone but cannot
i also try to make a recovery but phone wont go to the recovery..
help me please... i dont know what to do... HELP..HELP..
hi i had a sensation xe which i rooted before i may not be the most experienced but will try to help until someone more experienced comes along
Firstly does your phone turn on at all?
ti0 said:
hi i had a sensation xe which i rooted before i may not be the most experienced but will try to help until someone more experienced comes along
Firstly does your phone turn on at all?
Click to expand...
Click to collapse
yes my phone is turn on but with the screen Juopunut Bear only. i cannot make a factory reset.
I believe the jupontubear screen allows adb commands connect your phone to the computer and set up adb
Then type
adb reboot bootloader if that dosnt work then try
adb reboot recovery
I'm still a noob so take my information with caution and search on google first
Did the Juipunut Bear succeed? If no, you have to try till it does. (I did for 2 whole hours just to jolt till it works)
KiD3991 said:
Did the Juipunut Bear succeed? If no, you have to try till it does. (I did for 2 whole hours just to jolt till it works)
Click to expand...
Click to collapse
yes. it failed.. look i need to try also. thanks a lot for the info. how if Juipunut Bear not succeed. what can i do.
i got this message
first message error 66732337
2nd messange is error still sober
are you got this message too.
Failed to enter recovery after s-off using Juopunutbear
KiD3991 said:
Did the Juipunut Bear succeed? If no, you have to try till it does. (I did for 2 whole hours just to jolt till it works)
Click to expand...
Click to collapse
after i succeed Juopunutbear s-off then i remove the temproot-sensation-windows and after removo it. the Juopunutbear still have. in the hard reset screen top of the screen there have a text of Juopunutbear (its is normal) and why i can't access to the recovery. just like doing nothing. just back to hard reset main screen.
hard reset = i dont know what to call but on this screen have a hboot, fastboot, recovery, factory reset, simlock and image crc.
emitech21 said:
after i succeed Juopunutbear s-off then i remove the temproot-sensation-windows and after removo it. the Juopunutbear still have. in the hard reset screen top of the screen there have a text of Juopunutbear (its is normal) and why i can't access to the recovery. just like doing nothing. just back to hard reset main screen.
hard reset = i dont know what to call but on this screen have a hboot, fastboot, recovery, factory reset, simlock and image crc.
Click to expand...
Click to collapse
flash the recovery again
the see if you have access
rzr86 said:
flash the recovery again
the see if you have access
Click to expand...
Click to collapse
i just search for the flash recovery. but i can;t find the same situation same with me. any help or suggestion can u give. any link
I've taken this straight from the JuopunutBear website:
There are three ways to recover your ROM. Try each one in until you succeed:
Open the cmd prompt that is located in your ControlBear folder where you unzipped all of the files.
Type the following cmds into the cmd prompt.
1)ControlBear -r (This is run with the phone at the JuopunutBear/Arrow screen) If this succeeds recovery is complete otherwise continue to Step 2.
2)ControlBear -f (This is run with the phone at the fastboot screen). If this succeeds you're done otherwise continue to Step 3.
3)fastboot flash boot boot_backup.img
4)fastboot flash recovery recovery_backup.img (This is done with the phone in fastboot mode) If this succeeds continue to Step 5.
5)Boot the phone to android and install busybox from the market if not already installed.
6)adb push sdcard.img /data/local/tmp/
7)adb shell
8)$ su
9)# busybox dd if=/data/local/tmp/sdcard.img of=/dev/block/mmcblk1 conv=notrunc
10)Reboot the phone.
Choccie Milk said:
I've taken this straight from the JuopunutBear website:
There are three ways to recover your ROM. Try each one in until you succeed:
Open the cmd prompt that is located in your ControlBear folder where you unzipped all of the files.
Type the following cmds into the cmd prompt.
1)ControlBear -r (This is run with the phone at the JuopunutBear/Arrow screen) If this succeeds recovery is complete otherwise continue to Step 2.
2)ControlBear -f (This is run with the phone at the fastboot screen). If this succeeds you're done otherwise continue to Step 3.
3)fastboot flash boot boot_backup.img
4)fastboot flash recovery recovery_backup.img (This is done with the phone in fastboot mode) If this succeeds continue to Step 5.
5)Boot the phone to android and install busybox from the market if not already installed.
6)adb push sdcard.img /data/local/tmp/
7)adb shell
8)$ su
9)# busybox dd if=/data/local/tmp/sdcard.img of=/dev/block/mmcblk1 conv=notrunc
10)Reboot the phone.
Click to expand...
Click to collapse
to do this. what condition of phone. in the JuopunutBear screen with an arrow or phone in the bootloader
emitech21 said:
to do this. what condition of phone. in the JuopunutBear screen with an arrow or phone in the bootloader
Click to expand...
Click to collapse
i try with the phone in JuopunutBear screen with an arrow i already try 1,2,3 but at the step 3 the respond is waiting for device. then it not change at all. what should i do actually.
emitech21 said:
to do this. what condition of phone. in the JuopunutBear screen with an arrow or phone in the bootloader
Click to expand...
Click to collapse
i already succeed the third one. but i dont understand the instruction no.5. did i need to boot phone
emitech21 said:
i already succeed the third one. but i dont understand the instruction no.5. did i need to boot phone
Click to expand...
Click to collapse
probably yes
but if you fail to finish that process
then see here to flash a recovery
http://forum.xda-developers.com/showthread.php?t=1631861
only step 2
I was following this guide, I've gotten up to part 16 but now it won't flash anything, it starts and then says that it's the wrong version. I do not have a goldcard and the phone is locked to Orange UK, but I can't find the correct RUU for this anywhere, where can I get the Orange RUU?
lost4468 said:
I was following this guide
Click to expand...
Click to collapse
What an over complicated guide to do such things :silly:.
3 sec google search: http://www.filefactory.com/file/ca318a0/n/RUU_Saga_Orange_UK_1.31.61.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_178918_signed.exe
chninkel said:
What an over complicated guide to do such things :silly:.
Click to expand...
Click to collapse
Thanks but I already tried that one and it said it was an older version. Although I found out the official 4.0 worked even though it wasn't Orange.
lost4468 said:
Thanks but I already tried that one and it said it was an older version. Although I found out the official 4.0 worked even though it wasn't Orange.
Click to expand...
Click to collapse
You have to use misc_version first if you want to flash an older version.
Edit: in other words, step 13 in that guide.
teadrinker said:
Edit: in other words, step 13 in that guide.
Click to expand...
Click to collapse
Or you can do it like that:
1. unlock bootloader
2. flash 4EXT recovery recovery.img file using fastboot
Code:
fastboot flash recovery recovery.img
3. boot to recovery using volume/power key -> the recovery has root access.
4. Go to mounts | storage and mount /system and /data partitions.
5. Push and use misc_version
Code:
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 1.27.405.6
exit
6. unmount partitions, reboot to bootloader, relock it and run orange_UK RUU.
Hey there!
I'm kinda stuck.
I've recently unlocked the bootloader with htcdev, installed TWRP recovery, and then tried to S-OFF my device with rumrunner. It said I didn't have the right ROM installed to be able to S-OFF so I decided to install another ROM.
So I decided to install this one: http://forum.xda-developers.com/showthread.php?t=2791725
(I put the .zip file on the phone, did a factory reset via TWRP, and installed it via TWRP, It said it was succesfully installed)
When I tried to reboot my phone it didn't get past the HTC logo.
I went back to TWRP and found out the /system folder was empty and OS wasn't installed for some reason.
So I tried to adb sideload another ROM, to maybe be able to install that ROM, but adb sideload won't get past the message:
Starting ADB sideload feature...
I tried to use the adb via cmd, but when I type in 'adb devices' it doesn't show up.
Sooo this is basically where I'm at atm, stuck with not being able to flash a ROM to the device, and only being able to get into TWRP because there is no OS installed.
Could it be a driver problem, and how could a be able to find my device again?
[Update 1]
While going into fastboot, and trying to 'fastboot devices' via cmd, it does work, and commands like 'fastboot reboot-bootloader' do work aswell.
Still adb doesn't work for me.
[Update 2]
I got the ADB Sideload to work, but after any ROM I install, it keeps hanging at the HTC Logo. Any thoughts on this?
[Update 3]
Ok, I've just found out that the non-HTC ROMS (like CM11, and Mokee) do work, and do boot, but the official HTC ROM, and the Insertcoin won't boot. (Get stuck @ HTC Logo). Maybe this helps to understand what the problem is?
While running the CM11 or Mokee ROM, the device doesn't get recognized by the PC so I won't be able to try to S-OFF the device using rumrunner again. I'm also not able to install .apk files so that means I have no SU acces?
[Update 4]
It seems the problem was I didn't used the boot.img from the roms, but a boot.img file that I already had inside of my fastboot folder. My mistake.
Installing the MagioROM made me use rumrunner to S-OFF and SuperCID after. I'm currently running the Official Stock 6 ROM now. Thanks for all the help!
[Credits]
Thanks DezBucks for solving the abd problem, El_Svanto for helping me out with using boot.img and Andyt95 for the rest.
---
Btw, this is my phonestatus atm:
*** TAMPERED ***
*** UNLOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.24.40e.00.26
OpenSDP-v19.2.0268.0927
OS-3.10.401.6
eMMC-boot 2014MB
Mar 7 2014,18:44:01.0
I was having the same problem in Windows 7, I managed to get it working and I have written a how to...
http://forum.xda-developers.com/htc-one-mini/help/trouble-usb-dropping-solution-t2800682
Thanks for the help!
It did work, although I tried to install a ROM, but after any ROM I install, it keeps hanging at the HTC Logo. Any thoughts on this?
Did you flash boot.img? Because you're S-on you have to.
Download Philz CWM touch recovery (this is the only recovery I've found which allows S-ON adb push/pull and mounting simultaneously
Download Magio R4
Download the adb universal drivers and install them
Go to fastboot, type
Code:
fastboot flash recovery /path/to/philz.img
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner again, it should work, if it doesn't, let me know and I'll come up with a workaround.
Ok, I've just found out that the non-HTC ROMS (like CM11, and Mokee) do work, and do boot, but the official HTC ROM, and the Insertcoin won't boot. (Get stuck @ HTC Logo). Maybe this helps to understand what the problem is?
While running the CM11 or Mokee ROM, the device doesn't get recognized by the PC so I won't be able to try to S-OFF the device using rumrunner again. I'm also not able to install .apk files so that means I have no SU acces?
[Update]
It seems the problem was I didn't used the boot.img from the roms, but a boot.img file that I already had inside of my fastboot folder. My mistake.
Installing the MagioROM made me use rumrunner to S-OFF and SuperCID after. I'm currently running the Official Stock 6 ROM now. Thanks for all the help!
Andyt95 said:
Download Philz CWM touch recovery (this is the only recovery I've found which allows S-ON adb push/pull and mounting simultaneously
Download Magio R4
Download the adb universal drivers and install them
Go to fastboot, type
Code:
fastboot flash recovery /path/to/philz.img
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner again, it should work, if it doesn't, let me know and I'll come up with a workaround.
Click to expand...
Click to collapse
Rumrunner, revone or firewater doesn't work for me. Can you help?
nicniewid said:
Rumrunner, revone or firewater doesn't work for me. Can you help?
Click to expand...
Click to collapse
Rumrunner will work once you flash a ROM with an unsecure kernel ( like the JmzStock & JmzKernel ).
htc_one_mini_m4 said:
Rumrunner will work once you flash a ROM with an unsecure kernel ( like the JmzStock & JmzKernel ).
Click to expand...
Click to collapse
i installed Jmzstock & Jmzkernel. After second reboot into bootloader i received a message:
FATAL: Download updated package at rumrunner.us
Press ENTER to exit
nicniewid said:
i installed Jmzstock & Jmzkernel. After second reboot into bootloader i received a message:
FATAL: Download updated package at rumrunner.us
Press ENTER to exit
Click to expand...
Click to collapse
Are you using the latest Rumrunner version as it says ? ( v0.5.0 is what I used in conjunction with Jmz's stock rom & unsecure kernel to S-OFF my Mini ).
htc_one_mini_m4 said:
Are you using the latest Rumrunner version as it says ? ( v0.5.0 is what I used in conjunction with Jmz's stock rom & unsecure kernel to S-OFF my Mini ).
Click to expand...
Click to collapse
Yes, i'm doing everything like you, but it doesn't work
nicniewid said:
Yes, i'm doing everything like you, but it doesn't work
Click to expand...
Click to collapse
I'm kinda out of ideas, although I'm on a rush right now, so I can't tell for sure that there's not something I can think of
If you don't find a solution until Sunday or Monday, I can help you out remotely via TeamViewer if you want