Simple guide to [VM firmware recovery thread] v2 - HTC EVO 3D

Please go here now: http://forum.xda-developers.com/showthread.php?t=1653777
Mods should unsticky mine and sticky that instead.

Go to the above link if your a victim of virgin mobile firmware.

since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?

hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
So you have no data at all? I'd try a ##data# reset first.

hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
Never assume. Just because VM has a different firmware, that doesn't mean that Sprint 3d's will too. We do not fully know what the differences are between the 2 devices.
Thus the reason for this and other fix threads. I would suggest trying this fix, and see if it helps, and hope that there is a firmware fix in the future.

I will tell you how I restored my data. I first downloaded the following stock rom.
Stock 2.08.651.2 With HTC/Sprint Spyware Removed
http://forum.xda-developers.com/showthread.php?t=1285975
After flashing to the stock rooted rom above I then went into my dialer and typed in ##my MSL number# (Example: ##000000#) To get your MSL number simply download MSL reader from the market. I then clicked on edit and then edited my MDN with all zeros and MSID with all zeros. I pressed the menu button and then pressed reset. After the phone rebooted the phone activation screen came up when I unlocked the phone and it was able to automatically activate it and I got 3G data.

jlechner said:
So you have no data at all? I'd try a ##data# reset first.
Click to expand...
Click to collapse
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.

hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?

hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
Hockey, I have not seen this issue yet on my rom, PM me if you want to try mine, and let me know if you see any difference. I wonder if some of the SMS issues have to do with the ICS rom itself. BTW do not post my ROM anywhere as I do not release my stuff public, just want to help out a fellow hardcore flasher.
Cheers

jlechner said:
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
Click to expand...
Click to collapse
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue

Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.

hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Touch base with Mikey.

hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.

This thread can't be deleted. This has good info we need up.
I know it says Chad in it, but should we just take the name out?
Well, if we did, then we won't give credit where it's due.
Anyways,
Is there any general thought on the rough percentage of people this works 100% for?

Mikee4fun said:
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
Click to expand...
Click to collapse
is there a way to get to 1.42_003?

Thank god there's another one of these!
Ok so I got back from sprint again and the were totally in awe and had no idea whatsoever was wrong with my phone They ordered me a new one and it'll be here on like tuesday or wednesday and i'll see if I can get it not activated already.
Btw the sprint people are totally dumb.... They were talking to a couple and saying yeah, the more storage a phone has the faster it'll be! He said that 32gb phones out performed 16gb phones.... I was like wtf man... Also he was trying to sell them the galaxy s 2's and was telling them that they're new phones. Wtf sprint salesman, wtf...

hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
The 005 mod is actually 003, from my understanding.
Sent from my Sprint/Virgin Mobile hybrid.

jlechner said:
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
Click to expand...
Click to collapse
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.

hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
Yes, you need to go through the adb push process stated in the OP. I can assist you if you want through team viewer if you don't want to tackle it.

Unknownforce said:
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
Click to expand...
Click to collapse
Cool thanks!
Sent from my Sprint/Virgin Mobile hybrid.

Related

Whoa way over my head!! TP Verizon Rom!

