Hopefully I can get some help from you guys I'm currently on hboot 1.12 HTC devunlock and I'm running TWRP 2.2.1. I tried flashing CMX but I get "unfortunately phone isn't responding" right after that it says the UI isn't responding and the dialog boxes keep appearing. So I can't get past the lock screen. I've already tried wiping and reflashing and it didn't help. Any help would be appreciated.
gespinal0301 said:
Hopefully I can get some help from you guys I'm currently on hboot 1.12 HTC devunlock and I'm running TWRP 2.2.1. I tried flashing CMX but I get "unfortunately phone isn't responding" right after that it says the UI isn't responding and the dialog boxes keep appearing. So I can't get past the lock screen. I've already tried wiping and reflashing and it didn't help. Any help would be appreciated.
Click to expand...
Click to collapse
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
megabiteg said:
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
Click to expand...
Click to collapse
I thought it was only if you had updated to 1.15 for the hboot that you have to flash the bootimg..... nvm ill try it once i get home
Definitely sounds like you might have a bad download. Also download the superwipe zip and use that too. With hboot 1.12 you should be fine to flash without any special procedures.
Sent from my EVO using xda premium
A known issue in CMX is that phone process will crash, it does this while the phone searches for a signal, once a signal is found it should stop. Just try waiting it out, it doesn't really affect anything, once the message is gone you will be fine
durandetto said:
Definitely sounds like you might have a bad download. Also download the superwipe zip and use that too. With hboot 1.12 you should be fine to flash without any special procedures.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
om4 said:
A known issue in CMX is that phone process will crash, it does this while the phone searches for a signal, once a signal is found it should stop. Just try waiting it out, it doesn't really affect anything, once the message is gone you will be fine
Click to expand...
Click to collapse
i tried the bootimg and i still had the same problem, but ill try waiting it out
megabiteg said:
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
Click to expand...
Click to collapse
That is only for HBOOT 1.15 and up. HBOOT 1.12 allows for flashing of kernel from recovery with S-ON.
When you say you tried "wiping and reflashing", what exactly did you wipe? You should do a factory reset, then wipe data, system, cache, and dalvik. Then flash the ROM.
bilbo524 said:
That is only for HBOOT 1.15 and up. HBOOT 1.12 allows for flashing of kernel from recovery with S-ON.
When you say you tried "wiping and reflashing", what exactly did you wipe? You should do a factory reset, then wipe data, system, cache, and dalvik. Then flash the ROM.
Click to expand...
Click to collapse
Im running Viper4g on my evo lte 4g its a sense based rom i wipe the system, then dalvik cache, and cache. Ill try the factory reset now.
gespinal0301 said:
Im running Viper4g on my evo lte 4g its a sense based rom i wipe the system, then dalvik cache, and cache. Ill try the factory reset now.
Click to expand...
Click to collapse
Don't forget data too
One user kept corrupting his phone with a backup of user data, I don't know how or where he got the relevant knowledge to obtain just an image apps and user data but it was corrupt and he stuck himself in an endless cycle of reformat and reflash apps and data. A human boot loop lol I was thinking about adding it to the troubleshooting guide but what are the odds that someone who doesn't know what they are doing will create a zip install of backed up data (or fail really since it is corrupt) and flash it *looks around in baited breath* well OK then
Well i think the factory reset worked now i get a not so frequent dialog saying process.phone.android has stopped. Should i reflash or just wait it out? lol
I would wait it out
I had this exact same problem. My issue was I had flashed a modified mail app that got rid of the Exchange Security Lock. Once I factory reset I was fine. When I tried flashing that Mail app again, I got the same Phone has quit error over and over.
gespinal0301 said:
Well i think the factory reset worked now i get a not so frequent dialog saying process.phone.android has stopped. Should i reflash or just wait it out? lol
Click to expand...
Click to collapse
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
xuohtx said:
I had this exact same problem. My issue was I had flashed a modified mail app that got rid of the Exchange Security Lock. Once I factory reset I was fine. When I tried flashing that Mail app again, I got the same Phone has quit error over and over.
Click to expand...
Click to collapse
I didn't use titanium backup the Play Store just started installing everything I needed which was why I thought it was weird. Everything is working great so far. Thanks to everyone for their input and help.
Google market back up has been a long time feature. Its just that OEMS won't include it or for some reason disable it. Every HTC Android phone I have own has asked permission for Google market back up but upon factory reset or flash, sense will disable it the automatic restore
bilbo524 said:
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
Click to expand...
Click to collapse
I also get the force close of the phone when I toggle airplane mode. Sometimes it doesn't stop and I have to reboot.
Sent from my EVO using Tapatalk 2
bilbo524 said:
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
Click to expand...
Click to collapse
echo....echo...echo..nah I kid, just a bit bored haha
Related
My brother tried to install a rom in rom manager. Did not work. He got stuck at the hboot screen. He panicked and tried fixing by flashing the newest ruu. It does the update then when you reboot it gets stuck at the white htc screen for ever. Not sure what he did is even fixable im used to the samsung phone and we just odin back. I have tried to reinstall his cwm and flash the ruu thru there but same result. He was rooted running bamf and he still has s-off even after flashing ruu. Any help or ideas would be greatly appreciated and to save time hit me up on gtalk @ [email protected]. Thanks fellows.
Did he make a nandroid?
Stratejaket said:
Did he make a nandroid?
Click to expand...
Click to collapse
That would have been to easy...lol. nope sure didnt!
Wow fail on the no backup! I'd try to reboot into recovery, load a new rom on the SD and try to flash that.
What did he use to gain root?
Can you verify he still has s-off?
Bootloader version?
Stratejaket said:
Wow fail on the no backup! I'd try to reboot into recovery, load a new rom on the SD and try to flash that.
What did he use to gain root?
Can you verify he still has s-off?
Bootloader version?
Click to expand...
Click to collapse
He used revolutinary to root. Still has s-off and hboot is 6.04.1002
Do a system wipe, cache and dalvik. Then try to reinstall a rom, not the RUU.
Stratejaket said:
Do a system wipe, cache and dalvik. Then try to reinstall a rom, not the RUU.
Click to expand...
Click to collapse
tried and no good. just goes to htc screen and keeps rebooting.
might be time to smash and file a warranty....lol
Is there a pg05img.zip still on the root of the sdcard? If so delete it.
mongo41 said:
My brother tried to install a rom in rom manager. Did not work. He got stuck at the hboot screen. He panicked and tried fixing by flashing the newest ruu. It does the update then when you reboot it gets stuck at the white htc screen for ever. Not sure what he did is even fixable im used to the samsung phone and we just odin back. I have tried to reinstall his cwm and flash the ruu thru there but same result. He was rooted running bamf and he still has s-off even after flashing ruu. Any help or ideas would be greatly appreciated and to save time hit me up on gtalk @ [email protected]. Thanks fellows.
Click to expand...
Click to collapse
I wish more people would stop flashing roms in Rom manager. Reboot to recovery clear data,cache,davlik cache, hell format system while you are at it, wipe it all 3 times for good measure. I have always followed the same steps from day 1 and never any issues with roms other than known bugs. Another thing when something doesn't go right don't just flash with no reguard to your device. If something does not work try to clear everything and reflash again. If that does not work clear everything and flash your backup (yes you should always make a back up) rant over.
If I helped you in any way please use the thank you button
Is your problems resolved?
Hi,
I accidentally updated to Gingerbread on my Thunderbolt, and I forgot I rooted my phone, by the time I remembered it already had a blue android and an explaimation mark. So I did some random crap, and probley made it worse.
First I did the vol down power thing went to factory reset it loaded CWM v4.0.1.4
I wiped cache patition
Dalvick cache
and Battery stats
then I wiped data/factory reset
It loaded like it was brand new everything seemed fine till I updated and did same thing so I wiped the data again and now it keeps auto updating so I have to keep my internet off
and it's annoying as crap
I'm a noob so I don't understand stuff
should I go ahead with this guide:
http://forum.xda-developers.com/showthread.php?t=1009423
I couldn't understand it and if your not rooted why would you unroot I don't get that part...
Do I still have root?
What does flash exactly mean?
Current Specs (I don't know what to give but I'll guess)
Thunderbolt
Top says
Mecha XD S-OFF
HBOOT 6.04.1002
eMMC-boot
Android Version 2.2.1
(tell me if you need any other info)
Should I upgrade to gingerbread any way
Download a customer rom, put it on your sd card and flash it in CWM. I'm running BAMF forever and like it. There are plenty of roms to choose from. This should stop the update. After running the rom if you decide you like stock better you can flash the stock rom back and take the update. You will loose root.
Pull the update off the SD. It will stop flashing it
Sent from my ADR6400L using xda premium
Kidney Poker said:
Pull the update off the SD. It will stop flashing it
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I had a friend who's phone auto updated and is stuck on the htc boot screen. Will deleting the update off the sd card work also? Her phone is not rooted, just hoping to save her from having to replace it.
And how do you forget you rooted your phone?
If pulling the update off the sd what do i need to look for
i have a similar problem
my wifes phone is rooted though. it had a stock rom and she autoupdated
now i can only go to recovery mode.
is there a way to fix this and save the stuff on her phone
waltersobchak96 said:
i have a similar problem
my wifes phone is rooted though. it had a stock rom and she autoupdated
now i can only go to recovery mode.
is there a way to fix this and save the stuff on her phone
Click to expand...
Click to collapse
1) The phone will not boot all the way up?
2) is the recovery stock or CWM?
3) do you have a recent back up made?
4) do you have s-off?
jett2314 said:
1) The phone will not boot all the way up?
2) is the recovery stock or CWM?
3) do you have a recent back up made?
4) do you have s-off?
Click to expand...
Click to collapse
1. it boots up all the way, turns off after 10-20s each time, regardless of what action i'm taking
2. cwm recovery
3. no backups recent or not
4. i don't know if i 'have it' but when i load hboot the status is 's-off'
Does it crash or shut off? Maybe a hardware problem?
It powers down the normal way.
waltersobchak96 said:
It powers down the normal way.
Click to expand...
Click to collapse
If you clear the cache, the shutdowns will stop.
But the OTA will download again, and in a few days you will have to repeat the process.
A custom ROM fixed me, but now the same thing poped up.
May go back to stock .... trying xdabolt, but in the process lost my data.
Kidney Poker said:
Pull the update off the SD. It will stop flashing it
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
What am I looking for on the SD card to remove?
sounds like you still have s-off. Anything you are trying to save like app data is gone if you do not have a back up. I would down load a customer rom or even one of the rooted stock versions with the latest OTA and flash that with CWM recovery. Be sure to clear cache and dalvick wipe first when you flash it. There are RUU you could use to return it to stock, but you will lose root. I'm running BAMF forever 1.0.9 and like it. Play around with some roms and if you don't like them use a RUU to restore you back to stock. Most important is make sure you read up on things first.
Hey I endded up just unrooting using this video
(can't show video url)
(Search how to unroot on youtube you should see it by nat3mil and I think that's only if you have revolutionary)
and I guess the video would work too.
If you restored to factory settings using power and vol down buttons and wiped the data in the revolutionary thing, and then followed the video...
phones working now and the video's idiot-proof
just posting this if anyone else needded to unroot
syed2007 said:
and the video's idiot-proof
Click to expand...
Click to collapse
You would think but I have seen people who after being on here a year still don't know the difference between flashing something in ROM manager or recovery.
Sent from my ADR6400L using XDA App
unrooting is good and all, but if that happens again, just look around for the newest ruu and find a rooted version. most ruu get rooted that day... heck i had 2.11.605.5 rooted b4 verizon released it (the 2nd leak, the one WITH working vm notifications) thanks to eris of course. then you'd be up to date, stock, rooted... all you'd have to do is wipe dalvik, cache, and system... keep the data (if coming from sense 2.1 rom) and you'd be good.
i don't mess with sense 2.1/3.0 hybrid or 3.0 roms anymore, for this very reason. a ton of incompatibilities between the roms and framework, causing you to have to wipe data when switching... what a pita! i haven't wiped data in months. keep the data always to make life easier...
if you have problems, use clockwork's "fix permissions" and reboot. problem not solved? then retry rom installation WIPING EVERYTHING, then at least you tried to keep your stuff. titanium backup is great for backing up apps + data, so you can import the data back when you're stable on the new rom... just restore the apps + data for the necessary apps, and app only for the stuff that doesn't mnatter... never restore system apps + data for roms with severely different basebands or from completely different roms. unrooting won't be necessary next time
I had my phone half rooted, OTA came and I selected to defer, well I forgot and now I have the security warning.I tried flashing through the bootloader on my SD card the stock file and I still have the security warning. I use my phone as my internet source so it's been a big PITA. The phone starts, goes to 1x, then 4G, then restarts over and over.
Won't load into recovery, won't factory reset, using HBOOT USB and the command prompt the device isn't recognized.
Right now its as follows:
S-ON
1.04.0000
1.16.0223r
Feb 23 2011, 20: 42:55
Back to using my OG Moto DROID and I am going insane!! Any help would be GREATLY appreciated!!!
Wiped dalvik and flashed a new rom. Works fine now. Had to use a new radio but still.
tapatalk on thunderbread
flip218 said:
I had a friend who's phone auto updated and is stuck on the htc boot screen. Will deleting the update off the sd card work also? Her phone is not rooted, just hoping to save her from having to replace it.
And how do you forget you rooted your phone?
Click to expand...
Click to collapse
If the phones rooted you can prolly get into recovery VIA hboot.
If its not rooted you can prolly find a ota ruu and flash it in hboot. U can do that if its rooted too but ull lose root. Or if its a locked s off there's methods to roll back to factory and turn s on. And yes delete the orig update off the card
RobsCavZ24 said:
I had my phone half rooted, OTA came and I selected to defer, well I forgot and now I have the security warning.I tried flashing through the bootloader on my SD card the stock file and I still have the security warning. I use my phone as my internet source so it's been a big PITA. The phone starts, goes to 1x, then 4G, then restarts over and over.
Won't load into recovery, won't factory reset, using HBOOT USB and the command prompt the device isn't recognized.
Right now its as follows:
S-ON
1.04.0000
1.16.0223r
Feb 23 2011, 20: 42:55
Back to using my OG Moto DROID and I am going insane!! Any help would be GREATLY appreciated!!!
Click to expand...
Click to collapse
Anyone, or flash to Gingerbread? I really need my 4G my OG DROID battery is f**ked, I NEED THIS PHONE WORKING!
Hey guys, I've searched the forum for a while but haven't quite found an answer to this, so I thought I'd post here. Before I start, I'd like to say, yes I am an experienced flasher and know most of my basic things. I've got a pyramid working perfectly, but this has been giving me many problems.
Basically, I just s-offed my HTC Evo 3D GSM, with an old CID of RO____001(I think), and HBOOT 1.53.
So now here I am, with my unlocked phone, running HBOOT 1.49, with SuperCID. My old ROM was Cool ICS, and I couldn't stand it, so I wanted to change over to stock Jelly bean, preferably AOKP. I've got the latest AOKP ROM, and 4EXT Recovery. I went into recovery and wiped my user data and cache and tried flashing the ROM, and Gapps of course, and then I rebooted, but it booted into Cool ICS again! With this happening, I tried wiping all partitions(including system, no SD card) and then my phone booted into a bright white HTC screen and didn't exit it. Parents are mad that my phone is broken now.
Please help! Much appreciated!
Flash stock and try again
Sent from my Evo 3D CDMA using Tapatalk 2
italy2200 said:
I tried wiping all partitions(including system, no SD card) and then my phone booted into a bright white HTC screen and didn't exit it. Parents are mad that my phone is broken now.
Please help! Much appreciated!
Click to expand...
Click to collapse
Sounds more like the actual ROM is corrupt.
Redownload the ROM you want to run. Do a full wipe of the phone, including cache. Then transfer over the files. You can use 4EXT to transfer files to the phone via usb storage mode.
Then try flashing the ROM.
If it still doesn't work, try flashing a different ROM.
If that still doesn't work, report back here or feel free to PM me.
DjDom said:
Sounds more like the actual ROM is corrupt.
Redownload the ROM you want to run. Do a full wipe of the phone, including cache. Then transfer over the files. You can use 4EXT to transfer files to the phone via usb storage mode.
Then try flashing the ROM.
If it still doesn't work, try flashing a different ROM.
If that still doesn't work, report back here or feel free to PM me.
Click to expand...
Click to collapse
Thanks for the reply, DjDom. I'm kind of in a bigger pickle here. My recovery partition won't even work now. This was happening before I formatted all partitions, each time I wiped my data, it wiped the 4EXT app and the recovery partition. Does this mean I need to use the RUU again? And will the RUU re s-on the phone?
italy2200 said:
Thanks for the reply, DjDom. I'm kind of in a bigger pickle here. My recovery partition won't even work now. This was happening before I formatted all partitions, each time I wiped my data, it wiped the 4EXT app and the recovery partition. Does this mean I need to use the RUU again? And will the RUU re s-on the phone?
Click to expand...
Click to collapse
Damn if you can't access your recovery then you are in a bit of a trouble.
Maybe your downloaded ROM got corrupted or it didn't complete downloading that's why it's always recommended to check the HASH after you download something.
Good Luck on recovering your device back!
Hreidmar said:
Damn if you can't access your recovery then you are in a bit of a trouble.
Maybe your downloaded ROM got corrupted or it didn't complete downloading that's why it's always recommended to check the HASH after you download something.
Good Luck on recovering your device back!
Click to expand...
Click to collapse
Na, I can still access recovery by simply flashing the .img... The ROM did finish downloading, as the HASH was proper, there's just a problem with recovery actually flashing to system.
Bump.. Come on guys, I really need help.. It won't even load bootloader anymore.
Flash a new recovery with Fastboot USB (I recommend TWRP or 4ext as recovery) Then go onto your recovery an flash the desired ROM.
Goodluck!
Lost data after Beast 4.3 / or to sideloading and dirty-installing the M7 rom. Flashing different roms/radios made no difference.
SOLUTION TO DATA LOSS:
LakerStar25 said:
Just a heads up to anyone that's on the Verizon version having extreme data loss. If you messed with your apn it could have screwed something up were you might need to run the RUU to fix. It happened to me and micromod. So if that has happened and have tried to get data back and nothing has worked you will need to
1. Nandroid then install the pre ota hboot
2. Relock
3. Backup internal memory then Run RUU
4. After RUU finishes do a factory reset.
5. Reboot and data should be back.
6. Unlock if desired or just install ENG hboot and install recovery and flash your nandroid and good to go.
Click to expand...
Click to collapse
Watercycle said:
Was running Newt's M7, and flashed beast 4.1 fine, wanted to try flashing beast 4.3
After flash it began to boot-loop and ( foolishly ) without a backup I had to use ADB sideload to reflash M7. That worked, but now I have no data, it won't detect the sim card. Tried reflashing the radios+hboot ( yes unlocked and S-off ) to no avail.
Backed up to a stock rom made after S-off but that also doesn't have data ( and keeps yelling "droid" every 10 seconds ).
Click to expand...
Click to collapse
at this point I would suggest going back and read the flashing your recovery. Then after you do that go back in and try and flash kernel again.seems like all your problems are caused by bad last of the kernel.
Watercycle said:
Was running Newt's M7, and flashed beast 4.1 fine, wanted to try flashing beast 4.3
After flash it began to boot-loop and ( foolishly ) without a backup I had to use ADB sideload to reflash M7. That worked, but now I have no data, it won't detect the sim card. Tried reflashing the radios+hboot ( yes unlocked and S-off ) to no avail.
Backed up to a stock rom made after S-off but that also doesn't have data ( and keeps yelling "droid" every 10 seconds ).
Click to expand...
Click to collapse
have you tried reseating your sim card?
slimc84 said:
have you tried reseating your sim card?
Click to expand...
Click to collapse
Yes, tried reseating, no luck.
Also just tried cube's 'return to stock' zip along with reflashing beast 4.1, still without phone/data
Watercycle said:
Yes, tried reseating, no luck.
Also just tried cube's 'return to stock' zip along with reflashing beast 4.1, still without phone/data
Click to expand...
Click to collapse
reboot your phone and toggle airplane mode off and on waiting about 20 seconds in between
slimc84 said:
reboot your phone and toggle airplane mode off and on waiting about 20 seconds in between
Click to expand...
Click to collapse
Tried airplane spam for 3 minutes or so, no go.
Currently on stock and just flashed cubed kernel and modules, still no data.
Watercycle said:
Tried airplane spam for 3 minutes or so, no go.
Currently on stock and just flashed cubed kernel and modules, still no data.
Click to expand...
Click to collapse
sounds like it may be a SIM card error...might have to get a new one....
SOLUTION TO DATA LOSS:
LakerStar25 said:
Just a heads up to anyone that's on the Verizon version having extreme data loss. If you messed with your apn it could have screwed something up were you might need to run the RUU to fix. It happened to me and micromod. So if that has happened and have tried to get data back and nothing has worked you will need to
1. Nandroid then install the pre ota hboot
2. Relock
3. Backup internal memory then Run RUU
4. After RUU finishes do a factory reset.
5. Reboot and data should be back.
6. Unlock if desired or just install ENG hboot and install recovery and flash your nandroid and good to go.
Click to expand...
Click to collapse
I have spent the whole day flashing and trying to get my data back. I am so happy that LakerStar took the time to write out those steps. After flashing RUU there was still no data, but factory reset afterwards did the trick!
Watercycle said:
SOLUTION TO DATA LOSS:
I have spent the whole day flashing and trying to get my data back. I am so happy that LakerStar took the time to write out those steps. After flashing RUU there was still no data, but factory reset afterwards did the trick!
Click to expand...
Click to collapse
awesome. Please change your OP title to note fix found please.
I am pretty sure that I have a borked radio. I was running a "pre-flicker fix" Avatar ROM and upgraded to the 10-22 CM nightly. It worked great for about 4 hours and then lost the ability to send texts or make calls. I am trying to work my way through the steps to fix a messed up radio. I downgraded TWRP to 2.3.3 so I could apply the stock ROM, but the stock ROM hangs on the boot screen. I did apply the correct boot.img.
What am I missing?
evolwun said:
I am pretty sure that I have a borked radio. I was running a "pre-flicker fix" Avatar ROM and upgraded to the 10-22 CM nightly. It worked great for about 4 hours and then lost the ability to send texts or make calls. I am trying to work my way through the steps to fix a messed up radio. I downgraded TWRP to 2.3.3 so I could apply the stock ROM, but the stock ROM hangs on the boot screen. I did apply the correct boot.img.
What am I missing?
Click to expand...
Click to collapse
Did you happen to do a full clean wipe before flashing the 10/22 nightly?
evolwun said:
I am pretty sure that I have a borked radio. I was running a "pre-flicker fix" Avatar ROM and upgraded to the 10-22 CM nightly. It worked great for about 4 hours and then lost the ability to send texts or make calls. I am trying to work my way through the steps to fix a messed up radio. I downgraded TWRP to 2.3.3 so I could apply the stock ROM, but the stock ROM hangs on the boot screen. I did apply the correct boot.img.
What am I missing?
Click to expand...
Click to collapse
I would retry flashing the stock boot.img using fastboot. Sounds like it didn't take.
mdmower said:
I would retry flashing the stock boot.img using fastboot. Sounds like it didn't take.
Click to expand...
Click to collapse
I have tried flashing the boot.img a couple times, I thought the same thing.
I tried it one more time right be for I clicked "submit reply" with no luck.
TheGOAT232412 said:
Did you happen to do a full clean wipe before flashing the 10/22 nightly?
Click to expand...
Click to collapse
I did not do a full factory reset, but did wipe dalvik, cache, system and data.
evolwun said:
I did not do a full factory reset, but did wipe dalvik, cache, system and data.
Click to expand...
Click to collapse
You installed the rom AFTER wiping /system... right?
mdmower said:
You installed the rom AFTER wiping /system... right?
Click to expand...
Click to collapse
Yes
Ok, so I am getting close to having a fully functional phone. I got it working, but it was all luck. (note: I tried each of these steps before, just not in this exact order)
a. I installed a TWRP backup of my Avatar ROM
b. flashed the appropriate boot.img
c. then flashed the Avatar ROM and gapps over the top of the backup.
It is functioning, but I am unable to access the internal storage. In ES Explorer, I can get to "/external_sd/"(which contains files) and "/mnt/sdcard"(which is empty) but if I try to click on the sd card icon it says "SD Card empty, unmounted or not present. I am unable to save screenshots and pictures because of this. This could stem from the SD swap I did.
Now that I have the radio working, I think I want to just start over with the device, without the sd storage, some of the apps are not working correctly. The factory reset I did blasted a lot of stuff. Also my download speeds are VERY slow... it says 4G but I don't believe it. Does anyone have a link to a good walk through on completely starting from scratch on a phone? What is the most stable CM ROM that does not have screen flicker?
thanks for the help guys
I had this exact same issue with 10/22. The radio died, and in the process of trying to fix it, the internal sd disappeared.
I ended up doing a full RUU following the steps at unlimited.io (ignoring the chmod step and the sudo parts of the commands since I'm in Windows). Then, HTCDev unlocking again, installing TWRP and Viper. Now, it seems to be working okay.
I'm having bad luck flashing the CM nightlies lately, not sure if it's just my phone, but I had the same issue even with the 10/18 experimental build.
I did end up getting it going. I built off of what I did in my previous post. I have to format the phone's data partition (mounded via TWRP) to get it to go.