Hi!
I'm having some troubles with my DX since one week, tried a lot of manipulation and nothing is working... So I am asking you if you have any idea?
The first problem I had was the wifi that didn't "lock", it switched itself all the time from ON to OFF and opposite. The rom installed was ELEGANCIA and the recovery was TWRP. I thought it was a problem with the Rom. To try solving the problem, and because I'm curious, I installed Sense Revolution R5 and with this came my second problem...
It couldn't boot anymore, I think I did it right, not the first time I do that but we never know. And since then I'm unable to install custom Roms. The only thing that works fine is installing stock recovery, re-locking the phone and reverting back to stock using RUU, doing that the phone boots normally as when he got out of the box. But with custom Roms the phone doesn't want to boot... Where could this problem come from?
And for the wifi there is no change, it is still giving me the same bug... or sometimes I have the "activation" message without anything happening or an "error" message...
I tried disassembling the phone, as it was really dusty in it, I thought it was the problem but nope...
Thanks (sorry for my english mistakes)
Some news: unlocking, rooting and flashing custom recovery work fine.
But I tried flashing a custom kernel, and again it doesn't want to boot...
Nobody has any idea of what else I could attempt?
perhaps you aren't flashing the boot.img first?
thanks for your interest! i've just tried that once more, but nothing changes...
I have noticed though that it won't boot every time I do a system wipe. Wiping cache gives no problem, haven't tried wiping Dalvik Cache yet, and "Factory Reset" gives me a "Failed" message.
(All this using TWRP, who once worked perfectly on my phone)
EDIT: I've juste tried wiping Dalvik Cache and it doesn't give any problem... So maybe is the problem coming from the wiping of the system?
No suggestion? still having those problems... :/
Related
Hello
First off not sure if I should post here so my appologies in advance if I made mistake.
I have been flashing my HTC Hero for some time now and lately I have been expiriancing that phone will not boot at all. It just hangs with HERO logo and its stuck there.
Sure I can reflash it again but same thing happens again after few days of use and I AGAIN needed to reflash my phone.
Right now I am using SuperHero rom but same error came up with VillainRom and Crons so I dont think its ROM related.
Radio is not flashed in a while now so I do not think thats the problem eather.
So my question is does anyone here has same issue as me and can it be fixed ?
Thanks
I don't have that issue but if you are using amon_RAs recovery you should wipe everything. factory reset, dalvik wipe, ext wipe if youre using a2sd. then flash a new radio image:
http://forum.xda-developers.com/showpost.php?p=4594434&postcount=2
the last one there "63.18.55.06JU_6.35.09.26"
unfortunately your issue can be related to anything and pretty much nobody can guess. still as I see in your signature your radio is pretty much outdated and some ROMs seem to have broken a few radios. I think it's pretty much recommended that you sometimes re-flash your radio because of some broken ROMs out there. That's just what I have read but as I am not a developer I can't tell. So if you're having issues with your phone re-flashing does not hurt you, but if everything works fine there is no need to do that.
in short: imho wipe _everything_ and re-flash _everything_ and _don't_ restore nandroid backups or so, that way wiping does not make much sense
Update your Radio and Recovery maybe?
Sorry guys, but my signature is outdated.Will be updating it right away.
Of course I updated RADIO (some time ago) and version that I am using now is 63.18.55.06JU_6.35.09.26.
I always wipe everything before I use new ROM and setup everything from scratch. No restores at all.
@Feeyo what do you mean by update recovery (radio part I understand) ?
Thanks guys, still need input, ideas
Moved as not Android Dev.
Same thing is happening with my hero, only happened recently after i started using overclocked roms however, maybe something is wrong with the CPU?
hey there guys, long time lurker, first time poster *i think*
I searched the forums already but no posts has the same particular problem i have
after flashing the latest 1.9.1 rom, i started getting error everytime i try to enable portable wifi hotspot, i tried reflashing the rom but it still wont work...
anybody got suggestions on how to fix this?
thansk ^_^
mihajaru said:
hey there guys, long time lurker, first time poster *i think*
I searched the forums already but no posts has the same particular problem i have
after flashing the latest 1.9.1 rom, i started getting error everytime i try to enable portable wifi hotspot, i tried reflashing the rom but it still wont work...
anybody got suggestions on how to fix this?
thansk ^_^
Click to expand...
Click to collapse
How did you flash and what baseband are you running? I did a factory reset, flashed stock recovery, flashed stock 354 rom, flashed streakmod recovery, flashed 1.9.1, then did a Dell factory reset. Sounds worse than it really is. I haven't experienced your problem (nor other problems posted by other users) and can only assume that flashing over a fresh stock rom install in some way helps.
Did a cursory test of wifi tethering and it seems to work fine.
Paired my old iphone 3g and browsed a bit and no hitches.
Have you tried doing a factory reset? Installing streakdroid leaves all data in place so reinstalling is only half of it
strick242 said:
How did you flash and what baseband are you running? I did a factory reset, flashed stock recovery, flashed stock 354 rom, flashed streakmod recovery, flashed 1.9.1, then did a Dell factory reset. Sounds worse than it really is. I haven't experienced your problem (nor other problems posted by other users) and can only assume that flashing over a fresh stock rom install in some way helps.
Click to expand...
Click to collapse
Im pretty sure did the same thing more or less.. i forgot to mention that it used to work until i tried to create a password for users to connect, upon trying to change or enable a wep code, the activity crashed and since then, it gave me errors everytime i try to enable tethering...
^_^
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
I'm helping a friend with her S3 i9300. It was running very sluggishly and starting in the last couple months she's been having a sleep of death issue.
It works fine (albeit slowly) while she's using it but when it sleeps for more than 10 minutes it doesn't turn back on without a lot of trouble or a holding down the power button and hard resetting. Every once in a while it only boots if I go indirectly through download mode.
I've confirmed with the play store app that she does NOT have the "insane chip" involved in the SDS issue. I've also factory resetted, rooted, tried flashing a custom kernel, a custom TW ROM (S5 sensation) and now an AOSP ROM (resurrection remix) and the problem persists.
Looking at other users' suggestions I took it apart and cleaned/played with the power button, even replacing it with the one from my old t999. Still the same.
I'm at a loss at this point. Has anyone run into this issue and found a fix I'm missing? Thanks for the help.
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
TENN3R said:
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
Click to expand...
Click to collapse
Thanks for the reply. Before flashing any ROMs I've always made sure to do a factory reset and then individually wipe System, Data, Cache, and Davlik Cache even though I know I'm duplicating some of the wiping. Unfortunately that did not work in this case.
I'll give the MEGA/SUPER wipe a try and report back.
Thanks again.
Looks like MEGA wipe didn't do the trick either. The phone is on NA8; is there a newer baseband I can try? Not sure what else to try.
At this point I'm thinking it might just be a hardware issue.
Flash the latest stock firmware from sammobile then factory reset, remove sd card and sim then test with a different battery.
If still the same then it is a hardware fault, motherboard/cpu.