[Q] Freeze and Reboot after flashing Virtuous Prime - Asus Eee Pad Transformer Prime

I followed all instructions in the Virtuous Prime thread in the development section, my tf201 boots up and shows the home screen but as soon as i try to open anything (app drawer, notification area etc) it locks up and reboots.
When it boots if i don't click anything it still reboots after about a minute.
I tried restoring to my nandroid backup but this also locks up if i try to open any app.
Anyone have any idea what the problem is? My Prime is effectively an expensive paper weight if i cant fix this

ApoPiso said:
I followed all instructions in the Virtuous Prime thread in the development section, my tf201 boots up and shows the home screen but as soon as i try to open anything (app drawer, notification area etc) it locks up and reboots.
When it boots if i don't click anything it still reboots after about a minute.
I tried restoring to my nandroid backup but this also locks up if i try to open any app.
Anyone have any idea what the problem is? My Prime is effectively an expensive paper weight if i cant fix this
Click to expand...
Click to collapse
I would recommend you wipe cache, wipe dalvik, wipe all user data (factory reset) and install the ROM again. I'm currently running this ROM with zero issues.
Sent from my Transformer Prime TF201 using xda premium

Yeah i cannot wait to flash this bad boy. Im nervous because I've been playing zenonia 4 and dont want to start over. I used titanium backup to back it up to transfer to my phone to play but then says save file is curupt. So im scared it may do the same thing if i backup on my prime to flash rom and restore that i may get that same curupt file thing and have to start over

cfaberlle said:
I would recommend you wipe cache, wipe dalvik, wipe all user data (factory reset) and install the ROM again. I'm currently running this ROM with zero issues.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Hi guys. I just came from stock build 14t tos custom rom. The main reason for swapping was that i had the random freeze/reboot issues after the ics upgrade that many were facing.
Any ideas how or why its happening?
To be clear.. my reboots is not like what apopiso is facing

Related

[Q] Anyone have any tips about this?

Now my head i about to explode
Anyhow, I have an annoying problem.
Before the upgrade to XXALF6 I noticed no problem other than the known drainage of the battery in idle mode.
I rooted and flashed a ROM and it was ok.
But I got sick of the ROM and I hard reset the phone.
No problems.
Then I upgraded to XXALF6 - still unrooted and all.
First thing I notice is that the phone is lagging a bit now and then. Then when I sent and recieved an SMS or two the phone hung and rebooted.
I seems that happend because when vibration was active.
Also there was a new message saying "com.google.process.gapps" stopped working. And that came up again and again.
As far as I could find online that had to do with syncing the calendar and it should help to clear calendar cache in the phone. It did not.
Then I rooted the phone, just "CF-Root-SGS3-v6.4", no other ROM.
Now the problem was even worse and also the sound stops working on and off all the time.
I tried to find the "com.google.process.gapps" with a file explorer with no luck.
I do find it in ROM Toolbox but its not possible to see the where on the phone the file is even there. Also its not possible to uninstall or even kill the process.
I did notice there seem to be doubles of some apps that I didnt notice previously to flashing CF-Root this time.
And I recall the new guide never mentions to wipe any phone data whatsoever during rooting the phone, and now I am thinking that maybe that should have been in the guide?
Anyhow.. appreciate ANY tips at all, Im so sick of this for the moment ^^
Go to cwm recovery, wipe cash, wipe dalvik cash, wipe data/factory reset, then go to mounts&storage, format system. Then put your phone into the download mode and flash ROM again with odin. This should give you a nice and clean install,without any force closes..
Sent from my GT-I9300 using xda app-developers app
pedja381 said:
Go to cwm recovery, wipe cash, wipe dalvik cash, wipe data/factory reset, then go to mounts&storage, format system. Then put your phone into the download mode and flash ROM again with odin. This should give you a nice and clean install,without any force closes..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I did wipe all things, cache, Dalvik, battery and user data with CWM.
At the moment it seems the phone is quite okay actually! The only thing left is SU.
U think I have to format system as well? What else would really be "cleaned" out that wasn't allready with the wipes?
Trust me,some of the devs insisted on formating system before flashing their custom roms,and I did have a bunch of force closes,until I decided to go their way and fully format the phone. It then installs everything from the scratch,so there's no way anything to go wrong.. give it a try,and report back... btw. make sure that you DO NOT restore any of the system data,if you use TB
Sent from my GT-I9300 using xda app-developers app
Yeah I pretty much learnt same way as predja it is always better to do full system wipe, it is not always necessary with some roms but if you do it you won't come across the problems you have as often.
sent from my SGS3 Using XDA app

