Please HELP! Reboot Problem! TRIED A LOT Different Things! :( - TouchPad Q&A, Help & Troubleshooting

Okay I have tried EVERYTHING! I tried uninstalling my CM9 Alpha 2 completely with Acme Uninstaller and then doing a fresh install. I tried wiping data, cache, davlik, and still nothing! I don't know what to do. I tried so many things and have been working on this for the past 5 or 6 hours today! Please SOMEONE ANYONE have any ideas? My Touchpad is fine for about 2 minutes and no matter what I am doing it freezes for a second or two, screen goes black for a second, and then it reboots. Please SOMEONE HELP! I am about to give up on Android and I didn't love ICS so much I would! Thanks for all the help!

Have you changed any of the DPI settings? in the build file?

Have you tried booting into recovery and performing a full wipe? Wipe data, cache, dalvik cache.
Sent from my Rocket in the Sky (SGH-i727) using XDA Premium.

I haven't tried changing the DPI Settings. As for wiping data, cache, and davlik cache I tried all that. When I wipe the davlik cache though in recovery I get this error:
E:unknown volume for path [/sd-ext]
Would that have anything to do with the rebooting? I don't ever recall having this error before. If so, how do I fix it???
Thanks for both suggestions!

Shound I uninstall everything and just start from scratch and put CM7 Alpha 3.5 and then update it the CM9 Alpha 2 or do you all think that would work???

I suppose the quickest answer would be to just to start again reload back to webos, then do the process again. I've never had any issues like your having and maybe instead of installing cm7 them cm9 just install straight to cm9. May of been a buggy install. Also maybe before that try redownloading another rom. May of just been a slightly messed up rom you installed.

alias4ever said:
I haven't tried changing the DPI Settings. As for wiping data, cache, and davlik cache I tried all that. When I wipe the davlik cache though in recovery I get this error:
E:unknown volume for path [/sd-ext]
Would that have anything to do with the rebooting? I don't ever recall having this error before. If so, how do I fix it???
Thanks for both suggestions!
Click to expand...
Click to collapse
The error is troubling. If it were me, I'd completely redo the CM7 to CM9 install process starting with the uninstall. And get a fresh download of the rom and gapps and every file that you have not used successfully once in an install.

Related

[Q] how do i wipe cache via adb?

I'm trying to load different Tom's and nothing has worked. Running darchdroid 2.8 now and whei think nothing is installing cus I can't wipe cache via recovery. It tells me to wipe via advanced and I don't know how or the commands. Is this probably the reason I can't get any other Roms to load?? Please help!!
coreymartin85 said:
I'm trying to load different Tom's and nothing has worked. Running darchdroid 2.8 now and whei think nothing is installing cus I can't wipe cache via recovery. It tells me to wipe via advanced and I don't know how or the commands. Is this probably the reason I can't get any other Roms to load?? Please help!!
Click to expand...
Click to collapse
Dalvik Cache?
Just do a system wipe. Most ROMs wipe cache when they are flashed (causing a long boot time, which makes most ppl think it isnt working )
If you're using recovery Amon_RA v. 1.5.2, it still does wipe dalvik cache through the recovery console even though it tells you "run dalvik wipe via adb!". That is merely an output error from the recovery console, it still actually does wipe your dalvik cache like it's supposed to, it just outputs the wrong text string when it's finished. So that is not your problem installing ROMs, it must be something else. What steps are you using when trying to do this?
I tried installing a couple froyo roms.did system wipe then tried cache and when I tried the Rome I got status 7 and some unsigned error
coreymartin85 said:
I tried installing a couple froyo roms.did system wipe then tried cache and when I tried the Rome I got status 7 and some unsigned error
Click to expand...
Click to collapse
Please tell us exactly what steps you did, in order, so that we know if you are trying to flash a ROM correctly. Also tell us which recovery version you're using (should say at the bottom of the recovery screen).
Anytime I go from sense to any aosp Rom then back to sense, I have to reformat and reparation SD card. Then just drag items back into SD, wipe, and reflash. All will be right and make SENSE.
Sent from my fresh hero.
coreymartin85 said:
I tried installing a couple froyo roms.did system wipe then tried cache and when I tried the Rome I got status 7 and some unsigned error
Click to expand...
Click to collapse
Check to make sure the ROM is from a good source... if it's not signed then it won't be recognized as valid.
-mb

[Q] SpeedMod update issue

Dear all,
I start using SpeedMod since version K12K.
There is no problem when I update the kernel from K12K to K12L, K12M, K12P, until from K12P to K12Q and so on.
After flashing with Odin and reboot, the phone becomes very slow, both in operation and the touch screen response.
I have tried updating from K12P to K12Q, K12R and K12S, they have the same symptom and slow. When I flash back to K12L or K12P, it becomes normal.
Any advises please?
Thanks in advance.
My phone info:
ROM: Stock 2.2 FROYO.ZSJPE
Maybe you should wipe the dalvik cache and cache. Go to recovery mode - clockworkmod options - wipe dalvik cache. do the same with cache partition.
Then reboot. That first reboot will take longer than usual because the dalvik cache has to be rebuild again. After that everything should be fine.
Thanks for your reply.
I have tried wiping the cache, then the dalvik cache, but it seems remain the same --- slow and lag. I would like to know if there is any sequence, let's say wipe the cache first, then wipe the dalvik cache, then flash the phone? or something else?
After wiping the cache, in general speaking, how long do I have to wait after the reboot?
Thanks in advance.
Sent from my GT-I9000 using XDA App
What i mean is that the first reboot after wiping the dalvik cache takes longer than usual because the dalvik cache has to be rebuild again.
You might check in the task manager if there's any running process cunsuming cpu time, which could lead to laginess. There are many things that could produce lags (widgets,apps etc.) I dont know what's installed on your phone.
Sent from my hand
I see. However, I am thinking if the lag is because of the apps. Since I am using the same apps before and after the kernel update. I did wipe the dalvik cache after flash, but after reboot, the phone response very slow, and whenever I click the home button, it just did not show up.
Any more ideas? Thanks a lot.
Sent from my GT-I9000 using XDA App
What i would do in your case would be:
Backup all important data/apps etc.
Then do a complete wipe and reset to factory defaults.
Then flash the latest firmware: froyo 2.2.1
Then flash speedmod kernel and apply all recommended tweaks.
After that restore app by app and rethink the real use of each app (do you really need/use it?).
Might sound complicated but it might be even easier than loosing more time on hopeless attempts to solve the problem...
Sent from my hand
Cheers man, this will be my last step. Thank you for your help.
Sent from my GT-I9000 using XDA App
NP Tell us if you succeeded. You might want to try wiping thumbnail database before (forgot to mention that beforehands).
Sent from my hand
Just done a factory reset (erase data + data cache + dalvik cache)
and flash the new version of kernel. The phone is back to normal now.
Sent from my GT-I9000 using XDA App

[Q] CM7 bootloop initial boot

Well, i am stuck at bootlooping after flashing CM7.1 onto my friend's device, we've tried many times flashing it with different ways, but it seems to get stuck everytime at the bootscreen, i know the initial boot can take up to something like half an hour but after 2,5 hours we gave up, downgraded to 2.3.4 again using odin, and tried again on a different way (different recovery)
this is how we flashed it:
-made sure we had 2.3.4
-wiped data and cache with CWM 4.0.0.idk (the odin package for this CWM was included in the thread)
-installed CM7, everything went smooth
-rebooted, and then it got stuck
I really want to get this to work for him, any help from you guys?
is it because i wiped after flashing ?
Well the process should be like this :
1. Wipe data - Wipe cache - Wipe Dalvik-cache - Wipe Battery stats
2. Flash ROM
3. Wipe data - Wipe cache - Wipe Dalvik-cache - Wipe Battery stats
So twice?
He's not here right now with the device, but i want to gather enough info for tomorrow to retry
`leon said:
So twice?
He's not here right now with the device, but i want to gather enough info for tomorrow to retry
Click to expand...
Click to collapse
Yeah, it is safe to wipe before and after flashing.
And you're sure you did wipe dalvik-cache right ?
errrrmm, i don't remember, i think i did tho, i will, as again, retry tomorrow with also wiping dalvik
Well, as for me, when something went wrong, i flashed my device back to stock froyo first.
Then flash GB, Flash CWM, clear data and cache, flash the rom, clear data and cache again.
Reboot.
That's it
Sent from my GT-S5570 using xda premium
K, he's not here, i will give it a try now, fingers crossed :x
i know though what went wrong before
`leon said:
K, he's not here, i will give it a try now, fingers crossed :x
i know though what went wrong before
Click to expand...
Click to collapse
Always explain what went wrong, if someone with the same issues is reading the thread they'll know what not to do then.
So, what went wrong before?

flashing issue

Every time I flash any 4.2.2 rom the install appears to go fine but afterwords it says that it cannot read the cache in cwm then when I reboot to try the rom it just stays on the bootloader unlock screen. I have flashed many roms in the past and never had any issues. I have tried fastboot flashing MR and rsdlite back to ATT stock along with rewriting Epinters cwm and switching to mattlegroffs cwm but the same thing happens. But I am able to flash xperiamod and holoblur without issue. Scratching my head on this one anybody got any ideas.
Are you making sure to clear cache and dalvik cache?
sent from my PACman Atrix HD
Kohwali said:
Are you making sure to clear cache and dalvik cache?
sent from my PACman Atrix HD
Click to expand...
Click to collapse
always
frog1982 said:
always
Click to expand...
Click to collapse
For some ROMs you may need to clear the caches before and after installation. Just a heads up.
Are you saying you're stuck in the "bootloader is unlocked" screen after any installation of a ROM?
In that case are you making sure to do system wipe before installing?
Kohwali said:
For some ROMs you may need to clear the caches before and after installation. Just a heads up.
Are you saying you're stuck in the "bootloader is unlocked" screen after any installation of a ROM?
In that case are you making sure to do system wipe before installing?
Click to expand...
Click to collapse
I always wipe data, cache, dalvik, and system before any ROM flash but I have not tried wiping the cache after install I will try that when I get a chance.
update: tried wiping cache after install and the same thing happen but instead i unmounted the cache before install and it booted
Make sure you aren't using safestrap recovery.
Sent from my Atrix HD

[Q] Help Stuck in CWM bootloop after formatting system

Hey guys sorry if this has already been posted. I tried to search through the other threads but couldn't find anything with my exact problem. I am a noob when it comes to this stuff so please bear with me. I was trying to reinstall my ROM when I made the dumb mistake to format system, When I was in recovery I wiped data/factory reset, wiped the cache partition, wiped Dalvik cache, and then for some reason went to format system. After I did that and went to reboot the phone it asked me to fix root. I did this and it started the CWM bootloop. Does anyone have any ideas what I can do to fix it?
exitrecovery.zip will stop the boot loop.
Sent from my Nexus 10 using Tapatalk 2
chadsky92 said:
Hey guys sorry if this has already been posted. I tried to search through the other threads but couldn't find anything with my exact problem. I am a noob when it comes to this stuff so please bear with me. I was trying to reinstall my ROM when I made the dumb mistake to format system, When I was in recovery I wiped data/factory reset, wiped the cache partition, wiped Dalvik cache, and then for some reason went to format system. After I did that and went to reboot the phone it asked me to fix root. I did this and it started the CWM bootloop. Does anyone have any ideas what I can do to fix it?
Click to expand...
Click to collapse
Also try this...
Pull battery..
Count to 10.
Replace battery.
Press and hold Volume Down and power until the Factory Reset screen comes up..
Hit the power button twice, once to start and the second to confirm.
This should put you into your recovery mode... There you should be able to install the ROM again..
At least this is what has always worked for me...

Categories

Resources