Related
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Whoareyou said:
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Click to expand...
Click to collapse
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
krook6023 said:
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111)...
Click to expand...
Click to collapse
Maybe an issue with SuperCID...
You should read this thread: http://forum.xda-developers.com/showthread.php?t=2753631
People had a similar problem and a few were able to get back into hboot by plugging the phone to computer and persistently pressing power and volume down and/or volume up in different combinations. If you can get back to the boot loader flash a know working firmware. It's worth a shot... Here are some relevant comments from that thread...
streather said:
Same problem here, bricked the phone.
I have managed to get it to turn back on and got to the silver HTC logo but I sent the wrong command over fastboot and it turned off again
Click to expand...
Click to collapse
BanBoo said:
How do you managed it?!
Click to expand...
Click to collapse
simaka said:
OK, I got back to the bootloader.
Guys, be persistent in pressing power+vol buttons while usb connected to PC, it took me about 10-15 minutes but now I am back to fastboot!
Any ideas what would be the best course of action now?
Click to expand...
Click to collapse
simaka said:
Not sure if it was power + vol down or + vol up... But I definitely waited each time about 20 secs before switching to the other possibility. And the phone was usb connected to my pc.
Click to expand...
Click to collapse
simaka said:
Yes, each time. I also tried pressing both + and - at the same time, but that was not the winning combination.
Click to expand...
Click to collapse
yoshi8 said:
how did you recognized that you are in fastboot again? did your screen turn on again?
Click to expand...
Click to collapse
simaka said:
Yes, it has booted and screen is lit and I am in fastboot. Now wondering what is the best next step... Which firmware should I upgrade with...
Click to expand...
Click to collapse
simaka said:
Here is what I did the last time:
1. winclock showing seconds in front of me.
2. hold power + vol down.
3. Count 3 seconds
4. release.
5. Go to 1 and add 1 second on step 3 . In about 20 minutes (when I surpassed 20 secs I started from 3 seconds on step 3 again) I woke it up.
good luck!
Click to expand...
Click to collapse
Sent from my HTC One_M8 using Tapatalk
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
NxNW said:
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you know what i mean, it was all 1s also holding the buttons didnt work
Whoareyou said:
you know what i mean, it was all 1s also holding the buttons didnt work
Click to expand...
Click to collapse
Just checking- someone said it could be an issue with the CID, and that would definitely be "an issue" ; )
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Click to expand...
Click to collapse
That right there is what bricked your phone. I honestly don't know why people care so much about the red message on boot to flash a modded Hboot. Most devs on the One international forum are starting to pull of their modded Hboots as people usually don't know flashing a modded one can brick phones on future updates or so.
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Jorakal said:
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That is a good way however we should point if one has a moded hboot and applies the official RUU will brick the phone. Just pointing that out.
Sent from my HTC One using Tapatalk
Firmware Update
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Tewessarino said:
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Click to expand...
Click to collapse
Take a look @Behold_this thread TMOUS Firmware Packages - Release Builds for the correct firmware to return you to stock hboot.
factory reset
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
matador1510 said:
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
Click to expand...
Click to collapse
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
factory reset
majmoz said:
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
Click to expand...
Click to collapse
thanx i will try this will let you what happens
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
majmoz said:
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
Click to expand...
Click to collapse
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
lordtopher said:
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
Click to expand...
Click to collapse
Can you connect the phone to a computer and is it recognized?
If yes, then I would recommend flashing the firmware. It contains hboot and you may have an issue with hboot.
Here is the procedure for flashing the firmware. If your phone is already in bootloader/FASTBOOT USB you can skip the first line.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Does anyone happen to have a Rogers RUU?
Nope, the Telus RUU works fine on Rogers though. They use the exact same modem firmware so the only difference would be the crap apps they bundle.
mrplowdan said:
Nope, the Telus RUU works fine on Rogers though. They use the exact same modem firmware so the only difference would be the crap apps they bundle.
Click to expand...
Click to collapse
I'm trying to fix my bricked HTC Desire 601 with Rogers, and I tried the Telus RUU 4.2.2 and it failed with "Model ID error".
The thing is I think I bought my phone with 4.4.2 update already on it and that might be causing the error.
So I wanted to try using RUU for 4.4.2, but it's not available. What should I do ?
I can lock/unlock bootloader, i'm S-ON so no ROM flashing....
Thanks for any help.
black-venomz said:
I'm trying to fix my bricked HTC Desire 601 with Rogers, and I tried the Telus RUU 4.2.2 and it failed with "Model ID error".
The thing is I think I bought my phone with 4.4.2 update already on it and that might be causing the error.
So I wanted to try using RUU for 4.4.2, but it's not available. What should I do ?
I can lock/unlock bootloader, i'm S-ON so no ROM flashing....
Thanks for any help.
Click to expand...
Click to collapse
Sorry dude, I'd flash twrp and try to flash insert coin. Good luck. I sold this crappy phone and bought a used nexus 5. No more BS.
mrplowdan said:
Sorry dude, I'd flash twrp and try to flash insert coin. Good luck. I sold this crappy phone and bought a used nexus 5. No more BS.
Click to expand...
Click to collapse
InsertCoin is the reason I'm in this s*h*i*t*hole in the first place. I'm S-ON so it's not possible.
Thanks anyway.
black-venomz said:
InsertCoin is the reason I'm in this s*h*i*t*hole in the first place. I'm S-ON so it's not possible.
Thanks anyway.
Click to expand...
Click to collapse
Even if your s-on you can still flash twrp and install roms. You bought your phone new and it already had 4.4.2? Go to the bootloader and check to see what your hboot version is. Although I sold the phone I'll step you through.
mrplowdan said:
Even if your s-on you can still flash twrp and install roms. You bought your phone new and it already had 4.4.2? Go to the bootloader and check to see what your hboot version is. Although I sold the phone I'll step you through.
Click to expand...
Click to collapse
I've tried flashing multiple ROMs (custom and roms apparently stock).
The flash went well but after reboot the bootloop was still there (it probably never installed in the first place).
My hboot version is : 2.20.0000
I already have TWRP installed.
What should I do ?
Thank you for the help.
black-venomz
black-venomz said:
My hboot version is : 2.20.0000
Click to expand...
Click to collapse
Theres your issue, thats the jb hboot. First off make sure your twrp is the correct version. Boot into recovery and mount data and system and use the file browser to make sure its mounting properly. You'll have to find a twrp backup or flashable zip of 4.2.2. Once your back up and running s-off that sucker. Then change your mid to telus' and run the ruu. Then just ota as normal.
mrplowdan said:
Theres your issue, thats the jb hboot. First off make sure your twrp is the correct version. Boot into recovery and mount data and system and use the file browser to make sure its mounting properly. You'll have to find a twrp backup or flashable zip of 4.2.2. Once your back up and running s-off that sucker. Then change your mid to telus' and run the ruu. Then just ota as normal.
Click to expand...
Click to collapse
Couldn't find any TWRP backup for Zara_UL. Only one for Zara_CL.
The flashable zip, is it the one from HTCDev website ? Because there is one for my device.
If not, could you point out where I could find such thing ?
You have to understand I have tried many many things already and I'm kind of tired of it so sorry for all the lame questions .
Here my thread if you want to check it out : http://forum.xda-developers.com/android/help/soft-bricked-htc-desire-601-zaraul-s-t2893035/post55799596#post55799596
black-venomz said:
Couldn't find any TWRP backup for Zara_UL. Only one for Zara_CL.
The flashable zip, is it the one from HTCDev website ? Because there is one for my device.
If not, could you point out where I could find such thing ?
You have to understand I have tried many many things already and I'm kind of tired of it so sorry for all the lame questions .
Here my thread if you want to check it out : http://forum.xda-developers.com/and...1-zaraul-s-t2893035/post55799596#post55799596
Click to expand...
Click to collapse
No not from HTC dev. Try this http://forum.xda-developers.com/des...lockworksenseless-4-2-2-4-4-2-coming-t2845247
Have you checked to ensure twrp is mounting your partitions correctly?
mrplowdan said:
No not from HTC dev. Try this http://forum.xda-developers.com/des...lockworksenseless-4-2-2-4-4-2-coming-t2845247
Have you checked to ensure twrp is mounting your partitions correctly?
Click to expand...
Click to collapse
Now that you mention it, I have often seen the errors :
Unable to mount /system
Unable to mount /data
I just tried mount with TWRP and I can't even select System and Date (you have to check the box, and it won't let me check it).
Tried mounting with CWM and can't mount.
I thought that was the point of S-ON ? That you can't access and write in the system partition ?
black-venomz
black-venomz said:
Now that you mention it, I have often seen the errors :
Unable to mount /system
Unable to mount /data
I just tried mount with TWRP and I can't even select System and Date (you have to check the box, and it won't let me check it).
Tried mounting with CWM and can't mount.
I thought that was the point of S-ON ? That you can't access and write in the system partition ?
black-venomz
Click to expand...
Click to collapse
Good, making progress... Your using the wrong twrp. You'll need to flash the proper one. Not sure which one of these will work but I know for sure one of the 2.7 versions will http://techerrata.com/browse/twrp2/zaracl
I know this is for zara cl but they work with zara ul as well. I'm not sure but i think the older ones are for jb and the newer for kk. Just try a few until you can mount properly while in recovery, then flash that rom I posted.
S-on just restricts some fastboot commands and /system protection while booted into android, doesn't affect recovery. Some kernels are patched so /system is writable in android even with s-on
mrplowdan said:
Good, making progress... Your using the wrong twrp. You'll need to flash the proper one. Not sure which one of these will work but I know for sure one of the 2.7 versions will http://techerrata.com/browse/twrp2/zaracl
I know this is for zara cl but they work with zara ul as well. I'm not sure but i think the older ones are for jb and the newer for kk. Just try a few until you can mount properly while in recovery, then flash that rom I posted.
S-on just restricts some fastboot commands and /system protection while booted into android, doesn't affect recovery. Some kernels are patched so /system is writable in android even with s-on
Click to expand...
Click to collapse
Hope we have a solution there ! Thank you for the walkthrough. I'll try it when I have time (exam 2morrow).
black-venomz
black-venomz said:
Hope we have a solution there ! Thank you for the walkthrough. I'll try it when I have time (exam 2morrow).
black-venomz
Click to expand...
Click to collapse
Tried every version in the link (and others I found).
They all failed to mount System, Cache, Data.
As I said before I'm not really surprised because I believe S-ON is there to prevent us from doing exactly that.
I think I should look into "fastboot boot" command (already tried and failed but it seemed promising).
Any ideas ?
Thanks again.
black-venomz
Flash the jb rom via twrp https://drive.google.com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&usp=sharing
black-venomz said:
Tried every version in the link (and others I found).
They all failed to mount System, Cache, Data.
As I said before I'm not really surprised because I believe S-ON is there to prevent us from doing exactly that.
I think I should look into "fastboot boot" command (already tried and failed but it seemed promising).
Any ideas ?
Thanks again.
black-venomz
Click to expand...
Click to collapse
I can assure you it's not related to being s-on. Can you get adb access from any of the recoveries? fastboot boot doesn't work for a number of newer HTC devices, unfortunately including that zara so that's a dead end
Child's Play said:
Flash the jb rom via twrp https://drive.google.com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&usp=sharing
Click to expand...
Click to collapse
He has to get recovery working properly first. Good call on the backup though.
mrplowdan said:
I can assure you it's not related to being s-on. Can you get adb access from any of the recoveries? fastboot boot doesn't work for a number of newer HTC devices, unfortunately including that zara so that's a dead end
He has to get recovery working properly first. Good call on the backup though.
Click to expand...
Click to collapse
Do u need to mount in order to flash the stock rom zip?
Child's Play said:
Do u need to mount in order to flash the stock rom zip?
Click to expand...
Click to collapse
I got adb sideload running a while.
Just to test it I transfered a rom via "adb sideload c:/rom.zip"
It actually failed after like 40% transfer with "file corrupt".
When starting adb sideload my log had several errors that could help :
"""
TWRP 2.8.0.1
Unable to recreate /data/media folder
Updating partition details...
Unable to mount /cache
Unable to mount /data
Unable to mount /system
Unable to mount internal storage
Unable to mount /data/media during GUI startup
Unable to mount /cache
Kernel does not hav support for reading SELinux contexts (Might be because I flashed KofilaKernel ?)
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /data/media/TWRP/.twrps when trying to read settings file
Unable to mount /data
MTP Enabled
Using RAM for sideload storage
Etc...
""""
I did, at some point, flashed KofilaKernel (found on in HTC Desire 601/Kernels). I can't find a stock kernel. Could it be messing with TWRP ?
Child's Play what file should I flash ? You can flash a ".img" via recovery ? (Though it was .zip only)
U flashed kofilakernel sense 6.0?
Child's Play said:
U flashed kofilakernel sense 6.0?
Click to expand...
Click to collapse
I flashed this : http://forum.xda-developers.com/desire-601/development/kernel-kofilakernel-t2857403
Edit : I flashed the 2.2 version, wich is probably Sense 6.0
hello guys, please help, before one week i update my HTC 601 to KitKat and i make mistake, my phone is much much slower, on jelly bean phone work perfect,
can i downgrade to jelly bean without root and losing warranty?
No. Do a factory reset and see if it helps
Child's Play said:
No. Do a factory reset and see if it helps
Click to expand...
Click to collapse
i try factory default, but no so smooth like on the jelly bean, what is this: Sense 5 JellyBean RUU - Sprint Sense 5 JellyBean RUU.exe, i download but how to install this?
all the best
Its for returning to stock
Child's Play said:
Its for returning to stock
Click to expand...
Click to collapse
can i install this https://drive.google.com/uc?id=0BzrP5DWIlpplTGE4cWVYRDBsUFU&export=download
my phone is
ZARA_UL PVT SHIP S-ON RL
HBOOT 2.22.0000
RADIO1.27.40c.00.11
No. We dont have a tool that allows us to downgrade to jb
Child's Play said:
No. We dont have a tool that allows us to downgrade to jb
Click to expand...
Click to collapse
if i lose my warantty, how to downgrade to jelly bean, is there any way?
all the best
Theres no way to do that. I suggest that u replace the phone
gigidel said:
if i lose my warantty, how to downgrade to jelly bean, is there any way?
all the best
Click to expand...
Click to collapse
Go to s-off.
Flash firmware for JB ( hboot, etc )
https://www.dropbox.com/s/4fgu7hs7chvt88g/firmware.zip?dl=0 ( rename to 0P4EIMG.zip and copy on sdcard, then run bootloader. This downgrade you hboot etc. )
flash recovery for jelly bean,
https://www.dropbox.com/s/a9ojea649b8qdn9/recovery%20modry.img?dl=0
flash stock rom for zara UL ( mount system and delete with file manager in recovery file /system/bin/hcheck )
https://www.dropbox.com/s/205a9uuolilh6ot/stock_odex_Zara_ul_JB422_SENSE50_1.10.401.8.zip?dl=0
remove tampered text ( skip point 9. Lock bootloader fastboot oem lock )
http://forum.xda-developers.com/showpost.php?p=47576052&postcount=7
lock bootloader
http://forum.xda-developers.com/showthread.php?t=2475914
and remove s-off with command fastboot oem writesecureflag 3
And warranty continues
Tested and working
We can downgrade to jb from kk?
Child's Play said:
We can downgrade to jb from kk?
Click to expand...
Click to collapse
On Zara UL without problem. Locked bootloader, remove tampered text, s-on, stock rom, kernel and recovery.
What about zara-cl?
Child's Play said:
What about zara-cl?
Click to expand...
Click to collapse
I think the process will be the same.
Good to know. Didnt know we could downgrade to jb but only knew i could downgrade hboot
Child's play, do you mind testing on the CL. I would but my computer is out of commission as of now. Getting together with my Tech instructor to see if we can fix it. Until then, I probably won't be able to help much dev testing. Aside from suggestions and what not.
Sent from my HTC0P4E1 using XDA Free mobile app
I've downgraded my zara_ul just by flashing firewater hboot before running the ruu. All while s-off and bootloader unlocked. It'll bootloop once downgraded to jb due to it's hcheck not liking s-off and the unlocked bootloader at the same time but that's besides the point.
That's great. Basically just lock boot loader and you should be fine. We need someone to test on the CL now. Again, I apologize for my inability.
Sent from my HTC0P4E1 using XDA Free mobile app
Im still on jb
I'm sorry to break in in this conversation, but I have a problem. I followed the guide on page 1. Flashed the firmware.zip, flashed twrp recovery 2.6 and successfully installed the stock.zip from page 1(according to twrp). But when I want to reboot the screen hangs at the htc logo. Anyone know what I did wrong? I checked hboot and it said 2.20.
Thanks for any help.
Smellie2 said:
I'm sorry to break in in this conversation, but I have a problem. I followed the guide on page 1. Flashed the firmware.zip, flashed twrp recovery 2.6 and successfully installed the stock.zip from page 1(according to twrp). But when I want to reboot the screen hangs at the htc logo. Anyone know what I did wrong? I checked hboot and it said 2.20.
Thanks for any help.
Click to expand...
Click to collapse
R u s-off?
Hi, i need help, i had my htc one x+ stuck where it would boot up, but was pretty much paralyzed, it couldnt access the sd card, wifi, buetooth sharing didnt work etc, so i had the bright idea at 3 am to
WIPE THE SYSTEM PARTITION, so im stuck with no os installed, but thats not the worst part,
adb sideload gets a constant "error device not found)
same with adb push
i got sideload working once but the idiot that i am cancelled it because i didnt flash the boot image
and YES i have installed the CWM universal drivers.
please help me.
INFORMATION;
**unlocked**
CID HTC__001
enrc2b_u pvt ship s-on irl
hboot-1.35.0000
CPLD-none
MICROP-none
RADIO-3.1204.168.32
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: off
i have cwm touch recovery, sideload only worked once with twrp.
You can flash the boot.img before or after flashing a new rom, it doesn't matter! So try it again
leefear said:
You can flash the boot.img before or after flashing a new rom, it doesn't matter! So try it again
Click to expand...
Click to collapse
Damn it! i should've left it! thank you though, now i know jic it works randomly, but imma keep trying:good:
i360droid said:
Damn it! i should've left it! thank you though, now i know jic it works randomly, but imma keep trying:good:
Click to expand...
Click to collapse
Don't worry about it, these things happen! also run fastboot erase cache after doing in the boot.img, that can help solve issues with boot loops and stuff!
leefear said:
Don't worry about it, these things happen! also run fastboot erase cache after doing in the boot.img, that can help solve issues with boot loops and stuff!
Click to expand...
Click to collapse
i get an error could not erase so i cant
leefear said:
don't worry about it, these things happen! Also run fastboot erase cache after doing in the boot.img, that can help solve issues with boot loops and stuff!
Click to expand...
Click to collapse
update! Adb push worked for the gapps and rom! Installing now!
twrp failed, cwm might have worked!
booting into cm , but bootlooping, so im installing a snapshot of cm11, i was using a nightly
i360droid said:
booting into cm , but bootlooping, so im installing a snapshot of cm11, i was using a nightly
Click to expand...
Click to collapse
good luck, hope all is going well :good:
i360droid said:
booting into cm , but bootlooping, so im installing a snapshot of cm11, i was using a nightly
Click to expand...
Click to collapse
you need to flash the boot.img
Lloir said:
you need to flash the boot.img
Click to expand...
Click to collapse
i solved it, it was my hboot to low. i flashed android revolution, and im a fan llior!
i360droid said:
i solved it, it was my hboot to low. i flashed android revolution, and im a fan llior!
Click to expand...
Click to collapse
There's no HBOOT requirement for the enrc2b (international x+) It's just you HAVE TO flash the boot.img (kernel) manually on the X+ due to no way to have S-OFF
Lloir said:
There's no HBOOT requirement for the enrc2b (international x+) It's just you HAVE TO flash the boot.img (kernel) manually on the X+ due to no way to have S-OFF
Click to expand...
Click to collapse
I did, i did fastboot flash boot boot.img and fastboot boot boot.img, neither worked :/
i360droid said:
I did, i did fastboot flash boot boot.img and fastboot boot boot.img, neither worked :/
Click to expand...
Click to collapse
did you full wipe? wipe system wipe data or perform factory reset. THEN flashed the new rom?
Lloir said:
did you full wipe? wipe system wipe data or perform factory reset. THEN flashed the new rom?
Click to expand...
Click to collapse
yeah, cm kept bootlooping but android revolution worked like a charm first time so...
i360droid said:
yeah, cm kept bootlooping but android revolution worked like a charm first time so...
Click to expand...
Click to collapse
So it's something you've done wrong...I know CM works properly, flashed it on my X+ not 5mins ago
Sent from my Find 5 using Tapatalk
Lloir said:
So it's something you've done wrong...I know CM works properly, flashed it on my X+ not 5mins ago
Sent from my Find 5 using Tapatalk
Click to expand...
Click to collapse
no 1; how long did it take to boot,
no 2; what hboot are ya?
no 3; s-on or off
no 4; superCID?
no 5; what cm build?
i360droid said:
no 1; how long did it take to boot,
no 2; what hboot are ya?
no 3; s-on or off
no 4; superCID?
no 5; what cm build?
Click to expand...
Click to collapse
Takes around 5minutes
1.72
There is no real s-off
This doesn't make a difference
Any from the past months
Sent from my Find 5 using Tapatalk
do a factory reset in recovery or bootloader after flashing rom and kernel. This helped me to boot omni
Did that many times, I'm just running android revolution now
Sent from my HTC One X+ using XDA Free mobile app
Ok so I messed up trying to root my phone for the first time. I skipped the whole S-Off step and now my favorite phone is just this brick.
So my situation is I was running a GPE edition no problems but when I tried to flash stock recovery so it would do an OTA update everything went bad.
My bootloader turned black and my bootup screen has this lock icon at the bottom now.
I can't flash any ROMs on my phone and nothing seems to work. I just need to get any sense based ROM to work on my phone so I can get it working.
I will probably S-OFF next chance i get though.
HTC BOOTLOADER SCREEN
***TAMPERED***
***UNLOCKED***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1,16,21331931
OpenDSP~V38.2.2-00542-M8974.0311
OS-
eMMC-BOOT 2048MB
JUN 16 2014,18:47:55.0
RECOVERY=TWRP V2.8.1.0
fombat said:
Ok so I messed up trying to root my phone for the first time. I skipped the whole S-Off step and now my favorite phone is just this brick.
So my situation is I was running a GPE edition no problems but when I tried to flash stock recovery so it would do an OTA update everything went bad.
My bootloader turned black and my bootup screen has this lock icon at the bottom now.
I can't flash any ROMs on my phone and nothing seems to work. I just need to get any sense based ROM to work on my phone so I can get it working.
I will probably S-OFF next chance i get though.
HTC BOOTLOADER SCREEN
***TAMPERED***
***UNLOCKED***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1,16,21331931
OpenDSP~V38.2.2-00542-M8974.0311
OS-
eMMC-BOOT 2048MB
JUN 16 2014,18:47:55.0
RECOVERY=TWRP V2.8.1.0
Click to expand...
Click to collapse
I don't think you absolutely NEED s-off. In fact, if you have s-on then your phone is fine and it protected and most likely not bricked. Can you boot into your twrp recovery?
OP is missing a lot of facts and details (needed to help properly):
fombat said:
So my situation is I was running a GPE edition
Click to expand...
Click to collapse
Was it originally a GPE version, did you convert it by RUU, or just running a GPE ROM?
fombat said:
So my situation is I was running a GPE edition no problems but when I tried to flash stock recovery so it would do an OTA update everything went bad.
Click to expand...
Click to collapse
What did you try to flash?
fombat said:
I can't flash any ROMs on my phone and nothing seems to work.
Click to expand...
Click to collapse
Meaning what? Does it fail to flash in TWRP, any error message, or it flashes but doesn't boot?
What ROMs have you tried? Did you try a GPE or AOSP ROM?
redpoint73 said:
OP is missing a lot of facts and details (needed to help properly):
Was it originally a GPE version, did you convert it by RUU, or just running a GPE ROM?
What did you try to flash?
Meaning what? Does it fail to flash in TWRP, any error message, or it flashes but doesn't boot?
What ROMs have you tried? Did you try a GPE or AOSP ROM?
Click to expand...
Click to collapse
OK I'm sorry this was my first post and I didn't know
It was working with a GPE ROM I didn't flash any RUU or anything like that
Also I have tried a number of different m8 Roms such as skydragon, android revolution, maximus hd and various others all to no avail the only ROM I have gotten to work is Sinless GPE edition but it's a 4.4.2 ROM and also CM 11 but there are no sense features.
Using Sinless and Sunshine I managed to get s-off but none of the roms I want skydragon or android revolution to work.
With skydragon it will flash successfully but not boot up and if it does boot up after I turn it off it won't boot up again. With android revolution I get the error that syslink failed.
fombat said:
Using Sinless and Sunshine I managed to get s-off but none of the roms I want skydragon or android revolution to work.
With skydragon it will flash successfully but not boot up and if it does boot up after I turn it off it won't boot up again. With android revolution I get the error that syslink failed.
Click to expand...
Click to collapse
For the current Skydragon (Sense) and ARHD, you need to update your firmware. This might be your issue right there.
More info here: http://forum.xda-developers.com/showthread.php?t=2696282
Also you mentioned you tried to flash stock recovery, and I asked what you flashed. You didn't answer that (only mentioned the ROMs you tried). What stock recovery did you try to flash?