I'm trying to reinstall my old phone to give to a friend.
I do a complete reset, and install a fresh ROM. The phone starts, sometimes even gets to full functionality, then restarts and is mostly stuck on bootloop. Other times it restarts during the initial set-up process.
I've tried different ROMs.
Does that mean it's a hardware issue, or can reinstalling custom recovery or even re-rooting help?
Have you tried stock roms like RedRom?
If it still bootloops, it's a battery issue.
Johnny TDN said:
Have you tried stock roms like RedRom?
If it still bootloops, it's a battery issue.
Click to expand...
Click to collapse
Well, I'll be dammed, RedRom seems to have no reboot issues! Why is that?
Lauriso said:
Well, I'll be dammed, RedRom seems to have no reboot issues! Why is that?
Click to expand...
Click to collapse
I don't know.
Have you tried when you used those different roms, a clean flash? Sometimes problems occur when you "dirty" flash (aka flash roms without factory reset).
Johnny TDN said:
I don't know.
Have you tried when you used those different roms, a clean flash? Sometimes problems occur when you "dirty" flash (aka flash roms without factory reset).
Click to expand...
Click to collapse
Hmm, I was doing factory resets always, but this time I manually selected to wipe EVERYTHING apart from external sd, as well as cache/dalvik AFTER installation, and the problem seems to be fixed! Thanks for pointing me in the right direction!
Related
i tried multiple roms and every time my phone freeze to a point that i have to take the battery out. any idea what could be the problem?
When is it freezing?
Did you wipe your data, cache, and dalvik-cache before flashing?
...
tuamazing said:
i tried multiple roms and every time my phone freeze to a point that i have to take the battery out. any idea what could be the problem?
Click to expand...
Click to collapse
Are you full wiping between flashes? If so and you're still getting problems you can try to flash a stock image via Odin and if the problem persists it may be a hardware problem.
I'm at wit's end here. My TF101 will not stop rebooting. it doesn't matter what firmware I have on it (stock rooted, stock UNrooted, CM9, Frozn). it just reboots. the majority of the time it goes into a boot loop, or, if I'm lucky, I'll actually get to the homescreen for about five seconds, then it reboots. I just tried flashing the stock rom again. can't even get to the welcome screen now. I Never had this problem until I downloaded a firmware update (for stock ROM)
Using Rogue XM Recovery 1.5.0 (cwm doesn't want to work, for some reason)
S/n: C10KAS158799
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Go back to stock using easyflasher. It'll wipe your device clean, so make sure to back up important data. Then start over. I suggest Fred's guide over at transformeforums, it's the most complete one out there.
frederuco said:
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Click to expand...
Click to collapse
Tried that. Still boot-looping. nothing I do seems to help. so far, I've had the most luck with Frozn. CM9 nor the Stock asus firmware seem to work at all anymore. apparently the recovery is borked too. anytime i try to wipe something, It freezes.
am I just SOL?
(edit) alright, so I tried it again. instead of boot-looping, now it just sits at the Eee pad screen forever
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command (see the terminal method here: http://www.teamw.in/project/twrp2/109)
frederuco said:
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command)
Click to expand...
Click to collapse
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Des0late Law said:
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Click to expand...
Click to collapse
Did flashing the stock ROM replace TWRP? It should have...
frederuco said:
Did flashing the stock ROM replace TWRP? It should have...
Click to expand...
Click to collapse
It did. Now I can actually get into the OS for awhile, but it still reboots randomly (and bootloops, although not as often). I've been doing some googling. apparently the reboot/bootloop problem Is ICS based (or so some think) and, to be honest, I didn't have any problems with it before I updated from Honeycomb. that being said, someone wouldn't happen to have a spare honeycomb ROM lying around, would they? google (oddly enough) turned up nothing, and Android Revolution just leads to dead links...
Edit: never mind, someone fixed the links. will try 3.2 after I get home from work.
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Well, I haven't had the SoD issue, just reboots. I was able to use it most of the day yesterday, before I shut it off myself. It turned on fine this morning, too (rebooted once).
Sent from my LGL75C using xda app-developers app
frederuco said:
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Click to expand...
Click to collapse
Alright. So, I flashed it back to Honeycomb. Haven't had a reset or reboot all weekend. I guess the problem WAS ICS-based. Can't figure why, though.
only downside to that is, can't use some apps on the market. oh well, I'll live!
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
I had this problem for months. I did a clean install and it fix the problem. Try doing that and it might work for you too.
What do you mean by clean install?
Gigatrig said:
What do you mean by clean install?
Click to expand...
Click to collapse
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt.
Sent from my SCH-I535 using xda app-developers app
kude87 said:
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt
Click to expand...
Click to collapse
Do you mean in the "mounts and storage" menu? Use format /system... /data... /sdcard? I think that's what you mean, but I've not had to use those before, so I wanna make sure.
Thanks
:laugh:
Gigatrig said:
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
Click to expand...
Click to collapse
I had the same problem with my phone, I made a thread a little while ago with what I did. http://forum.xda-developers.com/showthread.php?t=2492304 ask any questions you have on there I want to improve it as this was a very frustrating and time consuming fix for me.
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.
You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!
Good day all,
I've run into a bit of a problem and I'm starting to pull out my hair.
I have a A32 5G with stock OS thats rooted with TWRP.
And after fiddling a bit to much I now have problems with a few things including GPS etc and I want to factory reset so I can start fresh, But everytime when I wipe with TWRP and boot up again the stock camera app has a wierd issue, it crashes as soon as it goes into the video or any other mode although it does take photes. I've tried clearing the cache and data from the app as well as in TWRP. Also opencam works fine but I would much prefer the stock app to work.
Also when I restore my old backup with TWRP it works again but ofcourse the other bugs also come back too.
Any suggestions would be welcome. Thanks!
That's weird. my suggestion would be to clean flash via Odin whatever version your at.
then flash twrp and run multidisabler twice and format data...
financeledger said:
That's weird. my suggestion would be to clean flash via Odin whatever version your at.
then flash twrp and run multidisabler twice and format data...
Click to expand...
Click to collapse
You are the definition of awesome!! It worked! Many Many Thanks!
a_private_identity said:
You are the definition of awesome!! It worked! Many Many Thanks!
Click to expand...
Click to collapse
Im glad it worked !!
It was a software issue then probably some app broke the camera functionality.