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.
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
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.
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.
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
try going back to 100% stock by flashing stock firmware on ODIN. Next root and twrp.
sarreq said:
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
Click to expand...
Click to collapse
I have a t700 and had the same problems you have installing marshmallow. What worked for me was advanced wipe in twrp, everything except internal storage and sd card. From there hit the home key, and flash the marshmallow rom, then reboot into recovery, next flash su 2.5x, then reboot into recovery. Lastly, flash the benzo gapps, and reboot system. My play store started working after i installed in that sequence on t700. Ive heard a few others have had to do that process 2 or 3x before it works, and some, it doesnt work at all. Worth a try though. Good luck.