Need serious Help concerning roms - AT&T, Rogers HTC One X, Telstra One XL

Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36

What's your Cid? It should be 1111 etc.. Make sure ur super cid, then s- off.. After following those steps then try running the RUU
Sent from my Nexus 4 using XDA Premium 4 mobile app

zinter95 said:
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
Click to expand...
Click to collapse
Why did you change the CID to HTC__621? That doesn't even look like it's for our device. That's the reason the RUU is failing.
The reason cm10.2 won't boot is because you need to RUU to 3.18 with the 2.14 hboot to flash that ROM, it does state that clearly in the install instructions for that ROM.
You're gonna need to get SuperCID first, then you can get s-off, then you can RUU to 3.18, then you can flash the cm10.2 ROM.
Sent from my Evita

I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Any solutions?

Ok, but why did you change it HTC__621? I don't think that's a CID for our device, were you trying to install software or something? The only problem is that without s-off you can only manually change the CID once, and you've used that one chance up by changing it to HTC__621. As far as a solution goes I'm not sure, there are a few different methods to change your CID, I'd suggest you try them all.
Sent from my Evita

zinter95 said:
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Click to expand...
Click to collapse
SuperCID is mandatory for the s-off method. So yes, that is why you can't s-off.

i changed my cid to 11111111 now, but i still cannot change it to s-off i followed the instructions but i always failed.

You need to give more info. Where in the process did it fail?
Sent from my Evita

At the first time i failed when i type that code;
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
and when i wanted to try another time it keeps failing in the step before that one.

You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita

timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
heey, im in this step right now
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
any time i run that command it says Device offline or device not found, but i have the latest updates of htc synmanager ..
im running RageXl 1.03 ROM.
How can i solve it please?

Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita

timmaaa said:
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
Click to expand...
Click to collapse
i uninstalled htc syn manager but it still telling me device offline!!!!!!!!!!!!!!!!!

Wow, that's a lot of exclamation marks. Maybe you need to try on a different ROM. Check your drivers, check adb, make sure usb debugging is enabled. It's almost impossible for me to diagnose what's going on without being there, you need to troubleshoot it.
Sent from my Evita

timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
Heey,
I installed an aosp rom, and everything was going alrgiht until the last step , the last command;
C:\Android>adb shell su -c "/data/local/tmp/soffbin3.zip"
/data/local/tmp/soffbin3.zip[2]: ┴¹Í♣î¶: not found
/data/local/tmp/soffbin3.zip[4]: syntax error: '³' unexpected
/data/local/tmp/soffbin3.zip[2]: ©╚ÇÎ⌂idþº╬R░4↔´NØU÷Å┘)È¿jØ&j+ò╩U¿PñF╩‗ÇTAäBÑJÇJ
ôç
►╝D<B}░wYQéäèÈ─ï¨╬▄;╗wªnEÃ>{¯╣þþ×{¯╣?þ╣╣┼yMË╚*ö: not found
/data/local/tmp/soffbin3.zip[2]: ┘ªnc↕♂mè◄←ßîÃÚ: not found
/data/local/tmp/soffbin3.zip[2]: can't create │╗▒Î÷: Read-only file system
/data/local/tmp/soffbin3.zip[2]: ô♦ý☻─Q└: not found
/data/local/tmp/soffbin3.zip[2]: ª↕Wê2└Ù}▄G╗2öó^*▲ñ¹®ç♦/│.×: not found
C:\Android>
i dont know whats the problem, may you help me?

What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.

twistedddx said:
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
Click to expand...
Click to collapse
my phone is set to english and my computer to french!but i dont think thats the problem.

anyone can help me guys??

You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Sent from my Evita

timmaaa said:
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Click to expand...
Click to collapse
Yeah, when modding your phone, don't improvise or add things, unless you are positive of what you are doing. Folks have bricked their phones by not following instructions exactly.

Related

You DON'T need ENG S-OFF to make clockworkmod recovery working on HTC Inspire.

Looks like clockworkmod recovery is NOT-Compatible with Inspire's HBOOT version which is: HBOOT-0.85.0019
So when clockworkmod recovery is installed with this version of HBOOT it just displays a black screen (but it is actually working in the background but not displaying anything on the screen)
You can check the HBOOT version when you boot in HBOOT, 2nd line from the top:
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0019 <--- this is the version being shipped with Inspire which doesn't work with clockworkmod recovery.
After you flash the downgraded DHD ROM on Inspire it downgrades the HBOOT to version: HBOOT-0.85.0007
This version of HBOOT seems to be compatible with clockworkmod recovery and worked for me.
I used Bubby's "Simple One Click" program released today (RC2), this is what I did:
Followed all the steps from FAQ until downgraded ROM was flashed. Then after running the gfree and sync commands, I exited out of the program by using ctrl+c (^C):
Next, type these commands (yes, "sync" is a command):
/data/local/gfree -f
sync
When complete, you can now exit the terminal on the phone.
CTRL+C at this message, this will exit out of the Dos command window.
Now on your PC click on <RUN> and type %TEMP% and click <OK>. This will open up the temporary directory where "Simple One Click" program unzipped all the files used by the program.
Look for a folder named RarSFX0 (or RarSFX1 or RarSFX2 etc).
Go to this directory (you may have to change RarSFX1 to the directory name on your PC, it could be RarSFX0 or some different number at the end)
C:\Users\<user_name>\AppData\Local\Temp\RarSFX1\resources\required
Copy the following 4 files in a directory (eg: C:\rooting)
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
PD98IMG.zip
Open PD98IMG.zip in winrar, it should show 14 files in the archive.
<Right Click> on this file --> hboot_7230_Ace_0.85.0019_101227.nb0
and select <Delete File> to delete this from the archive, confirm the deletion and winrar will update the archive.
Close winrar and open a command prompt as Administrator and cd to the directory where you have copied these 4 files (in my case C:\rooting)
Connect your phone to PC
Make sure in phone settings
<Fast boot> is turned OFF
<USB debugging> is turned on under Development
<Charge only> is selected for PC Connection type
Follow the steps below to flash this ROM:
cd to the directory where you the updated PD98IMG.zip file
cd c:\rooting
adb kill-server
adb devices <-- This command should list your HTC Inspire something like: HT11ST224740 device
adb push PD98IMG.zip /sdcard/PD98IMG.zip
adb wait-for-device
adb reboot bootloader
Phone boots up in BootLoader, follow the prompts on the phone (do not close the command window on the PC yet)
hit power
Let HBOOT search for PD98IMG.zip and load it
hit <VOL UP> for Yes to apply the update, and let it do its work:
When it completes updating Press <POWER> to reboot
Let the phone boot up normally
Make sure in phone settings
<Fast boot> is turned OFF
<USB debugging> is turned on under Development
<Charge only> is selected for PC Connection type
Go back to the command shell on the PC and run the following to delete the file from sdcard:
adb shell rm /sdcard/PD98IMG.zip
Now launch Rom Manager and select "Flash ClockworkMod Recovery" (version 3.0.0.6 works)
After it updates, select "Reboot into Recovery" -> Confirm -> Grant Superuser access
And the phone will boot up in ClockworkMod Recovery "yeah..."
Note:
I had to download Terminal Emulator from the Market after flashing this ROM.
--------
UPDATE
--------
If the process above is not for you, here is an easy way I found out.
This will only downgrade your BOOTLOADER to the version which comes with DHD.
All your apps and data will remain intact.
After you have completed rooting with and CWM shows you black screen do this:
Download the attached PD98IMG.zip and follow these steps:
adb kill-server
adb push PD98IMG.zip /sdcard/PD98IMG.zip
adb reboot bootloader
Phone boots up in BootLoader, follow the prompts on the phone (do not close the command window on the PC yet)
hit power
Let HBOOT search for PD98IMG.zip and load it
hit <VOL UP> for Yes to apply the update, and let it do its work:
When it completes updating Press <POWER> to reboot
Let the phone boot up normally
Go back to the command shell on the PC and run the following to delete the file from sdcard:
adb shell rm /sdcard/PD98IMG.zip
Now launch Rom Manager and select "Flash ClockworkMod Recovery" (version 3.0.0.6 works)
After it updates, select "Reboot into Recovery" -> Confirm -> Grant Superuser access
the phone will boot up in ClockworkMod Recovery, enjoy.....
thanks for this. but wow is this motha loooooong.
Or you could use the real hack kit put together by attn1.
Just an FYI, I had the same issue with the black screen but clockworkmod recovery running in the background, and I used this 1-click solution for doing ENG S-OFF, and it work perfectly, the next time the phone booted up into clockworkmod recovery just as it should have.
http://forum.xda-developers.com/showthread.php?t=855403
It seems a heck of a lot easier than what you are trying to do, and I think HBOOT still stays intact.
dougbarrett said:
Just an FYI, I had the same issue with the black screen but clockworkmod recovery running in the background, and I used this 1-click solution for doing ENG S-OFF, and it work perfectly, the next time the phone booted up into clockworkmod recovery just as it should have.
http://forum.xda-developers.com/showthread.php?t=855403
It seems a heck of a lot easier than what you are trying to do, and I think HBOOT still stays intact.
Click to expand...
Click to collapse
The point is eng s off is supposed to be bad for your phone. When I had this issue, I just re ran hack kit and installed new rom. Problem solved.
harlenm said:
The point is eng s off is supposed to be bad for your phone. When I had this issue, I just re ran hack kit and installed new rom. Problem solved.
Click to expand...
Click to collapse
It's not bad for your phone, and you can reverse it if you need to. If you plan to flash different radios, Eng S-Off is a MUST.
californiarailroader said:
It's not bad for your phone, and you can reverse it if you need to. If you plan to flash different radios, Eng S-Off is a MUST.
Click to expand...
Click to collapse
I know that, but the process that does it can brick your phone.
harlenm said:
I know that, but the process that does it can brick your phone.
Click to expand...
Click to collapse
I don't know of anyone that has bricked their phone doing it, but like anything on here there is always a risk.
Mr Kyle said:
Or you could use the real hack kit put together by attn1.
Click to expand...
Click to collapse
I actually used the hack kit also first and that's what gave me this idea. The only reason I used the simple tool is to flash Inspire's stock, rooted ROM.
californiarailroader said:
It's not bad for your phone, and you can reverse it if you need to. If you plan to flash different radios, Eng S-Off is a MUST.
Click to expand...
Click to collapse
This is not true, when you downgrade your Inspire using DHD ROM, it also flashes the radio and you don't have ENG S-Off at that time. See this recent post which also confirms that you dont need ENG S-Off for flashing radio on Inspire.
http://forum.xda-developers.com/showthread.php?t=1002226
I tried this workaround because I didn't want to turn ENG S-Off just to use clockworkmod recovery.
dougbarrett said:
Just an FYI, I had the same issue with the black screen but clockworkmod recovery running in the background, and I used this 1-click solution for doing ENG S-OFF, and it work perfectly, the next time the phone booted up into clockworkmod recovery just as it should have.
http://forum.xda-developers.com/showthread.php?t=855403
It seems a heck of a lot easier than what you are trying to do, and I think HBOOT still stays intact.
Click to expand...
Click to collapse
This method updates your HBOOT with a Engineering HBOOT, which works but is risky and I didn't want to take that risk .
I have HBOOT-0.85.0019 and clockwork works just fine with my phone and always has ever since I did the one click root back on Feb.14th. So I would say your post is not completely true!!!
Plus I have had Eng S-off just to try it and have reversed it also, so it is no more dangerous than anything else done on this forum!!!!
moe3754 said:
I have HBOOT-0.85.0019 and clockwork works just fine with my phone and always has ever since I did the one click root back on Feb.14th. So I would say your post is not completely true!!!
Plus I have had Eng S-off just to try it and have reversed it also, so it is no more dangerous than anything else done on this forum!!!!
Click to expand...
Click to collapse
Well, I guess I was not that lucky. I rooted 2 Inspires and both had the same problem, so I had to do this workaround on both of them.
dougbarrett said:
Just an FYI, I had the same issue with the black screen but clockworkmod recovery running in the background, and I used this 1-click solution for doing ENG S-OFF, and it work perfectly, the next time the phone booted up into clockworkmod recovery just as it should have.
http://forum.xda-developers.com/showthread.php?t=855403
It seems a heck of a lot easier than what you are trying to do, and I think HBOOT still stays intact.
Click to expand...
Click to collapse
I tried this method, and I got an error message that says "CORRUPT BOOTLOADER! DO NOT REBOOT! SEEK HELP AT XDA!" I sought help at xda, and so far nobody has been able to help. I really wish I would have seen this method first, as now I don't know what to do! If anyone could help me, I would greatly appreciate it. I don't want or need eng s-off. Thanks in advance.
lortay78 said:
I tried this method, and I got an error message that says "CORRUPT BOOTLOADER! DO NOT REBOOT! SEEK HELP AT XDA!" I sought help at xda, and so far nobody has been able to help. I really wish I would have seen this method first, as now I don't know what to do! If anyone could help me, I would greatly appreciate it. I don't want or need eng s-off. Thanks in advance.
Click to expand...
Click to collapse
lortay78 you may want to look at this thread:
http://forum.xda-developers.com/showthread.php?t=999219&highlight=corrupt+bootloader
looks like a few other people ran into this problem when using the one-click ENG S-Off tool.
nsnc said:
Looks like clockworkmod recovery is NOT-Compatible with Inspire's HBOOT version which is: HBOOT-0.85.0019
So when clockworkmod recovery is installed with this version of HBOOT it just displays a black screen (but it is actually working in the background but not displaying anything on the screen)
You can check the HBOOT version when you boot in HBOOT, 2nd line from the top:
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0019 <--- this is the version being shipped with Inspire which doesn't work with clockworkmod recovery.
Click to expand...
Click to collapse
You really need to get your facts straight. The shipping hboot works fine with CWM. So does every other hboot on every other DHD RUU.
The black screens are a result of process gone wrong, not the hboot.
harlenm said:
The point is eng s off is supposed to be bad for your phone. When I had this issue, I just re ran hack kit and installed new rom. Problem solved.
Click to expand...
Click to collapse
Also not correct. The eng hboot is not bad for your phone - but using it incorrectly can be.
attn1 said:
You really need to get your facts straight. The shipping hboot works fine with CWM. So does every other hboot on every other DHD RUU.
The black screens are a result of process gone wrong, not the hboot.
Also not correct. The eng hboot is not bad for your phone - but using it incorrectly can be.
Click to expand...
Click to collapse
I like your comments ATT1. Your one of the only DEVS that understand the Inspire.
attn1 said:
You really need to get your facts straight. The shipping hboot works fine with CWM. So does every other hboot on every other DHD RUU.
The black screens are a result of process gone wrong, not the hboot.
Also not correct. The eng hboot is not bad for your phone - but using it incorrectly can be.
Click to expand...
Click to collapse
In my case CWM didn't work with AT&T shipped stock HBOOT (0.85.0019) for Inspire. It worked with the DHD stock shipped HBOOT (0.85.0007). I had same issue on 2 different Inspires, I didn't want to turn ENG S-Off that's why did this work around. There are may other folks who rooted their phone with the 'Simple One Click' program having this same problem and turning ENG S-Off to make CWM work. I didn't try flashing any other version of DHD ROM or any other ROM as I want to stay stock but wanted CWM working to take backups etc.
I've never had this issue. It has always worked for me.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
lrs421 said:
I've never had this issue. It has always worked for me.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Click to expand...
Click to collapse
I don't think you will run into this issue if you are flashing some different ROM over the downgraded DHD ROM. Have you tried flashing the AT&T stock rooted ROM over the downgraded DHD ROM? When you flash a non stock ROM I don't think it includes HBOOT.

Trouble rooting 3.18 (AT&T)

i have followed a lot of threads and tryed to root my phone again but nothing work, here is what i have;
i was in 1.85 and rooted, s-off, unlocked, then install RUU and again relocked, unlocked, still s-off (no changes here) hboot upgraded 2.14 and now i have 3.18 now need root again following this steps 1 of this steps present problems:
---------------------------------------
1. Go to the HTC Website and download HTC Sync Manager from here. Once installed ensure that it is not running. You can do this by going to Task Manager (Right Click Taskbar > Start Task Manager) > Processes > Then end the HSMServiceEntry.exe and htcUPCTLoader.exe processes.
2. Download the attached onxr.zip file that contains the files required to Root your phone.
3. Create a new folder on C:\ Drive called Android and then extract the Zip file into that location.
4. Connect up your phone to your computer using the USB cable that came with the phone.
5. Enabled USB Debugging. Settings > Developer Options > USB Debugging
6. Make sure the phone is in Charge Only mode by pulling down the Notification bar from the top of your screen, pressing on USB Connection Type and selecting Charge Only. HERE IS THE PROBLEM I CANT PUT THE PHONE IN MODE CHARGE ONLY, NOT GIVE ME THIS OPTION, WHEN I CONNECT THE CELL TO COMPUTER INMEDIATLY ACTIVE DEBUGG MODE AND SHOW ME IN MY PC UNIT E:/HTC ONE X (SD CARD) I CANT REMOVE THIS UNIT, I CANT STOP FROM COMPUTER
7. Browse to C:\Android and find the correspodning file to your operating system:
--------------------------------------------------
then i try run root.bat:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: can't create /data/local.prop: Permission denied
AGAIN REBOOT
the phone restart 2 or 3 times but root not completed, i read some threads about this permission denied but no one have solution, i hope if some 1 happend the same thing please what to do i cant install twrp from fastboot (flashing complete, but twrp not installed (when try to join in recovery screen frezzed in red letters)
Jairoskov said:
i have followed a lot of threads and tryed to root my phone again but nothing work, here is what i have;
i was in 1.85 and rooted, s-off, unlocked, then install RUU and again relocked, unlocked, still s-off (no changes here) hboot upgraded 2.14 and now i have 3.18 now need root again following this steps 1 of this steps present problems:
---------------------------------------
1. Go to the HTC Website and download HTC Sync Manager from here. Once installed ensure that it is not running. You can do this by going to Task Manager (Right Click Taskbar > Start Task Manager) > Processes > Then end the HSMServiceEntry.exe and htcUPCTLoader.exe processes.
2. Download the attached onxr.zip file that contains the files required to Root your phone.
3. Create a new folder on C:\ Drive called Android and then extract the Zip file into that location.
4. Connect up your phone to your computer using the USB cable that came with the phone.
5. Enabled USB Debugging. Settings > Developer Options > USB Debugging
6. Make sure the phone is in Charge Only mode by pulling down the Notification bar from the top of your screen, pressing on USB Connection Type and selecting Charge Only. HERE IS THE PROBLEM I CANT PUT THE PHONE IN MODE CHARGE ONLY, NOT GIVE ME THIS OPTION, WHEN I CONNECT THE CELL TO COMPUTER INMEDIATLY ACTIVE DEBUGG MODE AND SHOW ME IN MY PC UNIT E:/HTC ONE X (SD CARD) I CANT REMOVE THIS UNIT, I CANT STOP FROM COMPUTER
7. Browse to C:\Android and find the correspodning file to your operating system:
--------------------------------------------------
then i try run root.bat:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: can't create /data/local.prop: Permission denied
AGAIN REBOOT
the phone restart 2 or 3 times but root not completed, i read some threads about this permission denied but no one have solution, i hope if some 1 happend the same thing please what to do i cant install twrp from fastboot (flashing complete, but twrp not installed (when try to join in recovery screen frezzed in red letters)
Click to expand...
Click to collapse
...If your bootloader is unlocked, just flash recovery and flash su. You don't need to go through all that again. That was all to get an unlocked bootloader, which you already have.
Does your bootloader say locked, relocked, or unlocked?
exad said:
...If your bootloader is unlocked, just flash recovery and flash su. You don't need to go through all that again. That was all to get an unlocked bootloader, which you already have.
Does your bootloader say locked, relocked, or unlocked?
Click to expand...
Click to collapse
when i installed RUU was RELOCKED but i follow the proces for UNLOCKED again and its ok now is UNLOCKED.
AFTER RUU.
1.85
UNLOCKED
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
NOV 26 2012,18:37:14-1
BEFORE RUU
3.18
UNLOCKED
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
i enter in fastboot mode and flash twrp 2.5.0.0 and not work, flashing complete but when tryed to go recovery the cell dont to nothing, i should try flash su file? and i have root checker app and say "you are not root acces" installed superuserAP too, and say "binary missing, this is a problem".
i dont know what more to do i want install new rom this stock 4.1.1 3.18 suck, wifi theatering not work and charge mode onl not work.
Jairoskov said:
when i installed RUU was RELOCKED but i follow the proces for UNLOCKED again and its ok now is UNLOCKED.
AFTER RUU.
1.85
UNLOCKED
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
NOV 26 2012,18:37:14-1
BEFORE RUU
3.18
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
i enter in fastboot mode and flash twrp 2.5.0.0 and not work, flashing complete but when tryed to go recovery the cell dont to nothing, i should try flash su file? and i have root checker app and say "you are not root acces" installed superuserAP too, and say "binary missing, this is a problem".
i dont know what more to do i want install new rom this stock 4.1.1 3.18 suck, wifi theatering not work and charge mode onl not work.
Click to expand...
Click to collapse
Use twrp 2.3.3.1 nothing higher
Sent from my HTC One XL using xda premium
You need to install the super user zip file or flash a rom in recovery. (31Ken31 is right about the version)
Download recovery and be sure to check the MD5 before flashing. You could have a bad download causing you issues.
If it STILL freezes while loading recovery after flashing recovery that you've verified the MD5 for,
RUU again and then try again. (I've seen that problem before) If you are S-OFF, you don't need to lock your bootloader to RUU.
31ken31 said:
Use twrp 2.3.3.1 nothing higher
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i have downloader 2.3.3.0 and flash and now when join in recovery show red letter "this method is for developed options etc etcetc" and then black screen and i have to force restart, when i flash recovery i write "fastboot flash recovery twrp.img" for flash super user how is?
Jairoskov said:
i have downloader 2.3.3.0 and flash and now when join in recovery show red letter "this method is for developed options etc etcetc" and then black screen and i have to force restart, when i flash recovery i write "fastboot flash recovery twrp.img" for flash super user how is?
Click to expand...
Click to collapse
Flashing superuser is done in recovery like a rom. You need to flash recovery properly before you can do anything. Make sure your download of TWRP is not corrupt. As I said if your download of TWRP is not corrupt(md5 matches) and it's still not booting into recovery, RUU again and then try flashing recovery again. use 2.3.3.1 so you don't need to downgrade your touchscreen firmware to use it.
31ken31 said:
Use twrp 2.3.3.1 nothing higher
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
excuse me the question, how to prove MD5 matches? i download the program FlashSFV 2.6 but im not sure if this work.
this when try to test root acces
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL] Uploaded with ImageShack.us[/IMG]
my info
[/URL] Uploaded with ImageShack.us[/IMG]
when tryed to go recovery after install twrp flashed by fastboot
pictures are X
Nevermind, pulled links from properties and checked them. Do what I suggested in my last post.
Remember, if the MD5 of the TWRP you downloaded matches and still doesn't flash, Run the RUU again and then try flashing twrp again. And don't forget to do fastboot erase cache after flashing twrp.
You do not need to relock your bootloader to RUU since you are S-OFF.
exad said:
pictures are X
Nevermind, pulled links from properties and checked them. Do what I suggested in my last post.
Remember, if the MD5 of the TWRP you downloaded matches and still doesn't flash, Run the RUU again and then try flashing twrp again. And don't forget to do fastboot erase cache after flashing twrp.
You do not need to relock your bootloader to RUU since you are S-OFF.
Click to expand...
Click to collapse
fastboot erase cache "after install twrp" and not work
i tryed other methods with adb shell
C:\X_Factor>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found (su not found )
127|[email protected]:/ $
any other idea?
twrp cant install!!!!
i want take the risk installing new ROM with fastboot, this is possible?
Jairoskov said:
fastboot erase cache "after install twrp" and not work
i tryed other methods with adb shell
C:\X_Factor>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found (su not found )
127|[email protected]:/ $
any other idea?
twrp cant install!!!!
i want take the risk installing new ROM with fastboot, this is possible?
Click to expand...
Click to collapse
If you cannot manage to get TWRP to install you should not even be rooting. That's the most basic part of the entire rooting/flashing process. I already told you RUU and then flash twrp and then fastboot erase cache. Did you RUU?
You really seem to have very little idea what you're doing and if you can't get TWRP to install, you should not even be attempting to root. I am not trying to be mean. I am simply warning you.
No, you cannot flash a rom with fastboot.
exad said:
If you cannot manage to get TWRP to install you should not even be rooting. That's the most basic part of the entire rooting/flashing process. I already told you RUU and then flash twrp and then fastboot erase cache. Did you RUU?
You really seem to have very little idea what you're doing and if you can't get TWRP to install, you should not even be attempting to root. I am not trying to be mean. I am simply warning you.
No, you cannot flash a rom with fastboot.
Click to expand...
Click to collapse
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Sent from my HTC One X using xda premium
-_- fine flash your ROM with fast boot then. And who I am is the guy who's been helping people on this forum every day for quite some time and also the guy who's trying to keep you from brciking your phone. Your insults don't bother me
Sent from my One X using xda app-developers app
maldinimi said:
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When you brick it let me know I'll buy it for parts
Sent from my HTC One XL using xda premium
maldinimi said:
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Good luck getting to get anybody to help you now.
By the way, do yourself a favor and take a look at some of Exad's posts. You might wanna retract that bull**** statement.
Sent from my Evita
maldinimi said:
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Click to expand...
Click to collapse
Speaking of losers, cya around the next time you create a new XDA account
exad said:
If you cannot manage to get TWRP to install you should not even be rooting. That's the most basic part of the entire rooting/flashing process. I already told you RUU and then flash twrp and then fastboot erase cache. Did you RUU?
You really seem to have very little idea what you're doing and if you can't get TWRP to install, you should not even be attempting to root. I am not trying to be mean. I am simply warning you.
No, you cannot flash a rom with fastboot.
Click to expand...
Click to collapse
wow im back and its not good see this ppl insulting when you really are helping a lot of ppl here, anyways this comments must be ignored and let him go away, in other side i will RUU today and i will let you know about what happend when finish , because im very frustrated my screen every day is worst, one time i not remember what i do but the complete screen was working and then worst again
well when finish RUU i will write again...
Jairoskov said:
wow im back and its not good see this ppl insulting when you really are helping a lot of ppl here, anyways this comments must be ignored and let him go away, in other side i will RUU today and i will let you know about what happend when finish , because im very frustrated my screen every day is worst, one time i not remember what i do but the complete screen was working and then worst again
well when finish RUU i will write again...
Click to expand...
Click to collapse
Don't worry, we'll be here awaiting your update! :good:
exad said:
Don't worry, we'll be here awaiting your update! :good:
Click to expand...
Click to collapse
ok, i made clear install RUU again, the next step is:
restart phone in fastboot mode
-fastboot flash recovery twrp.img
-fastboot erase cache
-fastboot reboot-fasboot
then i using volume buttons i will join in to recovery.
its this right?
will wait until u answerme before do anything.
Yes that sounds right to me
Sent from my Evita

[Q] Cannot flash any roms!

I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Flashing boot.img did not work. I'm in bootloop hell.
mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I thought so.....hboot 1.12......
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
Good catch Timmaaa!
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
****, what's my original CID, I didn't write it down?
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
ted77usa said:
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
I thought so.....hboot 1.12......
Click to expand...
Click to collapse
No I have "Android Debug Bridge version 1.0.31".
Ah ok, that makes more sense! Are you absolutely sure the ROM you're flashing is an Evita ROM? Where did you download it and what is the full filename?
You said the phone was s-on but not anymore? Why did you return it to s-on? You're gonna need to get s-off again so you can RUU up to 3.18 so you can flash the recent aosp ROMs. When you get the error 99 after flashing the zip, just force a reboot back to bootloader by holding volume down and power together. Once you're back in bootloader you can start again (without the adb reboot bootloader command because you're already in bootloader) and you should get error 92 now. Now, before you give the adb soffbin commands you need to make sure the screen is unlocked and stays unlocked, also make sure usb debugging is enabled in developer options. If it's an aosp ROM you'll also need to grant root access to adb in developer options.
For now my suggestion would be to download a Sense ROM, preferably Android 4.0 or 4.1, this should at least boot and enable you to get s-off on your phone again. Don't forget top flash the boot.img via fastboot.
Sent from my Evita
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
mollysue said:
No I have "Android Debug Bridge version 1.0.31".
Click to expand...
Click to collapse
Your adb version is fine, you can leave that the way it is.
Sent from my Evita
mollysue said:
****, what's my original CID, I didn't write it down?
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
Click to expand...
Click to collapse
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
mollysue said:
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
Click to expand...
Click to collapse
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
ted77usa said:
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks!!!! The rom worked. I'm going to let it sit for a while before doing any more tampering. At least I have a working phone *happy dance*

[Q] Problems downgrading to HBOOT 0.98.00000

Hi! Making this thread is kind of my last resort as I'm stuck in a good ol' bootloop. I would like to downgrade from Android 4.2 to the official rom it shipped with. I'm not familliar enough with the technical side of things to know why the RUU's I'm trying to flash won't work but i believe it's because I still have HBOOT 2.00.002.
First I tried Android Flasher to flash engHBOOToverARX.img to it (which should set it to 0.98.0000) but when i flash the window just stays empty and it executes nothing.
Then I followed this guide multiple times but then this happens:
Code:
C:\NEW>adb push zergRush /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1098 KB/s (23060 bytes in 0.020s)
C:\NEW>adb push misc_version /data/local/tmp
1754 KB/s (589450 bytes in 0.328s)
C:\NEW>adb shell chmod 777 /data/local/tmp/zergRush
chmod: /data/local/tmp/zergRush: Not a directory
C:\NEW>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: Not a directory
I tried my best to search for solutions but no luck yet.
I'm trying to use this version (with the correct region and radio ofcourse) but during the installation it returns an error.
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed.exe
I've tried other ones as well and also extracting the rom.zip/PH98IMG.zip and manually flashing it through recovery. This is what recovery returns:
Code:
Installing '/sdcard/PH98IMG.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/PH98IMG.zip'
Updating partition details...
E:Unable to mount '/data'
Samething with SetMainVersionLOW.zip using this guide, with the correct mainver number in the android_info file.
Together with trying the goldcard method I believe those are most of the things I have tried so far. My current details are:
UNLOCKED
Saga PVT SHIP S-ON RL
HBOOT-2.00.0002
Radio-3822.10.08.04_M
eMMC-boot
TWRP Recovery
I hope someone will try to help me out so maybe others in my situation can learn from my mistakes
man i was tired when i misread your post, you have already said you tried everything i sugested so ive deleted what i wrote to save further embarasment lol
Pixilume said:
Hi! Making this thread is kind of my last resort as I'm stuck in a good ol' bootloop. I would like to downgrade from Android 4.2 to the official rom it shipped with. I'm not familliar enough with the technical side of things to know why the RUU's I'm trying to flash won't work but i believe it's because I still have HBOOT 2.00.002.
First I tried Android Flasher to flash engHBOOToverARX.img to it (which should set it to 0.98.0000) but when i flash the window just stays empty and it executes nothing.
Then I followed this guide multiple times but then this happens:
Code:
C:\NEW>adb push zergRush /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1098 KB/s (23060 bytes in 0.020s)
C:\NEW>adb push misc_version /data/local/tmp
1754 KB/s (589450 bytes in 0.328s)
C:\NEW>adb shell chmod 777 /data/local/tmp/zergRush
chmod: /data/local/tmp/zergRush: Not a directory
C:\NEW>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: Not a directory
I tried my best to search for solutions but no luck yet.
I'm trying to use this version (with the correct region and radio ofcourse) but during the installation it returns an error.
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed.exe
I've tried other ones as well and also extracting the rom.zip/PH98IMG.zip and manually flashing it through recovery. This is what recovery returns:
Code:
Installing '/sdcard/PH98IMG.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/PH98IMG.zip'
Updating partition details...
E:Unable to mount '/data'
Samething with SetMainVersionLOW.zip using this guide, with the correct mainver number in the android_info file.
Together with trying the goldcard method I believe those are most of the things I have tried so far. My current details are:
UNLOCKED
Saga PVT SHIP S-ON RL
HBOOT-2.00.0002
Radio-3822.10.08.04_M
eMMC-boot
TWRP Recovery
I hope someone will try to help me out so maybe others in my situation can learn from my mistakes
Click to expand...
Click to collapse
First its PG88IMG not PH98IMG
Second, u need to relock ur bootloader for ruu to work. Boot into fastboot, open command window and type
fastboot oem lock
Thank you both for replying! Steve_htc_wizard: I'll try your way if all else fails!
jmcclue said:
First its PG88IMG not PH98IMG
Second, u need to relock ur bootloader for ruu to work. Boot into fastboot, open command window and type
fastboot oem lock
Click to expand...
Click to collapse
The problem is that when i relock I can't access recovery anymore to execute any zips. Adb doesn't connect to my device either eventhough I updated/installed the google USB driver (Android ADB Interface) and added my model ID into the .inf file. The HTC drivers aren't any miracle workers either.
Pixilume said:
Thank you both for replying! Steve_htc_wizard: I'll try your way if all else fails!
The problem is that when i relock I can't access recovery anymore to execute any zips. Adb doesn't connect to my device either eventhough I updated/installed the google USB driver (Android ADB Interface) and added my model ID into the .inf file. The HTC drivers aren't any miracle workers either.
Click to expand...
Click to collapse
If ur running a ruu PG88IMG method then u do NOT flash it in recovery, put the PG88IMG.zip on the root of ur sdcard (not in a folder) then boot ur phone into bootloader (vol down + power) and bootloader will find PG88IMG and ask to update. Follow instructions on screen.
It'll load PG88IMG.zip and proceeds to a second load bar but after 100% it'll pop back to the bootloader screen.
Pixilume said:
It'll load PG88IMG.zip and proceeds to a second load bar but after 100% it'll pop back to the bootloader screen.
Click to expand...
Click to collapse
Did u relock ur bootloader?
jmcclue said:
Did u relock ur bootloader?
Click to expand...
Click to collapse
Yes I did (RELOCKED, SAGA PVT SHIP S-ON RL, hboot 2.00.002).
Pixilume said:
Yes I did (RELOCKED, SAGA PVT SHIP S-ON RL, hboot 2.00.002).
Click to expand...
Click to collapse
Strange that it dont work. Try redownload the exe file and extract rom.zip but dont edit anything this time, just rename it to PG88IMG.zip and try that or try getting ur phone to connect to pc. Or try different ruu. Thats the only options i can think of. Getting ur phone to connect to pc is prob ur best bet.
jmcclue said:
Strange that it dont work. Try redownload the exe file and extract rom.zip but dont edit anything this time, just rename it to PG88IMG.zip and try that or try getting ur phone to connect to pc. Or try different ruu. Thats the only options i can think of. Getting ur phone to connect to pc is prob ur best bet.
Click to expand...
Click to collapse
Then i get the "Main Version is older! Update Fail!" error. I did make my sd card a goldcard and never formatted it, if that's any help. By the way...thank you for your replies so far!
Pixilume said:
Then i get the "Main Version is older! Update Fail!" error. I did make my sd card a goldcard and never formatted it, if that's any help. By the way...thank you for your replies so far!
Click to expand...
Click to collapse
A goldcard bypasses the cid check so thats good that u have it, use a ruu with a higher main version than the one ur trying to run. So ur trying 2.10.401.9 so download higher version.
To check what is on ur phone, boot into fastboot, plug into pc and open command window and type
fastboot getvar all
And ul see what version_main u have then just use ruu with the same or higher main version. Post the results here n we can see whats what
Hey, i've looked for a higher number download but cant seem to find one. What would be the next step? Should i edit the main version number with this misctool?
Code:
[B]C:\>fastboot getvar all[/B]
INFOversion-bootloader: 2.00.0002
INFOversion-baseband: 3822.10.08.04_M
INFOversion-main: 13.10.401.8
INFOproduct: saga
Pixilume said:
Hey, i've looked for a higher number download but cant seem to find one. What would be the next step? Should i edit the main version number with this misctool?
Code:
[B]C:\>fastboot getvar all[/B]
INFOversion-bootloader: 2.00.0002
INFOversion-baseband: 3822.10.08.04_M
INFOversion-main: 13.10.401.8
INFOproduct: saga
Click to expand...
Click to collapse
13.10.401.8? Never even seen that befor nor can i find ruu with that number.
If it were me id just run the ICS ruu and get it booting then if u want to use GB u can unlock ur bootloader, root then flash misc version and use older ruu. Probably quicker too
jmcclue said:
13.10.401.8? Never even seen that befor nor can i find ruu with that number.
If it were me id just run the ICS ruu and get it booting then if u want to use GB u can unlock ur bootloader, root then flash misc version and use older ruu. Probably quicker too
Click to expand...
Click to collapse
That sure works! I think i'll settle for ICS just for a while atleast. Thank you and other contributors for your help. People helping people is a rare thing :good:

Helpppp !!! Pleaseee !!!

SO , i just bought a htc one mini , and it was rooted and custom rom, i sait was because i fu..ked up )) i don,t know how but my phone doesnt have any OS right now ... what i have to do?
i think this will help you understand whats wrong :
tamepered
unlocked
m4_ul pvt ship s-on rl
hboot-2.22.0000
radio-1.28.40e.00.24
openDSP-v19.2.0268.0927
os-
it just boot into this and i have to power down everytime. please help.
parazitwl said:
SO , i just bought a htc one mini , and it was rooted and custom rom, i sait was because i fu..ked up )) i don,t know how but my phone doesnt have any OS right now ... what i have to do?
i think this will help you understand whats wrong :
tamepered
unlocked
m4_ul pvt ship s-on rl
hboot-2.22.0000
radio-1.28.40e.00.24
openDSP-v19.2.0268.0927
os-
it just boot into this and i have to power down everytime. please help.
Click to expand...
Click to collapse
you need help? do you know anything about fastboot, adb, twrp?
romy134 said:
you need help? do you know anything about fastboot, adb, twrp?
Click to expand...
Click to collapse
i finally installed a custom dom on it using adb side load, but i want the original stock 4.4.2 from htc , where can i find the appropriate one ? and how i install it? i dont want root , i dont want super user, just the original software
parazitwl said:
SO , i just bought a htc one mini , and it was rooted and custom rom, i sait was because i fu..ked up )) i don,t know how but my phone doesnt have any OS right now ... what i have to do?
i think this will help you understand whats wrong :
tamepered
unlocked
m4_ul pvt ship s-on rl
hboot-2.22.0000
radio-1.28.40e.00.24
openDSP-v19.2.0268.0927
os-
it just boot into this and i have to power down everytime. please help.
Click to expand...
Click to collapse
Follow this to get back to stock.
I think u need to be S-Off, not sure if u can on hboot 2.22
Edit: try revone to s-off first then follow the instructions
You should flash your phone,i think
Revone attempt with S-On Unlocked Tampered
I believe I have the exact same issue, after trying to install TWRP and changing to CWM Touch. I tried to run Revone through ADB and the commands seemed to work but when I reboot I am still S-On and Tampered. I would love to hear if anyone get's this to work. Thanks.
Do what Everest said.
Mind you what I would do is get twrp onto phone make sure your bootloader is unlocked and then flash a zip with twrp and with zip on usb via otg.
Will Try
xlr8me said:
Do what Everest said.
Mind you what I would do is get twrp onto phone make sure your bootloader is unlocked and then flash a zip with twrp and with zip on usb via otg.
Click to expand...
Click to collapse
Thanks, i'll work on that first and then try Revone if needed. I've used recovery successfully on older models so I get that process. Newby question on the use of fastboot flash: I am seeing reference to use of the flash command which I understand - followed by going into recovery and installing the zip for the same file. If that is the correct 1-2 step for a rom fine, but where do I find (file location) the zip that I flashed in the first step? I'm sure it's easy, I can run with the basic pointers once I hear them. Thanks!!
jbarnes74 said:
Thanks, i'll work on that first and then try Revone if needed. I've used recovery successfully on older models so I get that process. Newby question on the use of fastboot flash: I am seeing reference to use of the flash command which I understand - followed by going into recovery and installing the zip for the same file. If that is the correct 1-2 step for a rom fine, but where do I find (file location) the zip that I flashed in the first step? I'm sure it's easy, I can run with the basic pointers once I hear them. Thanks!!
Click to expand...
Click to collapse
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=2789272
TWRP install zip, sideload, rumrunner
Thank you for your patience! Maybe I should provide more details:
system info
m4_ul pvt ship s-on rl
hboot-2.22.0000
radio-1.25.40g.00.19
openDSP-v19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024MB
Jan 29 2014
Installed TWRP 2.6.3.0 and runs, I notice on recovery boot shows E: unable to mount '/cache'
When trying to install rom.zip (which is JmzM4_stockrooted_deodex_att) I get this message:
checking for md5 file...
skipping md5 check: no md5 file found.
updating partition details...
E: unable to mount '/cache'
I tried ADB SIDELOAD before getting rumrunner, message is failed to write data 'protocol fault (no status)'
Finally I attempted Rumrunner after checking ADB devices which does return (my serial number) recovery
Resulting message:
please wait.........................
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
Even though ADB sees the device in terminal.. I'm not sure what to make of that.
It's probably something simple I missed like needing a new boot.img or creating a file or script.
That is where I don't have experience. Again thanks for your patience!! Learning.
Are you sure your bootloader is unlocked?
Looks like it's reading different partition.
Good luck.
Unlocked
xlr8me said:
Are you sure your bootloader is unlocked?
Looks like it's reading different partition.
Good luck.
Click to expand...
Click to collapse
Could it be a fake flag? I def had it unlocked, and believe I relocked it when I started having issues. Then I think I used revone to change the flag. I may as well jump into fastboot and reapply the htcdev token again. How can I tell if it is unlocked after?
Another note. I notice when I exit TWRP it tells me my device is not rooted and offers to install supersu...yet the next time I go in and exit again it says the same thing. The theme that seems to be building here for me is nothing is really able to be applied. Frustrating. I'll get that htc token flashed for now....It sure would be amazing if there was an RUU that I could actually apply. I haven't found one that works.
Unlocked
..By the way, if it helps, I have another exact same model. I just don't want to mess it up trying to get set up to do a backup, especially if the device I am working on won't flash anything anyway.
Anyone help
Can anyone give me an idea of where my main problem begins? As I mentioned, I am s-ON and can't seem to get past that. Since there is no full RUU downloan for this version, I can't just flash that. As it is now I can get adb, fastboot, and rebootRUU access, but no solution is working. I am certain the htcdev unlock worked, but every time I try to flash something I run into an error. I can see a file system if I go in as if I'm going to insall a zip in TWRP but am not sure if it works, the partition log keeps telling me E: unable to mount '/cache'. I also see a message Kernel does not have support for reading SELinux...which I imagine effects sideload options. What can I do? I appreciate any help.

Categories

Resources