Need confirmation that I won't brick my phone - HTC Droid DNA

I'm about to install Avast Anti-Theft on my phone. I went to the Avast app, went through the process of creating the update.zip folder that needs to be installed via recovery because of the secure NAND filesystem, and I'm about to install it.
I went into TWRP, pressed Install, selected update.zip, and I'm ready to install it.
I got TWRP's message that installing incompatible software might brick my phone. I know that this message displays for everything, but this stage in the rooting process wasn't explained to me fully. This feature only installs (i.e. forces the system to accept the installation of) software, so I'm good using this method to install the zip archive, correct?

M0rtiferrimus said:
I'm about to install Avast Anti-Theft on my phone. I went to the Avast app, went through the process of creating the update.zip folder that needs to be installed via recovery because of the secure NAND filesystem, and I'm about to install it.
I went into TWRP, pressed Install, selected update.zip, and I'm ready to install it.
I got TWRP's message that installing incompatible software might brick my phone. I know that this message displays for everything, but this stage in the rooting process wasn't explained to me fully. This feature only installs (i.e. forces the system to accept the installation of) software, so I'm good using this method to install the zip archive, correct?
Click to expand...
Click to collapse
The worse that could happen is your ROM won't boot but your phone still will. S-on makes it to where what we flash can't access what would completely screw our phones up. Its a gift and a curse lol
Sent from my HTC6435LVW using Tapatalk 2

I see. So as long as the S flag is on, it's impossible to truly brick your phone?

M0rtiferrimus said:
I see. So as long as the S flag is on, it's impossible to truly brick your phone?
Click to expand...
Click to collapse
No, you can defintly brick your phone with s on. A number of people have bricked it while unlocking their phone.
Sent from my HTC6435LVW using xda app-developers app

In the att one x forums people brick theirs by flashing intl one x roms. And we have s-on

omario8484 said:
In the att one x forums people brick theirs by flashing intl one x roms. And we have s-on
Click to expand...
Click to collapse
I don't see how since a Rom flash doesn't access the hboot at all if youre s-on. Are you sure they werent soft bricks?
Sent from my HTC6435LVW using Tapatalk 2

Related

