[Q] Alpha-X ROM ICS --- Keeps rebooting! HELP! - HTC EVO 3D

PLEASE HELP!!
I installed the Alpha-X ICS ROM for Evo 3D. The problem that I'm facing is that it keeps re-booting to "No Service" state.
I've already tried toggling the "Airplane" mode method - the moment I turn Airplane mode off, the status bar shows that I'm connected to Sprint but within a second starts rebooting (showing the ICS start up screen animation) and goes in a loop for 5-6 times and then ends up back with "No Service" state.
Please help as I really like this ROM. I am a newbie here, hence XDA doesn't allow me to post directly to the Alpha-X thread.

[email protected] said:
PLEASE HELP!!
I installed the Alpha-X ICS ROM for Evo 3D. The problem that I'm facing is that it keeps re-booting to "No Service" state.
I've already tried toggling the "Airplane" mode method - the moment I turn Airplane mode off, the status bar shows that I'm connected to Sprint but within a second starts rebooting (showing the ICS start up screen animation) and goes in a loop for 5-6 times and then ends up back with "No Service" state.
Please help as I really like this ROM. I am a newbie here, hence XDA doesn't allow me to post directly to the Alpha-X thread.
Click to expand...
Click to collapse
Hello,
How did you flash this ROM? Are you on HBoot 1.5?
If so, you will need to re-flash this ROM using Fastboot (PM Me if you cant find the instructions)

Yes, I'm on HBoot 1.5 and flashed it using Flash GUI.
I was earlier using ClearROM.

Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess

[email protected] said:
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
Click to expand...
Click to collapse
I just wrote a post about this lol. Yes, it is only the system spp/data that will cause the issues. You shouldn't have problems restoring all of your user apps and data. I am running ALPHA X with all of my apps and data restored through TB with zero problems.

Bamba1260 said:
I just wrote a post about this lol. Yes, it is only the system spp/data that will cause the issues. You shouldn't have problems restoring all of your user apps and data. I am running ALPHA X with all of my apps and data restored through TB with zero problems.
Click to expand...
Click to collapse
im going to try this to solve my problems i have been having with my phone... you will be getting lots of thanks if it works lol

[email protected] said:
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
Click to expand...
Click to collapse
LOL....restoring system data can cause all sorts of hell for you as Bamba1260's already pointed out and you've already figured out the hard way, and there's nothing wrong with being a "noob" either, but keep in mind if you're looking for a stable and fully functioning phone or prone to freaking out when something goes wrong.....this is after all an ALPHA (experimental / for testing and bug reporting purposes only) rom. Indeed it is a very good alpha state rom, but things are likely to and should be expected to go wrong with it periodically.

hockeyfamily737 said:
LOL....restoring system data can cause all sorts of hell for you as Bamba1260's already pointed out and you've already figured out the hard way, and there's nothing wrong with being a "noob" either, but keep in mind if you're looking for a stable and fully functioning phone or prone to freaking out when something goes wrong.....this is after all an ALPHA (experimental / for testing and bug reporting purposes only) rom. Indeed it is a very good alpha state rom, but things are likely to and should be expected to go wrong with it periodically.
Click to expand...
Click to collapse
Yeah.. that's one more thing I did realize.. but was so enamored by the ICS ROM that I wanted to "taste" it one way or other..
Anyway, since I'm not done with my first 10 posts, I will have to post this bug(?) here for everybody's FYI that the GPS doesn't seem to work with this ROM.
So, know before you jump...
P.S. I still love this ROM - one of the smoothest that I've tried.

Related

[Q]Wifi issue still present factory reset fixed.

So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App

[Q] WiFi suddenly stopped working

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

Stuck on boot screen and have tried many, many times...

The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.

com.android.phone Crashing

