Related
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!
So currently I am pre-OTA 2.04.605.2 710RD, and I heard that this update fixes the SIM card issues. My phone has been plagued with this shortly after I got it. Currently it is rooted with S-Off, however I don't really use the feature much, my phone is pretty bone stock minus ClockworkMod and the menu button mod. I'm sick of the SIM card error and would like to update, however the install always fails in ClockworkMod (that's where it goes after rebooting) so my question is how can I update now, and just wait for S-off or root to become available later?
Put the stock recovery on and install the ota. Then reinstall cwm
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Put the stock recovery on and install the ota. Then reinstall cwm
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed back to stock recovery, when trying to do the OTA I get an error 'assert failed: apply_patch_check("system/apps/Settings.apk)'
NeroMorg said:
Flashed back to stock recovery, when trying to do the OTA I get an error 'assert failed: apply_patch_check("system/apps/Settings.apk)'
Click to expand...
Click to collapse
if you like stock I will trade you mine
ocman40 said:
if you like stock I will trade you mine
Click to expand...
Click to collapse
I would gladly take you up on that offer, but I have my phone setup the way I need it, and I use it as a GPS a lot. It's hard to use it when the SIM error comes up 2-3 times a week.
NeroMorg said:
I would gladly take you up on that offer, but I have my phone setup the way I need it, and I use it as a GPS a lot. It's hard to use it when the SIM error comes up 2-3 times a week.
Click to expand...
Click to collapse
My wife's got the sim error once. I took it out, cleaned it with an eraser then put it back in pressing down pretty hard. Never an issue again.
ocman40 said:
My wife's got the sim error once. I took it out, cleaned it with an eraser then put it back in pressing down pretty hard. Never an issue again.
Click to expand...
Click to collapse
Unfortunately that has not worked for me, and I have had the SIM card replaced. I've heard the update fixes SIM card detection issues. Is this true? I still can't get it to install.
Just install the new radio's
ocman40 said:
Just install the new radio's
Click to expand...
Click to collapse
I don't know how to do that. Care to give a guide, or a link?
There is a thread in the dev section. Search it and then install. I think the sim stuff is in the new radio's.
NeroMorg said:
I don't know how to do that. Care to give a guide, or a link?
Click to expand...
Click to collapse
Are you s off?
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Are you s off?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
First post he stated he was.
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Is it overlaying the signal bars or above the bars, like the data indicator in AOSP?
Sent from my CarbonROM 4.3'd HTC DNA
jlinn75 said:
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Click to expand...
Click to collapse
I had to reset mine to stock, relock it and return it on warranty, apparently there is a known issue with the sim card slot or tray or something. On my third now, debating whether to unlock and try again. No matter what I flashed on it, RUU, stock roms, anything, I couldn't get it back working right. Always had the roaming. New sim card didn't work either.
So your gonna have to do some work to get it back to stock and proper relocked, and then request a new phone from verizon.
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
jlinn75 said:
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This happen to me also. Luckily I had an upgrade available.
So reverting back to stock and then getting a new sim won't work.?
Sent from my Nexus 7 using Tapatalk 4
Harvey Dent said:
This happen to me also. Luckily I had an upgrade available.
Click to expand...
Click to collapse
what phone did you end up getting?
jlinn75 said:
what phone did you end up getting?
Click to expand...
Click to collapse
I ended up getting the S4. Wanted the One but figured I would give the S4 a go.
I just ****ing got this phone and having the same exact issue.. Got it off swappa so now looks like I'm ****ed
Sent from my Nexus 7 using xda premium
I to have the triangle
Are their any current threads on how to ruu back to stock?
I also have the triangle and was told flashing back to stock would fix it I guess we'll see lol
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Kevin3328 said:
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried replacing my sim with no luck. Is there a step by step guide to return to s-on with the moonshine method?
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
Click to expand...
Click to collapse
I did that and it did not work I had to warranty replace it
Nothing will fix it sorry guys
Sent from my HTC6435LVW using xda app-developers app
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
eyegor said:
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I don't think this has anything to do with renting towers. The same thing happened to me while I was flashing the GPE rom for the DNA. I spent two days trying to revert back to s-on and stock out of the box. Finally figured out how to do it. Next I took the ota and the triangle disappeared and showed 4G LTE.
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
I have the 'triangle' problem on a moonshine s-off DNA, but ADB doesn't recognize the phone, I only get "list of devices attached" and blank. It will connect in fastboot, but I've tried 3 computers, multiple usb ports, installing and updating drivers, etc. The device shows up in windows attached by usb and I can drag and drop files- any ideas? I am NOT a programmer by the way, so have been trying to rely on step by steps. Is there a way to fix it without adb? I guess even if I have to go back to box stock that will be better than no phone!
Also, the other things I've read do say you have to lock the bootloader in order to flash the stock hboot and run the RUU.
Thanks in advance-
Click to expand...
Click to collapse
Try these drivers for adb
https://db.tt/GMMd9IFX
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
Try these drivers for adb
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Planedoc, thanks for that, nogo however...when I tried to manually install those I got a Windows (7) error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems."
I did try to install Koush's universal drivers as well via the exe he provided, and it still didn't recognize the phone in ADB, and then every time I plug the phone in it tries to install it's own drivers again, currently the DNA is showing up in device manager with device name: HTC6435LVW, Device type ortable devices, Location: Port_#0004.Hub_#0005, and driver files \Windows\system32\DRIVERS\WinUSB.sys and \Windows\system32\DRIVERS\WUDFRd.sys
Maybe I'll try my wifes macbook tonight and see if it shows up there.
So, I used Moonshine to unlock and root the VZW Droid DNA, and after it was all said and done, I installed CM11 with the KK Gapps.
Normally, I don't have an issue with this kind of thing, but I could call and text after for approximately two hours, then it just stopped.
I now can't text at all, and when I call, it says something about needing to go to an external operator on VZW's service,
but what gets me is that I still have LTE, I still have data, I can browse the internet, I just can't call or text. I'm baffled.
In settings, in about phone, it says it's connected to service, it isn't roaming, it has all connectivity and even shows me my number.
Why could this be? I really need this phone to have service. Thanks to all who help!
Have you tried it on stock to see if it does the same Thing.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Same issue
thayl0 said:
Have you tried it on stock to see if it does the same Thing.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same issue as him but i can still receive both calls and texts. This issue seems to be occurring on both stock and custom roms and it started after i updated to the cm 11 snapshot.
Ironclad6 said:
I am having the same issue as him but i can still receive both calls and texts. This issue seems to be occurring on both stock and custom roms and it started after i updated to the cm 11 snapshot.
Click to expand...
Click to collapse
Have you tried flashing a different radio
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Same issue here. All data works via LTE (status bar icon turns blue) but without SMS or phone ability. Traveling on business this week I noticed poor connectivity and ran the *228 #2 option to update my roaming coverage. I thought that was the cause, but it may not be if others are experiencing the same. I can reach Verizon activation if I switch CDMA mode to automatic (goes to roaming) but activation cannot complete. Seems like we need reprogramming for some reason but I doubt Verizon will want to assist us with customized software.
Wise people of XDA, please help/advise us confused souls.
Verizon DNA, Moonshine, TWRP beta, CM11 (no difference with stable CM10.2.1).
Sent from my BN NookHD+ using xda app-developers app
Phibernaut said:
Same issue here. All data works via LTE (status bar icon turns blue) but without SMS or phone ability. Traveling on business this week I noticed poor connectivity and ran the *228 #2 option to update my roaming coverage. I thought that was the cause, but it may not be if others are experiencing the same. I can reach Verizon activation if I switch CDMA mode to automatic (goes to roaming) but activation cannot complete. Seems like we need reprogramming for some reason but I doubt Verizon will want to assist us with customized software.
Wise people of XDA, please help/advise us confused souls.
Verizon DNA, Moonshine, TWRP beta, CM11 (no difference with stable CM10.2.1).
Sent from my BN NookHD+ using xda app-developers app
Click to expand...
Click to collapse
This is for 1.15
http://www.mediafire.com/download/8627edlqwbwrfsf/PL83IMG+-+1.15+Recovery.zip
This is for 3.0.6
http://www.androidfilehost.com/?fid=23269279319195733
Try***
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash Stock Recovery***.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
thanks to Santod
other way RUU*...
finanandroid said:
http://www.mediafire.com/download/8627edlqwbwrfsf/PL83IMG+-+1.15+Recovery.zip
Try***
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash Stock Recovery***.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
other way RUU*...
Click to expand...
Click to collapse
This is the same method I used to get mine working again.
Something happened to my radio partition, it was showing my phone number as 000-000-0000 and would not recognize the SIM. Too many ROM flashes. Hahaha. This will rebuild all the factory partitions.
Worked like a champ for me.
sdamark said:
This is the same method I used to get mine working again.
Something happened to my radio partition, it was showing my phone number as 000-000-0000 and would not recognize the SIM. Too many ROM flashes. Hahaha. This will rebuild all the factory partitions.
Worked like a champ for me.
Click to expand...
Click to collapse
Yup! I saw this like a cool alternative, instead go to full Ruu route
I'm sure this is a silly question I'll find the answer to immediately after I hit "Submit", but... I've found the Sense 5 deodexed ROM mentioned in similar threads but how do I know which recovery download to use? 1.15 or 3.06?
Sent from my HTC6435LVW using xda app-developers app
Phibernaut said:
I'm sure this is a silly question I'll find the answer to immediately after I hit "Submit", but... I've found the Sense 5 deodexed ROM mentioned in similar threads but how do I know which recovery download to use? 1.15 or 3.06?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
1.15 is Stock HTC Sense 4.1 as droid dna came from factory (jelly Bean 4.1.1)
3.0.6 is Stock Htc sense 5 is the new Vzw Ota (jelly bean 4.2.2)
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?
EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
Phibernaut said:
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?
EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
Click to expand...
Click to collapse
a red "!" triangle over a phone, its stock recovery, reboot and go to setting and perform Phone Reset.
Phibernaut said:
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?
EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
Click to expand...
Click to collapse
NVM
Similar "!" images indicated recovery issues on my old Droid 3. Here they're a good thing and I'm back in action after using the steps discussed. Thanks all!
Sent from my HTC6435LVW using xda app-developers app
After a day or two of use I have lost LTE and a second reset has not brought it back. I have had past sporadic SIM card error messages upon boot of fresh CM installs but assumed it was normal. Connectivity would eventually resume but I'd nudge the card tray anyway. 3G seems strong & solid - thoughts/suggestions?
Sent from my HTC6435LVW using xda app-developers app
i am trying to root a friends htc evo 4g lte, and finally got the bootloader unlocked, then started the root process. i got to the point of the custom recovery, where you mount the internal storage, but it some how has been deleted, and it is asking me for a decrypt password, to unlock the internal storage data, and that i only have 30 attempts before it will be lost. according to her, she has never setup any accounts or passwords on her phone, so i am wondering if there is a factory password, or what else I should do, as the root process was in the middle, and not complete? please get me an answer to this, as she uses this phone for her business, and needs it immediately. i have samsung phones, and the root is much easier, so i didn't expect all of this. any help is extremely appreciated.
stevae said:
i am trying to root a friends htc evo 4g lte, and finally got the bootloader unlocked, then started the root process. i got to the point of the custom recovery, where you mount the internal storage, but it some how has been deleted, and it is asking me for a decrypt password, to unlock the internal storage data, and that i only have 30 attempts before it will be lost. according to her, she has never setup any accounts or passwords on her phone, so i am wondering if there is a factory password, or what else I should do, as the root process was in the middle, and not complete? please get me an answer to this, as she uses this phone for her business, and needs it immediately. i have samsung phones, and the root is much easier, so i didn't expect all of this. any help is extremely appreciated.
Click to expand...
Click to collapse
Unlocking the bootloader wipes the phone so any internal data I believe isn't there anymore. Reboot back to fastboot and try reflashing the recovery. Also HBOOT info would probably help. Just keep calm. It'll be okay.
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
Unlocking the bootloader wipes the phone so any internal data I believe isn't there anymore. Reboot back to fastboot and try reflashing the recovery. Also HBOOT info would probably help. Just keep calm. It'll be okay.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if this was my phone i would be a lot calmer, but this is her only phone, and she uses it for business. the samsung rooting is a million times easier, and without a single problem. i have done dozens of them, and NEVER had any issues. i don't understand why htc makes you do the bootloaded, which is a monster process all to its own, and then puts you through so many trials and tribulations to complete the root. when i root a samsung, all the information is still thereso i assumed it would be the same on any android device. as you can imagine, i am bugging to lose her all her info.
ok, so i reflashed recovery using the cmd prompt, and it flashed ok. then i loaded supersu. no problem. but then when i try to load the stock htc rom, it says it can't find md5, and reloads into a white screen with green htc on it. that's it. it goes no further. anything you can tell me to help get this thing up and running?
stevae said:
if this was my phone i would be a lot calmer, but this is her only phone, and she uses it for business. the samsung rooting is a million times easier, and without a single problem. i have done dozens of them, and NEVER had any issues. i don't understand why htc makes you do the bootloaded, which is a monster process all to its own, and then puts you through so many trials and tribulations to complete the root. when i root a samsung, all the information is still thereso i assumed it would be the same on any android device. as you can imagine, i am bugging to lose her all her info.
ok, so i reflashed recovery using the cmd prompt, and it flashed ok. then i loaded supersu. no problem. but then when i try to load the stock htc rom, it says it can't find md5, and reloads into a white screen with green htc on it. that's it. it goes no further. anything you can tell me to help get this thing up and running?
Click to expand...
Click to collapse
What rom are you trying to flash? Also HBOOT info I'm guessing HBOOT 2.09.0000
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
What rom are you trying to flash? Also HBOOT info I'm guessing HBOOT 2.09.0000
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the hboot is 2.10.0000
and the rom is: Download 3.16.651.3 Stock Firmware with root for HTC Evo 4G LTE (Flash with TWRP after factory reset)
when i try to flash it, it says, "no md5 file". then just goes to the white screen and stays there.
but i am willing to flash any rom to get it up and running. i have no problems getting into bootloader or recovery.
top of my fastboot screen says:
******* tampered
******* unlocked
jewel PVT SHIP S-ON RL
HBOOT-2.10.0000
RADIO 1.13.11.1105
OpenDSP-V33.1.0.45.1128
eMMC-boot
stevae said:
the hboot is 2.10.0000
and the rom is: Download 3.16.651.3 Stock Firmware with root for HTC Evo 4G LTE (Flash with TWRP after factory reset)
when i try to flash it, it says, "no md5 file". then just goes to the white screen and stays there.
but i am willing to flash any rom to get it up and running. i have no problems getting into bootloader or recovery.
Click to expand...
Click to collapse
Did you or she ruu to the new partition? If so, try this one, http://forum.xda-developers.com/showthread.php?t=2807651
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
Did you or she ruu to the new partition? If so, try this one, http://forum.xda-developers.com/showthread.php?t=2807651
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
man, i don't even know what ruu is? we don't have that with samsung phones. when i wiped the partition, i just tried to load the twrp and then the rom.
so i'm guessing you want me to flash: Novitious_Jewel_4.3_Sense5.5_N1.zip - 831.88 MB
do i just flash it like any other rom, or do i have to do something special for this ruu?
It's a normal rom but you saying HBOOT 2.10.0000 tells me that someone updated it. Before you started the process was the phone Android version 4.3?
Sent from my EVO using XDA Premium 4 mobile app
---------- Post added at 03:50 AM ---------- Previous post was at 03:49 AM ----------
Is there any way you could post a pic of the bootloader screen?
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
It's a normal rom but you saying HBOOT 2.10.0000 tells me that someone updated it. Before you started the process was the phone Android version 4.3?
Sent from my EVO using XDA Premium 4 mobile app
---------- Post added at 03:50 AM ---------- Previous post was at 03:49 AM ----------
Is there any way you could post a pic of the bootloader screen?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i think it was. and yes, it was upgraded today. i spent quite a while unlocking the bootloader. that took forever. then i tried to root it. but had a problem right in the middle of that. when i went to mount the int sd card, it said nothing was there. then it told me i needed a decrypt password. so i was told to wipe everything. so i did. then reloaded twrp and supersu. that is where i am now. man, i just want to get this thing up and running again, no matter what rom or anything else. this is not my phone, and she uses it for business. she needs it as soon as possible, and i know so very little about htc.
stevae said:
i think it was. and yes, it was upgraded today. i spent quite a while unlocking the bootloader. that took forever. then i tried to root it. but had a problem right in the middle of that. when i went to mount the int sd card, it said nothing was there. then it told me i needed a decrypt password. so i was told to wipe everything. so i did. then reloaded twrp and supersu. that is where i am now.
Click to expand...
Click to collapse
Well since it was updated you need a rom that is built on the new layout. The link I have you is for a rom that should work fine for you. It is sense 5.5 and personally I love it. Hopefully your friend will too. Just dl and flash. Also you need a modified twrp recovery from Captain_Throwback.
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
Well since it was updated you need a rom that is built on the new layout. The link I have you is for a rom that should work fine for you. It is sense 5.5 and personally I love it. Hopefully your friend will too. Just dl and flash. Also you need a modified twrp recovery from Captain_Throwback.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so the recovery i have won't work? do you have a link for this modified twrp? and is it a zip file, because i can flash zip files, but image files don't even show up.
stevae said:
so the recovery i have won't work? do you have a link for this modified twrp? and is it a zip file, because i can flash zip files, but image files don't even show up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=50112370
Either of the twrps listed in this thread should work. Fastboot flash recovery nameofrecovery.img. personally I would rename the recovery to either twrp or recovery and make sure it is in the same folder as the fastboot files. Or if you are s-off put in a zip fodder after renaming to recovery.img
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
http://forum.xda-developers.com/showthread.php?p=50112370
Either of the twrps listed in this thread should work. Fastboot flash recovery nameofrecovery.img. personally I would rename the recovery to either twrp or recovery and make sure it is in the same folder as the fastboot files. Or if you are s-off put in a zip fodder after renaming to recovery.img
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok, i got them. i'll go give it a shot. i really appreciate all the help, i'll hit your thanks bar many times.
update: i hit your thanks bar for every post you made in this thread. thanks again. hope it all works.
man, i can't believe i went through all the things i went through, and i am right back in the same boat i was this afternoon. i renamed and flashed the custom recovery. i then flashed the rom, and when it looked like it was doing everything right, and starting to load the rom, it took me right back to the prompt "Decrypt Storage". type password to decrypt storage.
30 attempts remain before device data is deleted.
how can i get past this thing? i wiped everything there was to wipe on this phone.
stevae said:
man, i can't believe i went through all the things i went through, and i am right back in the same boat i was this afternoon. i renamed and flashed the custom recovery. i then flashed the rom, and when it looked like it was doing everything right, and starting to load the rom, it took me right back to the prompt "Decrypt Storage". type password to decrypt storage.
30 attempts remain before device data is deleted.
how can i get past this thing? i wiped everything there was to wipe on this phone.
Click to expand...
Click to collapse
Reflash recovery again. Or try a different one from captains thread.
Sent from my EVO using XDA Premium 4 mobile app
---------- Post added at 05:24 AM ---------- Previous post was at 04:52 AM ----------
@Captain_Throwback, you got any insight for this particular situation?
Sent from my EVO using XDA Premium 4 mobile app
gstanke said:
Reflash recovery again. Or try a different one from captains thread.
Sent from my EVO using XDA Premium 4 mobile app
---------- Post added at 05:24 AM ---------- Previous post was at 04:52 AM ----------
@Captain_Throwback, you got any insight for this particular situation?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i got so mad about the decrypt thing popping back up, that i went into wipe and did a full "format data". now the decrypt message is gone, but the phone will not recognize the internal sd card. the only place it shows up is in advanced wipe area, and i can wipe it individually, but in the other areas of the phone, it doesn't show up. for instannce, if i try to usb mount, there is no internal card, so it will not show anything. so how do i get this internal sd card back? i can't flash anything right now because it isn't recognized.
two other questions, should the int sd card be formatted in fat32 or exfat? and is the rom you gave me odexed or deodexed?
UPDATE: so i finally decided to use the root folder to flash the older twrp, and it worked. then i was able to see the internal folder again. so i tried to reload the supersu, and rom you suggested, but when it loaded up, it took me right back to the "decrypt storage" message. so i tried to reload the newer twrp, you suggested, and the int sd card is not recognized again. so i am guessing i have a lot of miss matched software on this phone, and maybe that is the reason i am getting this message. any idea how to determine exactly which ones are out of place? in the mean time, i googled the decrypt storage message, and many people have been through this also, but i haven't seen a fix. so i will go back to your friends site, and try the other twrp for now.
UPDATE2: i just decided to relock the bootloader, and ruu it back to original. i hope this works. i was able to relock the bootloader, and i am in the middle of ruu'ing it now.
UPDATE3: yeah, i've got it back up. so glad to get this thing running again. i wish i had of understood what you meant by ruu before, i would have saved myself a lot of grief.
the fact that, while setting things up for the first time, this phone will not let you skip accounts, and just get into your phone is crap. you should be able to set the accounts up at your whim. and even if you try to set a new account up with htc, the code the phone gives you, will not work on the htc site. even if you keep generating a new code on the phone, the site will not take it. what the hell is that? this entire experience with this phone makes me appreciate having a samsung much, much, much more than ever before. htc needs to get their head out of their ass, and stop making everything so difficult.
Based on a quick read on this thread, the problem appears to have been an incomplete update to the new layout. The HBOOT got updated, but the image doesn't appear to have been flushed again to update the data and system partitions fully, and then the ROM booted to ensure everything was initialized properly. That would be the way to fix it going forward.
Also, you can skip through all of the account setup stuff in the ROM - I'm not sure what you mean about that .