OK so I have bricked my HOX again & I am trying to install the latest stock ruu but am getting An error 155 - Why & how do I fix this?
Ta
HERE
If you can find your boot.img on your computer i think i remember flashing that last time i bricked mine.(thanks to bumble-bee)
Some devs can help with recovering that img via your bootloader and adb if i am not mistaken it should be the one before you flashed to a brick.
Sent from my HTC One X using XDA
walaway said:
If you can find your boot.img on your computer i think i remember flashing that last time i bricked mine.(thanks to bumble-bee)
Some devs can help with recovering that img via your bootloader and adb if i am not mistaken it should be the one before you flashed to a brick.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
I get a failed remote not allowed when i try to flash a stock boot img
WTF, i already google it and you still dont find it ?
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator"."
(1) You dont have enought battery
(2) You dont use the right RUU that matches your CID
(3) You downloaded a corrupt file (redownload it)
(4) You dont run the file as you phone is in recovery (in fastboot mode)
(5) You didnt relock your bootloader
edit: IT IS NOT BRICKED
Your 2 best solutions i can think and suggest because i am not a dev:
1. Get support from your target ROM, if they have irc that would be sweet.
2. Google search to unbrick is all i can say otherwise.
You could look up the "one x all in one root kit", it is somewhere here in the forums and i think it might help.
Sent from my HTC One X using XDA
muamers said:
WTF, i already google it and you still dont find it ?
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator"."
(1) You dont have enought battery
(2) You dont use the right RUU that matches your CID
(3) You downloaded a corrupt file (redownload it)
(4) You dont run the file as you phone is in recovery (in fastboot mode)
(5) You didnt relock your bootloader
edit: IT IS NOT BRICKED
Click to expand...
Click to collapse
I did follow your link & read.
(1) You dont have enought battery - it keeps rebooting to to bootloader so it lit up all the time even when i shut down
(2) You dont use the right RUU that matches your CID - I was on1.29.401.7 & tried to install tha ruu
(3) You downloaded a corrupt file (redownload it) - I have used it before
(4) You dont run the file as you phone is in recovery (in fastboot mode) - which mode do i run it in as i can only get in to fastboot
(5) You didnt relock your bootloader - YES i have
Thanks - Still Bricked though
@home said:
I did follow your link & read.
(1) You dont have enought battery - it keeps rebooting to to bootloader so it lit up all the time even when i shut down
(2) You dont use the right RUU that matches your CID - I was on1.29.401.7 & tried to install tha ruu
(3) You downloaded a corrupt file (redownload it) - I have used it before
(4) You dont run the file as you phone is in recovery (in fastboot mode) - which mode do i run it in as i can only get in to bootloader
(5) You didnt relock your bootloader - YES i have
Thanks - Still Bricked though
Click to expand...
Click to collapse
If its NOT bricked whats wrong with it then???? & how do i fix?
Ta
All i can think of is fetching that ruu's boot.img while it is running, it should be found on your computer's %temp folder in a zip.
Are you on stock recovery?
Battery could be the problem make sure you let it hang on charging for a while
Sent from my HTC One X using XDA
@home said:
If its NOT bricked whats wrong with it then???? & how do i fix?
Ta
Click to expand...
Click to collapse
Try to unlock your phone again and instal stock recovery from HERE and relock your bootloader again ...
And BTW, did you maybe perform a update on-the-air after you instal 1.29.401.7, whats your HBOOT version ? (in bootloader example: hboot-0.94.000)
Get the 1.29.401.11 RUU and use that
muamers said:
Try to unlock your phone again and instal stock recovery from HERE and relock your bootloader again ...
And BTW, did you maybe perform a update on-the-air after you instal 1.29.401.7, whats your HBOOT version ? (in bootloader example: hboot-0.94.000)
Click to expand...
Click to collapse
H-boot is 0.95
I installed the ruu via pc
I now no longer have enough battery & its not charging cause when i power down the damn thing starts up again whe i plug it in to the mains
@home said:
H-boot is 0.95
I installed the ruu via pc
I now no longer have enough battery & its not charging cause when i power down the damn thing starts up again whe i plug it in to the mains
Click to expand...
Click to collapse
0.95 means most probably you have .11, that means you have to use the above mentioned RUU ... and read THIS to get your battery back into live
muamers said:
0.95 means most probably you have .11, that means you have to use the above mentioned RUU ... and read THIS to get your battery back into live
Click to expand...
Click to collapse
I tried those methods for the battery but it just fires back up as soon as its plugged in
@home said:
I tried those methods for the battery but it just fires back up as soon as its plugged in
Click to expand...
Click to collapse
You need just 20% to be able to flash the latest CWM recovery over fastboot so you can charge your phone ... just dont panic, theres always a way out
muamers said:
You need just 20% to be able to flash the latest CWM recovery over fastboot so you can charge your phone ... just dont panic, theres always a way out
Click to expand...
Click to collapse
Yeah but I have relocked the bootloader
Back up an running now thanks for the help.
Related
Hi guys, I got a HTC DESIRE for my Wife but I tried to root it and somehow its failed:
Its a T-mobile UK locked device
Now I cant see anything on my device its working as I can hear the startup sound and when I try to run the official tmobile uk update it detects it but failed looking for bootloader mode.
Code:
[COLOR="Red"]SOME PROGRESS HERE NOT SURE IF ITS GOOD OR BAD[/COLOR]
[url]http://forum.xda-developers.com/showpost.php?p=7895731&postcount=44[/url]
My wife going to kill me
This is where the instructions I was using goldcard was succesful etc
http://theunlockr.com/2010/06/07/how-to-root-the-htc-desire/
The last stage I reach was n0.7
If anyone can help me I would appreciate it
Firstly, I'd recommend using unrevoked to root the phone. The way you are using is old and complicated.
Secondly, i imagine that your hboot is not 0.8 which means you'll need to downgrade.
It might be http://forum.xda-developers.com/showthread.php?t=750852 that you need to read and follow, although I'm not sure.
It would help if you knew what hboot you were.
iinga said:
Firstly, I'd recommend using unrevoked to root the phone. The way you are using is old and complicated.
Secondly, i imagine that your hboot is not 0.8 which means you'll need to downgrade.
It might be http://forum.xda-developers.com/showthread.php?t=750852 that you need to read and follow, although I'm not sure.
It would help if you knew what hboot you were.
Click to expand...
Click to collapse
hboot was 0.75 tmobile version was 1.15
With goldcard in the device, can you flash http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_127570_signed.exe successfully?
iinga said:
With goldcard in the device, can you flash http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_127570_signed.exe successfully?
Click to expand...
Click to collapse
Device wont go into bootloader mode I'm trying this one now
RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed
as the PB99IMG_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed_txt.zip
1 hour to download
This is crap
The RUU itself can't put into bootloader?
If you want to try unrevoked, this is the post you need:
Q. My screen goes blank when I use custom recovery with unrevoked3.
A. You have an SLCD display and will need to use an updated recovery image until unrevoked3 itself is updated. It is safe to use this updated image on AMOLED screens too. You can download the image here: http://crop.floodbit.org/~defer/recovery-clockwork-2.5.0.1-bravo-slcd.img
http://forum.xda-developers.com/showthread.php?t=749551 - has everything about slcd rtc
The main problem is my screen is black and I cant see anything although windows is still detecting device
Instead of the RUU, try giving unrevoked a whirl with that custom recovery image (make sure phone is unplugged whilst started unrevoked). Also, follow the instructions from unrevoked about installing the htc drivers (unless you have already installed the latest htc drivers).
Battery pull, then turn on whilst holding volume down. Hopefully this will give you bootloader and unrevoked should be able to do its magic (if you select that custom recovery image)
This will give you root.
iinga said:
Instead of the RUU, try giving unrevoked a whirl with that custom recovery image (make sure phone is unplugged whilst started unrevoked). Also, follow the instructions from unrevoked about installing the htc drivers (unless you have already installed the latest htc drivers).
Battery pull, then turn on whilst holding volume down. Hopefully this will give you bootloader and unrevoked should be able to do its magic (if you select that custom recovery image)
This will give you root.
Click to expand...
Click to collapse
ok bro I will try how do I flash the image?
duttythroy said:
ok bro I will try how do I flash the image?
Click to expand...
Click to collapse
http://unrevoked.com
1. Choose desire then download.
2. Follow instructions in hboot driver.html (to make sure your phone is recognised correctly)
3. Run reflash.exe
4. File>Custom Recovery (Ctrl+R)
5. Download and select http://crop.floodbit.org/~defer/recovery-clockwork-2.5.0.1-bravo-slcd.img
6. Plug in desire - hopefully you have USB debugging enabled. If not, I think you can achieve root by loading bootloader yourself (battery pull device and then vol down + power)
iinga said:
http://unrevoked.com
1. Choose desire then download.
2. Follow instructions in hboot driver.html (to make sure your phone is recognised correctly)
3. Run reflash.exe
4. File>Custom Recovery (Ctrl+R)
5. Download and select http://crop.floodbit.org/~defer/recovery-clockwork-2.5.0.1-bravo-slcd.img
6. Plug in desire - hopefully you have USB debugging enabled. If not, I think you can achieve root by loading bootloader yourself (battery pull device and then vol down + power)
Click to expand...
Click to collapse
I will try bro thanks again
duttythroy said:
I will try bro thanks again
Click to expand...
Click to collapse
I done everything but still dont understand what to do with this recovery-clockwork-2.5.0.1-bravo-slcd.img
the drivers were installed correctly and my computer can see my device,
But still no luck I think I'm missing something I cant see anything on my screen, I know the device alive as I can hear the atrt up sound and compuer now detect in device manager
This is what hapens when I try to attempt flashing with official ruu
Ok unplug the desire from the pc then battery pull and then hold volume-down (on left hand side of the phone) and then press power (whilst holding volume-down). Then plug in and run the RUU again.
With that recovery-clockwork-2.5.0.1-bravo-slcd.img, you select it in unrevoked by pressing ctrl + r (on windows) and then just connect your desire.
Do the RUU first
first think u sholud know about rooting is hboot version.. maybe you have hboot 083 version
read here
http://forum.xda-developers.com/showthread.php?t=749551
and here
http://forum.xda-developers.com/showthread.php?t=748498
http://forum.xda-developers.com/showthread.php?t=762638
monyozt said:
first think u sholud know about rooting is hboot version.. maybe you have hboot 083 version
read here
http://forum.xda-developers.com/showthread.php?t=749551
and here
http://forum.xda-developers.com/showthread.php?t=748498
http://forum.xda-developers.com/showthread.php?t=762638
Click to expand...
Click to collapse
Thanks I will try, I think my device was 0.75 software version 1.15 but will try, I'm getting annoyed now
Did u try to flash using xp instead of Vista or seven? Hope it will help, because I've installed a dual boot seven/xp in my laptop to root and flash, as seven recognized my Desire but I couldn't detect the phone with HTC sync or official ruu
Sent from my HTC Desire using XDA App
djigane said:
Did u try to flash using xp instead of Vista or seven? Hope it will help, because I've installed a dual boot seven/xp in my laptop to root and flash, as seven recognized my Desire but I couldn't detect the phone with HTC sync or official ruu
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Its detected and ruu runs and check my current version and shows which version I'm uploading to, the problem is its trying to detect bootloader and thats where its failed
Did you do what i said? battery pull, then voldown + power?
This is the failed flash ruu after trying to find bootloader
I think this is getting hopeless and I want to thank so far all those who are helping me
Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help
Gomezie said:
Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help
Click to expand...
Click to collapse
Please specify which RUU's you have tried
Hey thanks for your prompt reply, It is greatly appreciated.
Here are the RUU's i have tried:
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.26.161.2_Radio_1.1204.90.13_release_251227_signed
Thanks
Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM
EddyOS said:
Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM
Click to expand...
Click to collapse
It was purchased from phones4u online.. the phone came unbranded, and is on a vodafone contract.
I am sorry about the RUU.. I wasnt aware it was something you had to acquire first..
You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!
EddyOS said:
You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!
Click to expand...
Click to collapse
Thanks mate.. just waiting on the download slots and Ill grab it
Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it
EddyOS said:
Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it
Click to expand...
Click to collapse
Spot on mate, I relocked the bootloader and the status reads "*** RELOCKED ***"
The RUU also ran perfectly, thanks for that
Would I just flash a stock recovery to restore the bootloader now? (so that it doesnt say RELOCKED)
I want to ensure that the phone is in the exact shape it needs to be before sending back.
Thanks again
It'll always say relocked - you can't do anything about that...
Ah thats a shame, should be a doorstep swap for a replacement handset anyways so thats probably no issue.
Thanks again mate, you have saved my bacon
-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA
wolfraim said:
-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
OP has already got it done, just asked if you could change the bootloader to say 'LOCKED' as it does out the box as opposed to 'RELOCKED'
RUU
So I have kind of a problem, I wanted to unlock my bootloader, only HTCDEV servers are a couples of days now overloaded.
So I can't get the unlock code bin.
I need to use my phone and it won't start normally because new firmare was flashed in RUU mode with JBWFTOOL.
So I want to flash a stock RUU. Only my main version is 3.14.401.41.
My phone was repaired by HTC and I got it back LOCKED and well.
Can I flash a other version RUU or do I have to wait for HTCDEV becoming normal again.
HOX E11 Europe.
H.BOOT 1.39
3.14.401.41
I am not doomed right?
Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator
Mr Hofs said:
Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator
Click to expand...
Click to collapse
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD
jelmer-p said:
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD
Click to expand...
Click to collapse
Yeah i knew that, im on the same cid
Mr Hofs said:
Yeah i knew that, im on the same cid
Click to expand...
Click to collapse
YEAH it worked thanks!
jelmer-p said:
YEAH it worked thanks!
Click to expand...
Click to collapse
Top ! Have fun :thumbup:
HELPPP!!! no OS and scary msg "this bulid is for development process only..."
Something went wrong which I am not gonna explain too much.
Now My phone doesn't have an OS.
I have RELOCKED Bootloader,
I have NO CWM installed. Cannot access with some line when booting "this bulid is for development process only..."
I don't have any rom in the SDCARD.
I can boot into boot loader, I can see fastboot USB.
is there anyway i can flash new rom?
currently im downloading second RUU cause the first one is wrong, but im afraid of the batt went out and wont ever start again...
I feel for you
Can't advise much I'm afraid, but try this thread - should be something in there that will help.
http://forum.xda-developers.com/showthread.php?t=1609190
Oh, and whatever you are not going to explain too much, don't do it again
Yeah don't leave it on. The RUU will cancel out if you don't have at least 30% battery. The only way to recover is to either send the phone into HTC for repair or disassemble to charge the battery manually (if it drops below 30%)
but why you can't charge it sorry? (sorry i'm a king of noob here )
glukosio said:
but why you can't charge it sorry? (sorry i'm a king of noob here )
Click to expand...
Click to collapse
Oh that's true. If you can get into HBOOT then theoretically it'll charge when off. I was thinking it was totally fubarred.
Option 1:
Just unlock it again and it will boot into system.
Option 2:
If you want to have stock rom then leave it relocked
run RUU.....exe grab rom.zip
go in fastboot usb mode
run fastboot oem rebootRUU wait bit till it connects to your computer then run fastboot flash zip rom.zip.
headache.
just got it working from (http://forum.xda-developers.com/showthread.php?t=1609190) -thanks anyway gonzo99, i also found that link through googling and now im unlocked again. below is the line that helps me.
If you re-locked the bootloader
Unlock with the same Unlock_code.bin file provided by HTC and follow this link: http://www.htcdev.com/bootloader/unl...ctions/page-4/
one question, the internet here is very slow, how do i determine which RUU should i use?
It should be the one matching the version you had on your phone originally, e.g. if you had 1.26.401.1 out the box any RUU with x.xx.401.x is suitable
EddyOS said:
It should be the one matching the version you had on your phone originally, e.g. if you had 1.26.401.1 out the box any RUU with x.xx.401.x is suitable
Click to expand...
Click to collapse
Thanks for your fast response EddyOS, can i just run the RUU without the command line, i mean just go through the installation process?
RUUs are Windows EXE applications, just you just run them in Windows
You need a re-locked bootloader to use them, though, and you need to be connected to the PC in fastboot mode for them to work
EddyOS said:
RUUs are Windows EXE applications, just you just run them in Windows
You need a re-locked bootloader to use them, though, and you need to be connected to the PC in fastboot mode for them to work
Click to expand...
Click to collapse
great will give it a try, im waiting my phone charging now while waiting for the download to finished in about 12 minutes.
Many thanks weather it work or not.
Great my phone is now working again...
thanks a lot to all user and others mention in all of this thread...
two thumbs up
Hi,
I´ve had a problem for about a month now. I always look for the solution before even thinking about creating a new thread, but this time I´m stumped, I really don´t know what to do. I have a HTC One M8 Developer Unlocked edition; I bought it off of Amazon. A few months ago I rooted it because I wanted to use Pushbullet. After a few tries I got it working with TWRP.
A few weeks ago I learned that Lollipop was being released and I wanted to upgrade my phone, unfortunately you can´t get it unless the phone is unrooted, so I tried that. I followed theunlockr guide "How to unroot the htc one m8" up to the point of switching S-ON.
After that I tried to upgrade to Lollipop, it didn´t work. The phone would get stuck in the installing screen, and then a red triangle with an exclamation mark would appear. This has happened every single time I tried to install the upgrade.
After that I tried to reset to factory using RUU, but I couldn´t do it. I got the error 150… Now I have a supposedly stock ROM but I can´t install Lollipop… Can you help me? This whole story comes to this.. How can I revert my M8 back to stock so I can get Lollipop?
Right now it has S-ON, if that helps.
Thanks in advance and sorry for my English, it´s not my native language.
1. There is no need to change S-Off to S-On
2. There is no need to unroot when you're not sure how-to
3. When the phone get stuck in the installing screen, and then a red triangle with an exclamation mark appear, press and hold volume up and tap power button once, it will give you the error log then you'll know what are the problems that stopping the update
4. When you use a RUU when S-On, you need to relock bootloader before you run RUU
ckpv5 said:
1. There is no need to change S-Off to S-On
2. There is no need to unroot when you're not sure how-to
3. When the phone get stuck in the installing screen, and then a red triangle with an exclamation mark appear, press and hold volume up and tap power button once, it will give you the error log then you'll know what are the problems that stopping the update
4. When you use a RUU when S-On, you need to relock bootloader before you run RUU
Click to expand...
Click to collapse
Ok thanks, I´ll try that as soon as I get home. What do you think its better, turn S-OFF and then run RUU or relock the bootloader first?
Jsrz said:
Ok thanks, I´ll try that as soon as I get home. What do you think its better, turn S-OFF and then run RUU or relock the bootloader first?
Click to expand...
Click to collapse
When S-Off - just run RUU
When S-On - relock bootloader then run RUU
ckpv5 said:
1. There is no need to change S-Off to S-On
2. There is no need to unroot when you're not sure how-to
3. When the phone get stuck in the installing screen, and then a red triangle with an exclamation mark appear, press and hold volume up and tap power button once, it will give you the error log then you'll know what are the problems that stopping the update
4. When you use a RUU when S-On, you need to relock bootloader before you run RUU
Click to expand...
Click to collapse
Ok I did what you told me. I got this message:
Installing Update package...
L50QCT.01.101.007
htc/brightstarus_wwe/htc_m8: 4.4.4/KTU84P/389838.5:user/release-keys or
htc/brightstarus_wwe/htc_m8: 5.0.1/LRX22C/448934.8:user/release-keys;
this device has htc_europe/htc_m8: 4.4.4/KTU84P/389838.9
As far as I understand I have the EU version (Don´t ask me how...), what can I do now? What would be the next move?
Thanks
htc/brightstarus_wwe/htc_m8: 4.4.4/KTU84P/389838.5:user/release-keys or
htc/brightstarus_wwe/htc_m8: 5.0.1/LRX22C/448934.8:user/release-keys;
this device has htc_europe/htc_m8: 4.4.4/KTU84P/389838.9
That's your problem.
You have a Dev Edition installed but using EU stock recovery.
You need Dev Edition stock recovery.
If you can't find one, copy the OTA zip from internal storage/Download folder to PC. Open the OTA zip with 7-zip, open firmware.zip, extract out recovery.img
This recovery.img is what you need.
Or try this one : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.1540.5_recovery.img/download
Couldn't quote.
ckpv5 said:
htc/brightstarus_wwe/htc_m8: 4.4.4/KTU84P/389838.5:user/release-keys or
htc/brightstarus_wwe/htc_m8: 5.0.1/LRX22C/448934.8:user/release-keys;
this device has htc_europe/htc_m8: 4.4.4/KTU84P/389838.9
That's your problem.
You have a Dev Edition installed but using EU stock recovery.
You need Dev Edition stock recovery.
If you can't find one, copy the OTA zip from internal storage/Download folder to PC. Open the OTA zip with 7-zip, open firmware.zip, extract out recovery.img
This recovery.img is what you need.
Or try this one
Click to expand...
Click to collapse
Hi! Sorry for taking so long, had to work.
I searched for the HTC ONE M8 Developer Edition but could't find it.. So I downloaded the OTA, extracted the recovery.img but I don't know what to do now, I tried to run the Recovery from the bootloader but I still get the red triangle with the exclamation mark.
What can I do now?
Thanks.
Jsrz said:
Hi! Sorry for taking so long, had to work.
I searched for the HTC ONE M8 Developer Edition but could't find it.. So I downloaded the OTA, extracted the recovery.img but I don't know what to do now, I tried to run the Recovery from the bootloader but I still get the red triangle with the exclamation mark.
What can I do now?
Thanks.
Click to expand...
Click to collapse
I guess some of the system files are not pure stock.
The easiest way is run RUU.
1. Download Dev Ed RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
2. RUU will wipe all in internal storage. Make a backup of your files before you run RUU
3. Put your device on bootloader/fastboot mode
4. If your device is S-On
a-relock bootloader - fastboot oem lock
b-run RUU (select run as administrator in your windows explorer context menu)
5. If your device is S-Off - run RUU (select run as administrator in your windows explorer context menu)
ckpv5 said:
I guess some of the system files are not pure stock.
The easiest way is run RUU.
1. Download Dev Ed RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
2. RUU will wipe all in internal storage. Make a backup of your files before you run RUU
3. Put your device on bootloader/fastboot mode
4. If your device is S-On
a-relock bootloader - fastboot oem lock
b-run RUU (select run as administrator in your windows explorer context menu)
5. If your device is S-Off - run RUU (select run as administrator in your windows explorer context menu)
Click to expand...
Click to collapse
It worked, after I ran the RUU it automatically installed Lollipop. I can't thank you enough, really. One last thing before I stop bothering you, for future reference, how can I check the version of my software, how can I know if I have the BrightstarUS, instead of the EU version?
Anyway, the last thing is not that important. I really thank you!
Jsrz said:
It worked, after I ran the RUU it automatically installed Lollipop. I can't thank you enough, really. One last thing before I stop bothering you, for future reference, how can I check the version of my software, how can I know if I have the BrightstarUS, instead of the EU version?
Anyway, the last thing is not that important. I really thank you!
Click to expand...
Click to collapse
Great :good::good:
How to know ? Simple
Check the OS no. written on bootloader or run command fastboot getvar all
You'll see the version-main no.
x.xx.401.x is EU
x.xx.1540.x is Dev Ed (BrightstarUS)
ckpv5 said:
Great :good::good:
How to know ? Simple
Check the OS no. written on bootloader or run command fastboot getvar all
You'll see the version-main no.
x.xx.401.x is EU
x.xx.1540.x is Dev Ed (BrightstarUS)
Click to expand...
Click to collapse
Yup, I got the Dev edition. Thank you for your time and your instructions!.
First of all im trying to find a way to solve this problem without sunshine if possible since its nearly impposible to get it where i live .
So the problem started when i was trying an RUU file that i discovered later is not for my region and was US based and got an error code of 131 which is wrong device ID cause the RUU file doesnt match the device CID.
I have tried the RUU.zip method also but i also got an error then discovered that i cant flash an older firmware on my device "which is running on 7.0 .
So the main problem on my device now is that while im using , it will start random bootloop unless i connect my device .
The sweetspot of it to happen is between 60 and 70% charge and when i boot it up after connecting my charger it goes all the way to between 30 and 45% .
The second problem would be that someyimes after the bootloop and boot the device up the red led for charging and the charging notification get stuck and i have to remove and reconnect the charger to fix it.
And i want to know if this problem will affect my device health in the future .
Thanks in advance .
Update
I have installed accubattery and in the battery health section i found out that it read only 785Mah capacity from 3000 Mah , i heared About battery calibiration but i dont know if it worth to try out and how to di it proberly .
Walid seraj said:
I have installed accubattery and in the battery health section i found out that it read only 785Mah capacity from 3000 Mah , i heared About battery calibiration but i dont know if it worth to try out and how to di it proberly .
Click to expand...
Click to collapse
See THIS post. I don't know if it works with the 10 as well. It's worth a try though.
Why not try to flash it through cmd?
matekaneve said:
See THIS post. I don't know if it works with the 10 as well. It's worth a try though.
Click to expand...
Click to collapse
Is there a way to turn off fastboot on the htc 10 , i have looked for it my self and didnt find any option under settings.
matekaneve said:
See THIS post. I don't know if it works with the 10 as well. It's worth a try though.
Click to expand...
Click to collapse
fdgd1998 said:
Why not try to flash it through cmd?
Click to expand...
Click to collapse
Actually the same error code was appearing as trying to flash it through sd card
Walid seraj said:
First of all im trying to find a way to solve this problem without sunshine if possible since its nearly impposible to get it where i live .
So the problem started when i was trying an RUU file that i discovered later is not for my region and was US based and got an error code of 131 which is wrong device ID cause the RUU file doesnt match the device CID.
I have tried the RUU.zip method also but i also got an error then discovered that i cant flash an older firmware on my device "which is running on 7.0 .
So the main problem on my device now is that while im using , it will start random bootloop unless i connect my device .
The sweetspot of it to happen is between 60 and 70% charge and when i boot it up after connecting my charger it goes all the way to between 30 and 45% .
The second problem would be that someyimes after the bootloop and boot the device up the red led for charging and the charging notification get stuck and i have to remove and reconnect the charger to fix it.
And i want to know if this problem will affect my device health in the future .
Thanks in advance .
Click to expand...
Click to collapse
First of all what's your CID and MID? are you still trying to find the correct RUU?
yldlj said:
First of all what's your CID and MID? are you still trying to find the correct RUU?
Click to expand...
Click to collapse
I know my CID and MID its HTC__j15 but when i tried the ruu method i discovered i cant roll back and there's no update yet as im on 7.0
Walid seraj said:
I know my CID and MID its HTC__j15 but when i tried the ruu method i discovered i cant roll back and there's no update yet as im on 7.0
Click to expand...
Click to collapse
The cid is HTC__J15 and the MID 2PS620000, aren't they?
Walid seraj said:
I know my CID and MID its HTC__j15 but when i tried the ruu method i discovered i cant roll back and there's no update yet as im on 7.0
Click to expand...
Click to collapse
You can flash the latest WWE RUU. Yeah you cant downgrade but you can flash the same.
https://androidfilehost.com/?fid=817550096634797504
Download from the link
Rename the zip to 2PS6IMG. zip and place on ex sd card.
Boot to downloade mode and press up to flash.
Remember everything will get erased.
yldlj said:
You can flash the latest WWE RUU. Yeah you cant downgrade but you can flash the same.
https://androidfilehost.com/?fid=817550096634797504
Download from the link
Rename the zip to 2PS6IMG. zip and place on ex sd card.
Boot to downloade mode and press up to flash.
Remember everything will get erased.
Click to expand...
Click to collapse
I guess i will give this one a try and post an update as if it worked correctly or not , i guess i tried another .zip file as i can remember it has a different size than this one.
Thanks for the reply
You always also flash trough cmd tho.
fdgd1998 said:
You always also flash trough cmd tho.
Click to expand...
Click to collapse
SD card method is easiest way.
yldlj said:
SD card method is easiest way.
Click to expand...
Click to collapse
I personally haven't tested the recovery method, but I think it should be easy.
fdgd1998 said:
I personally haven't tested the recovery method, but I think it should be easy.
Click to expand...
Click to collapse
It's not recovery method. You don't use recovery you use download mode.
yldlj said:
It's not recovery method. You don't use recovery you use download mode.
Click to expand...
Click to collapse
It's obvious I don't use it so much.
Update: so I succeeded in flashing the RUU.zip file through SDcard but when i power on my device it will do the same bootloop, then I tried again but this time I did a full reset plus cleared cache but the same thing happen though I noticed 2 things:
First is while flashing I noticed that the process have bypassed about 3 or 4 lines I didn't catch the names of those lines since it was happening so fast.
Second thing that I can't get my battery to 0% , I have tried slot but it can't seem to happen.
So my battery would go to almost 60 and start boot looping then when I connect the charger it says that it's 4 then I would turn on the device while charger connected and it says 57 .
And it happen the other way around , I charged to 100 % while the device is off and when I turn it on as reaches 96 it start bootlooping and when I connect the charger to power it up the battery shows 56 "as I can remember" .
So I don't know what to do next
yldlj said:
It's not recovery method. You don't use recovery you use download mode.
Click to expand...
Click to collapse
any ideas? , i will try flashing through cmd and see if there's any change.
Walid seraj said:
any ideas? , i will try flashing through cmd and see if there's any change.
Click to expand...
Click to collapse
If after flashing the RUU your device is having the same problems as before it's got to be a hardware issue and not software. Flashing through cmd isn't going to do anything.
yldlj said:
If after flashing the RUU your device is having the same problems as before it's got to be a hardware issue and not software. Flashing through cmd isn't going to do anything.
Click to expand...
Click to collapse
But the problem wasnt there before using the wrong RUU !