So my com.andoird.phone has been crashing constantly which means I can't even do anything without the stupid popup coming up. I believe it's due to a faulty application. Anybody had any luck on fixing this? (running CM10 test build on my Evo 4g LTE)
Secondary question. Is it possible to remove the app from fastboot USB or recovery? If that were possible I think the system would sort itself back out. Thanks in advance
First, which build are you running? There have been like an average of 3 builds a day since Sunday.
Second, they have seen progressive improvements on each build.
I suggest getting the latest build from IRC if what you are running is a day or so old.
Also there are a lot of great people in there to help if you stick around.
sent from my LTEvo
elitelimfish said:
So my com.andoird.phone has been crashing constantly which means I can't even do anything without the stupid popup coming up. I believe it's due to a faulty application. Anybody had any luck on fixing this? (running CM10 test build on my Evo 4g LTE)
Secondary question. Is it possible to remove the app from fastboot USB or recovery? If that were possible I think the system would sort itself back out. Thanks in advance
Click to expand...
Click to collapse
Did you get this sorted out? I had the same problem of speradic fcing on that from the latest buil at 8pm last night. I wiped everything and reinstalled. It fc'd continuously until I got through the setup with my turbo fingers.
Everyone will tell you the same thing. The builds are on IRC and so are the bugs. Deck has not made a fix for this bug. It is a known issue. Get on IRC and off XDA for these builds.
AsinX said:
Everyone will tell you the same thing. The builds are on IRC and so are the bugs. Deck has not made a fix for this bug. It is a known issue. Get on IRC and off XDA for these builds.
Click to expand...
Click to collapse
I can talk wherever I please thank you...get off xda and go back to irc
Sent from my EVO using Tapatalk 2
ditto
I had a variation on this same issue. Did a TB of my user apps and system settings (not system apps) from my flex 1.75 install. Full wipe, installed the latest 8/2 CM10 from IRC, phone started fine, got one com.phone crash dialog and then everything seemed to be fine. Did the TB restore and when I rebooted I was stuck in an endless com.phone and android.process.acore crash loop. Only clue I have is that I noticed my wifi was connected when I rebooted (since my settings were restored).
Flashed to venom :-/
I'm on latest radios/firmware, s-off etc, latest TWRP, matching md5s etc
ristrettodreams said:
I had a variation on this same issue. Did a TB of my user apps and system settings (not system apps) from my flex 1.75 install. Full wipe, installed the latest 8/2 CM10 from IRC, phone started fine, got one com.phone crash dialog and then everything seemed to be fine. Did the TB restore and when I rebooted I was stuck in an endless com.phone and android.process.acore crash loop. Only clue I have is that I noticed my wifi was connected when I rebooted (since my settings were restored).
Flashed to venom :-/
I'm on latest radios/firmware, s-off etc, latest TWRP, matching md5s etc
Click to expand...
Click to collapse
Yeah i didn't have the issue except on reboot until I rebooted this morning then it went psycho. Its a pretty solid build otherwise.
Sent from my EVO using Tapatalk 2
ristrettodreams said:
I had a variation on this same issue. Did a TB of my user apps and system settings (not system apps) from my flex 1.75 install. Full wipe, installed the latest 8/2 CM10 from IRC, phone started fine, got one com.phone crash dialog and then everything seemed to be fine. Did the TB restore and when I rebooted I was stuck in an endless com.phone and android.process.acore crash loop. Only clue I have is that I noticed my wifi was connected when I rebooted (since my settings were restored).
Flashed to venom :-/
I'm on latest radios/firmware, s-off etc, latest TWRP, matching md5s etc
Click to expand...
Click to collapse
Pretty sure restoring system settings fro sense to aosp is a bad idea. It made it so you could not connect to data and that's why you had the error loop. just saying
sent from my LTEvo
Yep, user error
Rxpert said:
Yep, user error
Click to expand...
Click to collapse
I retried full wiping/flashing just restoring user apps, and while it didn't immediately go into the loop the same way, it still did it if my wifi was on and associated when I rebooted. It's apparently something to do with not getting data making the process go nuts.
ristrettodreams said:
I retried full wiping/flashing just restoring user apps, and while it didn't immediately go into the loop the same way, it still did it if my wifi was on and associated when I rebooted. It's apparently something to do with not getting data making the process go nuts.
Click to expand...
Click to collapse
Are you having the problem before restoring user apps? Sometimes I have found it best to re-install via market using appbak. Then once the apps are re-installed that way, just restore only the app data you need from TB, don't restore all apps/data at once.

