I'm on the newest CM9 release, so my phone is pretty unstable right now. Right when it got to the point where it asked for my input on scrolling speed, my phone crashed. I'm new to this stuff, so I'm not too sure how bad that is, I just tried rerunning the script though, and it doesn't start.
I'm just wondering, did I screw anything up? If the script didn't finish, how can I get it to run again and complete? The phone seems to be running fine, I just want to know if V6 finished doing its job, and if not, how I can get it to do so. Thanks for the help guys.
BrahManty said:
I'm on the newest CM9 release, so my phone is pretty unstable right now. Right when it got to the point where it asked for my input on scrolling speed, my phone crashed. I'm new to this stuff, so I'm not too sure how bad that is, I just tried rerunning the script though, and it doesn't start.
I'm just wondering, did I screw anything up? If the script didn't finish, how can I get it to run again and complete? The phone seems to be running fine, I just want to know if V6 finished doing its job, and if not, how I can get it to do so. Thanks for the help guys.
Click to expand...
Click to collapse
Download Smanager from the market and see if you can run the script. But have you tried CM9 mashed up?? It makes a world of difference alone.
tallyforeman said:
Download Smanager from the market and see if you can run the script. But have you tried CM9 mashed up?? It makes a world of difference alone.
Click to expand...
Click to collapse
Thanks! I was trying to run it with terminal emulator and I can see now why they said to use Script Manager. Much easier! Just finished the script and am now rebooting...
And yeah, I was previously running CM9 Alpha 3 with the Mashup, and it didn't seem to make any difference to me. I'm now trying Alpha 4 with both the Mashup and supercharger, and I'm hoping ICS will be somewhat stable!
BrahManty said:
Thanks! I was trying to run it with terminal emulator and I can see now why they said to use Script Manager. Much easier! Just finished the script and am now rebooting...
And yeah, I was previously running CM9 Alpha 3 with the Mashup, and it didn't seem to make any difference to me. I'm now trying Alpha 4 with both the Mashup and supercharger, and I'm hoping ICS will be somewhat stable!
Click to expand...
Click to collapse
I seemed to have the best luck Alpha 4 only mashed up. Try it both ways and see what works best!
If I were you I'd attempt to remove the script entirely. I ran it on cm9 and mine died mid run. Rebooted and everything looked peachy then my phone started opening and closing apps on its own. When I would open the keyboard everything would spazz out. Wipe Cache and Dalvik and if the option to un-supercharge in the V6 menu is still there, do that before wiping.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Forgive me if missed this, but I'm finally getting mine from HP tomorrow, and I think I'll hold off on CM until some of the major bugs are worked out, but I still want to play with WebOS.
--
Sent from my Droid Bionic.
You can still install the cyanogen mod alpha with the update, it doesn't change anything as far as that goes. If you have the alpha installed already, you'll have to rerun the command to install it again, but it still works with the update.
You will have to install only moboot not everything.
Update first and then install CM7. I did this and can confirm that it works.
rootnik said:
Update first and then install CM7. I did this and can confirm that it works.
Click to expand...
Click to collapse
+1 ... Just did a co-workers TouchPad today and CM7 installed smoothly.
Side note: 3.0.4 is in fact really "snappy", I like the updated camera app and no lag on the stock kernal.
So my touchscreen didnt want to work anymore yesterday.
I restarted my phone several times and it didnt work.
I then went into xrecovery and clicked 'fix permissions'
Then more stuff didnt want to work anymore
I reinstalled the update.zip file, did a factory reset etc
And now my phone is stuck at the boot with 'Sony Ericsson'
I had minicm6 v6 on my phone (u20i)
I tried reinstalling a backed up zip, but still nothing.
What now?
If you made a backup you should try to restore that.
Sent from my Xploded Dinc2
Edit: Got my phone working, but now when I download something from the market, the phone restarts when it installs ?
Have you figured out the reason why it keeps restarting? If not I would try to reflash the rom.
Keep us updated.
Sent from my Xploded Dinc2
Ok I did another factory reset and cleared dalvik cache.
Everything is working good now
Thanks
No problem that's is what this community is here for
Sent from my Xploded Dinc2
Sweet
Soooo now that everything is working fine again, would anyone like to recommend me a new ROM to install? Some CM7 mod/rom maybe?
Which ones are the best?
(I know there is a list with all of the roms available for my phone, just thought I'd ask)
Im not sure which roms are available for your phone but cm7 is always a good choice.
Sent from my Xploded Dinc2 using xda premium
I ended up in installing CyanoCream Sandwich v2.0
Looking good so far
demozzracy said:
Sweet
Soooo now that everything is working fine again, would anyone like to recommend me a new ROM to install? Some CM7 mod/rom maybe?
Which ones are the best?
(I know there is a list with all of the roms available for my phone, just thought I'd ask)
Click to expand...
Click to collapse
Check this one Its the best one and quite fast then other ROMS
http://forum.xda-developers.com/showthread.php?t=1415026
I had Stornmix V2 installed for a couple of weeks and it's fast and stable...I really like it.
The only problem I noticed is that when I'm using the video camera, the phone just freezes and I need to remove the battery to make it work again.
The problem with that one is the requirements:
Unlocked bootloader
Latest version of the nAa kernel
I dont know if I have those things on my phone.
And Im not too sure on how to put it on, if i have too
Update:
CyanoCream Sandwich is a bit slow to be honest. I think I will be looking for a new one to install
You will learn little by little by searching through the forums. Unlocking takes some time and some patience.
If you only follow the instructions step by step then you will get an unlocked bootloader and you can install any kernel. dont worry, you will get it soon.
my regards and good luck for that.
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
mooter said:
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
Click to expand...
Click to collapse
logcat or it didnt happen.
task650 said:
logcat or it didnt happen.
Click to expand...
Click to collapse
I see some logs in the root folder, is that what you're referring to? I'll happily help you investigate if I can but it'll help if you point me in the right direction. Actually, maybe I'll try again and see how I get on? Restoring from backup was pain-free so not much to lose but 20 mins
Regardless, I very much look forward to seeing your work progress on this one over time! I know you're busy but superstars have obligations dude haha ;D
edit - trying again now with logcat reader installed - I'll report back!
do you have Ti backup installed? I would first try to see if there is some kind of phone apk in there. If there is try to clear the phone apk data and cache. If that doesnt work maybe try freezing it. Its strange that you have this error since tasks rom is a stock galaxy tab 10.1 ics build. Maybe try to wipe everything again and follow tasks instructions one more time step by step. sometimes weird things happen and a reflash might fix that. And just a stupid question but you have the wifi p7510 tab right
Folks
I've unlocked the bootloader, rooted phone, installed all different ROMs possible - and also ran the overheating fix as is prescribed.
Which is, running the touchpanel.sh through script me or Gscript lite tools from play store.
The script works (I am assuming it does because my phone shut down when I ran it under root) - but the phone overheat problem does not go away
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
I run the same touchpanel script with all possible ROMS and it just wouldnt work - what is it that can be done if anyone knows please?
thanks
Dhruv
dhruvraj said:
Folks
I've unlocked the bootloader, rooted phone, installed all different ROMs possible - and also ran the overheating fix as is prescribed.
Which is, running the touchpanel.sh through script me or Gscript lite tools from play store.
The script works (I am assuming it does because my phone shut down when I ran it under root) - but the phone overheat problem does not go away
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
I run the same touchpanel script with all possible ROMS and it just wouldnt work - what is it that can be done if anyone knows please?
thanks
Dhruv
Click to expand...
Click to collapse
Flash stock firmware, i seriusly doubt that it can solve your problem, but give it a try..
dhruvraj said:
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
Click to expand...
Click to collapse
You'll need an older stock GB rom that has a utility called "cyttsp_fwloader" included for touchpanel.sh script to work; CM9 or 10 dont include it.
ideopath said:
You'll need an older stock GB rom that has a utility called "cyttsp_fwloader" included for touchpanel.sh script to work; CM9 or 10 dont include it.
Click to expand...
Click to collapse
Thanks a lotttttt man. You've just made my phone usable again. Owe you half a dozen beers at least
dhruvraj said:
Thanks a lotttttt man. You've just made my phone usable again. Owe you half a dozen beers at least
Click to expand...
Click to collapse
Its a pleasure @dhruvraj, i remember how good it felt when i fixed it, so HTH.
I run that script so many times when I was on stock (rooted) rom, before switching to FXP.. sadly never solved my problem (its still here).
BTW, don't try to move the cyttsp_fwloader in CM10/FXP and run it there... it broke my touchscreen instantly, I had to flash the stock rom back again to repair it.
cosmacol said:
I run that script so many times when I was on stock (rooted) rom, before switching to FXP.. sadly never solved my problem (its still here).
Click to expand...
Click to collapse
Actually the script didnt work for me either - i opened an adb shell, su'd to root and did this as a one-liner
Code:
cyttsp_fwloader -dev /sys/devices/platform/spi_qsd.0/spi0.0 -fw /system/etc/firmware/touch_smultron_sony.hex -verify_only
BTW, don't try to move the cyttsp_fwloader in CM10/FXP and run it there... it broke my touchscreen instantly, I had to flash the stock rom back again to repair it.
Click to expand...
Click to collapse
Thanks for the headsup, i was thinking this was a possibility if the problem comes back on a future rom!
how do u think about this?
my touch didnt work on bottom screen area (see attchment).
it happen when ive use phone for long time or when my phone become warmed.
yes, i sent from my phone using Xda Premium, so what?
phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues