Related
can someone help me out please? i rooted my g2 today and about 2 hours later dropped it flat on its face. the lcd broke, i cant see anything on the phone just vibrates when i turn it on.. is there some way using the sdk on the computer to unroot the phone so i can send it for an insurance replacement?
If its anything like the desire you can apply a RUU update.exe that flashes the phone rom, hboot, radio and recovery i.e. stock. However if yours is branded i.e. has your carriers software all over it, you'll need to find the corresponding RUU for that carrier. Also if its branded you'll probably (desire does) need to make a goldcard if you were to apply an unbranded RUU.
richardpearce123 said:
If its anything like the desire you can apply a RUU update.exe that flashes the phone rom, hboot, radio and recovery i.e. stock. However if yours is branded i.e. has your carriers software all over it, you'll need to find the corresponding RUU for that carrier. Also if its branded you'll probably (desire does) need to make a goldcard if you were to apply an unbranded RUU.
Click to expand...
Click to collapse
EDIT: didn't realise the G2 was T-Mobiles phone (if Im not mistaken and check me on this is the HTC Hero)... erm heres a link to a load of G2 roms, radios etc http://forum.xda-developers.com/showthread.php?p=4525584
do some researching into tutorials to make sure your doing the right thing. Also to research is whether your phone is GSM or CDMA as you will also have to flash the right RUU for that too.
When you rooted did you only root the rom or also patch a modded recovery too? If its the rom I suppose you could apply just the rom update, however if you applied a recovery you'll have to flash that with a stock one too.
Sorry its a bit confusing...
Ok So my friend from work wanted his sensation rooted after I did mine. He has S-OFF and has sucessfully permanently rooted it with the SU-bin 3.03 blah blah zip file. I've succesfully rooted my own with CID of 11111111 and used 4EXT recovery to install the 3.24 firmware. He, however, gets the known boot loop problem, which I know is due to firmware not being upgraded. I can't for the life of me connect his phone and have ADB connect to it to change his CID.
I've got the same exact model phone, down to the same carrier, so I have the HTC sensation USB drivers (HTC sync) installed on my pc. It won't detect it though because of it not being able to boot into android's OS.
I'm attempting to download a rom that is based off of the stock firmware hoping this will solve my problem, but wouldn't mind any insight on it.
Well, if i got it right you just need to pick a firmware flashable for that phone without supercid, am i right? In that case there's the topic where you can find all firmware adjusted to a particular CID, grab that from your phone, put into your sd (you may want to put a ROM to flash too), then put your SD with the matching firmware onto his phone, reboot and it's done! Finally swap again the SD card.
daddoso said:
Well, if i got it right you just need to pick a firmware flashable for that phone without supercid, am i right? In that case there's the topic where you can find all firmware adjusted to a particular CID, grab that from your phone, put into your sd (you may want to put a ROM to flash too), then put your SD with the matching firmware onto his phone, reboot and it's done! Finally swap again the SD card.
Click to expand...
Click to collapse
Yes I would think so, but I can't figure out what current CID he has on his phone because I can't boot up into android's OS and connect to my phone on my PC with ADB (adb devices shows up, but when I try to set the CID it wont work).
Fails to "set" or fails just the command? Because if its only a "set" issue, the command may (unlikely) work and show you the cid! Or we can try to find it out with some info like brand/country/etc ..
Figured it out, had to do with the sync cable I was using. used a different one and i was able to set the CID to 1111111 or w/e. Installed the new firmware and the silly boot loop stopped.
Sent from my Asus Transformer of The Prime Kind.
I've read previous threads that instruct to search for rom.zip in the temp folder. I have found the rom.zip but it does not flash using CWM. How do I get the rom which I can flash through CWM?
You don't flash it through cwm, you rename it accordingly (PHxxIMG.zip) based on your phone model and flash it through HBOOT.
Sent from my ADR6425LVW using XDA
hellhawk741 said:
You don't flash it through cwm, you rename it accordingly (PHxxIMG.zip) based on your phone model and flash it through HBOOT.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Okay. I do recall my phone searching for similarly named images when I booted the phone to recovery. How exactly am I supposed to flash them after renaming and placing them in the root of my SD Card?
Also, do normal regional restrictions still apply to this process? (Will it bail if I try flashing the phxximg.zip of a European RUU on a asian phone?)
Thanks a lot.
Don't know about the regional restrictions. To flash it you just put the renamed zip in the root of your SD card and reboot into bootloader. It'll scan for the file and ask you to press some key if you want to flash the update. That's it.
Sent from my Desire HD using xda premium
Regional restrictions apply unless you have changed your CID to allow for flashing of other regions ROMs. This is called "SuperCID". I'm not sure which HTC phone you have otherwise I'd link you to how to get it on your phone, but it's a simple google search "SuperCID *phone name*"
When you have SuperCID, it allows the flashing of any ROM by any carrier so if you intend on doing an Asian ROM on a Euro phone, check and make sure the hardware is the same, otherwise you'll bork something.
Example: if you flashed a CDMA EVO 3D ROM on a GSM EVO 3D, you'd likely lose your data, signal at least, given that the CDMA and GSM 3D's have different radios. You'd probably lose even more but the data and signal at least are for sure.
PoorCollegeGuy said:
Regional restrictions apply unless you have changed your CID to allow for flashing of other regions ROMs. This is called "SuperCID". I'm not sure which HTC phone you have otherwise I'd link you to how to get it on your phone, but it's a simple google search "SuperCID *phone name*"
When you have SuperCID, it allows the flashing of any ROM by any carrier so if you intend on doing an Asian ROM on a Euro phone, check and make sure the hardware is the same, otherwise you'll bork something.
Example: if you flashed a CDMA EVO 3D ROM on a GSM EVO 3D, you'd likely lose your data, signal at least, given that the CDMA and GSM 3D's have different radios. You'd probably lose even more but the data and signal at least are for sure.
Click to expand...
Click to collapse
Exactly, just got an incorrect CID error. I'm trying to do this on HTC One V. The bootloader is unlocked. Can you please link me to the SuperCID for HTC one V? Is it software or hardware?
Also for this process, do I need to have stock recovery or having CWM won't cause any issue?
Moreover, is it okay if the bootloader is unlocked or do I "relock" it?
PoorCollegeGuy said:
Regional restrictions apply unless you have changed your CID to allow for flashing of other regions ROMs. This is called "SuperCID". I'm not sure which HTC phone you have otherwise I'd link you to how to get it on your phone, but it's a simple google search "SuperCID *phone name*"
When you have SuperCID, it allows the flashing of any ROM by any carrier so if you intend on doing an Asian ROM on a Euro phone, check and make sure the hardware is the same, otherwise you'll bork something.
Example: if you flashed a CDMA EVO 3D ROM on a GSM EVO 3D, you'd likely lose your data, signal at least, given that the CDMA and GSM 3D's have different radios. You'd probably lose even more but the data and signal at least are for sure.
Click to expand...
Click to collapse
Can you please post me the link to the SuperCID for HTC One V. Googling didn't help much.
Another very important question, my stock ROM was an Indian one. I rooted and flashed a stock European ROM. Due to this process, do you think the original CID was modified?
abhishek_turbo911 said:
Exactly, just got an incorrect CID error. I'm trying to do this on HTC One V. The bootloader is unlocked. Can you please link me to the SuperCID for HTC one V? Is it software or hardware?
Also for this process, do I need to have stock recovery or having CWM won't cause any issue?
Moreover, is it okay if the bootloader is unlocked or do I "relock" it?
Click to expand...
Click to collapse
You'll most likely need to re-lock before flashing the RUU. I haven't heard of a way to get super-cid on the One V yet, but if it's possible you should be able to find it in the HTC One V forums.
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto
Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.
you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want
Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.
I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium
Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder). If I locate the Rogers 1.84 RUU, can I run it without downgrading?
don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network
Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.
if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work
Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.
factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery
donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link
I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?
Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Thanks again.
for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network
Hi guys, something pretty bad happened tonight to my Htc One S.
I had maximusHD installed, so of course S-OFF and bootloader Unlocked. However, I was having some problems and decided to revert back to stock. I re-locked the bootloader, changed the CID back to the stock one and flashed the RUU. Everything went perfectly fine. Sort of. I noticed that the RUU I flashed was some kind of pre-release one (the whole interface was watermarked). I got that from androidruu.com
So I downloaded a newer RUU (yes, both of them were for the appropriate country) and flashed that one.
It went on normally for a while and then nothing. Black screen, no response, no charging light. It shows as QHSUSB_dload under Windows and as Qualcomm Gobi Wireless Modem under Linux.
Now, are RUUs so damn risky? Luckily the phone was Relocked and S-ON, so warranty should cover this. I read all kinds of threads about this problem but none of the proposed solutions worked... did I miss something or do really need to send it for repairs?
Thanks!
Camazza said:
Hi guys, something pretty bad happened tonight to my Htc One S.
I had maximusHD installed, so of course S-OFF and bootloader Unlocked. However, I was having some problems and decided to revert back to stock. I re-locked the bootloader, changed the CID back to the stock one and flashed the RUU. Everything went perfectly fine. Sort of. I noticed that the RUU I flashed was some kind of pre-release one (the whole interface was watermarked). I got that from androidruu.com
So I downloaded a newer RUU (yes, both of them were for the appropriate country) and flashed that one.
It went on normally for a while and then nothing. Black screen, no response, no charging light. It shows as QHSUSB_dload under Windows and as Qualcomm Gobi Wireless Modem under Linux.
Now, are RUUs so damn risky? Luckily the phone was Relocked and S-ON, so warranty should cover this. I read all kinds of threads about this problem but none of the proposed solutions worked... did I miss something or do really need to send it for repairs?
Thanks!
Click to expand...
Click to collapse
Hi,
I was stuck with the same issue. What threads have you tried I heard the only way is via JTAG but just wanna know if there is any other way
It seems like I could do something with the phone using QPST (which I have). What I'm missing are the device and chipset-specific files that need to be recovered from a working phone. There has been some talk about QPST and its usefulness here on xda, but I think they only made i work for some Samsung devices with Qualcomm chipsets.
Is there someone who is willing to help me, maybe by dumping the contents of his phone using QPST and posting them? I only need the SPL partition, which is the HBOOT i need to recover the phone.
Please, tell me I don't have to send it to HTC...
Camazza said:
It seems like I could do something with the phone using QPST (which I have). What I'm missing are the device and chipset-specific files that need to be recovered from a working phone. There has been some talk about QPST and its usefulness here on xda, but I think they only made i work for some Samsung devices with Qualcomm chipsets.
Is there someone who is willing to help me, maybe by dumping the contents of his phone using QPST and posting them? I only need the SPL partition, which is the HBOOT i need to recover the phone.
Please, tell me I don't have to send it to HTC...
Click to expand...
Click to collapse
QPST is just a software right... no hardware is required for it ha!!!!... I thought jtag is the only way to access a bircked phone.
our pc is able to detect QHSUSB_dload and via that itself will we be able to flash a mobile if we have a system dump??