Related
Hi
I have accidentaly wiped system and sd card in CWM and cant mount via usb. I cannot find a stock HTC One X RUU and I had downloaded o2 RUU (would prefer carrier branded as want to return!!! although doesn't matter) but that was corrupted and downloaded off a chiness site that has stopped hosting it!
Please help me!
Doesnt matter if all you can find is a recovery that you can mount USB!! That would be great!!
Thank you very much guys!!!!!!!!!!!!!!!!!!!!!!!!!!!
-----------------------------------------------------------------------------------------------------------------------------------------------------
Thank you very much for all of your help! I have solved my issue.
I needed to download the stock o2 uk RUU and relock the bootloader and run the program in fast boot. I have just made my nandroid backup and planning to upload it so anyone else can use it! (it wont have my details on, just as if the os has been installed from scratch)
Steven
Please read before posting/flashing/wiping.
What is the CID of your device. You can only flash a stock RUU with matching CID.
So you need to download the correct RUU for your device.
All stock RUUs available are here
.
Keep thread on topic please
How do I find my CID?
stevepork said:
Hi
I have accidentaly wiped system and sd card in CWM and cant mount via usb. I cannot find a stock HTC One X RUU and I had downloaded o2 RUU (would prefer carrier branded as want to return!!! although doesn't matter) but that was corrupted and downloaded off a chiness site that has stopped hosting it!
Please help me!
Doesnt matter if all you can find is a recovery that you can mount USB!! That would be great!!
Thank you very much guys!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
If you would have spent 10 seconds looking in the Dev thread you would have found a list of all the available RUU's to download.
(http://forum.xda-developers.com/showthread.php?t=1543604)
Download your required RUU, boot into Fastboot-USB and run.
Next time be more careful and fully understand what you are doing before doing it otherwise you will end up with a £600 paperweight.
dr9722 said:
If you would have spent 10 seconds looking in the Dev thread you would have found a list of all the available RUU's to download.
(http://forum.xda-developers.com/showthread.php?t=1543604)
Download your required RUU, boot into Fastboot-USB and run.
Next time be more careful and fully understand what you are doing before doing it otherwise you will end up with a £600 paperweight.
Click to expand...
Click to collapse
That is why I started this thread!!! I don't know which is the correct one!!! I started on o2 uk rom and then flashed android revolution!!!
You've just answered your own question - look for the RUU with o2 UK in the name...
stevepork said:
That is why I started this thread!!! I don't know which is the correct one!!! I started on o2 uk rom and then flashed android revolution!!!
Click to expand...
Click to collapse
Flash the one that says o2 UK then?
Though I also wonder. How do you match CID to the firmware package? When I try to get my CID in fastboot or w/e, it says no CID like i've read around here. Any thoughts?
EddyOS said:
You've just answered your own question - look for the RUU with o2 UK in the name...
Click to expand...
Click to collapse
i unlocked the bootloader so if the op did the same their CID will be "none" and therefore the RUU wont flash.
treebill said:
i unlocked the bootloader so if the op did the same their CID will be "none" and therefore the RUU wont flash.
Click to expand...
Click to collapse
Ahh, that is what I did. Does anyone know how to get around this or relock it. I understood that when you relock it, the CID doesnt change
stevepork said:
Ahh, that is what I did. Does anyone know how to get around this or relock it. I understood that when you relock it, the CID doesnt change
Click to expand...
Click to collapse
You can't get around it nor you can change the CID unless we get S-OFF.
shadowboy23 said:
You can't get around it nor you can change the CID unless we get S-OFF.
Click to expand...
Click to collapse
Okay, I guess i will have to wait until the clockwork recovery gets USB mount!
Sorry but if you just want to return to stock you can do
1. Restore you nandroid backup, flash stock recovery and then relock the bootloader.
OR
2. You can flash stock recovery, relock bootloader and then run the RUU that corresponds to your CID/region.
I am probably answering my own question my CID is H3G_001. There doesnt appear to a 3 mobile ruu at all. Any help here? Fortunately its not urgent but may be handy if/when they release the upgrade
oisindubh said:
I am probably answering my own question my CID is H3G_001. There doesnt appear to a 3 mobile ruu at all. Any help here? Fortunately its not urgent but may be handy if/when they release the upgrade
Click to expand...
Click to collapse
Is your ROM the O2 UK?
Ooops sorry about that.
shadowboy23 said:
Sorry but if you just want to return to stock you can do
1. Restore you nandroid backup, flash stock recovery and then relock the bootloader.
OR
2. You can flash stock recovery, relock bootloader and then run the RUU that corresponds to your CID/region.
Click to expand...
Click to collapse
Thank you, very much. That was all I needed. Why does everyone have to bee rude? Be kine to a newbie!! I have only had an iPhone and a Dell Streak before this device!
You have to relock the bootloader to flash the RUU
Sent from my HTC Sensation Z710e using xda premium
how are you guys checking CID?
Using terminal emulator? do you need root?
I tried ADB shell command since the fastboot command doesn't work, and I get error:device not detected
pewpewbangbang said:
how are you guys checking CID?
Using terminal emulator? do you need root?
I tried ADB shell command since the fastboot command doesn't work, and I get error:device not detected
Click to expand...
Click to collapse
CID getter from the market.
I dont know, sorry. I do know though that mine came originally with 02 uk rom and that CID will only work with the one rom that came originally with your phone. It may be different for unlocked devices.
Thank you very much for everyone's help
Steven
So, I'm running Android Revolution HD 6.0 and I want to get back to stock...
My phone came with an Asian Rom of some sort and I have a Nandroid Backup.
I've tried to simply flash a Ruu "Europe_1.29.401.11" but it force close before any process start.
Do I have to get back to that stock, then relock the bootloader to do so???
Can I re-Unlock the bootloader if I need sometime??
It's my first HTC, I'm ok about using odin and rsd lite but never flashed any Ruu, so in HTC matters I'm pretty noob.
Thanks.
lucasmine said:
So, I'm running Android Revolution HD 6.0 and I want to get back to stock...
My phone came with an Asian Rom of some sort and I have a Nandroid Backup.
I've tried to simply flash a Ruu "Europe_1.29.401.11" but it force close before any process start.
Do I have to get back to that stock, then relock the bootloader to do so???
Can I re-Unlock the bootloader if I need sometime??
It's my first HTC, I'm ok about using odin and rsd lite but never flashed any Ruu, so in HTC matters I'm pretty noob.
Thanks.
Click to expand...
Click to collapse
You have to re-lock bootloader to flash official RUUs, and you can unlock it everytime you want using the unlock.bin you get from HTCdev (on your mail).
But you have to be sure you are using the right RUU
Read the threads relating to ruu carefully. Pretty important.
One thing. You can't use any ruu. Your phone did have a Asian rom initially and so you need the ruu corresponding to that area. And if phone was branded, you need the ruu specific to that brand.
So like if you your phone was from Hong Kong region, you need Hong Kong specific and carrier specifi(if your hox was branded ) ruu.
One more thing, u can only use the ruu of your current os version.
So if you're on 1.29.11, you can't use ruu for 1.29.7
See stickies for in android development section for ruu.
Although I think re locking bootloader should be enough and you should be good to use ruu, do check it.
Not sure if it would require flashing stock rom or stock recovery.
Last thing... Why use ruu? It's probably the last thing you should do unless it's a try to reclaim warranty.
I just want to get my phone to a stock rom, that was why...
but I guess I'll just stick to custom roms, since the Ruu stuf is actually pretty scarring... I tought it was simple to do, since fhasing via odin was always fast and safe...
But that's ok!
Thanks!!!
So, that was my shipped Ruu...
Can I flash an European over it??
PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.4_Radio_1.1204
lucasmine said:
I just want to get my phone to a stock rom, that was why...
but I guess I'll just stick to custom roms, since the Ruu stuf is actually pretty scarring... I tought it was simple to do, since fhasing via odin was always fast and safe...
But that's ok!
Thanks!!!
Click to expand...
Click to collapse
It's very simple really.
1. Find the correct RUU
2. Flash stock recovery(not 100% sure if needed, I did it though)
3. Relock bootloader
4. Run RUU while still in fastboot.
Sent from my HTC One X using xda premium
lucasmine said:
So, that was my shipped Ruu...
Can I flash an European over it??
PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.4_Radio_1.1204
Click to expand...
Click to collapse
No. You've already had it explains to you once lol. Ruu must match hardware. Read the threads
Sent from my HTC One X using Tapatalk 2
lucasmine said:
So, that was my shipped Ruu...
Can I flash an European over it??
PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.4_Radio_1.1204
Click to expand...
Click to collapse
You can only flash the one that matches your region ... to find that out, you first have to find out your CID (something like HTC_001 or O2_002) out with THIS tool from the play store...and in the bootloader you will find the HBOOT version (0.94, 0.96 ...) ... post both here and ill let you know which RUU you need
lucasmine said:
So, that was my shipped Ruu...
Can I flash an European over it??
PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.4_Radio_1.1204
Click to expand...
Click to collapse
You're likely going to need RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed which supports CID HTC__044.
afaik there is no 1.29 RUU for that region yet
OK!
Thanks..
as I said in the first post, I'm pretty noob in HTC...
just another question, can someone clarify what the numbers in the name of the RUU files means?
lucasmine said:
OK!
Thanks..
as I said in the first post, I'm pretty noob in HTC...
just another question, can someone clarify what the numbers in the name of the RUU files means?
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_........................_X.XX.707.XX_Rad io_B.BBBB.BBB.BB_release_...........
X= software version
Y= region and/or branding
B= radio version
muamers said:
RUU_ENDEAVOR_U_ICS_........................_X.XX.707.XX_Rad io_B.BBBB.BBB.BB_release_...........
X= software version
Y= region and/or branding
B= radio version
Click to expand...
Click to collapse
Hmm... Mate all I see is Ys. I can't see any Xs or Bs.
Care to correct?
Electrostatic King said:
Hmm... Mate all I see is Ys. I can't see any Xs or Bs.
Care to correct?
Click to expand...
Click to collapse
Hahaha sorry, it was late The 777 above is the region and/or branding, here again the right way:
RUU_ENDEAVOR_U_ICS_........................_X.XX.YYY.XX_Rad io_B.BBBB.BBB.BB_release_...........
X= software version
Y= region and/or branding
B= radio version
edit ... If you still dont see, here:
The first 8 numbers are for software version and region/branding (region and branding are the numbers between the 2nd and 3rd dot, the other numbers are the software version) and the 2nd 10 numbers are the radio version
muamers said:
You can only flash the one that matches your region ... to find that out, you first have to find out your CID (something like HTC_001 or O2_002) out with THIS tool from the play store...and in the bootloader you will find the HBOOT version (0.94, 0.96 ...) ... post both here and ill let you know which RUU you need
Click to expand...
Click to collapse
How do I find the CID? I have rooted my phone by htcdev and I have not experienced the basic way to find the CID of my phone.
ri123 said:
How do I find the CID? I have rooted my phone by htcdev and I have not experienced the basic way to find the CID of my phone.
Click to expand...
Click to collapse
Sorry I misread your post with a link in it:thumbup:
Sent from my HTC Explorer A310e using XDA
I have software number 1.29.401.11, and hboot 1.12.0000
Please help me. What ruu i must to use.
Georgegalanos said:
I have software number 1.29.401.11, and hboot 1.12.0000
Please help me. What ruu i must to use.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30222514&postcount=1677
HI, my Cid its HTC__044 wwe sea asia.. ive downloades the endeavor ruu both oh them, and also the wwe asia, and in all the cases cames an error in the updated, diferent vendor or wathever...
Ive relocked the boot and the original recovery but nothing happs..
soo how could i go back to my stock ROM
HTC ONE X 32
CID HTC__044
THanks
Which specific ones did you try, what specifically was the error and what did you expect to happen?
I think you need the 2.17.707.x RUU, and before running it you need to lock the bootloader with:
fastboot oem lock
BenPope said:
Which specific ones did you try, what specifically was the error and what did you expect to happen?
I think you need the 2.17.707.x RUU, and before running it you need to lock the bootloader with:
fastboot oem lock
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.2_Radio_1.1204.90.13_release_251281_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed
ive tried those 4, with bootloader locked and on original recovery
if you try "fastboot getvar version-main" instead of "fastboot getvar cid" you will be given the number of the ruu you need.
For example, if it is the SEA_WWE version the number will be"1.29.728.12", but by the sounds of it, it isn't.
Let us know what result you get for it.
You need this file... "RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed"
Mine is the same _044 and it works.
Not neccesarily... I have CID _044 but need this RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
It's important to run the "fastboot getvar version-main" command.
peedub said:
Not neccesarily... I have CID _044 but need this RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
It's important to run the "fastboot getvar version-main" command.
Click to expand...
Click to collapse
Also, at least I think, is important - go in fastboot menu with your phone, then connect via usb and then start ruu.
I had same as yours CID - 044 and "Asia_WWE_2.17.707.3"worked perfectly.
Hope this helps.
Regards.
lets see if it works and soon i will post some news
u can run any ruu with 707 cod in that.
707 for htc__044 cid.its for asia sea wwe version.
becareful your phone has uper than 30% battry charge,beacus when you relock your hboot,its erase all recovery and you cant charge your device.so just you can run ruu,if you havent 30% charge it give an eror for battry charge and not install ruu.
Sent from my HTC One X using Tapatalk 2
shadow fiend said:
u can run any ruu with 707 cod in that.
Click to expand...
Click to collapse
I don't wish to be rude, but if you don't know what you're talking about, it's best not to add to the confusion.
In order to flash an RUU, you need to flash the hboot in the RUU, and the hboot cannot be downgraded. The hboot version is almost always increased for a new RUU. So, you can only flash the same or newer RUU.
I gave the solution in the post immediately following the original question.
mmm its not working, can get the stock ruu back on..
same error.. and in soma exe packages i cant even run it getting some error opening it.
tried in different pcs.. same deal
jachig said:
mmm its not working, can get the stock ruu back on..
same error.. and in soma exe packages i cant even run it getting some error opening it.
tried in different pcs.. same deal
Click to expand...
Click to collapse
If it's not working, then you'll have to fix it.
Due to some error, I say do it differently.
You know, in my first response to you I asked you to be more specific, you don't learn fast, we're not mind readers.
What is "it" that's not working? Flashing a specific RUU? Which one? Where you get it?
What error are you getting?
ERROR 155
Different Vendor
ERROR [280]
ERROR [294]
those errors, on
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.2_Radio_1.1204.90.13_release_251281_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed
WTF man?
Flash the 2.17.707 RUU like you've been told and tell is what happens.
Haha yes, this is getting a little frustrating.
You still haven't told us what result you get when you run this command: "fastboot getvar version-main"
fastbook getvar version-main gave me a: 2.17.707.3
so what do i have to do now?
well the error this time says... its in spanish but i will try to translated right
error 155: update error
the utility update of the rom could not update ur android phone
please obtain the correct rom and try it again.
jachig said:
well the error this time says... its in spanish but i will try to translated right
error 155: update error
the utility update of the rom could not update ur android phone
please obtain the correct rom and try it again.
Click to expand...
Click to collapse
fastboot oem lock
And run the RUU again.
This will delete all you data, so take a backup if you want.
Flash the 2.17.707.3 RUU and you'll be good to go
thats the one ive just used ¬¬
so the currently available JB test-roms only run on certain CID's. how come ICS-custom-roms don't give a **** about the CID?
in the future, for JB-custom-roms based on the OTA: will the devs have to create many files, one for each CID? or will one file rule them all, like before?
BigFatTony said:
so the currently available JB test-roms only run on certain CID's. how come ICS-custom-roms don't give a **** about the CID?
in the future, for JB-custom-roms based on the OTA: will the devs have to create many files, one for each CID? or will one file rule them all, like before?
Click to expand...
Click to collapse
the CID is related to the firmware and not to roms! you need a certain firmware to boot a rom, you need a certain CID to install a firmware... Every htc one x in here came out with stock ICS firmware on... that's it
So as soon as a RUU is available for our individual phone, our firmware will be updated and then any jellybean rom can be installed?
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
On a second point, why do carriers and HTC bother keeping s-on if it is separate to carrier locking? If we stay on the same carrier why do they care what software we are running?
thanks
Thank you very much, @matt95. So the CID is related to the firmware. Does firmware equal hboot?
if i can update my firmware to the soon-to-be-aired version, i can flash any JB rom i want?
@maniacaus: the way they install JB now, on the CID-legit versions, goes like this:
update hboot to 1.28
unlock the device again
flash recovery again
flash boot.img
flash rom
http://forum.xda-developers.com/showpost.php?p=32855238&postcount=29798
the problem seems to be that hboot can only be updated for the HTC*****-CID's. so we have to wait until HTC releases the OTA-update for our CID.
2nd point: they're probably just control freaks. if we void our warranty anyway by unlocking the phone, why shouldn't we be able to modify everything?!? i can't come up with any good reason for not letting us have S-OFF.
BigFatTony said:
Thank you very much, @matt95. So the CID is related to the firmware. Does firmware equal hboot?
if i can update my firmware to the soon-to-be-aired version, i can flash any JB rom i want?
@maniacaus: the way they install JB now, on the CID-legit versions, goes like this:
update hboot to 1.28
unlock the device again
flash recovery again
flash boot.img
flash rom
http://forum.xda-developers.com/showpost.php?p=32855238&postcount=29798
the problem seems to be that hboot can only be updated for the HTC*****-CID's. so we have to wait until HTC releases the OTA-update for our CID.
2nd point: they're probably just control freaks. if we void our warranty anyway by unlocking the phone, why shouldn't we be able to modify everything?!? i can't come up with any good reason for not letting us have S-OFF.
Click to expand...
Click to collapse
1-firmware is related also to HBOOT yes, if you install a certain firmware you can run every JB rom based on it, so not every JB rom that will come out (eventually)...
2- well for examples, if we have S-OFF then we could also revert everything back without leaving any sign of unlocking and things like that... so if someone that has unlocked the bootloader and breaks his phone then his warranty is voided, but if that person has the S-OFF he could revert everything to stock and so it seems like he doesn't even voided his warranty that's a single point... there are many others i bet...
thanks a lot!
1 - so how will it work? how will we update the firmware/hboot?
will there be a firmware.zip for every CID?
##EDIT: ah, that's probably why this thread exists: http://forum.xda-developers.com/showthread.php?t=1957376 *feels smart*
(boot.img will still be universal since it contains only the linux kernel, right?)
2 - isn't that why they have this registration process that sends identification codes to HTC? couldn't they just make this ID-sequence unchangeable instead of entire partitions?!?
BigFatTony said:
thanks a lot!
1 - so how will it work? how will we update the firmware/hboot?
will there be a firmware.zip for every CID?
##EDIT: ah, that's probably why this thread exists: http://forum.xda-developers.com/showthread.php?t=1957376 *feels smart*
(boot.img will still be universal since it contains only the linux kernel, right?)
2 - isn't that why they have this registration process that sends identification codes to HTC? couldn't they just make this ID-sequence unchangeable instead of entire partitions?!?
Click to expand...
Click to collapse
boot.img is the same for everyone
2- i really don't know, only HTC knows its business
Sorry guys, I know it's kinda off-topic, but I have a quick question: What does it mean if my HOX doesn't have a CID? It's not that I don't know how to find it, CID Getter as well as "fastboot getvar cid" return just nothing.
Monsterkater said:
Sorry guys, I know it's kinda off-topic, but I have a quick question: What does it mean if my HOX doesn't have a CID? It's not that I don't know how to find it, CID Getter as well as "fastboot getvar cid" return just nothing.
Click to expand...
Click to collapse
it is impossible that your phone has not a CID, you probably didn't installed HTC Drivers
Monsterkater said:
Sorry guys, I know it's kinda off-topic, but I have a quick question: What does it mean if my HOX doesn't have a CID? It's not that I don't know how to find it, CID Getter as well as "fastboot getvar cid" return just nothing.
Click to expand...
Click to collapse
Try
fastboot oem readcid
BenPope said:
Try
fastboot oem readcid
Click to expand...
Click to collapse
Ah, thank you, it's VODAP102. Do you have any idea why CID Getter didn't find it?
Dear friends my phone has following informations from download mode .
cid is matching with US UNLOCKED
mid is matching with TW UNLOCKED
os is 3.16.401.2 afaik belongs to HTC__034 but leedroid rom has been installed.
Im having some troubles with rom and i want to back stock.
In this case which ruu or exe i must install?
Im S-OFF i tried to convert supercid but i got some errors in fastboot command screen.
I will be extreamly appriciated for your helps my friends.
alicine said:
Dear friends my phone has following informations from download mode .
cid is matching with US UNLOCKED
mid is matching with TW UNLOCKED
os is 3.16.401.2 afaik belongs to HTC__034 but leedroid rom has been installed.
Im having some troubles with rom and i want to back stock.
In this case which ruu or exe i must install?
Im S-OFF i tried to convert supercid but i got some errors in fastboot command screen.
I will be extreamly appriciated for your helps my friends.
Click to expand...
Click to collapse
What was error with trying to supercid?
Here's a nice tutorial
https://forum.xda-developers.com/htc-10/how-to/guide-supercid-htc-10-t3374484
You can change mid too so not sure what exactly device it is, but I'm guessing us locked, based on your firmware of 3.16.401.2
I think that is the newest firmware.
I would go ahead and flash that RUU.
https://androidfilehost.com/?fid=673956719939830809
https://forum.xda-developers.com/htc-10/help/waiting-ruu-oreo-europe-t3769317/page5
andybones said:
What was error with trying to supercid?
Here's a nice tutorial
https://forum.xda-developers.com/htc-10/how-to/guide-supercid-htc-10-t3374484
You can change mid too so not sure what exactly device it is, but I'm guessing us locked, based on your firmware of 3.16.401.2
I think that is the newest firmware.
I would go ahead and flash that RUU.
https://androidfilehost.com/?fid=673956719939830809
https://forum.xda-developers.com/htc-10/help/waiting-ruu-oreo-europe-t3769317/page5
Click to expand...
Click to collapse
Thank you very much for your quick answer .
Fastboot was giving me an error "Waiting for device" for all other commands except fastboot devices
i tried in my dekstop computer (win10) i succeed to change MID and CID . and after i flashed the file that you aimed.
This time im having [email protected] and [email protected] i believe this is a hardware failure.
Because non of sensors are working. :crying::crying::crying:
alicine said:
Thank you very much for your quick answer .
Fastboot was giving me an error "Waiting for device" for all other commands except fastboot devices
i tried in my dekstop computer (win10) i succeed to change MID and CID . and after i flashed the file that you aimed.
This time im having [email protected] and [email protected] i believe this is a hardware failure.
Because non of sensors are working. :crying::crying::crying:
Click to expand...
Click to collapse
Were sensors working before?
What did you change cid/mid to?
I would do supercid and change mid to match the RUU which is us locked, 2PS620000 iirc
Hopefully that will fix things up.
I also suggest flashing RUU using sdcard method, but fastboot works fine just make sure to use htc_fastboot not fastboot, for ruu
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Do a quick search though to confirm that's the mid u want that matches that Ruu.
Sorry I should have mentioned earlier.
When I take the phone first, was having sensor issues. I was thinking it's because of leedroid rom and sensors were driving crazy. Screen was closing itself, ice screen was appearing and back and other button blinking itself home button was not working etc. I barely acces to main screen
*#*#3424#*#* I couldn't diagnose hw so somehow I installed an app to see how sensors were behaving.
I couldn't read values so I thought that it's because of rom.
That's why as you said I change cid to supercid mid to 2PS620000.
After that I used sd card method from download mode and I installed the rom.
After the process I recieved the errors that I mentioned above
As final conclusion when mobile phone has leedroid rom, hw somehow damaged and was working strange because sensors.hub was there.
With clean installation sensor.hub didn't installed and hw is not working. And not behave strange.
It's my theory. I'm searching schematics for sensors to define where is exactly failure is.