Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
Related
My GS2 was rooted and had CWM before the OTA update. My update kept failing so i reverted to stock with bloatware and 3e recovery, re-rooted, and the OTA went through successfully. Wifi was working before and after, but, when I flashed CWM with Mobile ODIN Pro, my wifi no longer worked. Even reverted back to stock 3e with Mobile ODIN and it still didnt work. Have tested this 3 times with the same results. Has anyone else ran into the same issue?
D3M3NT3D_L0RD said:
My GS2 was rooted and had CWM before the OTA update. My update kept failing so i reverted to stock with bloatware and 3e recovery, re-rooted, and the OTA went through successfully. Wifi was working before and after, but, when I flashed CWM with Mobile ODIN Pro, my wifi no longer worked. Even reverted back to stock 3e with Mobile ODIN and it still didnt work. Have tested this 3 times with the same results. Has anyone else ran into the same issue?
Click to expand...
Click to collapse
The only way I was able to fix this was revert to stock 2.3.4 there is a thread somewhere here under rom 2.3.6 by vladm7 that has a wifi fix page 7. It was just easier for me to flash u.named rom
Sent from my SAMSUNG-SGH-I777 using XDA App
Hmm...that wifi fix seems like its only for Entropys kernel (according to op that is)
It is possible that it may work for other kernels. There is only a small change to define the wifi device node location. Backup your files by pulling them first before pushing the new ones to try it out. Reboot isn't necessary.
I have an initramfs update that MIGHT fix things in my kernel, I might be releasing tonight - not sure.
Very busy with the holidays.
ok, so i unlocked and rooted my rezound, everything was working 100%, then i start flashing diferent roms and it was conecting to wifi with no problems, however when i flashed ( or tried to flash ) a new kernel ( dont remember which one ) wifi stoped working for me, it scans but doesnt pick up any network. i went back to stock kernel and nothing, re-locked device and installed verizon factory Ruu for the rezound and Wifi still doesnt work. Im going crazy here please help, maybe im flashing the kernel wrong but re-locking and restoring to factory Ruu should have fixed it
I was also having the same issue and tried reinstalling kernals and nandroids. I was loading the kernal through Amon Ra interface directly and no matter what I did I still had issues. Sooo, I revised my recovery process and found that dummy me can't read instruction correctly. The issue was resolved after I did a factory reset on the rom (Ineffablis v1.0) then I followed the instructions for installing the kernal (I'm using the SmartassV2 kernal from dsb9938; flash from SD, then flashmethis file and finally through HBOOT, it's a process ok?), rebooted and I was able to get WiFi working again. I've had this issue whenever one of the additions I was trying did strange things to my phone and have sucessfully restored WiFi (about 10 times for this occurance). I've also had to do a hard reset (pulled the battery) and follow the process to get back to functioning. Hope this helps.
i locked the phone again, and ran the rezound stock Ruu and did factory reset, still not picking up any networks. the wifi doesnt give and error it scans and everything, but for some reason it just doesnt pickup any networks
If you read the complete directions when flashing a rom... They state you will need to flash the wifi module after a fresh install. So just flash the kernel over again and you will have wifi working.
Thanks a lot, finally got it working
Sent from my HTC REZOUND using xda premium
I'm having the same problem where my rezound won't find any networks. My bluetooth won't turn on either. How were you able to fix it?
thanks,
ron
Edit
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
Hi, been trying to flash the faux kernel on my girlfriends amaze. No matter what I do, it comes back with an error. I am s-offed and unlocked and using 4ext. Tried the flash img gui app and that returned an error of missing a file. I have redownloaded over and over, as well as tried different versions of the kernel, all with the same error. This all started because her phone kept rebooting my router and thought it might be tied to the ics wifi problem. Anyone have any ideas? I was able to flash android revolution, but viper would not boot. With revolution, it still reboots my router, but it is still using the htc kernel, so would like to try a different one. Any help would be appreciated. Thanks!
Edit: Saw something that was mentioned in a thread while doing another search: a "First time Kernel for Amaze", but the link didn't work. Do I need to do this first or what?
Well, got everything working. What I had to do was flash an insecure kernel, then I could flash other kernels. Unfortunately, the wifi problem is still there. As soon as I turn on wifi on the phone, my router reboots. Haven't been able to find any info on this. Anyone have any ideas on this issue? Currently using latest viper rom with faux kernel 31. Also, anyone recommend maybe a different rom that might fix the issue? Any others with sense 4 and Bluetooth working? Thanks.
New Kernel?
Been trying to flash the faux kernel myself with the status 7 assertion boot image error. What kernel did you flash first? And did you have to reboot and go back into recovery to flash the faux kernel?
Thanks!
I left my phone on the counter near the dish drainer and smoked the usb/mhl port. Another time, I filled the thing with crushed banana. I can charge the battery using an external charger (hasn't burned my house down yet), but can't use the usb port at all. So I set the phone aside for a while.
S-On, rooted, was running Scrosler's Cleanrom DE 1.4. I got tired of my wife's iPhone 4 and started using the ReZound again recently, but got myself into trouble flashing the clockworkmod recovery over my AmonRA and can't go back. I'm stuck on CarbonROM (used HTCDumlock) with no stability unless wifi and mobile data are disabled.
Is it possible to get AmonRA back (or at least restore the nandroid I made with AmonRA) without a usb? What about S-Off without any USB connection?
yimpierre said:
I left my phone on the counter near the dish drainer and smoked the usb/mhl port. Another time, I filled the thing with crushed banana. I can charge the battery using an external charger (hasn't burned my house down yet), but can't use the usb port at all. So I set the phone aside for a while.
S-On, rooted, was running Scrosler's Cleanrom DE 1.4. I got tired of my wife's iPhone 4 and started using the ReZound again recently, but got myself into trouble flashing the clockworkmod recovery over my AmonRA and can't go back. I'm stuck on CarbonROM (used HTCDumlock) with no stability unless wifi and mobile data are disabled.
Is it possible to get AmonRA back (or at least restore the nandroid I made with AmonRA) without a usb? What about S-Off without any USB connection?
Click to expand...
Click to collapse
Kind of a pickle without a working USB port...
You can not gain S-OFF without a working USB connection using any known (Juopunutbear, rumrunner, or firewater) S-OFF method, sorry. Although JTAG may be a possibility.
If Carbon is running and root is working, you could use Goo Manager to install TWRP, it has HTC Dumlock built in, and you could flash in Evervolv or something else more stable (later incarnations of Carbon caused me lots of issues as well). The backups are not compatible between Amon Ra, CWM, and TWRP though.
As far as getting Amon Ra installed without a working USB connection, it MIGHT be possible, but it is over my head... The real issue would be even if you did get it back on and restored your nandroid, being S-ON means you still need to flash your boot.img manually, even from a nandroid restore, which would be another issue altogether and probably highly difficult (if possible at all).
Although, if we are talking water damage and possible banana damage (did I really just type that?!?!) a different ROM may or may not help, this could all be a exercise in futility that one wrong move could brick you.
Hmmm. I did have the phone working well with CleanROM DE, so I know it's at least worth trying. I'm also not afraid of a brick seeing as what I have now is basically no better. Good point about the boot.img. I hadn't thought of that.
Carbon is working and moderately stable when wifi and mobile data are off. When I enable wifi, I tend to go into a boot cycle with 1-2s before reboot to disable it again. When enabling mobile data, I get frequent popups saying something like android.com.phone stopped working, and not data anyways. I do have a working recovery right now in CWM (up to date non-touch). But, I don't think that has HTCDumlock built in.
yimpierre said:
Hmmm. I did have the phone working well with CleanROM DE, so I know it's at least worth trying. I'm also not afraid of a brick seeing as what I have now is basically no better. Good point about the boot.img. I hadn't thought of that.
Carbon is working and moderately stable when wifi and mobile data are off. When I enable wifi, I tend to go into a boot cycle with 1-2s before reboot to disable it again. When enabling mobile data, I get frequent popups saying something like android.com.phone stopped working, and not data anyways. I do have a working recovery right now in CWM (up to date non-touch). But, I don't think that has HTCDumlock built in.
Click to expand...
Click to collapse
Have you tried just booting into CWM, wiping everything except external SD twice, and reflashing Carbon again, the same one so you don't have to try to flash the kernel?
Probably too late now but did you try drying it out via the bag of rice trick?
I found this nice app for getting files on and off via wifi, not doing you much good if your wifi makes you bootloop though.
https://play.google.com/store/apps/details?id=com.dmitril.droidoverwifi
At this point, an SDcard reader would be my investment and store your backups on the internal SDcard. This would allow you to use PH98IMG's. As far as your mobile data and wifi is concerned. It really sounds like you havent flashed the boot.img matched with the rom. If you still have the rom zip about place it on your external sdcard while in rom in a folder called lunar. Run sysrw in terminal emulator then invoke a script named "menu". Choose option 4, then choose the SAME zip you flashed. You might auto-reboot to recovery, just reboot back to system without any changes.
Thanks. I got wifii to run stable. Did a couple more wipes and re-flashed. ES file explorer disappeared, so maybe my previous wipes were insufficient. Also changed from "Launcher" to "Trebuchet", so a couple variables working together. Either way I flashed TWRP now, so I have HTCDumlock again.
Snuzzo, I'll try and follow your steps to see if that fixes mobile data. Not working right now with mobile roaming enabled, LTE or 3G. I can place calls now, though!
EDIT:: ran the Lunar Menu script and flashed the boot.img (seemed successful). wifi is stable, but no data.
At least you now know how to use LunarMenu and can flash a ROM using that instead also with using dumlock. Option 4 reboots you into recovery, let's you do your normal wipes which you then flash the matching ROM zip. Dumlock basically flashes recovery to your boot partition so to flash a rom , you would be flashing boot partition twice. My implementation flashes it only once.
Sent from my Nexus 7 using xda app-developers app
You guys have been a great help. Thanks a lot
It seems my data connectivity issue is unrelated to the ROM i'm using. I must have caused it while tinkering or trying to update firmware. Now I'm on Evervolv with the same issues. Both Carbon and Evervolv are mostly stable with cell signal for calls and wifi, but no mobile data.
TWRP 2.6.3.0
HBOOT 2.21.0000
Radio 1.22.10.0310r/1.22.10.0308r
Is there something I can flash via a PH98IMG.zip that might fix this issue? Or maybe it's an issue with Verizon that they could fix?
I've a feeling it isn't your own Rez. I have a rom cooked with updsated Telephony. If things go right, release is imminent and very soon. No eta promised tho.
Sent from my Nexus 7 using xda app-developers app
yimpierre said:
You guys have been a great help. Thanks a lot
It seems my data connectivity issue is unrelated to the ROM i'm using. I must have caused it while tinkering or trying to update firmware. Now I'm on Evervolv with the same issues. Both Carbon and Evervolv are mostly stable with cell signal for calls and wifi, but no mobile data.
TWRP 2.6.3.0
HBOOT 2.21.0000
Radio 1.22.10.0310r/1.22.10.0308r
Is there something I can flash via a PH98IMG.zip that might fix this issue? Or maybe it's an issue with Verizon that they could fix?
Click to expand...
Click to collapse
you are on a VERY old hboot and radios....that is what could be causing your mobile data issues
REV3NT3CH said:
you are on a VERY old hboot and radios....that is what could be causing your mobile data issues
Click to expand...
Click to collapse
Thanks for joining in! I tried to update these, but was having a hard time. When I was looking at firmware update PH98IMG.zip's, it looked like you need to relock to flash these up, then unlock again (both requiring usb). Is it possible to update hboot and radios without doing this?
yimpierre said:
Thanks for joining in! I tried to update these, but was having a hard time. When I was looking at firmware update PH98IMG.zip's, it looked like you need to relock to flash these up, then unlock again (both requiring usb). Is it possible to update hboot and radios without doing this?
Click to expand...
Click to collapse
also need to be s-off to do this....with broken usb though only possibility i would say is on pure stock youd have to do all the updates givin by them...including stock recovery as well...and relocked bootloader is required...im wondering if theres a way around this that can be possibly worked in somehow...this is a tight predicament with the phone having no usb function and s-on though
1I went back to an old ICS rom (CleanROM DE 1.4) and got the same issue. Everything works except no data. I thought I'd post an update, but it's not so pressing here: LG G2 is in the mail!