Hey guys, I've had my transformer for just under a year and love it to death, but for the last couple of days it has been giving me hell! I was running ARHD 3.4.1 with Guevor's ICS kernel (can't remember version, either 19.4, 20 or 21). Anyway, all was well until I changed to ARHD 3.5.1 and switched to raymanfx's harmony kernel to try it out. I couldn't get my videos to play on mxplayer, FC's on apps, random freezes and tablet kept randomly rebooting. So I reflashed ARHD 3.5.1 again, same, reflashed guevor kernel, same, updated CWM to Rogue XM Touch Recovery v1.5.0-R1, same. Finally used this method: http://www.theandroidsoul.com/update-and-restore-eee-pad-transformer-to-stock-ice-cream-sandwich/ to flash back to stock, no root, no nothing annnnnd... same! Same issues no matter what I try. So my question is, with a few weeks of ASUS global warranty left (bought it in HK so I can't take it back to 'shop') can/should I send it back now that it's flashed back to stock without them finding out I rooted it? Or is there something I'm missing that you guys can think of. Please let me know asap in case I do need to send it back. Thanks in advance. Oh and let me know if you need more info
Maybe a stupid question...
Did you do a factory reset in between flashing the different roms and kernels? Full factory reset, wipe cache and dalvik?
Not a stupid question at all, but yes, I tried all three
Sent from my R800i using Tapatalk 2
I can't think of anything else causing that behaviour. Restoring apps, data and system data with Titanium has been a source of trouble for me in he past. Restoring setCPU with profiles that don't work well with the new kernel for example. But I guess that's not the case here. At least stock ROM should be working.
Sorry, maybe someone else has another idea.
Related
Hi there, i got a problem...
i flashed kingxklick's aosp release, but then i wanted to revert to SuperD, so i did a nandroid restore...
but after that, every rom is getting that "process.android.acore stopped working", even on that roms that worked before...i also did a full wipe and taking out the battery for 5min, but nothing of that worked, it keeps crashing...
logcat is in the making...i'll upload in a couple minutes
arthofer said:
Hi there, i got a problem...
i flashed kingxklick's aosp release, but then i wanted to revert to SuperD, so i did a nandroid restore...
but after that, every rom is getting that "process.android.acore stopped working", even on that roms that worked before...i also did a full wipe and taking out the battery for 5min, but nothing of that worked, it keeps crashing...
logcat is in the making...i'll upload in a couple minutes
Click to expand...
Click to collapse
it is a known problem with 1.10.3 superd, either go do a .2 or wait for .4 to be released (which should be soon). Also if u still wanna stick with .3, change your launcher to home.
I recommend going to another version, coz .3 is also known to have battery drain issues.
Hello together,
after ive updated yesterday to the nightly 204 ive got a serious problem.
Every time i use the mobile data connection....the phone is rebooting.
The really wired thing is that after ive restored my backup which was totally stable, the problem is still there. Even when i try my really old recovery of the stock sense...the phone is rebooting something like 20 seconds after using
a mobile data connection (which is working in that amount of time)
I have really no idead what to do now.....any help is welcome.
Thx in advance!
Try reflashing the radio. (All 3 versions, if one of them doesn't solve the issue) I believe pyroblazer was having a similar issue on the RemPuzzleROM and a radio reflash fixed it.
at first i want to thank 3xeno for his quick help (as he always does). Really thanks..the community lives because people like you.
Ive solvend the problem....after 2 times wiping all... the only backup which is working flawless is my old stock sense, all other cm7 backups reboot after using mobile data connection. When i wipe all and install a clean cm7 nightly 204 ...its working too, but at moment ive no time to install everything, so i will keep the stock sense for some days.
The wired thing is...that this bug appears after i updated from the 202nightly to 204 and especially wired is that all my cm7 backups are now affected by this problem that never happend in the past.
hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
romitkin said:
hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
Click to expand...
Click to collapse
Try flashing a official image via any Nexus toolkits and then install the rom you want.. bakcup your data and also make a nandroid backup..:good:
Hi
I did that, flashed stock ROM and did a full wipe including the user storage.
Then I flashed Purity ROM and Semaphore kernel.
I still experience the reboots, a few times a day usually...
Should I try a different ROM or kernel?
Sent from my Nexus 4 using xda premium
I'm using Purity ROM for some time now and it's just awesome.
Kernel is purified kernel and as i read many people writing about semaphore having better battery live with purity, i tried it.
just for half a day, because it randomly rebooted twice in this time.
first time while talking with someone, second one while browsing the internet.
any idea why? for now i'm back to purified, but i just get normal battery life. maybe 2hrs screen on.
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
foxguard said:
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
Click to expand...
Click to collapse
Sounds like a radio issue. If you are running 3.99, you need the radio for 4.3 which I do believe 3.99 is based on. You need the radio for KitKat when running the new betas.
Sent with my Nexus® 10 minus 3
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
I think I basically said that. Sometimes I believe in not holding hands and let the guy/gal do some of the, legwork.
Sent with my Nexus® 10 minus 3
Thank you every one. I have reverted back to my recovery and all is well but I don't understand why when I flash the ROM ad gapps it happens. My recovery is the same ROM and gapps. No idea.
Oh well stuck with the screen delay for now!
Sent from my Nexus 4 using Tapatalk
mrhiab said:
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
Click to expand...
Click to collapse
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
foxguard said:
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
Click to expand...
Click to collapse
Ohh you are having issues with ur network !! Seen people completely losing their Imei during flashing !! Not to scare you but its better to get the imei files backed up !!
Check my post on the below mentioned link
http://forum.xda-developers.com/showpost.php?p=49753344&postcount=11
Hit the thanks button if you find my post useful
Before some weeks ive been asking here what ROM I should use. Ive done this cause my power drains to fast.
So I switched back to OxygenOS3.0 and everything worked fine until today.
Today my phone got always authentification problems with my WiFi at Home.
So ive thought to fully unroot my device and go back on the first stock ROM.
But it fixed nothing and I also restart my router so thats not the fault.
Also the Fingerprint Sensor including the Touch Function doesnt work anymore ive also got this problem before a half year but fixed it very fast after installing CM13.
Now ive wanted to know if someone got the same problems or one of them and could help or give some advices the phone is only 1 year old and I didnt want to swap to another one until a year.
What I would do is flash some other roms and make sure that you're using the hybrid twrp
Or probably start over again after flashing stock ROM.
Before that try clearing cache and Dalvik which solves issues on most deodexed ROMs.