Hi all. I am new to the xda developers forums, as well as new to the process of rooting an Android phone and installing a custom ROM. So please forgive me if I am posting in the wrong area, etc. If so, I am happy to take direction and go to the proper areas/forums.
I have a HTC One X from T-Mobile.
I have been following instructions to root the phone, flash a custom recovery, and then install a custom ROM. Unlocking the phone was no problem. Flashing the custom recovery *seemed* to be no problem (the commands ran fine and the phone appeared to write the file), but when I try to boot into recovery mode, I get a warning screen from HTC ("This image is for internal development only, blah, blah, blah), but then I just get a black screen. I can't do anything other than hard reset the phone. Any time I try to boot into recovery, all I ever get is a black screen.
The recovery image that I've been trying to use is recovery-clockwork-touch-6.0.4.8-endeavoru.img.
I'm just wondering if this is a known issue and if you can point me in the right direction. Am I simply using the wrong recovery image? Is there a different recovery image recommended for One-X's from T-Mobile (does the carrier even matter?)?
Sorry for the noob question. Any guidance you can provide would be sincerely appreciated.
TIA
Hawkser said:
Hi all. I am new to the xda developers forums, as well as new to the process of rooting an Android phone and installing a custom ROM. So please forgive me if I am posting in the wrong area, etc. If so, I am happy to take direction and go to the proper areas/forums.
I have a HTC One X from T-Mobile.
I have been following instructions to root the phone, flash a custom recovery, and then install a custom ROM. Unlocking the phone was no problem. Flashing the custom recovery *seemed* to be no problem (the commands ran fine and the phone appeared to write the file), but when I try to boot into recovery mode, I get a warning screen from HTC ("This image is for internal development only, blah, blah, blah), but then I just get a black screen. I can't do anything other than hard reset the phone. Any time I try to boot into recovery, all I ever get is a black screen.
The recovery image that I've been trying to use is recovery-clockwork-touch-6.0.4.8-endeavoru.img.
I'm just wondering if this is a known issue and if you can point me in the right direction. Am I simply using the wrong recovery image? Is there a different recovery image recommended for One-X's from T-Mobile (does the carrier even matter?)?
Sorry for the noob question. Any guidance you can provide would be sincerely appreciated.
TIA
Click to expand...
Click to collapse
UPDATE:
For what it's worth, I have the following information from the fastboot screen ...
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
Not sure if any of that helps in determining the issue or the right recovery image.
TIA
Hawkser said:
UPDATE:
For what it's worth, I have the following information from the fastboot screen ...
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
Not sure if any of that helps in determining the issue or the right recovery image.
TIA
Click to expand...
Click to collapse
Wow. /sigh. Apparently I have a HTC One S, not a One X. Been so long since I've had this phone that I forgot the part number. I'm just going to crawl away now.
For the record. All is well now. It's amazing how quickly and easily everything installs when you use the right files for the right phone. Now my only issue is that Google Play Store won't install any apps. The Play store runs fine...it just won't install any apps. Off to more searches for that.
Thanks anyway. I'm glad to at least have CyanogenMod running now. First time for me.
Related
[SOLVED]
As you can see in the title I have a lot going on.
I followed the correct steps to unlock the bootloader and it was successful as at one point I saw:
***TAMPERED***
***UNLOCKED***
Right off the bat I don't understand the reason for the "tampered" flag, but moving on...
For the record here is the other info below exactly as I see it:
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
After trying to flash different version of CWM Recovery with NO luck, I was stuck in a bootloop. Rebooted to FASTBOOT, erased cache, stock ROM loaded right away. At this point, every time I tried to flash ANY recovery (stock or CWM), I'd get the following message:
"This build is for developement purposes only Do not distribute outisde of HTC without HTC's written permission. Failure to comply may result in legal action."
And then it would proceed to a bootloop. I can't even use "FACTORY RESET" or get to the stock recovery, haven't been able to since the beginning.
At this point I thought to try "fastboot oem lock" and try again. That's precisely when I started to get this at the top of HBOOT:
***TAMPERED***
***RELOCKED***
***Securty Warning***
(Security Warning seems to come and go as it pleases at different times when accessing HBOOT, very awkward)
The interesting thing is, through all of this (as long as the phone allowed me to or as long as I erased cache through fastboot), the stock ROM (Rogers in Canada) actually works perfectly fine. I can boot into it no problem. But now I'm stuck with this odd issue inside of HBOOT and I don't know what to do to make it work. I found a bit of info suggesting that I could have a developer version of the phone if I'm getting that message following a recovery install. Keep in mind though this wasn't shipped to me, I got it from a retail store. Very odd.
Any insight regarding this would be greatly appreciated. I'm not bricked at the moment so that's nice, but I definitely would like to figure this out.
Thank you!
Can I ask you where did you get this phone from ?
I have gotten these messages alot when i had bricked my phone a while ago ...
Security warning always occured in HBoot when my battery was below 30%
Legal notice showed up when i tried booting custom Rom with a stock Recovery.
As long as it is relocked, try using a matching RUU. Make sure Battery is charged as much as possible. Also see Thread "Disaster Recovery" here in the forums
Wrong forum...
You have a Evita not a Endeavour you should post this in the right place not much we can do to help over here.
r0cafella said:
Wrong forum...
You have a Evita not a Endeavour you should post this in the right place not much we can do to help over here.
Click to expand...
Click to collapse
Evita is the code name for HTC One XL.
Really eh? I got it from Best Buy Mobile but it's a Rogers device. Advertised as the One X but yeah on GSM Arena it actually is the One XL. I'm guessing it's more or less exactly the same as the One X...for custom ROMs and what not...hopefully. Someone please correct me if I'm wrong!
In any case, I'm going to try to flash a shipped RUU (if I can download it from filefactory, error messages so far) then try to flashboot CWM again and see how that goes.
hv6478 said:
Really eh? I got it from Best Buy Mobile but it's a Rogers device. Advertised as the One X but yeah on GSM Arena it actually is the One XL. I'm guessing it's more or less exactly the same as the One X...for custom ROMs and what not...hopefully. Someone please correct me if I'm wrong!
In any case, I'm going to try to flash a shipped RUU (if I can download it from filefactory, error messages so far) then try to flashboot CWM again and see how that goes.
Click to expand...
Click to collapse
Ask it HERE ... and dont use the ONE X RUUs, it is not the same. Use that from the link i sent you (search it there).
muamers said:
Ask it HERE ... and dont use the ONE X RUUs, it is not the same. Use that from the link i sent you (search it there).
Click to expand...
Click to collapse
Thank you. Sorry mods please move this when possible.
I did make sure to download the correct EVITA ROM, it's flashing as we speak.
EDIT:
I should have tried the CWM version in that thread before flashing stock ROM. Oh well, better to start from a clean state anyhow.
DONE guys thank you very much for the info. Installed the correct version of CWM, rebooted, back to HBOOT, done. TAMPERED is there but as outlined in the thread that's normal. Now, on to flashing!
can u send me the rom
hv6478 said:
DONE guys thank you very much for the info. Installed the correct version of CWM, rebooted, back to HBOOT, done. TAMPERED is there but as outlined in the thread that's normal. Now, on to flashing!
Click to expand...
Click to collapse
hi my name is krunal
and i have the same problem u had
so can u please send me the rom u install
my phone is stuck at htc log screen
and it says security warning
thanks in advance
I've switched kernels multiple times and flashed a custom ROM on my One X but my HBOOT has never shown a "tampered" flag. Does anyone know why that is?
debani said:
I've switched kernels multiple times and flashed a custom ROM on my One X but my HBOOT has never shown a "tampered" flag. Does anyone know why that is?
Click to expand...
Click to collapse
Because your device is an Htc One X not an Htc One XL. Only One XL will show tampered flag.
i have the same error
after i ttying to update my HTC ONE X AT&T, i had this message, i think as your message
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
eMMC-boot
can you send to me your correct EVITA ROM and tell my how can i install it
Thank You
Ehabows
hv6478 said:
DONE guys thank you very much for the info. Installed the correct version of CWM, rebooted, back to HBOOT, done. TAMPERED is there but as outlined in the thread that's normal. Now, on to flashing!
Click to expand...
Click to collapse
I too have the same problem with my HTC One X from Rogers (or I thought it was HTC One X, from what I read here it could be an XL!).
Would you please step through the process you used to get CWM installed. I have TWRP presently installed.
Thanks
David
dkonkin said:
I too have the same problem with my HTC One X from Rogers (or I thought it was HTC One X, from what I read here it could be an XL!).
Would you please step through the process you used to get CWM installed. I have TWRP presently installed.
Thanks
David
Click to expand...
Click to collapse
This is the International Tegra3 One X forum, Post your question here : http://forum.xda-developers.com/forumdisplay.php?f=1538
One xl tampered Locked and s-on
I tried to unlock bootloader but it not possible to make it. i tried to Flash twrp but not succeed. could anyone help me to rescue the phone.
thanks in advance
best regards
Ok so I believe I bricked my phone. Currently all it does is boot to the HTC quietly brilliant screen, blink, then HTC quietly brilliant over and over forever. I am able to enter the Hboot no problem, but Recovery and Factory Reset don't help the problem.
Just so you know what I've done:
1) Started with the intention of rooting: Which now seems impossible due to me updating to the 2012 system update released before I realized it makes all the rooting instruction impossible to do.
2) I was able to UNLOCK the Hboot but the program that you normally run before hand would not work, so I did it all manually and successfully.
Current Hboot info is:
***UNLOCKED***
MarvelC PVT SHIP S-ON RL
HBOOT 1.10.0001
Microp-0354
Radio-0.94.00.0109
Apr 17 2012, 18:21:30 - I'm assuming this is the line that ruined rooting for me.
3) Tried and read every single program/walkthrough out there nothing works at all.
4) Today I tried using Hasoon2000's HTC Wildfire All in one kit.
5) Attempted to flash the recovery - thought it worked
6) As I knew about the system update mentioned above Apr17, 2012 I attempted to Flash the kernal with the boot rom inside the "RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.3 5.3029H_7.46.35.08_release_188032_signed". It went through and said everything worked perfectly. Upon restarting my phone is now stuck on the perpetual loop mentioned above and useless.
7) Booting into Hboot and attempting Flash does nothing as everything is still blocked it seems by that damm patch. Rooting using this program did not work either. I attempted to root from the Hboot USB promt (it was my only choice after the Brick)
Any assistance or ideas or leads really anything would be nice. I hope I supplied enough details.
[the omeessco
At what point of "rooting" were you at.. and which method were you using to "root"
the 2012 update made no difference to my NON marvel C handset when rooting via the official HTCdev method.
I'm not sure what you did... clockwork mod recovery installed?
I have abused my HTC & in the last 2 weeks has had about 10 diff rooms on it... I'm finding it hard to brick.. only soft brick
Glitch_Neo said:
At what point of "rooting" were you at.. and which method were you using to "root"
the 2012 update made no difference to my NON marvel C handset when rooting via the official HTCdev method.
I'm not sure what you did... clockwork mod recovery installed?
I have abused my HTC & in the last 2 weeks has had about 10 diff rooms on it... I'm finding it hard to brick.. only soft brick
Click to expand...
Click to collapse
I've been abusing it as well, this is the first time I've run into issue, but then again this is the first time I used this program and tried to see if I could roll back that system update with the KERNEL flash. That's the point at which all hell broke loose.
Drakons said:
I've been abusing it as well, this is the first time I've run into issue, but then again this is the first time I used this program and tried to see if I could roll back that system update with the KERNEL flash. That's the point at which all hell broke loose.
Click to expand...
Click to collapse
Really I'm not going to get any help at all? The Phone can't be Rooted so it's not rooted, just Unlocked HBoot as mentioned. It's in a constant Boot Loop.
Drakons said:
Really I'm not going to get any help at all? The Phone can't be Rooted so it's not rooted, just Unlocked HBoot as mentioned. It's in a constant Boot Loop.
Click to expand...
Click to collapse
Well I was able to get the phone to reboot by Fastboot flashing after extracting the rom.zip from the
RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.35.3029H_7.46.35.08_release_188032_signed
file, but the userdata, radio and recovery portions would not pass the Signatures portion.
So I'm unable to connect with my Wifi or The Phones network. Any ideas from here?
Sounds like a boot lopped have you tried flashing any roms?
Sent from my Wildfire S A510e using xda app-developers app
hmmm Im a newbie... let me research.. lol
Drakons said:
Really I'm not going to get any help at all? The Phone can't be Rooted so it's not rooted, just Unlocked HBoot as mentioned. It's in a constant Boot Loop.
Click to expand...
Click to collapse
LOL hey sorry my phone died and I was at work all last night.
You say its just in a perpetual boot loop... I had this with a "dodgy rom" install when I first started messing around. I managed to fix the issue with a complete wipe of SD card - formatted in the PC - then dalvic cach, cache etc... some "paid for" versions of App2sd etc that are patched or cracked also give loads of probs.
Stupic question, have you formatted / cleaned all aspects of mem card and phone acsessable files using the HBOOT.
When mine did it I just installed a fresh rom (cyanogen mod 10.1) and it worked again. without the reovery / install from SD isnt there I'm stumped.... noobie strikes... sorry
I'll have a read though... see what I can come up with.
I see from the Kernal You tried was for a MARVEL not MARVELC.... im sure the two should never be mixed up or bricking will happen
i'll get back to you later if i find anything out mate.
---------- Post added at 02:03 PM ---------- Previous post was at 01:59 PM ----------
WiseCrunchyEggroll said:
Sounds like a boot lopped have you tried flashing any roms?
Sent from my Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
From reading the tread properly, it seems a flash of the MARVEL Kernal onto a MARVELC phone is where the propblem lies.. Im pretty sure you should never mix the two... I could be wrong though - my wife tells me I often am! lol
good luck Drakons:good:
your best bet at this point is to flash a custom rom that is already rooted. you have the custom recovery already installed so just flash the rom. (whichever you like) for future reference the marvelc can be s-offed by placing the pj76diag.nbh onto the sdcard and booting to bootloader, allowing it to run and then selecting clean s58 data. once you have s-off you can supercid and then run any ruu that you want, should you ever get stuck in situations like this. where as the htcdev unlock blocks the use of ruu`s and pj76img.zips from bootloader
Drakons said:
Ok so I believe I bricked my phone. Currently all it does is boot to the HTC quietly brilliant screen, blink, then HTC quietly brilliant over and over forever. I am able to enter the Hboot no problem, but Recovery and Factory Reset don't help the problem.
Just so you know what I've done:
1) Started with the intention of rooting: Which now seems impossible due to me updating to the 2012 system update released before I realized it makes all the rooting instruction impossible to do.
2) I was able to UNLOCK the Hboot but the program that you normally run before hand would not work, so I did it all manually and successfully.
Current Hboot info is:
***UNLOCKED***
MarvelC PVT SHIP S-ON RL
HBOOT 1.10.0001
Microp-0354
Radio-0.94.00.0109
Apr 17 2012, 18:21:30 - I'm assuming this is the line that ruined rooting for me.
3) Tried and read every single program/walkthrough out there nothing works at all.
4) Today I tried using Hasoon2000's HTC Wildfire All in one kit.
5) Attempted to flash the recovery - thought it worked
6) As I knew about the system update mentioned above Apr17, 2012 I attempted to Flash the kernal with the boot rom inside the "RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.3 5.3029H_7.46.35.08_release_188032_signed". It went through and said everything worked perfectly. Upon restarting my phone is now stuck on the perpetual loop mentioned above and useless.
7) Booting into Hboot and attempting Flash does nothing as everything is still blocked it seems by that damm patch. Rooting using this program did not work either. I attempted to root from the Hboot USB promt (it was my only choice after the Brick)
Any assistance or ideas or leads really anything would be nice. I hope I supplied enough details.
Click to expand...
Click to collapse
I think you should change thread title to solved as you have solved tour problem...
Sent from my Wildfire S using Tapatalk 2
Hello guys,
I'm not gonna keep it short, because this is really important.
I recently bought my HTC One V and rooted it today. After a lot of trying, I flashed Clockworkmod on it.
After doing this, I tried to flash a custom ROM on it, so I wiped all system data, etc.
This went wrong, because I did something wrong that did not allow me to flash custom ROMs.
So here's my problem: I'm stuck! I cannot boot my phone, I get the HTC logo with some text like this:
"This version is distributed for developer purposes only...", etc.
So, I don't have any OS installed on my phone, I can only access my fastboot menu, CWM and stuff like that.
I tried installing other ROMs but it just does not work. This proves I screwed it up.
Then, after 2 hours of intensive Googling, I found this thing called RUU recoveries. I tried to find it for my HTC One V. Then, after another 30 minutes of Googling, I found it, downloaded it (took me another hour or so with the stupid server), opened it but got the error that I got the wrong version of the RUU Update Utility.
I cannot find the right one, I think it doesn't exist, because I live in the Netherlands and my carrier is Vodafone.
PLEASE HELP ME. How can I do a factory reset with the stock firmware? Please I really need help because I just bought this phone and I'm just a teenager so I can't afford another one.
ALSO PLEASE RESPOND ONLY IF YOU KNOW SOMETHING ABOUT THIS.
ofadlaoui said:
Hello guys,
I'm not gonna keep it short, because this is really important.
I recently bought my HTC One V and rooted it today. After a lot of trying, I flashed Clockworkmod on it.
After doing this, I tried to flash a custom ROM on it, so I wiped all system data, etc.
This went wrong, because I did something wrong that did not allow me to flash custom ROMs.
So here's my problem: I'm stuck! I cannot boot my phone, I get the HTC logo with some text like this:
"This version is distributed for developer purposes only...", etc.
So, I don't have any OS installed on my phone, I can only access my fastboot menu, CWM and stuff like that.
I tried installing other ROMs but it just does not work. This proves I screwed it up.
Then, after 2 hours of intensive Googling, I found this thing called RUU recoveries. I tried to find it for my HTC One V. Then, after another 30 minutes of Googling, I found it, downloaded it (took me another hour or so with the stupid server), opened it but got the error that I got the wrong version of the RUU Update Utility.
I cannot find the right one, I think it doesn't exist, because I live in the Netherlands and my carrier is Vodafone.
PLEASE HELP ME. How can I do a factory reset with the stock firmware? Please I really need help because I just bought this phone and I'm just a teenager so I can't afford another one.
ALSO PLEASE RESPOND ONLY IF YOU KNOW SOMETHING ABOUT THIS.
Click to expand...
Click to collapse
Hello ofadlaoui,
I might be able to help if you can give me some information from your fastboot menu. Copy all of the text. It should look something like:
Code:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT- 1.blah blah blah
RADIO- 1.blah blah blah
eMMC- boot
Some date in 2012, some time
Also as a second thought, did you flash the proper kernel/any kernel at all? That might be the problem that you're facing. Or the proper ROM... anyways, shoot me back a reply and I'll see if I can't find that goshdarn RUU for you.
Cheers, worldindo1.
Some personal notes: The CID for Vodafone NL is VODAPE17. Region code is x.xx.161.xx (Vodafone UK, which I found strange since Vodafone Switzerland-Germany is closer). Just need the hboot & radio versions you have and I can see if I might be able to get you a proper RUU.
worldindo1 said:
Hello ofadlaoui,
I might be able to help if you can give me some information from your fastboot menu. Copy all of the text. It should look something like:
Code:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT- 1.blah blah blah
RADIO- 1.blah blah blah
eMMC- boot
Some date in 2012, some time
Also as a second thought, did you flash the proper kernel/any kernel at all? That might be the problem that you're facing. Or the proper ROM... anyways, shoot me back a reply and I'll see if I can't find that goshdarn RUU for you.
Cheers, worldindo1.
Some personal notes: The CID for Vodafone NL is VODAPE17. Region code is x.xx.161.xx (Vodafone UK, which I found strange since Vodafone Switzerland-Germany is closer). Just need the hboot & radio versions you have and I can see if I might be able to get you a proper RUU.
Click to expand...
Click to collapse
Hey man,
First of all, thanks for replying. To be honest, I have no idea what you are talking about, as I am an Android amateur. I only used the Update Utility of HTC to try and flash the RUU but it didn't work. Anyway, I booted my device in HBOOT and this is what it says:
Code:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-3831.21.00.19_M
eMMC-boot
Jul 2 2012, 20:51:45
Patiently waiting for your answer, thanks a lot!
Don't worry... I hope u haven't flashed kernel.. first flash kernel then ur ROM...follow the steps correctly from given link.
http://forum.xda-developers.com/showthread.php?t=1996665
Hit thanks if I helped u...
Your device isn't bricked because it boots.. Just download the right kernel and the right rom and flash it according to the guides that can be found on this forum
Chill out man, yours is not bricked.
If you're using HOV CDMA, search custom rom in CDMA/PrimoC section.
But if you're using HOV GSM, then search in GSM/PrimoU section here or here.
Make sure if you choose Sense-based rom (MySense, MIUI, etc), pick the latest Titanium-Kiss kernel by Maxwen.
And if you choose CM10 based rom (PA, CM10, EverVolv, etc), pick the latest HellBoy by Maxwen, or SuperSick kernel by Simonsimons34.
Then after that, just copy the custom rom to your sd card, flash it to your phone.
Choose the right kernel & flash it too.
Voila! Your phone is ready to kick some asses.
Hope it turned out ok. Let us know how it goes. the advice others have given should get you back up and running.
theiNDrAs said:
Chill out man, yours is not bricked.
If you're using HOV CDMA, search custom rom in CDMA/PrimoC section.
But if you're using HOV GSM, then search in GSM/PrimoU section here or here.
Make sure if you choose Sense-based rom (MySense, MIUI, etc), pick the latest Titanium-Kiss kernel by Maxwen.
And if you choose CM10 based rom (PA, CM10, EverVolv, etc), pick the latest HellBoy by Maxwen, or SuperSick kernel by Simonsimons34.
Then after that, just copy the custom rom to your sd card, flash it to your phone.
Choose the right kernel & flash it too.
Voila! Your phone is ready to kick some asses.
Click to expand...
Click to collapse
You are on GSM so go pick out from those "here" or "here". If this doesn't work, do not despair as I will try to find the RUU for you. Hopefully it was just an improper ROM or kernel. If one of those ROMs/kernels works get back to me and I'll drop the search but from this point I will be scouring the stinkiest, smelliest, grungiest corners of the internet.
Hello, I'm completely new and completely stuck.
I decided yesterday to root my phone and try and install slim bean following these instructions.
http://forum.xda-developers.com/showthread.php?t=2092572
It all seemed to install properly and I thought it was all a piece of cake. However, much like the original poster my phone is now stuck on the HTC logo screen.
I have tried restoring my nandroid backup (if that's the right name/term) but it doesn't help. I have tried all-sorts of other things but none seem to work. So I assumed I must have to use a RUU. I tried to find one that is compatible but I get an error which says the model is incorrect or wrong, or whatever when I use it.
I have pretty much exactly the same fastboot details as the original chap, except for the date is different.
I cannot find an RUU with the same radio numbers (I don't know if that is important), the current one I'm using is the Europe one from here...
http://forum.gsmhosting.com/vbb/9187896-post22.html
The H3G UK ones are no longer available. I've also looked on androidfiles RUU page but they seem to have none for HTC One.
I am at a complete loss as to what I can do. You guys seems to have a wealth of knowledge and so I am hoping you'll be able to sort me out, if you can I thank you in advance!
:crying:
Perezvon said:
Hello, I'm completely new and completely stuck.
I decided yesterday to root my phone and try and install slim bean following these instructions.
http://forum.xda-developers.com/showthread.php?t=2092572
It all seemed to install properly and I thought it was all a piece of cake. However, much like the original poster my phone is now stuck on the HTC logo screen.
I have tried restoring my nandroid backup (if that's the right name/term) but it doesn't help. I have tried all-sorts of other things but none seem to work. So I assumed I must have to use a RUU. I tried to find one that is compatible but I get an error which says the model is incorrect or wrong, or whatever when I use it.
I have pretty much exactly the same fastboot details as the original chap, except for the date is different.
I cannot find an RUU with the same radio numbers (I don't know if that is important), the current one I'm using is the Europe one from here...
http://forum.gsmhosting.com/vbb/9187896-post22.html
The H3G UK ones are no longer available. I've also looked on androidfiles RUU page but they seem to have none for HTC One.
I am at a complete loss as to what I can do. You guys seems to have a wealth of knowledge and so I am hoping you'll be able to sort me out, if you can I thank you in advance!
:crying:
Click to expand...
Click to collapse
As it said in the OP on the Slim Bean ROM topic, you have to use a CM10 compatible kernel, such as maxwen's kernel. You can find this on One V Original Android Development.
Cm20? Cool!
Sent from my HTC One V using xda app-developers app
mr_nooby said:
Cm20? Cool!
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
xD Fixed that !
MameTozhio said:
As it said in the OP on the Slim Bean ROM topic, you have to use a CM10 compatible kernel, such as maxwen's kernel. You can find this on One V Original Android Development.
Click to expand...
Click to collapse
Hmmm, I guess I must have downloaded the wrong kernel - I thought I was using the right one. Anyway, it's working now, just to need to get some service signal then I'll be done, I hope.
Thanks!
I need an Obi-wan here. I'm a noob -- though I've gotten a solid four day education
hacking at this problem.
My wife's Android Desire Z - Stock ROM, S-ON, got stuck looping with a failed
android.process.acore message and after trying a cache clear that didn't help
I set out to factory reset it. Figured the nuclear option would be dead simple. Nope.
Factory Reset from the Hboot menu simply froze the phone
at the HTC menu for an hour. Not good.
From there dozens of resets and reboots and fastboots would sometimes successfully boot
to my wife's setup (so nothing was reset at all), only to get stuck in the acore loop again.
I was once quick enough to put it into
airplane mode and that stopped the error message loops. YAY! I could try a reset
via software! But when I attempted
Settings > SD & phone storage > Factory data reset it rebooted to HTC screen, Vodafone
screen, HTC screen, vodafone screen. ANOTHER loop.
OK, next try was to flash the ROM with an original shipped version.
Couple forums in Dutch said the shipped ROM for the Vodafone Desire z in NL was Bravo/Froyo World Wide English
so I located this file:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_
signed.exe
and attempted reset by running that on a pc.
But the USB connection failed after the unit reset: Error 171, Error 170.
Tried installing HTC Sync AND the Universal boot drivers
and the Android Booloader Driver, as per the helpful advice from Bob Denny at Phandroid. (As a noob, I can't post links here, sorry)
And yep, I disabled anti-virus, had a fully charged phone (I'm hoping you get
the picture here -- I've done my due dilligence and googling before asking for help.) but
nada. RUU rebooted the phone, waited for the bootoader, and either the phone never pings the USB
port to say it's there or the PC doesn't see it.
FINE. I can put a PC10IMG.ZIP on the SD card and dispense with the frustration of messing with windows, right? Well, no.
I extracted ROM.ZIP from the RUU renamed it PC10IMG.ZIP and slapped it in the root
directory of the SD card. I booted to Hboot with the volume down and power buttons, chose
Fastboot and watched the the Zip load (blue verticle progress bar upper right of screen),
check it (brown progress bar upper right), then NOTHING -- back to the Hboot menu.
No error message, and no invitation to
update. Reboot takes me back to screen loop. Normal power-on does the same.
Further searches make me question if this is the right shipped ROM.
The RUU reports that I'm running version 2.42.161.22
(of what? Vision Gingerbread?) and the Bravo/Froyo WWE Rom reported itself to be version 1.59 something.
As this is an S-ON phone, I know I can't roll back to earlier ROMS, and can only install
the exact version as shipped.
So the questions I THINK I need answered:
1. Does anyone know for certain, or know where I can find out, which ROM
shipped with the Vodafone NL Desire-Z in 2010? I can get Kernel source for it at the HTCDev site,
but I see no compiled ROM there -- anything I can do with kernel source?
2. Anyone know where can I get the right PC10IMG.ZIP file to flash the unit from the SD Card? (I tried Shipped-Roms.com and
dozens of google permutations)
3. Is my methodology for flashing the SD Card right or is there anything in the
description above that lends anyone to believe my problem or solution is anything
other than the one I'm obsessing over?
Any help deeply appreciated.
Info from Hboot screen:
VISION PVT SHIP S-ON
HBOOT-0.05.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-BOOT
Apr 11 2011, 23:36:27
Image CRC:
osbl: 0x1B4C7A4C
amss: 0xEF10821B
hboot: 0xCCCC4C36
recovery: 0x9627D8E8
system: 0xB6CE69CE
Please tell me I'm a stupid Noob and I've missed something so obvious I'll leave a
facepalm scar on my forehead, then tell me what it is so I can fix this dang phone and
get my life back. I'd be one appreciative noob.
-b
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip. If this doesn't work you may need to make a goldcard. This means you will need to boot the phone and get into setting to turn debugging on and will will also need to get the proper window drivers up and running in order to use adb. (Try holding the s key on the key pad while powering on, this may keep the bootloop away)
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip.
Click to expand...
Click to collapse
Yeah, sorry wasn't clear I extracted the zip from the RUU, not the rom itself, so I've tried this one already.
Safe boot doesn't boot -- gets me the HTC screen and freezes there. I'll keep trying, as I think gettting debugging on and going gold card may be my only hope if the problem isn't incorrect ROM (or if there's no finding the correct one).
Here's a simpler question: If in my hboot screen I see
VISION PVT SHIP S-ON
Does that mean the shipped ROM was vision gingerbread and that's the only one to try,
or could my wife's "system updates" upgraded the phone from a Bravo shipped ROM?
And when I get a CID Incorrect error on a Vision Gingerbread ROM, does that mean the WWE Vision Gingerbread ROM I tried to install isn't good because it's not Vodafone, or because it's not the shipped ROM?
Any help will be thankfully appreciated!
Sorry it took so long to get back,
ship s-on is referring to you have a shipped bootloader and your security flags are on, that line is not specific to any version of the desire z
You won't be able to flash any ROM like that unless it is an upgrade from current version. I believe if you go to HTC website the latest ruu was not released as an ota and may work for you as its probably newer. If it doesn't work then you will need to get super cid in order to flash something older, which means you need to get adb working
Sent from my Nexus 7 using xda premium
Hello,
I recently picked up an HTC M9 T-Mobile. I have ATT so I decided to go though the steps of unlocking the device via this link. I actually managed to it get done in a relatively short amount of time so I figured 'This is nice, but why not install a custom rom like you did on your m7, same stuff rite?'
I believe i was an idiot and installed a new kernel and firmware in addition to the rom making my IMEI vanish along with most of the important information about my device. I tried HD Rev 20 and ViperOne.
So I RUU back to my correct stock rom, and now I can't get into the twrp recovery. I was under the impression RUU didn't mess with the recovery partition. I've attempted to flash it several times however it shoots back an error : 35 ru_partition_not_support recovery
I have tried searching and searching for the past few hours and I don't know if I'm blind, or if I'm just screwed. I hate asking for help on here, I know the search function work I just can't seem to find this exact issue.
I'd like to just be clear and mention I can actually boot into stock. As well as booting into the bootloader, and adb recognizes the phone. Ironically the device is still 'unlocked' after all of this, however my recovery is missing entirely, I don't even have the original recovery. When I attempt to access the recovery I get a picture of a phone with a red ! inside it.
The RUU I used was 3.39.531.7
Something I feel may or may not be related, when in download mode I see at the bottom:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Click to expand...
Click to collapse
I have a feeling this is irrelevant if it has to do with the SD card. I also have a really strange feeling this is something stupid easy that I am missing.
Some additional information, please let me know if I missed something:
*** UNLOCKED ***
htc_himaul PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440801_97.04.60111G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.39.531.7
Kernel version
3.10.84-perf-ge2fbd28
[email protected]#1
SMP PREEMPT
Thanks in advance.
I am a dumbass.
I flashed with an older version of twrp and that fixed the issue.
Don't be like me kids.
Which version of twrp worked? I continue to get the same error with every version.