[Q] HTC EVO 3D CDMA bricked?

Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Daaaavinnn said:
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Click to expand...
Click to collapse
Were you able to reflash a kernel or the stock ROM?
I couldn't flash ANYTHING. -_-
Sent from my GT-I9100 using XDA App
I made the mistake of flashing one of the stock roms derived from RUU which was a big mistake since it flashed the hboot I no longer have revolutionary which lead me to not being able to fastboit anything. I can get the adb to.connect to the device while in recovery with system mounted. but that's pretty much it. If i install a custom ROM when I reboot revolutionary will see device but not ling enough to.root and install the drivers. Just setup your pc to use fastboot otherwise you might do the same thing I did. After two days of searching trying different things my fix was going and buying a new phone last night.
Sent from my PG86100 using XDA App
mteezey said:
I made the mistake of flashing one of the stock roms derived from RUU which was a big mistake since it flashed the hboot I no longer have revolutionary which lead me to not being able to fastboit anything. I can get the adb to.connect to the device while in recovery with system mounted. but that's pretty much it. If i install a custom ROM when I reboot revolutionary will see device but not ling enough to.root and install the drivers. Just setup your pc to use fastboot otherwise you might do the same thing I did. After two days of searching trying different things my fix was going and buying a new phone last night.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If you relocked your phone "fastboot oem lock" and installed a stock RUU, this should have brought your phone back to stock. This wasn't the case?
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
Daaaavinnn said:
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Click to expand...
Click to collapse
When you root your phone, never accept updates unless you unroot your phone and go back to stock. Are you on hboot 1.5? I would suggest finding a rom that you want to flash (I recommend Myn's warmtwopoint3 RLS1 Deodex). To do this go into fastboot USB and load the custom recovery in the folder you downloaded to root your phone "fastboot boot recovery.img" (recovery.img should be replaced with the name of the CWM***.img file in that folder. This will give you full access to write the kernal and install the rom). Your issue is only likely kernal related so unless you do what I just mentioned, you wont have access to write a new kernal.
JayDaKissEP said:
Your issue is only likely kernal related so unless you do what I just mentioned, you wont have access to write a new kernal.
Click to expand...
Click to collapse
Agreed. Sounds like a kernel issue to me.
JayDaKissEP said:
If you relocked your phone "fastboot oem lock" and installed a stock RUU, this should have brought your phone back to stock. This wasn't the case?
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
When you root your phone, never accept updates unless you unroot your phone and go back to stock. Are you on hboot 1.5? I would suggest finding a rom that you want to flash (I recommend Myn's warmtwopoint3 RLS1 Deodex). To do this go into fastboot USB and load the custom recovery in the folder you downloaded to root your phone "fastboot boot recovery.img" (recovery.img should be replaced with the name of the CWM***.img file in that folder. This will give you full access to write the kernal and install the rom). Your issue is only likely kernal related so unless you do what I just mentioned, you wont have access to write a new kernal.
Click to expand...
Click to collapse
I have hboot 1.4 it wasnt locked. I just falshed the pg86img for my hboot but since it flashed the hboot too it doesn't have fastnoot anymore
Sent from my PG86100 using XDA App
mteezey said:
I have hboot 1.4 it wasnt locked. I just falshed the pg86img for my hboot but since it flashed the hboot too it doesn't have fastnoot anymore
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Does it still show hboot 1.4? According to the instructions, after the PG86IMG.zip installs, you need to go into fastboot and type "fastboot oem writesecureflag 3"
I think your probably just doing something wrong. Pull your battery out, put it back in, hold down volume button and power to boot into bootloader. Explain to me what you see. You should see fastboot on the top and you should be able to press the power button to enter fastboot and when you plug in your phone it will show fastboot usb. If this isnt happening I'm very curious as to what is.
Daaaavinnn said:
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Click to expand...
Click to collapse
did you nandroid?
Thanks for the help everyone!
Hi everyone. The only reason why I wrote this status was because I rooted the phone for someone, and gave it back to them in working order. Then about a week later, they came back to me with that problem and I tried to fix it. But with no success as I stated above. They threatened to sue me or take me to small claims for this problem which i didn't even start. Talk about assholes. Anyways, they gave me the option of paying them 350 which is half of what they bought the phone for, or having me try to fix it. If I do fix it, no need to pay, but if I don't then I'd have to pay the full price which is 700. So I've decided to just pay them the 350 to shut their mouth, get my ass out of trouble, and get on with my life.
So yea, I guess I won't be needing this thread anymore. I really want to try fixing it to save me money, but I don't want to risk it. And yea, I know how much of an asshole they're being. But oh well, shows what kind of people they are.
Were you paid initially for services rendered, when first "working" on the phone? Did you make mention any guarantee/warranty for "work" performed? At any time was this person/persons aware of such forum/s which clearly express "do this at your own risk"?
Sent with L*W*H
Anytime your altering anything on anyone's phone always run them through the normal disclaimer. Make certain that they understand that you take ABSOLUTELY NO RESPONSIBILITY for any damage that might be caused by what THEY want you to do. **** happens sometimes and and you gotta cover your ass. This is why every Rom, Radio/firmware updates, themes and guides have the same disclaimer.
Sent from my PG86100 using xda premium
Just read the OP again. You only rooted the phone, didn't install a custom ROM? Also, after rooting it, the person whom you rooted the phone came to you after a week, not a day or two? In that time frame who knows what they tried to do. Also, someone mentioned a kernel issue as the most likely culprit. Are you able to get into recovery, volume down + power/recovery? Can you get to the bootloader/HBOOT screen? If you get anything other than just the bootloader screen, you may still salvage it. Any progress?
Sent with L*W*H
Daaaavinnn said:
Hi everyone. The only reason why I wrote this status was because I rooted the phone for someone, and gave it back to them in working order. Then about a week later, they came back to me with that problem and I tried to fix it. But with no success as I stated above. They threatened to sue me or take me to small claims for this problem which i didn't even start. Talk about assholes. Anyways, they gave me the option of paying them 350 which is half of what they bought the phone for, or having me try to fix it. If I do fix it, no need to pay, but if I don't then I'd have to pay the full price which is 700. So I've decided to just pay them the 350 to shut their mouth, get my ass out of trouble, and get on with my life.
So yea, I guess I won't be needing this thread anymore. I really want to try fixing it to save me money, but I don't want to risk it. And yea, I know how much of an asshole they're being. But oh well, shows what kind of people they are.
Click to expand...
Click to collapse
Did you check the SD card for anything that you didn't put on there? Sounds like you were scammed to me. Give me half now or try to fix it and if you can't you have to pay me full. Something doesn't sound right with that. Sounds like they didn't want to give you enough time to dig to deep into the phone. Did you check to see if it was even the same phone? Did you charge them for this service originally? What was the reason why they wanted root access?
Sent from my PG86100 using xda premium
Replies to all
Robert542 said:
Anytime your altering anything on anyone's phone always run them through the normal disclaimer. Make certain that they understand that you take ABSOLUTELY NO RESPONSIBILITY for any damage that might be caused by what THEY want you to do. **** happens sometimes and and you gotta cover your ass. This is why every Rom, Radio/firmware updates, themes and guides have the same disclaimer.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
That was the mistake I made, by NOT telling them that. Which is why I have absolutely NOTHING to cover my ass. Which is the reason why I'm going to pay for it to get out of this mess.
intrlude said:
Just read the OP again. You only rooted the phone, didn't install a custom ROM? Also, after rooting it, the person whom you rooted the phone came to you after a week, not a day or two? In that time frame who knows what they tried to do. Also, someone mentioned a kernel issue as the most likely culprit. Are you able to get into recovery, volume down + power/recovery? Can you get to the bootloader/HBOOT screen? If you get anything other than just the bootloader screen, you may still salvage it. Any progress?
Sent with L*W*H
Click to expand...
Click to collapse
I don't have the phone with me right now. Which is why I can't try anymore repairs. And I'm not going to in case it fails, then I'll have to pay full price.
Robert542 said:
Did you check the SD card for anything that you didn't put on there? Sounds like you were scammed to me. Give me half now or try to fix it and if you can't you have to pay me full. Something doesn't sound right with that. Sounds like they didn't want to give you enough time to dig to deep into the phone. Did you check to see if it was even the same phone? Did you charge them for this service originally? What was the reason why they wanted root access?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I don't remember what I did and didn't put on there. So I can't use that as a way to back myself up. And I honestly started thinking that it is a scam, but again, it is kind of is my fault for not taking extra precautionary measures to protect myself in the event that this thing happens. Yes, I did charge for the service. And they didn't say why they wanted it rooted. And even if they are scamming me, I'm just glad it happened sooner so that I could learn from it and prepare myself for the future. As for the money, I am bummed that I have to pay them, but God knows who's the better person and what kind of people they are so I'll let God deal with them.
I have the same issue, sort of. A friend brought me his Evo 3D for me to work on.
My friend 'rooted' his Evo3D through some steps up on youtube that claims root for the 1.5 hboot with S-ON. He then later DL Rom Manager and flashed the freEVO ROM. Now its only useful for WIFI, connected media/google talk/phone dialer/contacts do not work, they all say 'Could not launch the requested activity.'. I have tried factory resetting but it resets to the same issue, cant flash any other rom since there is no actual recovery.
Any ideas on how I can make this thing work
the258 said:
I have the same issue, sort of. A friend brought me his Evo 3D for me to work on.
My friend 'rooted' his Evo3D through some steps up on youtube that claims root for the 1.5 hboot with S-ON. He then later DL Rom Manager and flashed the freEVO ROM. Now its only useful for WIFI, connected media/google talk/phone dialer/contacts do not work, they all say 'Could not launch the requested activity.'. I have tried factory resetting but it resets to the same issue, cant flash any other rom since there is no actual recovery.
Any ideas on how I can make this thing work
Click to expand...
Click to collapse
You will find the answer for your problem here. Sticky's are our friend.
http://forum.xda-developers.com/showthread.php?t=1444285
Sent from my PG86100 using xda premium
thanks, i have already checked it out and tried some but this phone wont 'work'.
the258 said:
thanks, i have already checked it out and tried some but this phone wont 'work'.
Click to expand...
Click to collapse
I'm in the same boat. If I figure my phone out we will have a new guide "how to unbrick the EVO 3d"
Sent from my PG86100 using XDA App
mteezey said:
I'm in the same boat. If I figure my phone out we will have a new guide "how to unbrick the EVO 3d"
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
How is it bricked? Are you able to get into hboot or recovery. Never mind I read back.
Sent from my PG86100 using xda premium

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.

Rooting issues, "limbo" unrooted after trying manual method

I have experience rooting in the past but not on this phone.
I tried rooting using the manual method a couple months ago and it did not go all the way through. At one point during the root process when I had to reboot into the bootloader manually the phone entirely rebooted since the evo lte is kind of a pain to reboot into the bootloader.
Now it seems I am in a state of limbo as the phone actually has a recovery on it, but it is not rooted as i tried to use titanium backup. I have also tried to use the regawmod now that it works with version 22.13.651.1 but I can an unhandled exception error after pressing the root me button.
I assume something isnt playing nice with each other since my first attempt at rooting didnt go all the way through but did install the recovery. I actually tried to install the newest sprint update and it got stuck popping up the custom recovery. I think it would be best to revert back to completely stock and try again but i am not sure how to do so. appreciate any help!
If you have custom recovery, flash a rooted ROM to gain root access
Sent from my EVO using xda premium
corcgaigh said:
If you have custom recovery, flash a rooted ROM to gain root access
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I didnt realize that would actually work! When it popped up in recovery I could go to install from sdcard I just wasnt sure if there would be consequences doing so. So I could reboot into the bootloader, go into recovery and flash a rooted rom from there just like always and it would give me root? That would be awesome
midnite9150 said:
I didnt realize that would actually work! When it popped up in recovery I could go to install from sdcard I just wasnt sure if there would be consequences doing so. So I could reboot into the bootloader, go into recovery and flash a rooted rom from there just like always and it would give me root? That would be awesome
Click to expand...
Click to collapse
Yes, that's right!

May have a new one/can't believe I did this.

Well I may have truly found out how to brick this phone. First what you want to do is unlock the bootloader, then flash a recovery. Next you want to gain SU on the phone and root. If your their and you want to brick your phone you will need to do the following steps.
1. Forget to create a restore
2. Flash the google nexus 4.3 to the phone
3. realize it in a boot loop
4. format data on the phone (yeah that's right...I wiped everything)
5. sit back and admire your work.
Any ideas?
Jtag
jd1639 said:
Jtag
Click to expand...
Click to collapse
what he said
Can you get into recovery?
There is a way to adb a rom file onto the phone using twrp as long as you can get into recovery and the pc recognizes the phone....if no recovery though I don't know.. would have to be able to get into fastboot and flash twrp.
Sent from my HTC One using xda app-developers app
00mred00 said:
Can you get into recovery?
There is a way to adb a rom file onto the phone using twrp as long as you can get into recovery and the pc recognizes the phone....if no recovery though I don't know.. would have to be able to get into fastboot and flash twrp.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
I have tried to side losd a rom but either I'm doing it wrong or it just won't work. I keep getting errors. I can reboot the phone from ADB on the computer but I can't seem to move any information across...Heck I can even lock and unlock the bootloader but not side load.
Did you try this? http://forum.xda-developers.com/showthread.php?p=42426459
Sent from my HTC One using Tapatalk 4
Oh, i feel your pain, Just "soft" bricked my phone. Lucky it has plenty of juice and i was still able to get to booloader. Somewhat of an easy fix. But boy did my heart start pumping.
When you reboot, what does it do? Just sit there on the HTC screen, not light up at all, or something else?
I only ask because I thought I borked mine today going from the OTA, to .12, to S-OFF, the accidentally making it ENG S-OFF, and then the screen not lighting up when I'd try to do anything.
But I was able to get the silver HTC screen to pop up and flash the 4.1.2 RUU to go to WWE 4.2.2.
Sent from my HTC One using Tapatalk 4

Categories

Resources