MAC Address Unavailable after Flash

I am running a rooted TF201, and recently got NVFlash. I am on the latest Vicious ROM, and am a recent convert to TWRP. No matter the ROM that I flash, I get a "Turning WIFI On..." eternally, and when I go into settings the MAC Address is Unavailable. I have tried to flash CM10, EOS3, and CM9. All of them load clean, and I can tether off bluetooth, but I am unable to get a MAC Address to turn on the Wifi. I know this is not a hardware issue, as Wifi is working just fine on my Vicious nandroid. That is the only way I can use Wifi is on that specific backup. I have tried to wipe, and reload that ROM thinking my Prime just liked Vicious, but the Wifi was broken then as well. I have done a few Factory Resets, and wiped and flashed anything I can think of to try and fix it. Thank you very much in advance.
gavincm11 said:
I am running a rooted TF201, and recently got NVFlash. I am on the latest Vicious ROM, and am a recent convert to TWRP. No matter the ROM that I flash, I get a "Turning WIFI On..." eternally, and when I go into settings the MAC Address is Unavailable. I have tried to flash CM10, EOS3, and CM9. All of them load clean, and I can tether off bluetooth, but I am unable to get a MAC Address to turn on the Wifi. I know this is not a hardware issue, as Wifi is working just fine on my Vicious nandroid. That is the only way I can use Wifi is on that specific backup. I have tried to wipe, and reload that ROM thinking my Prime just liked Vicious, but the Wifi was broken then as well. I have done a few Factory Resets, and wiped and flashed anything I can think of to try and fix it. Thank you very much in advance.
Click to expand...
Click to collapse
When you installed these roms, did you wipe cache, dalvik and factory reset? Most devs say to wipe all 3, if you did try androwook rom though its discontinued I have never had a wifi issue. Actually I am running eos 3 build 37 now and it works also. You didn't do any kernel switching did you?
Sorry, should have included that. I did wipe everything every time, and I haven't touched a kernel. I am lost as to what is happening. I am using TWRP 2.2.1.4
Sent from my Galaxy Nexus using xda premium
Did you run a checksum on your downloads to make sure they are complete? I don't think I have seen this issue in the forum other then the kernel being not quite right...
I think there is something (i did) wrong with nvflash.... i'm stuck with another mac-address http://forum.xda-developers.com/showthread.php?t=1812773
I hope some nvflash devs can look @ those wifi problems. I also saw warnings on xda forums using nvflash, because it can change mac, imei & serial.
Yes, i made sure the downloads were good. I made some backups, then I used this file
http://forum.xda-developers.com/showthread.php?t=1670824
Placed a good fresh EOS3 ROM and GApps on my microSD, ran the wipe and Still didn't get a working Wifi. I am welcome to try any kernel option, see if it works.
Sent from my Galaxy Nexus using xda premium
I was able to get a clean fresh ROM to open and make a WIFI connection. After a full wipe, Virtuous Prime 9.4.2.28 v1 to load and work with no issues. I have a C2OK serial number, think that may be a reason I am having issues with other ROMs? Is it a way this particular ROM loads? I had tried other ICS ROMs, and I would have the same issue as JB ROMs, so I don't think it has anything to do with it. I got full function back, but am wondering why I can't load other ROMs.
Sent from my Transformer Prime TF201 using xda premium.
gavincm11 said:
I was able to get a clean fresh ROM to open and make a WIFI connection. After a full wipe, Virtuous Prime 9.4.2.28 v1 to load and work with no issues. I have a C2OK serial number, think that may be a reason I am having issues with other ROMs? Is it a way this particular ROM loads? I had tried other ICS ROMs, and I would have the same issue as JB ROMs, so I don't think it has anything to do with it. I got full function back, but am wondering why I can't load other ROMs.
Sent from my Transformer Prime TF201 using xda premium.
Click to expand...
Click to collapse
Mine is a c1ok but i haven't seen anyone with a particular serial number have issues and I do read a lot of posts... full wipe should in theory get you where you want to go but you may have something else going on.. bad download, bad cable (this I have seen) the bad download sometimes ends in failure to flash at all.. had that tonight actually lol... re downloaded checksum.. all good now... I have had a few oddities going from one rom to another but a second flash sometimes clears it up.. never had issues with wifi unless there is something up with the kernel...
Come to think of it.... there were a few posts that said they required a double full wipe... it's an option if your willing to put in the time.. full wipe, adb push wipe file again... wipe then push rom.... if i was going to take that route, i'd push androwook rom I went from that to jb EOS and haven't had any issues....of course that means cache wipe, dalvik wipe and factory reset in between....
I tried what you said, I'm and using the wipe zip, I triple wiped, and then loaded Baked ROM 4.1 to see. Md5 check was done of course. I got wifi to turn on, but it will not find any networks. I have reset my modem/router, and restoring my old ROM wifi works and connects just fine. I am going to repeat the process with a different ROM to see if it may be that specific ROM.
Sent from my Galaxy Nexus using xda premium
gavincm11 said:
I tried what you said, I'm and using the wipe zip, I triple wiped, and then loaded Baked ROM 4.1 to see. Md5 check was done of course. I got wifi to turn on, but it will not find any networks. I have reset my modem/router, and restoring my old ROM wifi works and connects just fine. I am going to repeat the process with a different ROM to see if it may be that specific ROM.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I am confused too. I did the same, using the wipe zip, and between wipes I wiped dalvik. I wiped three times, just for good measure. I then flashed AndroWook Hairy Bean v1 and AndroWook Prime v2.6, not at the same time obviously. With each ROM, I was unable to see any wifi network on my TF. The wifi may turn on, may not, but it will not even show any network. I am at a complete loss. I am able to connect via a blue tooth connection to get Internet with both ROMs.
Sent from my Galaxy Nexus using xda premium