OK i have done some searching and this sounds like a good one. http://forum.xda-developers.com/showthread.php?t=461524
Then i want to make shure i can get it back to the original rom i have right now so in case it breaks. this it? http://forum.xda-developers.com/showthread.php?t=427507&highlight=dump
Then do you guys know if in this rom it already has gps unlocked or do i have to do the bored thing? http://forum.ppcgeeks.com/showthread.php?t=49933
Then this is my first time doing this. is there anything else i am missing?
First, have you unlocked your phone? This is a must!!
Second, you do have to follow the steps from bored to unlock the GPS.
Third, check out bored's ROMs and kitchens on this forum. Updated today!!
Also, you can revert back to the original ROM and re-lock your phone if neccasary. So no worries. Also, for better signal strength you can also try a new radio (sticky on ppcgeeks). May not help but if you have weak service now, these could give you more bars and extend your battery life.
OH, and if your still on the stock ROM....WOW. You are about to LOVE your phone!! Its like a different phone with a custom ROM, SOOOO much faster
stanglifemike said:
OH, and if your still on the stock ROM....WOW. You are about to LOVE your phone!! Its like a different phone with a custom ROM, SOOOO much faster
Click to expand...
Click to collapse
AMEN!!!!!!
stanglifemike said:
OH, and if your still on the stock ROM....WOW. You are about to LOVE your phone!! Its like a different phone with a custom ROM, SOOOO much faster
Click to expand...
Click to collapse
ya i dont have a rom installed yet and i want a guide on how to install.
So first i have to unlock. Can it be relocked for warrenty.
Then i have to install the rom i have above. Can i install it back to the original rom on my touch pro. and if so how?
then i have to do the bored thing. Can i make so gvps is locked again?
I want to be able to have a new rom but i also want to be able to return it to normal for warrenty.
ReaperBoy said:
ya i dont have a rom installed yet and i want a guide on how to install.
So first i have to unlock. Can it be relocked for warrenty.
Then i have to install the rom i have above. Can i install it back to the original rom on my touch pro. and if so how?
then i have to do the bored thing. Can i make so gvps is locked again?
I want to be able to have a new rom but i also want to be able to return it to normal for warrenty.
Click to expand...
Click to collapse
I am not too familiar with XDA myself but PPCGeeks I would say is a better resource for your Verizon TP. I will post a few links that answer every one of your questions but you'll have to do a little reading yourself......
Unlocking and Relocking for Warranty Repair
Guide To Flashing
lllbored GPS Fix (very easy to do and includes the cab to revert if necessary)
Thread About RELOCKING for Warranty
In my Opinion these are all very easy things to accomplish as long as you made sure you READ the instructions throughly before attempting. Good Luck!
If i have a data connection will that get charged like double when i reastivate my phone? and were and how would i get my rom back to stock?
ReaperBoy said:
If i have a data connection will that get charged like double when i reastivate my phone? and were and how would i get my rom back to stock?
Click to expand...
Click to collapse
Stock CDMA ROMS
Not sure why you would think your Data plan would double???? I havent had any issues with my data plan changing except when buying a new device and they "assume" you want the Enterprise plan. As long as you made sure Verizon set you up on the $29.99 plan in the first place then it shouldnt change to my knowledge....... DONT CALL VERIZON AND TELL THEM THAT YOU UNLOCKED/FLASHED YOUR PHONE , lol.
Your data plan will be fine. Just dont do a lot of tethering if your plan isnt unlimited. Data usage will be the same as before though
GrandMasterB said:
Stock CDMA ROMS
Not sure why you would think your Data plan would double???? I havent had any issues with my data plan changing except when buying a new device and they "assume" you want the Enterprise plan. As long as you made sure Verizon set you up on the $29.99 plan in the first place then it shouldnt change to my knowledge....... DONT CALL VERIZON AND TELL THEM THAT YOU UNLOCKED/FLASHED YOUR PHONE , lol.
Click to expand...
Click to collapse
Lol no i am not that stupid! and all i see for verizon is the leaked rom? i dont knwo if i want to use this.
ok unlocking seems very easy. But now the flashing WOW. I wish there was a video tut for this because this seems pretty easy to screw %$#@ up. Could some one possibly make one?
ReaperBoy said:
Lol no i am not that stupid! and all i see for verizon is the leaked rom? i dont knwo if i want to use this.
Click to expand...
Click to collapse
Little history about that , bout 6 months ago I was helping someone in the CrackBerry forums flash a leaked beta on their Curve , they got confused , called Verizon for help flashing and of course were told that they had Violated customer agreements and the device warranty and how they were going to burn in hell for sinning against Verizon. This person then comes back to the forums furious at everybody that had been trying to help because WE had "voided" their warranty. Just wanted to make sure you werent going to do the same and be mad at me
That ROM is the leaked SHIP Rom that comes on the Verizon TP. Double check your Settings/System/Device Information if your not sure. Like I said in the post I linked above ,I have unlocked , flashed (MANY TIMES) and relocked and flashed the Verizon leaked rom so I could send it back and had NO issues whatsoever.
EDIT : Flashing a new rom is just as easy as unlocking was. Which ROM have you chosen for your first one??
GrandMasterB said:
Little history about that , bout 6 months ago I was helping someone in the CrackBerry forums flash a leaked beta on their Curve , they got confused , called Verizon for help flashing and of course were told that they had Violated customer agreements and the device warranty and how they were going to burn in hell for sinning against Verizon. This person then comes back to the forums furious at everybody that had been trying to help because WE had "voided" their warranty. Just wanted to make sure you werent going to do the same and be mad at me
That ROM is the leaked SHIP Rom that comes on the Verizon TP. Double check your Settings/System/Device Information if your not sure. Like I said in the post I linked above ,I have unlocked , flashed (MANY TIMES) and relocked and flashed the Verizon leaked rom so I could send it back and had NO issues whatsoever.
EDIT : Flashing a new rom is just as easy as unlocking was. Which ROM have you chosen for your first one??
Click to expand...
Click to collapse
all right and then when i am unlocking you get the screen on your computer with a picture of the touch pro and it has you accept the agreements. i have not done this yet but what does that do because it does not seem like that is the unlocker.
Damn this seems harder then putting custom firmware on a psp wich i did with ease.
ReaperBoy said:
all right and then when i am unlocking you get the screen on your computer with a picture of the touch pro and it has you accept the agreements. i have not done this yet but what does that do because it does not seem like that is the unlocker.
Damn this seems harder then putting custom firmware on a psp wich i did with ease.
Click to expand...
Click to collapse
I have had 3 different PSP's and never dared flashed the firmware on one , lol , but this is EASY. All you have to do is litterally follow the onscreen instructions.
GrandMasterB said:
I have had 3 different PSP's and never dared flashed the firmware on one , lol , but this is EASY. All you have to do is litterally follow the onscreen instructions.
Click to expand...
Click to collapse
ok that part seems really easy. but the flashing part? http://forum.ppcgeeks.com/showthread.php?t=43266
I am looking at this one and it has alot of words and i was reading and i dont get when you put the rom in.
this is were i get lost
3.then in the newly created RUU directory add the rom of your choice - (copy the RUU_Signed.nbh to desktop\RUU)
4.Place phone in bootloader mode (power button while holding volume down button)
5.open the ROMUpdateUtility.exe
6.follow the RUU on screen instructions from there
Oh and i just for fun did the power and down volume key and i went to the 3 color thing and it says security unlocked and i dont think i unlocked it yet......
ReaperBoy said:
ok that part seems really easy. but the flashing part? http://forum.ppcgeeks.com/showthread.php?t=43266
I am looking at this one and it has alot of words and i was reading and i dont get when you put the rom in.
this is were i get lost
3.then in the newly created RUU directory add the rom of your choice - (copy the RUU_Signed.nbh to desktop\RUU)
4.Place phone in bootloader mode (power button while holding volume down button)
5.open the ROMUpdateUtility.exe
6.follow the RUU on screen instructions from there
Oh and i just for fun did the power and down volume key and i went to the 3 color thing and it says security unlocked and i dont think i unlocked it yet......
Click to expand...
Click to collapse
and i have been reading and i think i take the ruu thing in my roms folder and put it into the RUU folder on my desktop?
ReaperBoy said:
and i have been reading and i think i take the ruu thing in my roms folder and put it into the RUU folder on my desktop?
Click to expand...
Click to collapse
That is dependant on which ROM you choose......... which rom did you choose?
Most roms are alot easier than that now.
EDIT** If it says .35 cmonex in bootloader then it IS unlocked. Nothing against XDA but for your CDMA Touch Pro you reallly need to be over at PPCGeeks for this. That Crossler post you linked to hasnt been updated for 3 months now. Crosslers Kitchen on PPCGeeks was updated yesterday , just a thought

