Hi all. Have a weird problem with my G1 that my girlfriend is using at the moment. It is rooted and I have tried various ROMs to see if I can fix the problem.
The problem I am having is that once the phone gets plugged into charge, it turns itself off and it seems to loose the ROM that has been flashed so then I have to reboot into recovery and re-flash it. It does this every time I try a different ROM so can't be related to one particular ROM.
Does anyone have any ideas why it would do this?
Related
Ok so here is my issue i was on 1.2 superD and when i try to turn on my wifi it reboots my g1, so i did a wipe clean install and tried again still the same, then i tried to run fix_perm then try still the same issue and since i wipe everything out i figure might as well update to new SD-rom so i flash danger , the flash supD 1.8 and tried to turn on wifi and still no go there, any have any idea what mite causing the reboots when trying to turn on wifi, i know it did work at one point, and i cant return the phone, open to ideas or suggestions. im think is hardware failure.. but i could be wrong too
any ideas anyone
same problem here. I messed with tiwlan.ini a couple of times and my htc dream AKA T-mobile G1 reboots every time i turn on wifi
I have pretty much the same problem, except my phone hangs and then reboots when i try to turn Wifi off using the pull down bar.
CM 6.1.0-DS
2.22.27.08
2.6.35.9-cyanogenmod [email protected]#1
anyone?
same problem here on htc legend. i know there was no problem before i flashed a new radio, but going back to the old radio doesn't help things.
found this: http://forum.xda-developers.com/showthread.php?t=1012925
trying the solution out. might help others too.
hi
I have got a Nexus ,just after i got it i unlocked and root it after it changed the Rom .
now it hangs most time for example when i plug the charger sometime it hangs and a big X with an open lock appears and i have no way else to remove the battery.
and some time when i use the GPS and navigation it restarts.
i have tried many Roms and Radios but even when i want to go to recovery it hangs too ,and sometimes no.
i tried to switch to ERD79 (fastboot commands)but i found out that when i finish it,still the radio Ver. is 4.06.00.12_7 .
when i change the Rom or radio it restarts and restarts and some time hangs again.
so please help me to solve this problem
thanks
Did you wipe the data?
yeah ,
every time i wiped data .
what's your version of Hboot and recovery?
HBOOT-0.35.0017
recovery Build RA-nexus-V1.8.0.1
really need help ,i can not use the phone .
it sounds like a hardware problem, but could you try a new ROM see if the problem is still there?
well ,last night i tried cyanogen 6.1 with radio 5.12.00.08 but still have problems.
how can i become sure about the hardware problem ?
is there any test or something like this ??
few days ago one of my friends told me to try RUU.
actually i don't know what is RUU and where i can find it.
i have searched for it and found some for desire but not for nexus.
I was hoping that maybe someone could help me troubleshoot my problem.
I recently flashed a new ROM and since then my WiFi has been acting up. It will turn off then instantly turn back on and sometimes take longer than normal to turn on. This is causing quite a problem as it doesn't allow for a stable connection.
At first I thought it could be the router but even when I'm out of range, in town, if the Wi-Fi is enabled it still turns off and on.
So I've tried flashing a custom kernel, and several different ROMs and even the Radio. Nothing seems to fix it. I have wiped and formatted everything I can think of several times but regardless of ROM the Wi-Fi still turns off and on constantly.
Any help would be greatly appreciated.
That happned to me when i flashed stock recovery of older rom version, for example: I had 1.29.401.16 rom with 1.29.401.7 recovery... Probably you have the same issue
Sent from my HTC One™
So you think it could be the recovery at fault?
Yes, are you running your htc with custom recovery, if yes, the problem is not in the recovey
Sent from my HTC One™
I am running clockworkmod recovery. Any more ideas?
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.