Related
I came from Das BAMF Remix 1.6.3; performed factory wipe/data reset, wipe dalvik and wiped cache. I flashed the GB Radio via Hboot (update=yes; then updates by doing 2 things, then hit power to restart). I then flashed the ROM.
The first two (2) times I flashed 2.0-4.0 and could NOT get Wi-Fi to work, but I had 3G working no probs as well as GPS. Went out for a couple hours and had no issues. Got Back, and I still could not get Wi-Fi to connect. I reflashed radio..no dice...re-downloaded the ROM, did a complete wipe and reflashed both the ROM and radio. Still would not connect, even after I downloaded Test7 kernel (kernel shouldn't mess with my mobile connection?).
I then went and downloaded 2.0-4.01, and now I can connect to Wi-Fi. Now the problem is that I am stuck on 1x Mobile Data and cannot get 3G. I've re-wiped, reflashed and downloaded Imeseyons new kernel..still stuck on 1x. I have even tried toggling Airplane mode, but cannot get it to 3G connection.
Any ideas?
Dunno if it will make any difference but flash the rom 1st then either battery pull or adb into hboot to flash the radio. Maybe others can confirm if this might help or not.
Not sure if this is the root of your problem, but the directions given by the developers of these gingerbread roms indicate that you should put the rom and radios on the root of sd card, flash the rom first in recovery, don't reboot, get into hboot via adb, then let the radios flash, and reboot. It sounds like you flashed the radios first, and then the rom. Maybe this is causing your problems?
lanceman5000 said:
Not sure if this is the root of your problem, but the directions given by the developers of these gingerbread roms indicate that you should put the rom and radios on the root of sd card, flash the rom first in recovery, don't reboot, get into hboot via adb, then let the radios flash, and reboot. It sounds like you flashed the radios first, and then the rom. Maybe this is causing your problems?
Click to expand...
Click to collapse
Don't think so, cause I have tried both ways. Also, in Ad's posts he recommended both ways.
Either way, if I botched it the first time, it doesn't make sense that with the same radio I was getting 3g but no Wi-Fi, but now I'm getting Wi-Fi and no 3g.
I reflashed back to Remix 1.6.3 and have 3g+Wi-Fi right away.
And 3g returns..On 1.6.3.
Sent from my ADR6400L using XDA App
Someone will correct me if im wrong, however it could ne a kernal issue, had the same problem, flashed imo's 2.4 test 7 kernal, and now i get get service on bamf 2.4, just a thought
Sent from my ADR6400L using XDA Premium App
Thunder Droid said:
Someone will correct me if im wrong, however it could ne a kernal issue, had the same problem, flashed imo's 2.4 test 7 kernal, and now i get get service on bamf 2.4, just a thought
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
When I wiped and reverted back to 1.6.3 I lost a Superuser file. I decided to re-root and start from scratch.
Re-rooted, then flashed 2.0-4.1 and let it startup. Then shutdown and went into Hboot and flashed GB ROM. Went through a normal startup and I had 1x which after a couple of minutes turned into 3G, but very laggy. I then flashed Imo's 2.5.4 kernel and re-started. 3G came up and speeds were just fine.
A lot of work to get BAMF to work, but I'm happy. Now working on adding Launcher Pro, Fancy Widget and a few other personalizations.
I'm Running Das Bamf 1.6 remix and I flashed leankernel extreme from Kernel Manager and now when I turn on wifi it just says error. I tried flashing two other kernels but I'm still getting a wifi error. I've restarted a few times and nothing has worked. Any suggestions? Thanks everybody
I would suggest downloading the kernel outside of kernel manager and flash it in recovery to see if that works. I prefer using recovery to flash things instead of Rom Manager of Kernel Manager. I have heard using something besides recovery could cause errors.
I would agree. Wipe Dalvik cache. I first flashed kernels through rom manager but it never worked great. Did it through recovery and things are very good. One small bug but hopefully that gets resolved soon. Im on Imoseyons lean kernel on normal mode. The battery saver mode did not work at all for me. Drained the battery like I drain a bottle of beer.
Its not just you, and at least my error has nothing to do with flashing it in through rom manager or kernel manager since I use neither. No matter the kernel I use, Ive not had wifi unless I had the stock kernel or for one day on Ziggys 5/3. Ive been having this issue for MONTHS now and Ive seen a lot of others have it with no resolution. I just tried nuking the Dav, restarting and nothing. Still getting the "Unable to scan for Networks" toast notification.
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
What gingerbread roms have you tried? Also, what kernels were you using?
Sent from my ADR6400L using Tapatalk
don't have this issue on Synergy 3.0 running the latest ziggy kernel
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
I would try wiping, then installing the setup in my signature, but don't restore any apps at first or sync with Google so they're downloaded automatically. I think that you've got an app and a kernel that's interfering with one another. Try the ROM bone stock before you start restoring apps and see if the problem is there.
Rooted Thunderbolt on BAMF Sense 3.0 RC 4 with MR2 radio and latest dreamKernel.
Silentdawn3 said:
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
Click to expand...
Click to collapse
when you say both kernels are you referring to the radios? cause mr2 and mr.5 are radios not kernels
Silentdawn3 said:
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
Click to expand...
Click to collapse
I share your pain with this exact problem. I have been doing all types of testing these last two days to see if there is any combination of ROMS and Kernals that would work for me.
I can flash any ROM I want, and the only Kernal that I can successfully use is this one:
Imoseyan GB Stock Kernal
With this Kernal, I can use my phone all I want, let the screen go black, hit the lock screen button and I have never had a reboot.
I have run Thunderstick, BAMF 2.1, BAMF 3.0, Gingertheory, with this kernal and it will run fine.
When I change to any of these Kernals, I get the constant reboots when my screen goes off, just like the OP described.
* Imoseyon Lean Test
* Imoseyon 184mhz
* Imoseyon USBfix
* Imoseyon 2.5.3 test 7
* Nerozehl's dreamkernal 2.3.2
Of course, when flashing any ROMS and Kernal combinations, I would do a complete wipe before doing so. I should also mention that I am using MR2 radio. I can also use MR2.5 with the GB Stock Kernal and it runs fine.
So like the OP, it seems to be something to do with the kernal that my phone does not like and can't figure out. Anything other than the stock kernal, and my phone will constantaly reboot after the screen goes black.
I should also mention that I have used the speektweah.sh in terminal emulator and tried all of the different voltage settings and it had no effect. Also disabled it and tried using SetCPU and no luck either.
I have also tried all of the ROMS without allowing any apps to update by skipping the google account sign in. So basically all of the ROMS were running in their native state, and the outcome would be the same.
FOR THE OP
Try running the stock kernal and let us know if that works for you. You should just be able to flash it in CWM, reboot and you will know right away if it is working correctly.
The real question I need to figure out is this. What is different about the GB Stock Kernal from all the others that would be having this impact on our phones?
I've tried all of this except installing the above kernel. I'll give that a shot, thanks.
As for installing without apps, I've tried that. Tried everything. Lets hope the stock kernel works!
I've been running Das BAMF Gingerstripped with Imo's kernel and never had this issue. It sounds like maybe something is bad with the cpu profiling becoming unstable when screen-off profiles kick in.
sg1dan said:
don't have this issue on Synergy 3.0 running the latest ziggy kernel
Click to expand...
Click to collapse
I can confirm that this one worked for me too. Synergy 3.0 running Ziggy's Kernal and everything works well.
Anyone know where to grab just the Kernal? Can't seem to find the latest download.
I should also add, that when I do flash the Stock GB kernal so that my ROM will be stable.... my camera freezes everytime I try to take a picture. Happens in every ROM I mentioned above. However, it works fine before I flash the stock kernal.
running "stock kernel" it looks to be fixed. Looks like I tried this before as I already had the file but.... works now for some reason
Thanks.
Will report back if it ****s up
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
yes its a kernel issue. what version of software are you running?
I had the wifi error issue, and i flashed the kernel on top of the rom and it works now
Depending on the ROM you flashed, it may or may not display "Flash Kernel after." In which then you flash it. This'll take care of all Bluetooth and Wi-Fi Issues!
If you're having issues let me know.
I had the same issue I was using stock kernel for tmobile version 1.36.531.6 on mine which I had over the air updated to 1.43.531.3. This created the wifi error and bluetooth issue, I had to try different kernels to try to figure this thing out...It will posted in my read me page when I get a chance
It's a kernel issue, there are actually three different kernels, not two, I posted this in xboarders thread, but He hasn't updated his page.
kernels
1: for tmobile software stock 1.43.531.3, this is not available anywhere on the amaze forums, i had to personally extract this from the rooted stock rom that xboarder provided
2: for tmobile software stock 1.36.531.6 and 1.36.531.5 and lower, this stock i believe is the one xboarder has up as the original boot.img
3: faux's custom kernel, this kernel will work with all versions i believe
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
andy55 said:
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
Click to expand...
Click to collapse
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
I told you rooting is not for you but you thought I was attacking you. But seriously if you do not know what you are doing you will mess up the phone. you still havent because there still is no s-off so pretty much your phone is kinda locked
seansk said:
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
Click to expand...
Click to collapse
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
seansk said:
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
Click to expand...
Click to collapse
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
yes lets wait, with people with lets experience, I tend to dumb things down when asking questions...I am not doing it to demean them, but It's the only way to get any real good answers and being able to help them. Then over time they'll learn
sean, I was running the android revolution 1.1, and tried a couple different kernels and nothing
But I ended up fixing the issue finally. The super wipe zip file I downloaded with AR 1.1 was corrupt, and wouldn't load properly, so I was installing a rom without doing a wipe every time. So, I put a working copy of the zip on the sd card, and did a manual wipe of the caches, re-installed AR 1.1 and all is well.
So, even though I was following all necessary steps, I failed to realize that the wipe zip was faulty, and really messed everything up, and when I changed the rom again to beastmod, I didn't install the correct kernel with it, so yet more issues.
Happy to say that it's all over, and I have a much faster phone with alot less bloat on it. Thanks to everyone!
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Flashed the kernel as xboarder showed in his thread and video.
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?