Accept T-Mobile Update?

My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.

[Q] How can I Factory Restore?

I have an unrooted HTC Aria (AT&T) that i upgraded to Froyo a couple of weeks ago. I have been using it for a while and i don't like the performance with the new upgrade, it used to be a LOT snappier before.
I would like to know if its possible to revert the phone to Factory Defaults (Eclair 2.1) and where i can get the ROM since HTC is no longer providing it in its website.
I'm not interested in rooting my phone nor custom roms i just want it the way it was at the moment I took it off the box and turned it on for the first time.
If the downgrade is possible I would really appreciate if someone could provide a list of steps to follow to make it happen.
Thanks in advance.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
http://www.mediafire.com/?cj56c2gfk86k8oe
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Theonew said:
Nope. Not possible since you don't want to root your device.
Click to expand...
Click to collapse
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
drumist said:
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
Click to expand...
Click to collapse
That post I made was a mistake. That's why I edited it. Sorry I didn't get to change it in time.
Theonew said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
Click to expand...
Click to collapse
To be honest the advice from those threads is not really very good anyway. You don't need temp root on your device. There are easier methods that ought to work fine. Namely, just putting the 2.1 RUU zip as LIBEIMG.zip on your SD card. But from what I've read, even just running the RUU should be enough.
(Nevermind, this doesn't work.)
Thanks for you advice, in fact did some research before creating the thread, but all the threads i found were about people who wanted to downgrade to get the root back, so they were either redirected to other threads or were given a lot information not relevant to what i really need.
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
eljuanpelos said:
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
Click to expand...
Click to collapse
Don't give up yet. This next method should work if that one didn't.
Download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
drumist said:
Don't give up yet. This next method should work if that one didn't.
Download this file:
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
Click to expand...
Click to collapse
Unfortunately this method doesn't work either, it throws an error that says "Main Version is older, Update Fail!"
I could have sworn I've read about this working before. I would have tested it first myself but I don't have a phone that isn't S-OFF. Sorry for making you jump through hoops.
You could try the methods in the other threads linked above. I guess you do need temp root to do a downgrade.
Alternatively, you could use AlphaRevX to S-OFF, install Clockwork, and install the factory original, unrooted ROM. The downside of this is that it requires voiding your warranty if you have one.
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Optic2 said:
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Click to expand...
Click to collapse
He wants to return to android 2.1 so that wouldn't help whatsoever. Plus he already did that which is why he wants to downgrade.
Oh my bad, I didn't read the whole thread. Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Optic2 said:
Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Click to expand...
Click to collapse
This is the reason which he said in his post:"I don't like the performance with the new upgrade, it used to be a LOT snappier before."
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
One question... I have HTC Gratia, which is operator free, so can I restore your original (backuped) ROM on my phone and update it, so I can use it just like original one?

Does anyone know....

I'm just wondering, I purchased a phone on ebay (not knowing it was flashed/rooted). The boot animation says "clean rom" so after researching this site and the forums for this device, I see that it's probably a rom you guys are familiar with and it seems to be ICS based (from what I can see). With that being said, does this mean when they actually RELEASE the stock ICS that I probably won't get the update to my phone? Because I really would like to see what their stock version will be like. Can anyone answer that question or has it even been asked before?
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
mighty_markus12 said:
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
Click to expand...
Click to collapse
So does this mean I will no longer be able to receive updates to my phone with this "s-off" or what ever? That sucks, and I can't seem to follow the steps that have been given to get it back to a stock rom or "ruu" what ever THAT means. lol ****that moment when you realize you might look dumb or "newbish" for posting what you just posted****
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
cpurick said:
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
Click to expand...
Click to collapse
To be honest, the only thing I really want is to be able to get it stock on the basis of the apps, getting system updates etc. I'm not concerned with it having evidence of being "tampered with" "hacked" or "rooted". lol It already says "re-locked" The problem is the instructions I've gotten on here seem to go over my head. I might have to be walked through it like a little 3 or 4 year old being taught to sound out little words for the first time. lol Hey, I'm just saying..... No seriously though, I have a MAC and all of the instructions here seem to be based on having a PC
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
cpurick said:
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
Click to expand...
Click to collapse
So this means I'll need to basically need to take or send it to someone to get this done? I don't know why all of these instructions seem like their in spanish to me now, about 3 years ago I used to flash and unlock WM devices almost every other day. I guess I should've never stopped, but once the g1 came out and switched to android devices I stopped flashing and now I'm lost because I need to "tamper with" my phone again, but can't seem to get going at all. I mean SERIOUSLY, I used to flash WM devices so often that if a certain period of time went by without me finding a rom worth "flashing" I'd start having withdrawals. Now i'm feeling like an absolute IDIOT when it comes to getting into these android devices. I think part of that has to do with the fact that I only had PC's and now not only am I trying to tamper with android for my first time, but I only have mac computers as well.
Go to settings, about phone, software information, more, and write what your baseband version is.
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Unless you have issues, I would leave it as is for the time being. Take time to learn how to do all the stuff you need to do.
The custom ROMs really do make the phone better, you may find you want to keep it in the end. Battery life is much better on a good ROM.
When the official update comes out, we will have a new ROM based on the update within a day or two at most of the release anyway.
The baseband (the radio firmware) is also important. And unfortunately we can not downgrade to older basebands due to not having S=off. So if you are on the newest leaked version then you can run the old stock software.
BTW S=off (or S=on) is a security flag located in the firmware. S=on limits what parts of the phone you can flash and change. S=off gives you full access, it will allow you to downgrade as well. S=off also makes it easier to brick your phone because it does let you change software that is bootstrap essential, the baseband and hboot (sort of like BIOS) for example.
I separate the idea of bootstrap from boot. Most people associate booting with the OS, but bricking effects the firmware initializing the hardware that allows the OS to load and boot. So you get to see the old school term used.
Kennnny1 said:
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
The baseband is 1.22.10.0310r, 1.22.10.0308r It also says clean rom 4.1. I don't mind waiting until an offcial ics is released, but I will I be able to receive THAT instead having to have a "dev equivalent" version is what I'm wondering....
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
cpurick said:
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
Click to expand...
Click to collapse
Well, I've kind of decided to just keep what I have. I don't have any issues other and it seems to run smoothly. What I REALLY want to see is what the official update will be like as being "stock released" when it comes out and was concerned that I might not be able to get the update because of the "clean rom" I have now being ICS based (as far as I can see). Other than that, I'm fine until then.
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
mdunn1066 said:
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
Click to expand...
Click to collapse
Good point, I mentioned it in the feeback portion and rated him low on the "item described accurately" portion
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
stelv said:
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
Click to expand...
Click to collapse
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
refuse2bstopped said:
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
Click to expand...
Click to collapse
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
nosympathy said:
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
Click to expand...
Click to collapse
Yes, I'm VERY interested, I'm not worried much about the data wipe, between what's backed up to my google account and my SD card, I'll be fine with a data wipe. My battery life is also HORRIBLE for some reason with this rom, but since I've not had it stock yet, I guess I can't REALLY say it's good or bad. But my Droid Bionic's battery life was at least twice as good as this phone's seem to be and I don't use it any more than I did the Bionic.
I will tell you right now the battery life will most likely get worse if you go to stock.
Now if the person who sold it installed a custom kernel rather than the one Scott includes in his ROM (scott makes clean ROM) then battery life could be worse than it should be.
Second, this is a 4.3 inch HD screen... it eats battery like a starving animal.
Third, try cleanROM developers edition (a very striped out cleaned up stock based ROM) or cleanROM senseless. I am running cleanROM developers edition and I get double to triple the battery life over stock.
Unless I actually use the phone... When I use it a lot, I do not get that big of a jump. When using the phone the battery life will be similar due to the screen and CPU use remains similar to what stock would be. (which you would expect, the screen will always use the same power, same for CPU) Its when the phone is in standby mode that you see the real gains. Because all the extra junk that is in the stock software is pulled out and isn't constantly running in the background, waking the phone, starting the cell radio to phone home, etc.
Senseless and the Developers edition have their quirks caused by removing so much of the stock sense based apps and functions and replacing with AOSP versions. Thinks like the caller ID not showing up on the screen until you unlock the phone because the sense phone/dialer can not talk to the AOSP lockscreen. Nothing major just different.

[Q] Flashed Revolution HD and all incoming calls go to voicemail on AT&T M8

Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.

Categories

Resources