[Q] "Process System Isn't responding" message on all jb roms

"Process system isnt responding. Do you want to close it?
wait report ok
I get this message ALOT on all the JB roms out there now; it happens after a reboot/restart, and if I click ok, things seem to work normally after a few seconds...
Anyone else seeing this alot? Anyone figure out a way to stop it?
thanks!
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnrippa said:
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
ZPaul2Fresh8 said:
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
Click to expand...
Click to collapse
did that many many times, and it doesnt help
wase4711 said:
did that many many times, and it doesnt help
Click to expand...
Click to collapse
Did you restore apps from titanium backup? If so that may be it.
_____________________
Black Star VIII
Me too
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11​.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Problem gone (i hope)
strainhunter said:
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11​.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Click to expand...
Click to collapse
Hello Again,
The problem is gone for me i found out that it has something to do either with the Theme i was using, or/and the Launcher. Because i first switched my Launcher (Nova Launcher) to the Stock one (Trebuchet) (merely just because i did not know how i should fix that problem) then at the after the first reboot with stock launcher the problem was gone, but came back after i rebooted again. So i changed my Theme (JellyBeanExtreme) and the problem did not appear again "knockin´3x on wood^^"
Maybe this can help someone who had or will have this problem.
Greetings,
Strainhunter
wase4711 said:
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
Click to expand...
Click to collapse
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
CPA Poke said:
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
Click to expand...
Click to collapse
Does that leave your apps and data in place? Never thought of that
Sent from my SGH-I717 using XDA Premium HD app
did u install the walkman app for the note?
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
jrea77 said:
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
Click to expand...
Click to collapse
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
CPA Poke said:
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
Click to expand...
Click to collapse
ya...i noticed nothing was really wrong while getting the error, it just bug me that i was getting that little pop up window. i would hit "wait" or "cancel" and it didnt seem to make a difference, it would go away and that was it. once in a while it would pop back up when getting a text or call, before i could answer the call i had to click it to make it go away to be able to answer. so i decided not to use the theme and not worry about that error.....so would it be any theme or just some themes? maybe ill try other themes and see what happens.....

