Hey there
I have been having weird problems with ARHD 17 and 17.1. About a week ago I looked at my device and realized there was no signal, so I went into Settings and saw that Wi-Fi said "Error" under it. I tried doing a hard reboot but the same thing continued. Then I decided I'd reflash the latest Nandroid backup I took but the same problem continued. I then wiped the device completely, flashed that ARHD boot.img, installed the ROM from CWM, and then rebooted the phone but the SAME THING HAPPENED AGAIN. It was really frustrating so I decided to try a different custom ROM and everything worked fine from then on.
I then tried installing ARHD again (after taking a Nandroid backup of my current ROM, of course) two days ago and the same problem happened. It's really frustrating and I don't know what else I could do.
Right now I am downloading ARHD 18 because I just love that ROM and I am hoping it won't have this issue.
My device is S-ON, international version (.401), 1.31 HBOOT (latest), and is GSM.
Any ideas?
Well, I thought I should update this just in case anyone faces the same problem in the future and uses the search feature.
I ended up doing a factory reset (which did not wipe my virtual SD partition, for some reason), flashed ARHD's boot.img, installed ARHD 18 and chose Improve EXT_4 performance and also Wipe Data and it worked!
For some reason, though, the installation percentage doesn't increase from 0 to 1 to 2 to 3 and stuff, but it remains as 0 and then it suddenly becomes a 100%; however, the process itself was fine since it extracted, copied, and installed files.
TarekElsakka said:
Well, I thought I should update this just in case anyone faces the same problem in the future and uses the search feature.
I ended up doing a factory reset (which did not wipe my virtual SD partition, for some reason), flashed ARHD's boot.img, installed ARHD 18 and chose Improve EXT_4 performance and also Wipe Data and it worked!
For some reason, though, the installation percentage doesn't increase from 0 to 1 to 2 to 3 and stuff, but it remains as 0 and then it suddenly becomes a 100%; however, the process itself was fine since it extracted, copied, and installed files.
Click to expand...
Click to collapse
I had the exact same problem 2 days ago - wifi error and also data off as "service not available". i had given up on ARHD, but will now try your method again, although I'm pretty sure I did tick the ext4 enhancement and data wipe.
Try factory resetting from within your current OS first, though. That's one thing I hadn't done in the past.
Related
Everything has been fine until yesterday morning, when at work I realised my phone was rebooting every 3 or 4 minutes.
I hadn't changed anything, I hadn't flashed anything, I don't O/C my phone. I'm usins AOKP Milestone 3 with Immoysen Kernel.
I've tried -
Reflashing AOKP with no custom kernel
Wipe & flashing CM9 Kang
Wipe & flashing MCR
When I tried to make a Nandroid of MCR (as it seemed to be okay for an hour or so) it gave an error when it got to backing up the data partition. Could their be a corrupt bit of memory there?
Also, at one point I think it might have reset while in recovery, which makes me think it's hardware, not software.
Today I've tried -
locking and unlocking the bootloader
Android_Revolution_HD_Super_Wipe_Lite
Wipe and flash AOKP B23
Generally it seems to be better after a wipe and a fresh install, for a little while, but then seems to start rebooting again later.
I locked and unlocked again around an hour and a half ago and all seems good at the moment, but I thought I'd post still to see if anyone else has had this happen or see if anyone has ideas of how to de-bug it should it come back?
I had this problem after upgraded to 4.0.2. Fresh install did solved this somehow but last week it came back again when dial starts...
Tho it seems un-checked all options in location services would not reboot during or after the call
Hope this info could help u
Thanks. Well, 6 hours since I locked the bootloader and unlocked it again (to wipe everything, including the SD storage) and it's not rebooted once. Looks like it's fixed *touch wood*
I have random turn offs... dunno if it relates. Its a little unnerving...and annoying. No roots, no unlocks, just vanilla 4.0.2.
Sent from my Galaxy Nexus using XDA App
Hey, guys!
I am in a desperate need of help. Here's my situation:
I've got an HTC Desire (obviously), which reboots every time the ROM starts. It all began after I decided to move back to a Sense ROM after having been testing ICS for the past couple of weeks. So, I flashed RCmix S - a ROM I knew to be stable and working snappily on my phone. Everything went well, I restored my apps with Titanium and then decided to remove some of the junk stock apps. When this was done, I restarted the phone, only to be faced with a series of reboots every time I got glimpse of the Sense UI (i.e. seconds after unlocking the SIM card).
I thought this might be a ROM-related issue, so I tried another one - Supernova. Same thing. Tried flashing it several times after full wipe always. No luck.
During the whole process I switched HBOOTs a few times - from stock, to Fatsys (IN2SD), back to stock. Tried several recoveries (AmonRA, 4Ext touch).
Even flashed official RUUs at least 3 times in order to get the phone back to its factory state. Once the stock ROM worked fine. Then I went on to root it and tried flashing one of the customs ROMs again, which, predictably, began rebooting just after SIM unlock.
I thought this might be connected to problems with the SD card, so I reformatted it completely - 6,8 GB FAT32 + 1 GB Ext4, using GParted. All by the book.
No I've got a clean SD (removed all the previous folders), but it doesn't seem to solve the problems.
Can anyone, please, think of something that I could do in order to get my phone back?
P.S. I forgot to mention, that my phone is S-Off. It struck me as strange, though, that it stayed S-Off even after flashing the RUUs.
New development: this morning, after successfully creating a Gold Card, I went on to try and flash a 2.2 RUU again. This time, however, the installer announced it was unable to access certain files and thus the flash process had failed. Meanwhile, the phone itself displayed a triangle and an exclamation mark on the 4 corners of the screen. I no long can access Recovery or the Bootloader. Help me, please!
Never mind, I managed it myself.
Team Vanir Jellybean v2-7, Galaxy Nexus Verizon
Last week i was having issues with the phone not booting, or just locking up not responding etc. A wipe seemed to help, and wit work for a while. I'd get my phone setup to where I wanted it again, and then the issues would come back.
I found a post that said it was possible EXT4 formatting issues because of a bad poweroff. So I downloaded all the stock 4.04 images, fastboot erased system boot recovery. Flashed the latest radios, stock system boot userdata and clockwork recovery 5.5.0.4. Booted seemed to be fine.
Rebooted into Clockwork and installed Vanir v7, ran fine for a few days. I thought the issue was gone. Until this morning when I got a text message and went to unlock the phone and it was locked up. I pulled the battery and that is when everything got extremely bad
Would not boot past the boot animation. I tried the following
I reinstalled the ROM,
i treid to wipe data,
wiped data and reinstalled the ROM.
although I was able to make a nandroid backup before I tried all of this
Then as a last resort I went into the mounts and storage and FORMATTED /system /data and /cache in CWM. Reinstalled the ROM and it actually booted.
What greeted me there is the last thing I'd EVER expect to see. I don't know how, what or why but all my data was there... every app text missed call... all of it.. even tho I had wiped AND formatted several times and did NOT restore my backup. EDIT: Even more oddness... My user apps didn't get wiped, they are all still there, but they are all acting like I had cleared their data through the applications menu....
I still don't know if this is because of a NAND issue that formatting fixed both times (flashing stock and using format in CWM) or if it will ever come back. Has any1 else had any issues of this sort? I really don't think this is a ROM issue.
you're probably causing more damage by flashing this, wiping this and that. best option is to leave it stock for now by flashing the factory image again. if it is a NAND issue then it would have stopped booting when the issue occured. but if it is still causing problems then send it back for a replacement.
I had a weird issue today, when re-installing rom, booted into recovery, started the installation process, and let the rom (maximus 3.3) format the partitions, all went well until it started to verify the partitions, the phone rebooted. So I went back into recovery, recopied the maximus rom, started to reinstall, got the verify partitions, same thing, rebooted. Tried ARHD, same thing. Went back to Maximus, told it not to wipe the partitions, everything installed correctly.
Has anyone had/heard of this issue? Is it possible I have bad memory in the phone? I've flashed multiple roms on this phone and never had an issue, just looking for some answers.
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.