Go back to stock AT&T ROM from Cyanogenmod - AT&T HTC One (M7)

First, let me apologize for my ignorance. Just made the move from the iDevice and am trying to navigate my way through this...
Currently, I have the 05/21/2013 Cyanogenmod nightly on my HTC One. I am having some issues with the call quality. If this weren't my daily driver that I use for work, I would just deal. I like this ROM and it seems to be pretty solid.
My question is, how to I get back to either the AT&T stock ROM, or some variant thereof? I tried flashing TrickDroid and the ROM (found here http://forum.xda-developers.com/showthread.php?t=2242319) using ClockworkMod recovery. Both resulted in the HTC One screen displaying and not moving past that. I was able to restore a backup both times.
I am obviously missing a step, but I have yet to figure it out. Any help would be appreciated.

There's a RUU in the Android development section that will bring you back to stock. be warned, you obviously lose root and it will probably flash stock recovery. RUUs are like iTunes IPSW packages to equate them to something you know.
As for flashing TrickDroid, first boot can take a while, up go several minutes in fact. I haven't had any problems flashing between CM10, ARHD, and TrickDroid aside the occasional Aroma hiccup
Sent from my HTC One

unremarked said:
There's a RUU in the Android development section that will bring you back to stock. be warned, you obviously lose root and it will probably flash stock recovery. RUUs are like iTunes IPSW packages to equate them to something you know.
As for flashing TrickDroid, first boot can take a while, up go several minutes in fact. I haven't had any problems flashing between CM10, ARHD, and TrickDroid aside the occasional Aroma hiccup
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for the reply. I will try TrickDroid again.
Am I correct in flashing the TrickDroid zip from the device using ClockworkMod recovery, or is there a different method I should be using?

ScubaR6 said:
Thanks for the reply. I will try TrickDroid again.
Am I correct in flashing the TrickDroid zip from the device using ClockworkMod recovery, or is there a different method I should be using?
Click to expand...
Click to collapse
I don't think it matters, but I use TWRP to great success.

unremarked said:
I don't think it matters, but I use TWRP to great success.
Click to expand...
Click to collapse
Sounds like you are doing it correctly. Making sure of course that you have a backup if you're having trouble flashing trickdroid you can try clearing your cache and dalvik cache from within recovery. Sometimes it is also useful to wipe your data as well.

TWRP worked like a charm. Not sure why I couldn't get it done with CWM. Thanks for the help guys!

It should work fine no matter what the recovery. I like CWM more than TWRP and my install was clean.
Sent from my HTC One using xda app-developers app

Related

Phone keeps getting stuck at HTC screen.

I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?

Flashing 3g and 4g radios

I am getting ready to root my bolt. I will use the revolution tool.
I want to flash thunderstick genII Rom. In the instructions they say to flash both radios. Is this needed if the phone being rooted has already been updated OTA? Shouldn't the radios be already updated?
Secondly, if it is safe to flash roms with Rom manager, will it know to flash the two radios?
Thanks!
Sent from my ADR6400L using Tapatalk
Radios are flashed in hboot ONLY! Look for a tutorial in the stickied topics
Sent from my TBolt using my f***king thumbs...
From looking at the original post for the thunderstick genII Rom it is a sense gingerbread ROM. It will use "MR2+" radios most likely (please don't make add the disclaimer... I'm not responsible for you turning your phone into a paper weight). They will be MR2 or MR2.5 etc.
Long story short, you should use what the dev. of the ROM suggests for the radio. It typically gives the best performance, least chance of bugs, and best battery life for the ROM. Follow the instructions in the post using HBOOT (Power on with the volume down pressed).
From the original post:
"install these radios
To do so,
1 - Downloaded the "CDMA" first file below to the ROOT of your SDCARD,
2 - Name the file PG05IMG.zip and reboot to your boot loader.
3 - Then follow the the prompts to install the update. Delete the file immediately after reboot.
4 - Repeat these steps for the second file "LTE". And you will have a upgraded radio that will work great with this ROM."
Not sure if the address space is accessible from CWR for radios, so you have to use hboot. It can be dangerous. Follow the steps, and if it is you first time, do the research!!!! There are much more involved guides.
I'm guessing that since radios and roms are flashed in different modes - hboot and recovery - devs can't include radios?
Sent from my ADR6400L using Tapatalk
gcodori said:
I'm guessing that since radios and roms are flashed in different modes - hboot and recovery - devs can't include radios?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
They wouldn't even if they could. There would be so many pissed users it wouldn't be funny. I'd be one of them. Nobody like flashing radios because its a far riskier deal.
Well to get thunderstick going I need to do both radios.
The tuts for flashing radios made it seem like flashing any other thing. Now you have me questioning doing this. This Rom is what I want from my phone...a tweaked sense rom.
If I'm right CWM let's you get to hboot to flash radios, right. And it let's you get to recovery to flash the Rom.
Jeez I came from a iPhone 3g and Jailbreaking was easy compared to this.
Sent from my ADR6400L using Tapatalk
gcodori said:
Well to get thunderstick going I need to do both radios.
The tuts for flashing radios made it seem like flashing any other thing. Now you have me questioning doing this. This Rom is what I want from my phone...a tweaked sense rom.
If I'm right CWM let's you get to hboot to flash radios, right. And it let's you get to recovery to flash the Rom.
Jeez I came from a iPhone 3g and Jailbreaking was easy compared to this.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
For some reason I've notice a lot of people calling RomManager by "CWM" lately and for some reason it annoys me. ClockworkMod is the "company name" Koush uses to identify his apps/products. The app you are referring to is RomManager and the recovery is called ClockworkMod Recovery.
Anyway, neither CWR nor RomManager deal with hboot. You can place the file on your sdcard and manually boot to hboot (Pwr+VolDwn or the advanced power menu in some roms). Full instructions for this should not be needed here since they are all over the place including the pinned Q/A thread at the top of this subforum: http://forum.xda-developers.com/showthread.php?t=1220484
I'm sure this will come off harsher than it was intended. I just wanted to throw those things out there. Anyway, welcome to Android
Absolute_Zero said:
For some reason I've notice a lot of people calling RomManager by "CWM" lately and for some reason it annoys me. ClockworkMod is the "company name" Koush uses to identify his apps/products. The app you are referring to is RomManager and the recovery is called ClockworkMod Recovery.
Anyway, neither CWR nor RomManager deal with hboot. You can place the file on your sdcard and manually boot to hboot (Pwr+VolDwn or the advanced power menu in some roms). Full instructions for this should not be needed here since they are all over the place including the pinned Q/A thread at the top of this subforum: http://forum.xda-developers.com/showthread.php?t=1220484
I'm sure this will come off harsher than it was intended. I just wanted to throw those things out there. Anyway, welcome to Android
Click to expand...
Click to collapse
Thank you for laying all that out there. I really cannot endorse what Absolute_Zero has to say about calling things by their proper names. When people don't do that, it gets VERY confusing when you try to help them.
Concerning ROM Manager, I don't see how it serves any useful purpose. Fixing permissions can be done just as well through a script like ScriptFusion or ClockworkMod Recovery. I know of no ROM dev that endorses flashing, wiping, backing up, or recovering through ROM Manager, which is a nice way of saying DO NOT USE ROM Manager. It's fairly reliable for flashing recoveries, but I've had issues with it even doing that right.
Just follow the instructions I've laid out for flashing radios. I've included all the links to every radio there. If you follow my directions, I can promise you with 99.9% certainty that your radio flash will go perfectly. It's nothing to be afraid of and nothing to really concern yourself with. Just don't go looking for the easy way of doing everything. This isn't a Motorola device and there's a lot more you can do outside of an app than with an app.
Actually being harsh is cool. When I said CWM I meant the recovery. I should have been more clear.
I will stay away from Rom manager and learn to flash the big boy way.
My last question is this...my SD card is pretty messy. What is the best advice to clear out the card after flashing thunderstick?
Sent from my ADR6400L using Tapatalk
gcodori said:
Actually being harsh is cool. When I said CWM I meant the recovery. I should have been more clear.
I will stay away from Rom manager and learn to flash the big boy way.
My last question is this...my SD card is pretty messy. What is the best advice to clear out the card after flashing thunderstick?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
The best way is to clean it up before flashing. Some ROMs install directories to the SDcard, but those should be clearly named. There's not really anything there that you can do that will render the phone junk. For me, it's just been a process of sorting through all the stuff, backing it up, formatting the card, and dropping the stuff I do want back on it.
Is there an option to format the SD card during flashing?
I have backed up my photos and any documents. After I copy over any videos I took, I would clear it out.
After installing a dozen or more apps, the card looks like a mess.
There's three folders with music in it, etc. Why can't there be an app folder with subdirectories for each app?
Sent from my ADR6400L using Tapatalk
gcodori said:
Is there an option to format the SD card during flashing?
I have backed up my photos and any documents. After I copy over any videos I took, I would clear it out.
After installing a dozen or more apps, the card looks like a mess.
There's three folders with music in it, etc. Why can't there be an app folder with subdirectories for each app?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
You can format it either in CWR, Android, or on a computer.
Rooted today with revolution. Pretty easy but it didn't install clockwork. Had to run it again. I noticed Rom manager doesnt recognize clockwork as installed. I wasn't planning on using Rom manager but was curious about this.
One last question before flashing thunderstick...if something fails and I revert to the nandroid backup, does that revert back to the old radio? I need to flash both radios and want to know if I can fall back to the backup if it fails.
Thanks.
Sent from my ADR6400L using Tapatalk
gcodori said:
Rooted today with revolution. Pretty easy but it didn't install clockwork. Had to run it again. I noticed Rom manager doesnt recognize clockwork as installed. I wasn't planning on using Rom manager but was curious about this.
One last question before flashing thunderstick...if something fails and I revert to the nandroid backup, does that revert back to the old radio? I need to flash both radios and want to know if I can fall back to the backup if it fails.
Thanks.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Nandroid backups don't include radios.
gcodori said:
Rooted today with revolution. Pretty easy but it didn't install clockwork. Had to run it again. I noticed Rom manager doesnt recognize clockwork as installed. I wasn't planning on using Rom manager but was curious about this.
Click to expand...
Click to collapse
RomManager will only recognize CWR as being installed if RomManager itself is what was used to flash it.
I'm dealing with this same thing (flashing Radios). I recently rooted my device (after having it since release) and froze the bloat. I never flashed a ROM and want to look to see if it's possible to find a ROM for my Thunderbolt that does not need me to change the Radio. If I don't Flash a ROM I'm more than happy with having root and dealing with the crapware and installing apps I couldn't use before. Good Luck. Enjoy your device.
Sent from my ADR6400L using xda premium
davidstech11 said:
I'm dealing with this same thing (flashing Radios). I recently rooted my device (after having it since release) and froze the bloat. I never flashed a ROM and want to look to see if it's possible to find a ROM for my Thunderbolt that does not need me to change the Radio. If I don't Flash a ROM I'm more than happy with having root and dealing with the crapware and installing apps I couldn't use before. Good Luck. Enjoy your device.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
What's you apprehension about flashing a radio?
I flashed the 802 radio right after installing NonS3ns3v2 on my Tbolt. Everything went fine and seems to be running smoothly.

[Q] Does anyone have the stock rom in a flashable zip?

I'm looking for something I can flash through recovery, not the ruu that you have to change to pmg.zip whatever. I've tried doing this and i can't seem to ever get it to work.
When you renamed the zip are you positive you renamed it to just .zip and not .zip.zip? So many people have a problem with this, as windows will not show the file type and they add .zip to the end. In reality the file was already named .zip at the end to begin with.
That being said there are some pretty clean stock-ish ROMS you can flash. Most just have been cleaned up a bit and a few minor tweaks added. I know lots of people like Fresh as his ROM is a cleaned up Stock type ROM.
If I remember in the morning, I'll link to something for you. Go back several pages in the cdma dev section if you're on CDMA. There's a thread for it.
Sent from my PG86100 using XDA App
Yeah I'm pretty sure I've never done the .zip.zip thing. I have a Mac and I've changed it with Astro and its never worked. Is there something I'm missing?
I always go into recovery, wipe everything, and then boot back into hboot, wait for the pmg.zip to load, it says it was successful, and then when I reboot it gets stuck at the HTC screen. I have to pull the battery and go back into recovery to flash something.
did you not make a stock nandroid?
maybe these
http://forum.ppcgeeks.com/htc-evo-3...ck-rooted-htc-evo-3d-shooter-odex-deodex.html
Mr.Esp said:
maybe these
http://forum.ppcgeeks.com/htc-evo-3...ck-rooted-htc-evo-3d-shooter-odex-deodex.html
Click to expand...
Click to collapse
Thanks that's perfect!
z50king said:
did you not make a stock nandroid?
Click to expand...
Click to collapse
I did.... but I wanted to try starting from scratch again.
go to scottsroms.com and he has all the stock roms like the ruu and zip.
I started over a week ago and I had to relock phone then run the ruu and all went well. I then rerooted to a stock rooted rom. Remember you have to relock before running the .zip stock rom.
i have my unlock code stored on my cpu so all i had to do is half the steps on HTC DEV. There is a walk thru on here somewhere to walk you thru unrooting the htc way.

Evo 3d won't boot past HTC screen

Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.

Help. Applying the OTA update?

I've asked for help in the threads posted about the OTA update and I cannot get the help I need. I've seen people post similar questions that I have and they are largely ignored. I had to stay away from the forums because I was getting so damn angry.
I have root and I have S-Off. I have not flashed any ROMs on this phone. I want to apply the OTA update but I do not know how to do that.
There's mentions of flashing firmware, radios, PRIs, PRLs, ROMs, Deoxed, Oxeded, hboot, bootloader, recovery, TWRP, etc. All of that across multiple threads does not compute well in my head.
I've read a lot and I am not sure what to do. Can someone please help me out? I will be forever grateful. I could send you a case for your phone for helping me. I promise I am not being lazy. I'm just not getting it.
If you're rooted and you have S-Off, you should have TWRP. First verify that by booting into the bootloader (Power + Vol Down) and going to Recovery.
Once in TWRP, do a backup. Backup everything. This way if something goes wrong you can restore your previous ROM.
Next download this: http://d-h.st/d2a
It's the firmware zip, courtesy of Haus. Rename the file to remove all of the stuff after PJ85IMG. Then put it on the root of your SD card and boot into the bootloader. It will scan for a zip and find it, and ask you if you want to update. This step is optional; you can flash new 1.22 ROMs without the new firmware.
After flashing that through bootloader, you can choose a 1.22 ROM that looks good to you, and download it. Boot back into TWRP, do a factory reset and wipe System, and then install the ROM. If you download it to your external SD card (in other words, an SD card you put in yourself), you'll have to mount it by going to Mounts and choosing external SD. That way you'll be able to access files on it.
To install the ROM after wiping, just hit Install from the main menu of TWRP and navigate to the location of the ROM zip you downloaded. Install it and reboot, and there you have it, you're on the new firmware and using a ROM with the new fixes in it!
The firmware zip is optional, but recommended. If you aren't comfortable flashing it, don't bother.
Sent from my EVO using xda premium
SoraX64 said:
If you're rooted and you have S-Off, you should have TWRP. First verify that by booting into the bootloader (Power + Vol Down) and going to Recovery.
Once in TWRP, do a backup. Backup everything. This way if something goes wrong you can restore your previous ROM.
Next download this: http://d-h.st/d2a
It's the firmware zip, courtesy of Haus. Rename the file to remove all of the stuff after PJ85IMG. Then put it on the root of your SD card and boot into the bootloader. It will scan for a zip and find it, and ask you if you want to update. This step is optional; you can flash new 1.22 ROMs without the new firmware.
After flashing that through bootloader, you can choose a 1.22 ROM that looks good to you, and download it. Boot back into TWRP, do a factory reset and wipe System, and then install the ROM. If you download it to your external SD card (in other words, an SD card you put in yourself), you'll have to mount it by going to Mounts and choosing external SD. That way you'll be able to access files on it.
To install the ROM after wiping, just hit Install from the main menu of TWRP and navigate to the location of the ROM zip you downloaded. Install it and reboot, and there you have it, you're on the new firmware and using a ROM with the new fixes in it!
The firmware zip is optional, but recommended. If you aren't comfortable flashing it, don't bother.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you Sora! I am going to follow your advice this afternoon and will let you know how it goes.
http://forum.xda-developers.com/showthread.php?t=1770501
This way will not cause you to lose any data, and installs the update on top of what you already have. Still recommend a backup in TWRP first, though
Robbie_G said:
http://forum.xda-developers.com/showthread.php?t=1770501
This way will not cause you to lose any data, and installs the update on top of what you already have. Still recommend a backup in TWRP first, though
Click to expand...
Click to collapse
I would personally recommend staying away from that method. As a rooted user you should never accept an ota. Doing it that way might work this time, but in the future there's no guarantee you won't lose s-off and never be able to get it again
Sent from my EVO using Tapatalk 2
Rxpert said:
I would personally recommend staying away from that method. As a rooted user you should never accept an ota. Doing it that way might work this time, but in the future there's no guarantee you won't lose s-off and never be able to get it again
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I know "never OTA" is your and some other people's mantra, but being able to do this is one of the benefits of S-off. I agree it is possible they could turn you back to S-ON in a future OTA (maybe...), but since it works for this current update, I don't think you should be dissuaded if you don't want to completely wipe your phone.
Robbie_G said:
I know "never OTA" is your and some other people's mantra, but being able to do this is one of the benefits of S-off. I agree it is possible they could turn you back to S-ON in a future OTA (maybe...), but since it works for this current update, I don't think you should be dissuaded if you don't want to completely wipe your phone.
Click to expand...
Click to collapse
It's a bad habit to start, and all he has to do my way is flash a ROM..
Sent from my EVO using xda premium
SoraX64 said:
It's a bad habit to start, and all he has to do my way is flash a ROM..
Sent from my EVO using xda premium
Click to expand...
Click to collapse
My man.
Exactly.
Just look at all of the people who show up on here going "Oh crap I took the OTA and now I can't get S-OFF"! The fact of the matter is, people don't check here before taking the OTA. If they look here and see that thread that says to just put on teh stock recovery and you're A-OK, thats what they'll do from then on.
When it happens, I'm just going to sit back and say "toldya so"... and let everyone else deal with the support. Until then, I'm going to keep preaching that you should never take an OTA if you are rooted or EVER thinking about rooting.
Sora, I looked at your instructions. I flashed ROMs before on my EVO 4G. That process I was comfortable with. Basically, the developer did all the work for me. I wanted to keep my phone stock for a while but I do want the updates.
cubbieswin said:
Sora, I looked at your instructions. I flashed ROMs before on my EVO 4G. That process I was comfortable with. Basically, the developer did all the work for me. I wanted to keep my phone stock for a while but I do want the updates.
Click to expand...
Click to collapse
It really comes down to this, if you're still having problems:
If you have recovery, just flash a ROM with the new base. Just like you'd do on your old Evo.
Sent from my EVO using xda premium
SoraX64 said:
It really comes down to this, if you're still having problems:
If you have recovery, just flash a ROM with the new base. Just like you'd do on your old Evo.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Ok, so I will have to flash a ROM. Do you think I can flash the deodexed version of this [ROM][STOCK] --- Stock Rooted 1.22.651.3 Odexed & DeOdexed (7/14/12)--- over my stock-from-Sprint setup?
I flashed TWRP. I'm going to update the firmware next with the file you pointed me to. I'm trying to find the info on clearing Google wallet.
...then the ROM.
Clearing GW data should say something about resetting it. It'll be in the app settings.
Seems like you've got it down now, I'm glad to say. You'll be able to flash that ROM without any issues.
Sent from my EVO using xda premium
SoraX64 said:
Clearing GW data should say something about resetting it. It'll be in the app settings.
Seems like you've got it down now, I'm glad to say. You'll be able to flash that ROM without any issues.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Sora, how do you flash your ROMs? Do you use TWRP? or something like Goo Manager? I haven't used Goo Manager before, but I see it flashes ROMs.

Categories

Resources