[Q] Freezeing with Siyah 4.1.5 and stock 4.0.4 help Plz

Since i have rooted and installed the Siyah Kernal, i am experiencing random crashes where apps stop working and the screen goes black for a minute and everything reloads again like as the phone has been restarted. i used a fresh made recovery and everything was ok but i had to reload everything from scratch. it has happened again but this time i can not even get past my pattern lock screen before it crashes and freezes. therefore i cant titanium backup my apps.
i have tried
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- reboot phone
I was wondering if anyone else was having this problem.
just in case it matters am using go launcher and just before the phone went funny i was browsing and using apps fine. however today i did use extweaker app and ticked the option to force usb storage, if this makes any difference
thanks.
i was wondering has anyone else had this problem and is there any ideas on why this may be happening.
it may because the phone is trying to do something that is causing a conflict. I believe the only way you are going to resolve the issue is to do a factory reset, to unfo the issue with the force usb storage.
Cosmic Blue said:
it may because the phone is trying to do something that is causing a conflict. I believe the only way you are going to resolve the issue is to do a factory reset, to unfo the issue with the force usb storage.
Click to expand...
Click to collapse
Thanks. For the reply. I was wondering what would be the best way to factory reset with out loosing root but giving me a fresh 4.0.4 with root also should i flash the latest siyeh kernel or stick with what i have. i am running ok at the moment after flashing a recover. but am paranoid it just going to get stuck and freeze on the lockscreen again. this could be a big problem if i need to make a important call or somthing. sorry for spelling mistakes written on my phone
editm i used galaxy s unlock from market. i dont want to loose this either
also most times i install a new app the whole screen just sticks and i have to reboot then it becomes fine again. any help would be appreciated.
Sent from my GT-I9100 using xda premium
Might be worth deleting the .siyah folder and then booting into recovery, flash a kernel cleaning script then siyah or whichever kernel again.
Sent from my GT-I9100 using Tapatalk 2

[Q] Unable to install ROM past EL01...CM10.1, CM10, AOKP all bypass setup...

And the all have the same green leaf for a home screen, so are my ROMS not being written to the right place or what. this is getting confusing. the ROM form about shows the different versions but all are skipping the setup and I have no 3G/LTE connection, only wifi.
Whatever I am doing I seem to be consistent about it
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
the AOPK had gapps folded in. what is odd is I have now tried AOPK and a CM10 and CM10.1 and they all seem to have the same start screen, come up after the boot like it is already installed, missing any 3G/4G connection. Now I have flashed back to EG01 and run up though iCS several times and it isn't taking the CWM now, says it installs ok but boots into stock recovery. Now I using the older CWM 5504 for the i-905 and it writes somewhere, but apparently not where it should be. I was going to try TWRP but that doens't appear to run on HC/ICS - is it JB only? I have shied away from the newer CWM for a long time because for a while they just seemed to boot-loop the tablet.
Any one have a suggested working version of CWM? This starting from scratch and rolling in all the updates is getting old - which is why I was wondering if there is a way to build my own ODIN set to just flash back to this point without having to go though reroot and install of the recovery (which apparently now I am not able to do - wts! )
Thanks!
Rob (lost) in Katy.
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
rgranger said:
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
Click to expand...
Click to collapse
Ok, i found another recovery laying around that seems to be working. I also found that the bug where you need to delete the script that deletes the new recovery. Once I got that far things started making sense. I guess whatever mod I was on before didn't need it. The next trick will be trynig to decifer how to do an odin backup so that I don't haver to roll though 4/5 upgrades to get here. I know someone is doing it. thanks for the help and a place to bounce ideas. will update if i come up with anything.
Rob

Categories

Resources