mdmower said:
In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.
Downloads
Stock ROM
recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391
Instructions
From your preferred recovery, run the factory reset option
Follow the directions in this thread to install the stock ROM
Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash the stock recovery:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
Let the phone reset and boot up
Allow network connectivity to be restored (make a test call)
Turn on all GPS location services: Settings > Location > (all three location services) = On
Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash your preferred recovery: CWM or TWRP
(If you just want to run this stock ROM, you can stop here)
From your preferred recovery, run the factory reset option
Restore your ROM backup and wipe cache again before rebooting
Click to expand...
Click to collapse
I followed the thorough instructions for HTCDevUnlock, FacePalm S-Off, and HBoot, everything was great until after installing CM 10.1 Nightly from 7/15/2013. Could not get past the "Waiting for Network" hangup, so decided to revert back to 2.17.605... as in this post.
I believe this is the "borked radio". Have tried several times to get through the instructions here, however when I occasionally get the phone to boot get a "1099 error" related to the phone.
Also, Recovery says "no OS is installed" and the Bootloader says "PJ53Diag.Zip" then "no image!"
Seems as I am way off the track. Can anyone help here?http://forum.xda-developers.com/images/smilies/frown.gif)
LeonMBarnes said:
I followed the thorough instructions for HTCDevUnlock, FacePalm S-Off, and HBoot, everything was great until after installing CM 10.1 Nightly from 7/15/2013. Could not get past the "Waiting for Network" hangup, so decided to revert back to 2.17.605... as in this post.
I believe this is the "borked radio". Have tried several times to get through the instructions here, however when I occasionally get the phone to boot get a "1099 error" related to the phone.
Also, Recovery says "no OS is installed" and the Bootloader says "PJ53Diag.Zip" then "no image!"
Seems as I am way off the track. Can anyone help here?http://forum.xda-developers.com/images/smilies/frown.gif)
Click to expand...
Click to collapse
This is not the borked radio condition. The nightlies are very unstable right now with both SELinux and RIL under heavy development. Consider using the latest mdm build instead if you want to try CyanogenMod.
mdmower said:
This is not the borked radio condition. The nightlies are very unstable right now with both SELinux and RIL under heavy development. Consider using the latest mdm build instead if you want to try CyanogenMod.
Click to expand...
Click to collapse
:highfive:
What a relief, I am now on mdm04. That flashed very nicely, I just had to hang in there while it fiddled around and finally locked on to the Verizon service. It also had a hard time with sumthin while trying to find my Google account. Last night I was up late fighting with it, a fresh mind does wonders. The tools, instructions and tips referenced in this thread are all First Rate.
Congratulations and Thank You for the Great Work, mdmower and everyone else that is participating!!!
So now I am having troubles with USB connectivity to my Win 7 64-bit machine. Am pretty sure it worked early on, now the phone just charges and hangs when trying to connect as USB storage.
I rebooted the laptop and phone, reinstalled the latest HTC drivers, rebooted the laptop again, no luck.
Had a bunch of backed up files to move, used TWRP Recovery and our old friend command line to get that done. Fortunately I don't need to do this very often.
Any ideas?
LeonMBarnes said:
So now I am having troubles with USB connectivity to my Win 7 64-bit machine. Am pretty sure it worked early on, now the phone just charges and hangs when trying to connect as USB storage.
I rebooted the laptop and phone, reinstalled the latest HTC drivers, rebooted the laptop again, no luck.
Had a bunch of backed up files to move, used TWRP Recovery and our old friend command line to get that done. Fortunately I don't need to do this very often.
Any ideas?
Click to expand...
Click to collapse
Try a new cable?
LeonMBarnes said:
So now I am having troubles with USB connectivity to my Win 7 64-bit machine. Am pretty sure it worked early on, now the phone just charges and hangs when trying to connect as USB storage.
I rebooted the laptop and phone, reinstalled the latest HTC drivers, rebooted the laptop again, no luck.
Had a bunch of backed up files to move, used TWRP Recovery and our old friend command line to get that done. Fortunately I don't need to do this very often.
Any ideas?
Click to expand...
Click to collapse
Make sure you're using a USB 2.0 port, not USB3.
Deleted
Related
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
babybear293 said:
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
Click to expand...
Click to collapse
can't do commands via usb, i'm reading this to mean, you don't have adb access.
after wiping the /data partition, where system settings are stored, including the toggle for adb access via, you will probably have to re-enable.
to enable adb access via usb on sense -> settings -> applications -> development -> usb debugging. this should be toggle on.
if that doesn't work, post back and we can start digging deeper but i'm hoping that'll resolve your isse!
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
thos25 said:
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
Click to expand...
Click to collapse
Well there is a lot going on in that post ... Not sure how my application Flash Image GUI failed. I would be more than happy to fix/resolve any bug or issue you've encountered!
Fastboot usb mode should always work. There is no setting in Android which will have any impact on fastboot usb mode (other than not allowing the device to boot into the bootloader). I generally find the best process to be, boot the device into the bootloader, plug in usb and then select fastboot.
Perhaps, once you're in the bootloader, you can also select fastboot and then plug in USB (this works best on my NS4G).
Either way, fastboot usb should always work. If you're using Windows, there could definitely be a drivers issue or Windows being finicky with the drivers and that might result in fastboot USB not working. A simple reboot of the Windows machine should clear any fastboot driver issues.
The best working method to correctly load a ROM is by properly loading the recovery to work with the HTC unlock method. HTC unlock method will only grant the recovery write access to the boot partition when the recovery image is temporarily fastboot boot'd. The command is: fastboot boot c:\android\cwm-recovery.img.
If you boot into the bootloader and select recovery from the menu, it will boot into the recovery, but the HTC unlock method will not grant the recovery write access to the boot partition. You can flash a ROM from here and restore a nand. Both will completely successfully and claim they flashed the kernel w/o any issues but the memory write lock will have prevented the kernel writes from being retained.
Also, regarding my application, Flash Image GUI, it should properly flash any EVO 3D kernel .zip file from normal Android mode as the HTC unlock method allows kernel write access while in normal Android mode.
Why did HTC block kernel write access from recovery mode? They haven't provided an answer .. we can only speculate ...
Hope that helps explain a few more steps to the process and provide greater clarity!
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
thos25 said:
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
Click to expand...
Click to collapse
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
I had a similar issue when i was switching to AOSP kernels/roms. I rebooted my phones once or twice and it connected fine. Maybe it have something to do with AOSP since MIUI is aosp also.
joeykrim said:
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
Click to expand...
Click to collapse
Thanks for the comments and lesson. I apologize for not responding sooner, but a recent death in family prevented me from really being on here too much lately.
1) I pretty much figured that. Yeah. I only try to flash using this method, that is why when my fastboot USB disapeared I thought I was really in a bad spot. Luckily I got it working again, so all was not lost.
2). Yes. I know it should remain on SD card, which was strange why I couldn't find it. However, thinking back on it, I do remember deleting some files off of my SD card on the same night. I probably just mistakenly deleted my CWM Recovery with my NAND backups. Sometimes when I double click a file to look at it, when I leave the file I see that there is a checkmark on that file. I may have just not noticed the checkmark on the CWM, went to delete another file, and mistakenly deleted CWM with it.
3) An RUU will not change a RADIO? I was under the impression that they did. Sort of like applying an OTA, but manually doing it through SYNC.
well, thanks again though. I learned some new things and appreciate it.
Flash image GUI works like a charm
Sent from my PG86100 using XDA App
i m a newbie
plz tell me how to get out of the fastboot usb mode. i m stuck with the G1 screen having fastboot usb title on the top.
PLZ HELP!!!
Hey all,
Running CM 10.1 Wild For The Night and I noticed my WiFi had disconnected. When I went to the WiFi settings, the toggle was greyed out and the screen was stuck on 'turning Wifi on'. I rebooted and the screen was still stuck. I wiped Dalvik and cache, and when I rebooted, WiFi was off. I tried turning it back on and the same situation happened. Completely wiped and reflashed, same problem. Today I flashed a new ROM (MiUi 3.2.8), same problems persist. Im on HBOOT 1.5 S-ON (I know, I know). WiFi did work before with the ROM for at least a week. Is it possible the WiFi chip is borked?
a7nachmb said:
Hey all,
Running CM 10.1 Wild For The Night and I noticed my WiFi had disconnected. When I went to the WiFi settings, the toggle was greyed out and the screen was stuck on 'turning Wifi on'. I rebooted and the screen was still stuck. I wiped Dalvik and cache, and when I rebooted, WiFi was off. I tried turning it back on and the same situation happened. Completely wiped and reflashed, same problem. Today I flashed a new ROM (MiUi 3.2.8), same problems persist. Im on HBOOT 1.5 S-ON (I know, I know). WiFi did work before with the ROM for at least a week. Is it possible the WiFi chip is borked?
Click to expand...
Click to collapse
Your kernel isn't flashing properly so the WiFi driver doesn't match.
To get things back in sync start your recovery with the following fastboot command:
fastboot boot recovery.img
Click to expand...
Click to collapse
Once booted into recovery wipe all partitions except SD card and make sure SmartFlash (S-ON) is disabled in the tools menu if using 4EXT. Then flash the entire ROM as you normally would, except this time the boot partition (kernel) will be flashed from recovery because of the way it was started.
ramjet73
ramjet73 said:
Your kernel isn't flashing properly so the WiFi driver doesn't match.
To get things back in sync start your recovery with the following fastboot command:
Once booted into recovery wipe all partitions except SD card and make sure SmartFlash (S-ON) is disabled in the tools menu if using 4EXT. Then flash the entire ROM as you normally would, except this time the boot partition (kernel) will be flashed from recovery because of the way it was started.
ramjet73
Click to expand...
Click to collapse
Thanks for the reply! Just tried it. It's been a long time since I've messed with ADB and fastboot. I booted the device into whatever the white screen thing that isn't recovery is called (ha ha), performed the fastboot command from the folder I saved it in on my computer, ran the command, and it booted into the 4ext. I disabled Smartflash, wiped everything, and flashed, and now its hanging on the boot screen.
a7nachmb said:
Thanks for the reply! Just tried it. It's been a long time since I've messed with ADB and fastboot. I booted the device into whatever the white screen thing that isn't recovery is called (ha ha), performed the fastboot command from the folder I saved it in on my computer, ran the command, and it booted into the 4ext. I disabled Smartflash, wiped everything, and flashed, and now its hanging on the boot screen.
Click to expand...
Click to collapse
What ROM are you flashing? Some people had problems booting ICS Sense ROM's with hboot 1.5 and S-ON. I never had that problem myself, but if you want to stay on hboot 1.5 and not go for S-OFF it might be worth it to relock your bootloader and flash the 2.17.651.5 RUU to make sure everything is in sync. Flashing the stock ROM will also let you confirm whether your Wi-Fi is working or not.
You'd really be better off going for S-OFF and I have a guide that can help here.
ramjet73
Ah, okay I got MIUI 3.2.8 to bot using the fastboot recovery method. Still having the WiFi issue. I've never messed with logcats before, how would I go about posting the relevant bit of text from this enormous jumble that happened when I ran adb logcat?
a7nachmb said:
Ah, okay I got MIUI 3.2.8 to bot using the fastboot recovery method. Still having the WiFi issue. I've never messed with logcats before, how would I go about posting the relevant bit of text from this enormous jumble that happened when I ran adb logcat?
Click to expand...
Click to collapse
I think that ROM might be having WiFi issues per this post by DH.
You could try flashing the Sense version of the Mac kernel after the ROM is flashed and that might fix it.
ramjet73
ramjet73 said:
I think that ROM might be having WiFi issues per this post by DH.
You could try flashing the Sense version of the Mac kernel after the ROM is flashed and that might fix it.
ramjet73
Click to expand...
Click to collapse
Hm. I had terrible data connectivity on MIUI so I'm back on CM10.1. The things that lead me to believe the problems are deeper than kernel/ROM are
1. The issue happened abruptly. After using CM10.1 for a week or so with no wifi issues, suddenly this happened. Not even after a reboot, it just happened.
2. Its happening on multiple ROMs with full wipes and stuff in between.
Would a logcat not be helpful in diagnosing the issue? I just don't know much about them. Do I need to connect my phone via USB and then attempt to recreate the problem in order for the correct info to be in the log? As I said before, I can't get my wifi to turn off without wiping cache and dalvik, even after a reboot its still giving me the 'turning wifi on' message.
a7nachmb said:
Hm. I had terrible data connectivity on MIUI so I'm back on CM10.1. The things that lead me to believe the problems are deeper than kernel/ROM are
1. The issue happened abruptly. After using CM10.1 for a week or so with no wifi issues, suddenly this happened. Not even after a reboot, it just happened.
2. Its happening on multiple ROMs with full wipes and stuff in between.
Would a logcat not be helpful in diagnosing the issue? I just don't know much about them. Do I need to connect my phone via USB and then attempt to recreate the problem in order for the correct info to be in the log? As I said before, I can't get my wifi to turn off without wiping cache and dalvik, even after a reboot its still giving me the 'turning wifi on' message.
Click to expand...
Click to collapse
You're best bet is probably to flash the 2.17.651.5 GB RUU at this point and check your WiFi in a stock configuration since not everyone is having these problems. You will need to relock your bootloader before flashing the RUU, then unlock and re-flash your recovery afterwards, but you can use the unlock .bin file you have already.
ramjet73
ramjet73 said:
You're best bet is probably to flash the 2.17.651.5 GB RUU at this point and check your WiFi in a stock configuration since not everyone is having these problems. You will need to relock your bootloader before flashing the RUU, then unlock and re-flash your recovery afterwards, but you can use the unlock .bin file you have already.
ramjet73
Click to expand...
Click to collapse
Willing to give this a go. Is there info on how to relock and unlock with the unlock .bin? Thanks again for the quick replies
a7nachmb said:
Willing to give this a go. Is there info on how to relock and unlock with the unlock .bin? Thanks again for the quick replies
Click to expand...
Click to collapse
Everything you need should be in mpgrimm2's guide.
Once you relock and flash the RUU you can boot into the stock ROM and test WiFi. If everything checks out you can root your phone the way you did the first time, or take it to Sprint for a replacement if it doesn't work.
ramjet73
ramjet73 said:
Everything you need should be in mpgrimm2's guide.
Once you relock and flash the RUU you can boot into the stock ROM and test WiFi. If everything checks out you can root your phone the way you did the first time, or take it to Sprint for a replacement if it doesn't work.
ramjet73
Click to expand...
Click to collapse
Awesome, thanks!
dude, just make it easy on you ...
flash any ics sense 3.6 rom from fastboot and it is going to get your wifi going.
you'd be stuck here until you are s-off ... so no fancy roms for you, sorry~
I can confirm
I'm using the same rom, miui walking dead ICS... Tried to flash it a couple of times.
Seems when turning the wifi toggle off, the whole networking in android locks up. It'll do this on it's own if you have wifi set to disable on sleep. I am running S-OFF Hboot 1.58, and what's really interesting is dropping to terminal and running, netcfg, you get nothing. It locks up as well, and trying to run ifconfig wlan0 down/up gives you nothing. Ctrl-C to cancel doesn't respond either. I don't see anything in logcat, so I think it's a kernel issue.
Normally, you can drop to terminal and su, then 'shutdown -h now' and have the phone shut off within a second or two, but once the wifi locks, it won't shut down, restart, anything. You have to pull the battery. Once the battery is pulled, and you boot back up, wifi will be toggled off, and you can toggle it back on fine, at least in my experience so far.
I'd really be interested in what digitalhigh says, but I can't post on the developer forum yet. :|
I'm s-off, on hboot 1.19, my baseband is 1.12.11.1210.
I just tried to change roms from meanrom ics to paranoid 3.99. Everything went fine in twrp. When I rebooted the phone it ran thru "upgrading android apps" & when it got to the spot where you'd start entering all your info, I got an error saying unfortunately, the process com.android.phone has stopped. There was another message underneath that one. I couldn't really read it but it said something about IU issues. I've tried reflashing the rom but the same thing happens. I have backups made & went to them in twrp, but they aren't a flashable zip like I thought they'd be. I can still get into the bootloader, but when I select fastboot I can't get my phone to connect to my cpu anymore. It was working before I tried all this. I even tried reinstalling meanrom but it gets about a 1/3 of the way thru the install & reboots to the splash screen & it just sits there. I know I'm probably missing something minor, but I could really use some fresh eyes.
Thanks in advance for the help.
ETA...I'm on twrp v.2.6.3.0 & can still get into the bootloader & recovery. Fastboot USB just won't work. I've tried doing system wipes & installing different roms & they either fail or get stuck in bootloop. I found my backups in twrp but they all fail to install when they get to /data. Some of them don't even make it that far.
Well, I went ahead & booted up off of one of my b/u that said it failed. I got my phone back to where I could start entering wifi info,ect...but I'm getting another error unfortunately the process android.process.acore has stopped. I went into twrp & did the "fix permission" thing. I now get the same error as before...unfortunately, the process com.android.phone has stopped.
Well I've been wanting to leave sprint...I guess today is as good a day as any.
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
buddahj said:
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
Click to expand...
Click to collapse
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
numel007 said:
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
Click to expand...
Click to collapse
So........I'm an idiot. I was forgetting to open the command prompt in the platform tools folder. My fastboot usb works fine. Right now, I'm just having trouble installing the htc mtp drivers.
Have the drivers been updated?
Took the red pill. HTC evo 4G LTE evilution red pill.
So I got confirmation I can get the unlock now what? The GUI allows me to log in but gets to 50%.
Any clues?
Do I have to wait longer or flash the beta?
Any good backup software in case It goes tits up? I have the stock rom setup pretty nice so If I can image it to my sd card or windows it would be great.
Factory reset your phone, then try again.
Archit9169 said:
Factory reset your phone, then try again.
Click to expand...
Click to collapse
I was tinkering with twrp over the weekend but I wanted the official unlock so I MiFlashed the latest Global just yesterday.
I tried it directly after clean flash and first boot.:silly:
Why did I revert, 2% battery bug and I had a cursor arrow on twrp. I had accidentally flashed the wrong boot image. I reflashed the boot.img but had the heebie jeebies with these bugs. I prefer to start with a clean stock base.
Run your pc in driver disable environment, make sure you are using a 64bit os, run the tool as administrator. Make sure usb debugging is on, proper drivers are installed.
I had the same trouble and i don't know how but somehow i managed to unlock it without doing anything. It was stuck at 50%, tried a few days later and it unlocked.
Good afternoon everyone, I got a dilemma here I can't seem to resolve or find a solution on here for. I have a new HTC One M9 (hima) and I was attempting to do a full root and install Lineage OS and Open Gapps. The phone is S-Off, but appears to have a locked bootloader still since it does not have the fastboot option on the bootloader, only boot to downloader, boot to recovery, reboot, and power down options.
When I attempted to install Lineage, I made the mistake of doing an advanced wipe, wiped the data, cache, dalvik cache, and internal storage prior to install figuring this would be like the many installs of custom ROMS I've done in the past.
Well, I cannot get any ROM to work at this point, CM 12, CM13, Bad Boyz, and Viper roms all seem to install ok but will hang on the first boot process and will not load up to the in initial first run wizard screens. I also cannot get Open Gapps to install at all, it reports errors and rejects the install. I've tried it with the verify zip box checked and unchecked, I've tried both the 7.1 ARM and 7.1 ARM64 versions, I've also used Gapps 6.0 with the CM 12 and 13.
Unfortunately I didn't realize I needed to enable OEM unlocking in developer options prior to attempting a boot loader unlock, I have no ROM installed so I cannot do this now.
So my question to everyone is, how do I get an OS installed again on this phone so I can get back to where I was prior to wiping everything so I can begin the root and bootloader unlock process again?
Thanks for your help with this everyone.
I am not a dev, so not positive this is what you will need to do. I think you need to RUU your phone. If phone is Sprint HTC M9, OMJ has a thread with the latest RUU and all the instructions. Of course this does assume you can get into download mode. I had a similar issue a while back, ended up I had to use adapter for SD card into PC to transfer the RUU. Then put SD card back into phone. Hope this gets you started.
Ok thanks, I'll try that.
fldave612 said:
Ok thanks, I'll try that.
Click to expand...
Click to collapse
You get this fixed?
Yes, I was able to get it fixed, I had to RUU it with a signed firmware from HTC directly. Thanks for the help.