please help!!!! random reboots with mutiple roms..

for some reason every rom I flash works great until I Install my apps. Now I use Titanium for my backup and installation of all my apps . Ive ran a scan in my app data and everything is clean. Ive even gone so far as to manually download every app I have from the market one by one . But every time I finally get everything set up and customized the way I want my phone start rebooting every 5 min.it reboots and loads everything fine and once i start using my phone my soft keys stop working but my screens touch works fine I can scroll click on things etc . thats when I know its going to reboot.then it starts every five minutes... now Ive used Cyanogen 9,Mikrom,Viper,Synergy and every one does this. Of course I do a complete wipe of all my data ,cache and partitions etc before I flash Every rom but nothing helps. Ive gone through the process of factory resets and wiping everything at least 10 times with each rom. Upon my days and hours apon hours of research the only suggestions I found was the possibility of a corrupted partition, and to re-install the ruu to completely clean all partitions and set everything back to original then try again . so I did , then I rerooted and and flashed a rom. with the same results. i know its either something Im doing or not doing thats causing this because to have his happen with every rom I flash isnt just the rom. now ..when Im on my stock rom I dont have this issue . so I know Its not a hardware issue. its just when I flash a new rom.
and another thing I noticed is after a couple random reboots it takes a while to connect to my 3g and turn my signal on. in fact sometimes it wont automatically connect until i open my connection in settings. I dont have to click on connect or anything ,all i have to do is basically open my settings or my quick toggles in my navigation bar.
and on a side note. well maybe its a side note maybe might be the actual cause of the problem haha.. when i do a factory reset through recovery everything works fine but i get an error [E: format_volume: make_extf4fs failed on /dev/block/mmcblk1p2] but everything finishes and resets fine as far as I know ... but could this be whats causing these reboots? when i look through my file explorer I find all of the mmcblk files but it seems that this file is the only one not there. can I fix this ?
Evo3d cdma rooted s-off hboot 1.4 revolutionary
Your "side note" might just be your problem. Have you tried a factory reset with another recovery, or maybe redownload and flash the same recovery.
Also, are you restoring data for system apps with titanium backup?
Are you flashing the correct hboot for the Rom you're installing?
Wikd said:
Your "side note" might just be your problem. Have you tried a factory reset with another recovery, or maybe redownload and flash the same recovery.
Also, are you restoring data for system apps with titanium backup?
Are you flashing the correct hboot for the Rom you're installing?
Click to expand...
Click to collapse
I redownloaded and installed the same recovery when I unrooted and rerooted ...is there another recovery you suggest trying ? I used the recovery that came with the revolutionary.zip
No I'm just restoring user apps from the market and 3rd party downloaders (4shared etc.)
And as far as the h.boot. when i was downgrading my h.boot to 1.4 ,after I downgraded my bootloader said 1.4 but I couldn't root through revolutionary . And I found that I needed to downgrade my software from 2.18.... In order for me to be truly at 1.4 hboot and run revolutionary. So I did and it worked perfectly . So now my software is 1.13.651.7. To be honest I wasn't sure if me upgrading to a newer software and running a newer RUU (not an ota ,just higher than 1.13...if it would cause any problems with my root as far as upgrading my h.boot to one that doesn't work with revolutionary as I had that issue with trying to root originaly.
Sent from my PG86100 using xda app-developers app
So I think its something to do with me moving my apps to sd. I only move my user apps and use titanium to do so. Now I have all my apps restored from titanium but didn't move any to sd and I havent had any reboots ...my internal memory is kind of low but its not lagging ... But I can't put any of my games on because they are big on memory . And I'm already low . Does anybody know what's causing my reboots when I move my apps to sd ? Would creating a partition on my sd card fix this ?
Oh and I used a different recovery to do my full wipe ( team wins recovery ) and it didn't give me the error I was getting before . Which is good .but I still got my random reboots .. but I noticed I only get them when I move all my user apps to sd . ( besides my lwps , widgets, system apps and things like setcpu etc.)
Sent from my PG86100 using xda app-developers app

Categories

Resources