How to extract stock Rom? The case is that I haven't done backup of my stock Rom branded by era provider.
Now some guy told me that he just bought desire z from era and his Rom is identical to RUU_Vision_HTC_WWE_1.72.405.2_R_Radio_12.28e.60.14 0f_26.04.02.17_M2_SF_release (available on this forum)
except radio code which is ending with fU instead f.
So if I would like to get Rom which is flashed on his device, to have exactly what was on mine on the beginning what and how it should be done?
Sent from my HTC Vision using XDA Premium App
Searching XDA found this: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#RUU_Flashing
I think it's just connect phone, run RUU*.exe
tan-ce said:
Searching XDA found this: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#RUU_Flashing
I think it's just connect phone, run RUU*.exe
Click to expand...
Click to collapse
Ok thanks it is for sure usefully guide but I'd like to know how to retrieve or backup stock Rom from the phone with original stock?
Sent from my HTC Vision using XDA Premium App
Ok, if I understand you right, you currently have a phone with stock ROM, and you want to take a backup of that phone, correct?
If that's the case, I think you'll still need to root the phone in order to install Clockwork recovery. Once you have Clockwork, then you can take a nandroid backup of your phone. So I don't think you can grab a backup of stock ROM before it was rooted.
tan-ce said:
Ok, if I understand you right, you currently have a phone with stock ROM, and you want to take a backup of that phone, correct?
If that's the case, I think you'll still need to root the phone in order to install Clockwork recovery. Once you have Clockwork, then you can take a nandroid backup of your phone. So I don't think you can grab a backup of stock ROM before it was rooted.
Click to expand...
Click to collapse
Yeah so this a problem. During rooting it is necessary to downgrade your soft to 1.34 what automatically force you to loose your stock Rom. :/
Sent from my HTC Vision using XDA Premium App
Oh right, now I remember. I think if you can't find the exact RUU, you're out of luck. What do you want that backup for anyway?
tan-ce said:
Oh right, now I remember. I think if you can't find the exact RUU, you're out of luck. What do you want that backup for anyway?
Click to expand...
Click to collapse
No no I wanted only to have a possibility to back to the stock Rom if my phone will have to be sent to service on warranty.
I know one guy from Poland who also bought a phone from the same telcom operator - era.
He gave me info that the stock Rom on his phone is:
12.28e.60.140fU_26.04.02.17_M2
While on the forum can be find the same but with one difference in radio code - only f instead fU
12.28e.60.140f_26.04.02.17_M2 and can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=879384
But what does it mean this difference mentioned above and if it is negligible or not?
Sent from my HTC Vision using XDA Premium App
Well, unless you've flashed a custom radio, another option could be to extract everything from that RUU you found in the forum and flashing everything except the radio.
Although if you want to send your phone for warranty you'll probably have to do a bit more work to get s-on again...
tan-ce said:
Well, unless you've flashed a custom radio, another option could be to extract everything from that RUU you found in the forum and flashing everything except the radio.
Although if you want to send your phone for warranty you'll probably have to do a bit more work to get s-on again...
Click to expand...
Click to collapse
I've flashed two ROMs first one was CM7-R2 and then I've decided to use Virtuous 1.0.1. I don't know if during that process also radio was flashed :/ Was it? I am new Android so I don't know some things yet.
Sent from my HTC Vision using XDA Premium App
Btonh ohyj uiibf hgv
meXdroid Ghost Chilli
Sebalos said:
I've flashed two ROMs first one was CM7-R2 and then I've decided to use Virtuous 1.0.1. I don't know if during that process also radio was flashed :/ Was it? I am new Android so I don't know some things yet.
Click to expand...
Click to collapse
I'm quite sure that flashing those ROMs do not change your radio. So if you need to send for warranty, I think you'll just need to flash the ROM part of the RUU (should be able to find a post somewhere which tells you how to extract just certain parts of the RUU) and then reflash partition 7 to get S-OFF. If you used gfree, it would have made a backup of that partition before it gave you S-OFF. Hopefully you still have it.
Actually, have you taken a look at this?
Related
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
mapko11 said:
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
Click to expand...
Click to collapse
Wat is the hboot versoin?
Sent from my Incredible using XDA App
Where do I find that out?
mapko11 said:
Where do I find that out?
Click to expand...
Click to collapse
In the bootloader it should say.
Sent from my Incredible using XDA App
Hboot-0.79.0000
mapko11 said:
2. Trying to install the OTA so I can run 2.2 the right way.
Click to expand...
Click to collapse
Well, "the right way" would be to wait for the actual OTA. Verizon would also have your back if you brick. But, anyway...
If you're still on the 1.00.03.04.06 radio, you can probably follow the instructions in that thread now that you've flashed back to the stock ROM. However, there still seem to be a few cases of people bricking their phones or being stuck in a bootloop after flashing leaks.
If you are confused/concerned/afraid of bricks then you just shouldn't flash the leaked OTA. This is not a flame, this is sound advice. Wait for the real one.
I'm fine with flashing. I just keep hearing about this "double install OTA and brick your phone" issue and I'm trying to avoid doing that. If the one guy didn't chime in with the suggestion to use ROM Manager, I wouldn't of had this issue.
My radio is still 1.00.03.04.06. I just want to make sure I don't run a risk of bricking.
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
jdkoreclipse said:
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
How do I know if the HBOOT has been updated? I posted my version above?
mapko11 said:
How do I know if the HBOOT has been updated? I posted my version above?
Click to expand...
Click to collapse
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Anyway to undo this and go back?
mapko11 said:
Anyway to undo this and go back?
Click to expand...
Click to collapse
Try the PB13IMG.
Sent from my Incredible using XDA App
jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
And you needed to un root before applying the ota
Sent from my Incredible using XDA App
jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May, and she sure as hell didn't have no 720p camcorder. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
But absolutely, running the PB13IMG should ensure that he's as far back as he can go, so why not try it just to be safe...
jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That's what I just did before I posted this thread. I installed the PB13IMG and restored everything back to stock. You asked about the HBOOT version and that's .79. I'm comfortable flashing and doing the update. What should HBOOT say? Has anyone successfully updated the OTA from .79 HBOOT?
Thank you for the help. Sorry for the questions. I completely comfortable with rooting, flashing roms, and kernals. This is going back to unroot stock is just new.
I want to install the OTA and I'm good to go. Just making sure it's safe now....
alexdw369 said:
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
Click to expand...
Click to collapse
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
jdkoreclipse said:
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
alexdw369 said:
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
Click to expand...
Click to collapse
I appreciate the help guys. I guess my question would be if I ran PB13IMG, lost my root, back to stock, my HBOOT is .79 and my radio is still 1.00.03.04.06 and not 2.05.00.06.11, I should be at the same point as everyone else for installing the OTA from my SD card. Right or wrong?
When you read these threads and people are installing the OTA twice and bricking, are they installing the OTA again when the radio is already updated to 2.05.00.06.11?
Yep. I think you can flash it again, but be real cautious, as this is your second time flashing it, but if the radio is still the old versoin, you should be safe.
Sent from my Incredible using XDA App
Hi all. I'm new to this world so asking a, may be silly, question.
I play with roms every now and then. Change my rom from one to another in couple of weeks. I found STOCK HBOOT OFFERS LESS INTERNAL SPACE THAN CM7 OR CM7r2 hboots for custom roms.
I haven't experimented yet with these things. Can someone tell me how to convert my hboot to cm7 or cm7r2? I haven't done anything with my hboot so I suppose I'm on stock hboot. Difference between cm7 and cm7r2?
Any drawbacks of doing this? And will be able to flash app2sd and data2ext normally as I do now?
Any help would be highly appreciated.
Sent from my HTC Desire using XDA App
The difference is that the hboot versions offer you a diffrent internal partition layout
you can look them up http://alpharev.nl/ <-- there
also you can download it from there
You can flash it via fastboot or via the PB99IMG.zip method or you simply use android flasher(recommanded, it´s selfexplaining)
Is there any chance of bricking my phone?
When I switch between roms sometimes I get stuck in boot loops. *no worries*
I just pull out the battery. Reboot in recovery and restore nandroid backup.
In this case I'm cautious because if I'm stuck where would I go because I'm playing with hboot. I think I won't be able to access recovery in that case, right?
Sent from my HTC Desire using XDA App
You can brick it if your downloaded hboot.img is not downloaded correcly
If you are in a bootloop you simply go into fastboot and flash the correct table(hboot) and flash your ROM
and yes you will be able to boot into recovery(if youre in a bootloop)
mohsinraza said:
Is there any chance of bricking my phone?
When I switch between roms sometimes I get stuck in boot loops. *no worries*
I just pull out the battery. Reboot in recovery and restore nandroid backup.
In this case I'm cautious because if I'm stuck where would I go because I'm playing with hboot. I think I won't be able to access recovery in that case, right?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
If your download was corrupt or you pulled the cable in the seconds during the flashing period then you'd most probably brick your phone, but during my time on this forum I have never heard of any such misfortunes occurring..
By the way instead of posting try searching... this is just common knowledge info and can be found with a quick google search or a visit to alpharev.. it really isn't hard and not really worth posting a new thread about.
bortak said:
If your download was corrupt or you pulled the cable in the seconds during the flashing period then you'd most probably brick your phone, but during my time on this forum I have never heard of any such misfortunes occurring..
By the way instead of posting try searching... this is just common knowledge info and can be found with a quick google search or a visit to alpharev.. it really isn't hard and not really worth posting a new thread about.
Click to expand...
Click to collapse
I've already gone through alpharev but this question of mine about bricking the phone was never answered
Sent from my HTC Desire using XDA App
loler90 said:
You can brick it if your downloaded hboot.img is not downloaded correcly
If you are in a bootloop you simply go into fastboot and flash the correct table(hboot) and flash your ROM
and yes you will be able to boot into recovery(if youre in a bootloop)
Click to expand...
Click to collapse
Thanks a million. Now this means I take a nandroid backup and download cm7r2 hboot from alpharev. Flash it and then flash a compatible rom.
Do I need a complete wipe before flashing hboot?
Sent from my HTC Desire using XDA App
One more question:
I'm on stock hboot. Will I be able to restore nandroid backup when I switch to cm7r2?
Sent from my HTC Desire using XDA App
mohsinraza said:
One more question:
I'm on stock hboot. Will I be able to restore nandroid backup when I switch to cm7r2?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
if your ROM fits
bortak said:
if your ROM fits
Click to expand...
Click to collapse
Fit where and in what?
Just asking for information. I'll definitely flash a clean new rom.
I'm using Aurora for Desire. It supports both stock and cm7r2.
Will flash that rom again but then I'll have way more internal memory as compared to what I'm getting now.
Sent from my HTC Desire using XDA App
I know I'm going to ask a silly question. Sorry in advance
It's written on alpharev that check MD5SUM after downloading the hboot.
How do I check whether it's correct or not?
Don't wanna brick my phone :-(
Sent from my HTC Desire using XDA App
The nandroid needs to have the HBOOT you had, when you made that nandroid.
So if U had STOCK HBOOT when making a nandroid wich U like to go back to, then flash STOCK HBOOT - BEFORE - U nandroid back.
So for now... flash the HBOOT U want, and then right after the ROM.
And if U wanna restore your nandroid, then flash STOCK HBOOT, and then restore nandroid.
AND remember... U CAN NOT FLASH RADIO IF U ARE ON CM7R2 HBOOT,
that will brick your phone.
So flash RADIO before, OR do the procedure with ADB if U are already on CM7R2.
----------------------------------------------
MD5 checksum program: hashcalc (google it)
Jakedude2011 said:
The nandroid needs to have the HBOOT you had, when you made that nandroid.
So if U had STOCK HBOOT when making a nandroid wich U like to go back to, then flash STOCK HBOOT - BEFORE - U nandroid back.
So for now... flash the HBOOT U want, and then right after the ROM.
And if U wanna restore your nandroid, then flash STOCK HBOOT, and then restore nandroid.
AND remember... U CAN NOT FLASH RADIO IF U ARE ON CM7R2 HBOOT,
that will brick your phone.
So flash RADIO before, OR do the procedure with ADB if U are already on CM7R2.
----------------------------------------------
MD5 checksum program: hashcalc (google it)
Click to expand...
Click to collapse
Thanks a lot for your detailed answer. Will flash cm7r2 and new rom as soon as I get to my PC.
Sent from my HTC Desire using XDA App
No problem. Good Luck.
unzip
10 chars
bortak said:
unzip
10 chars
Click to expand...
Click to collapse
Thanks buddy. I'm a hostellite. Plan to go home on this weekend.
Will give it a try then.
Sent from my HTC Desire using XDA App
MD5 SUM check
Alright so I read about the md5sum check got the software to check it as well, even though it didnt match, I still managed to get the cm7/r2 hboot & flash insertcoin. I want to know how exactly we know if md5sums have matched cos i want to change my rom & i want to know how i can check if the rom is compatible with the cm7/r2 hboot.
Insertcoin freezes a lot on my phone I have no idea why.
Lots of questions on this post from me, someone please answer. need help
gyak88 said:
Alright so I read about the md5sum check got the software to check it as well, even though it didnt match, I still managed to get the cm7/r2 hboot & flash insertcoin. I want to know how exactly we know if md5sums have matched cos i want to change my rom & i want to know how i can check if the rom is compatible with the cm7/r2 hboot.
Insertcoin freezes a lot on my phone I have no idea why.
Lots of questions on this post from me, someone please answer. need help
Click to expand...
Click to collapse
This is very awkward if you still managed to flash cm7r2 even though md5sum didn't match.
I haven't tried it yet. Will give a try tomorrow.
Every rom has mentioned which hboots are compatible. You can check it from there.
Sent from my HTC Desire using XDA App
gyak88 said:
Alright so I read about the md5sum check got the software to check it as well, even though it didnt match, I still managed to get the cm7/r2 hboot & flash insertcoin. I want to know how exactly we know if md5sums have matched cos i want to change my rom & i want to know how i can check if the rom is compatible with the cm7/r2 hboot.
Insertcoin freezes a lot on my phone I have no idea why.
Lots of questions on this post from me, someone please answer. need help
Click to expand...
Click to collapse
You do realise... the point of an md5 match is so that you know the thing that is uploaded.. is exactly the same thing that you downloaded... so... when it matches "hooray lets flash away"... when it doesn't "holy mother of god get the hell of my computer"... you sure you used it right?
mohsinraza said:
This is very awkward if you still managed to flash cm7r2 even though md5sum didn't match.
I haven't tried it yet. Will give a try tomorrow.
Every rom has mentioned which hboots are compatible. You can check it from there.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
if you are using cm7r2 hboot, make sure to flash market cache fix else you will face issue when you download large size apps from market.
After trying several different ROMs (mainly Sense 1.9 up to 3.5) and 3 different memory cards I am still having reliability problems with my Desire. The main problem is now and again I press the wake button and nothing. The power button doesnt even work I have to take the battery out and reset.
I also get a fair bit of lag, especially with incoming calls, even after having a play with Daemon Controller settings.
I can just about live with it but as I am likely to want to sell the phone soon i was wondering if anyone could recommend the most solid ROM. Preferably one that doesn't use an EXT3/4 partition as it could possibly be running apps from this that's causing the problem. I'm not bothered about Sense either.
I am currently running AceSMod007 v42, Recovery 4EXT v2.2.7 RC6, Stock HBoot.
The easier it is to install the better and even if its vanilla android I'm not bothered. I just don't want any comebacks when I sell it as the phone has caused me enough headaches.
ps Is a new battery likely to help or is that clutching at straws?
Put it back to stock like it used to be. That will eliminate or at least lessen the possibility of buyer comebacks caused by buggy custom roms. If the buyer wants it rooted, he/she should do it themselves.
How do you do that exactly?
Sent from my HTC Desire using Tapatalk
Reflash the Froyo RUU which you can pick up at www.shippedroms.com, or the Gingerbread RUU which you can find at www.htcdev.com/devcenter/downloads.
Good luck!
plinders said:
Reflash the Froyo RUU which you can pick up at www.shippedroms.com, or the Gingerbread RUU which you can find at www.htcdev.com/devcenter/downloads.
Good luck!
Click to expand...
Click to collapse
Thanks! Can I flash that straight over any ROM? and does that mean it won't be rooted anymore either?
Steveh8204 said:
Thanks! Can I flash that straight over any ROM? and does that mean it won't be rooted anymore either?
Click to expand...
Click to collapse
I haven't done it personally but I believe you can flash it over as long as the phone is on stock hboot which I think it is. If you are s-off, you may need to flash a downgrader from alpharev. (Can anyone confirm this is required for stock hboot? I had the impression it's only for cm7r2 and oxygen hboots.)
You'll lose root and s-off (if you s-offed your device before). Make sure you chose the right RUU for your phone.
stankyou said:
Can anyone confirm this is required for stock hboot? I had the impression it's only for cm7r2 and oxygen hboots.
Click to expand...
Click to collapse
Only r2 hboots.
I think I might have to give it a try as my phone is very unreliable now as it keeps just switching off and won't reset unless I pull the battery. Happens about once a day.
Do I flash it through recovery as usual?
Also, if you want a solid rom, you can't get much more solid than Cyanogenmod. It's actually more stable than the stock rom for my part. Another option is MIUI, but the iPhone-like interface might be a bother.
Thanks, do you mean CyanogenMod-7 for Desire GSM V7.0.3 rom as the download link was broken when I checked?
Steveh8204 said:
Thanks, do you mean CyanogenMod-7 for Desire GSM V7.0.3 rom as the download link was broken when I checked?
Click to expand...
Click to collapse
You're selling the phone. Stick to your original plan.
Sent from my HTC Desire using Tapatalk 2
Possibly not for another 6-8 weeks so I don't fancy returning to Stock and still having problems and having to mess about getting it S-Off and rooted again.
And to be fair if it wasn't randomly switching itself off I might consider hanging on to it longer as when it works properly its a pretty decent phone, I just cant live with the unreliablility.
So has anyone got a link for the CM Rom?
Steveh8204 said:
I don't fancy returning to Stock and still having problems and having to mess about getting it S-Off and rooted again.
Click to expand...
Click to collapse
If this is the way it turns out, I think you should start considering RMA.
Sent from my HTC Desire using Tapatalk 2
Look in desire android development it should be there
Sent from my HTC Desire using xda premium
Ok thanks, just a couple of things though, what is RMA and how do I flash the stock? can I do it through 4Ext recovery and do I need to wipe anything first?
http://www.google.ie/url?sa=t&sourc...jLn2Aw&usg=AFQjCNH-nCOyaY1Gor2f_Iah8MF8Wxwjbg
Sent from my HTC Desire using xda premium
jmcclue said:
http://www.google.ie/url?sa=t&sourc...jLn2Aw&usg=AFQjCNH-nCOyaY1Gor2f_Iah8MF8Wxwjbg
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Thats CM official page
Sent from my HTC Desire using xda premium
Steveh8204 said:
Ok thanks, just a couple of things though, what is RMA and how do I flash the stock? can I do it through 4Ext recovery and do I need to wipe anything first?
Click to expand...
Click to collapse
Consult Bortak's guide on that, I'm not writing it over again here.
RMA is a warranty claim.
Sent from my HTC Desire using Tapatalk 2
Steveh8204 said:
Ok thanks, just a couple of things though, what is RMA and how do I flash the stock? can I do it through 4Ext recovery and do I need to wipe anything first?
Click to expand...
Click to collapse
Go to desire android development then go into stickies everything u need to know will be there and thank OP if they helped
Sent from my HTC Desire using xda premium
Hey, if you've ever used SEUS you know what I'm looking for, is there and application to do the same stuff with HTC phones?
Also I would like to backup my whole phone, what software should I use? I don't care about what's on the sd card or in the phone nor apps/apk since I can just redownload them. I wanted to backup everything, current firmware, all default HTC stuff, how do I do that?
My phone is not rooted, branded etc. Desire Z, not Vision.
Thanks
Untill your rooted I don't know of a good way, don't think there is one. Once rooted a simple nandroid does that
Sent from my HTC Vision using xda premium
Doesn't HTC Sync do that?
bogdan5844 said:
Doesn't HTC Sync do that?
Click to expand...
Click to collapse
There's no option to simply recover the phone, basically I want an official software so when I just want to go back to my stock ROM I just one-click it and it restores it from their own databse online (the latest available build).
That's a great Sony Ericsson feature. Too bad HTC Sync doesn't have that, or maybe I just can't find it.
demkantor said:
Untill your rooted I don't know of a good way, don't think there is one. Once rooted a simple nandroid does that
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Problem is I can't be rooted until I downgrade which removes my stock rom forever, correct?
stranded.eu said:
Problem is I can't be rooted until I downgrade which removes my stock rom forever, correct?
Click to expand...
Click to collapse
No. Rooting doesn't necessarily involve flashing a new ROM. You can keep it stock. After you downgrade/root, you can flash the official Gingerbread ROM, which is exactly the same as you have now, just rooted and with bloatware removed.
Can you please point me some directions to that official Gingerbread ROM then? It's really hard to find something legit.
stranded.eu said:
Can you please point me some directions to that official Gingerbread ROM then? It's really hard to find something legit.
Click to expand...
Click to collapse
Of course. Here: http://forum.xda-developers.com/showthread.php?t=1169004&highlight=pc10img
This is the official, stock, untouched but rooted ROM for the Desire Z, World Wide Edition. You can find root tutorials in the Dev section. Good luck
My One X Plagued With "Unfortunately The Process com.EVERYTHING Has Stopped" Messages
A few weeks ago my One X started giving me stopped process error messages for, well, for everything. Within 5 minutes of booting the phone up, everything would start stopping. gapps, acore, htc.bg launcher, browser, exchange...everything.
This was on my carrier's stock, ICS ROM, but, since then I've tried a custom JellyBean ROM that I found here. The problem is exactly the same, so I guess it's something deeper....
I've tried factory resets, I've tried with and without a google account linked (as I've read that can be a problem sometimes)....I've cleared cache partition and Dalvik cache....what else can I do?
Is there a "nuclear" option, that's even more intensive a wipe than a "factory reset"?
What else can I try?
Try ARHD 7.2 its basically a stock Rom were as jellybean is a ported version with not much working first I would sugguest flashing back to stock choosing the RUU from your country after your completely stock check for updates then go in bootloader and restore device factory settings don't install any apps until your sure the problem has gone if your still getting problems I would return for repair or replacement
Sent from my HTC One X using xda premium
canna666 said:
Try ARHD 7.2 its basically a stock Rom were as jellybean is a ported version with not much working first I would sugguest flashing back to stock choosing the RUU from your country after your completely stock check for updates then go in bootloader and restore device factory settings don't install any apps until your sure the problem has gone if your still getting problems I would return for repair or replacement
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Okey doke, I'll give that a try thanks. I'll be back with some dumb questions soon, probably.
Actually, here's one to start with: What's RUU?
JimBadger said:
Okey doke, I'll give that a try thanks. I'll be back with some dumb questions soon, probably.
Actually, here's one to start with: What's RUU?
Click to expand...
Click to collapse
I would ask guys from link below I've never had to flash all stock radio and firmware before just know the right ruu is important
http://forum.xda-developers.com/showthread.php?p=25018342
Sent from my HTC One X using xda premium
Erk....I'm stuck.
I downloaded a zip full of stock ROMs (One_X_1.26.114.3_odexed.zip), but I don't know what to do to get just the bits I need from it.
Having done "fastboot oem readcid", I know that I need ORANG001 stock ROM, but not sure how to "cook" it. Or even if I need to.
These are the instructions I'm trying to follow, but it's the "extracted and cooked from right RUU" bit that has flummoxed me....I've looked around for the answer, but can't find a thread that doesn't assume a level of pre-knowledge (or intelligence) that I don't have
Install stock rom of your CID
-fastboot oem readcid (to know your CID)
-all roms are based on x.xx.401.xx , so you need to download the right RUU(that matches your CID) and extract rom.zip to cook a stock rom for you
-flash custom stock rom(extracted and cooked from right RUU) on custom recovery
-fastboot flash boot c:\boot.img (flash stock kernel that's inside custom stock rom boot.img file)
RElock the bootloader (you can allways unlock)
-fastboot oem lock
Right RUU file for your CID
-put your phone on fastboot (it will not boot because you have a custom rom on a locked bootloader)
-now you can run the RUU exe file and upgrade your phone
Click to expand...
Click to collapse
Once I've got the stock ROM bit sorted, I think I'll be okay with the rest! (famous last words)
It tells you to download stock Rom matching your cid then extract it on pc (winRAR) you should get 2 folders one is the boot.IMG and the other is the Rom copy the Rom xxxx.zip to your phone and flash in cwm recovery then fastboot boot.IMG. That's it before updating your phone check stock Rom if its fixed your issues just whack arhd or some think stock based there more reliable
Sent from my HTC One X using xda premium
canna666 said:
It tells you to download stock Rom matching your cid then extract it on pc (winRAR) you should get 2 folders one is the boot.IMG and the other is the Rom copy the Rom xxxx.zip to your phone and flash in cwm recovery then fastboot boot.IMG. That's it before updating your phone check stock Rom if its fixed your issues just whack arhd or some think stock based there more reliable
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Okay, thanks, I get that bit now. But I don't know how to tell which ROM matches my CID...
I've googled phrases like "ORANG001 stock RUU" etc, but every thread seems to lead to a different
Is it likely to be this (for ORANG001): RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_...?
The actual flashing, etc, I'm comfortable with...it's just finding the right thing to flash that is doing my head in.
JimBadger said:
Okay, thanks, I get that bit now. But I don't know how to tell which ROM matches my CID...
I've googled phrases like "ORANG001 stock RUU" etc, but every thread seems to lead to a different
Is it likely to be this (for ORANG001): RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_...?
The actual flashing, etc, I'm comfortable with...it's just finding the right thing to flash that is doing my head in.
Click to expand...
Click to collapse
Ok give me a few hours I'll download and have a look I need to reinstall android SDK first that may take some time
Remember hitting the thanks button would show that you appreciate my time
Sent from my HTC One X using xda premium
Cool, I've thanked each of your posts.
I've tried both of these RUU exe's, but both just end with an "Unknown error"...which obviously isn't very helpful.
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.29.061.11_Radio_1.1204.105.14_release_260736_signed.exe
and
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_release_256475_signed.exe
JimBadger said:
Cool, I've thanked each of your posts.
I've tried both of these RUU exe's, but both just end with an "Unknown error"...which obviously isn't very helpful.
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.29.061.11_Radio_1.1204.105.14_release_260736_signed.exe
and
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_release_256475_signed.exe
Click to expand...
Click to collapse
Have a read thru this thread it may help
http://forum.xda-developers.com/showthread.php?t=1799881&highlight=back+to+stock
I'm still installing android SDK it takes so long :banghead: I'm not sure if I'll get time today if I don't I'll check it tomorrow bit busy tonight :beer::beer::beer::beer:
Sent from my HTC One X using xda premium
canna666 said:
Have a read thru this thread it may help
http://forum.xda-developers.com/showthread.php?t=1799881&highlight=back+to+stock
I'm still installing android SDK it takes so long :banghead: I'm not sure if I'll get time today if I don't I'll check it tomorrow bit busy tonight :beer::beer::beer::beer:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'll have a look, thanks. Enjoy the beers! Have one or two for me.
Omg just got backk its still downloading my firewall was blocking it defo have a look tomorrow
Sent from my HTC One X using xda premium
JimBadger said:
Erk....I'm stuck.
I downloaded a zip full of stock ROMs (One_X_1.26.114.3_odexed.zip), but I don't know what to do to get just the bits I need from it.
Having done "fastboot oem readcid", I know that I need ORANG001 stock ROM, but not sure how to "cook" it. Or even if I need to.
These are the instructions I'm trying to follow, but it's the "extracted and cooked from right RUU" bit that has flummoxed me....I've looked around for the answer, but can't find a thread that doesn't assume a level of pre-knowledge (or intelligence) that I don't have
Once I've got the stock ROM bit sorted, I think I'll be okay with the rest! (famous last words)
Click to expand...
Click to collapse
I'm free now I've just tried to download orange001 but its a filefactory link and I don't have premium account if possible please upload (mediafire.....) Or any were that allows more than 500mb to non premium members and pm the link
Edit: don't need Rom watch video
Sent from my HTC One X using xda premium
Watch this video very quick guide and easy to understand www.YouTube.com/watch?v=SZuAjz4PIjU
And yes for orange001 it is .x61.xx as you mentioned above
Sent from my HTC One X using xda premium