I just installed cm7, and when I try to boot into bsr, the phone shuts off. Any suggestions ? I installed it correctly, just a little confused.
Sent from my MB870 using Tapatalk
Try flashing your phone again. then wipe data and cache. re install cm7 then wpie data and cache again. then reboot. that should set you straight.
Related
Hi there!
Today I noticed there were some new widgets and updates. I started to download them on Wifi in my home.
And then I gotta leave my home. When I left Wifi connection disconnected and updates stopped. After few hours my battery depleted so my phone shut down.
When I come to home I charged it and turned Wifi on. When I looked on get HTC widgets tab There was "Installing" labels next to some of the widgets but they weren't installing actually.
I waited for 15mins -enough time to install Win7 on my phone - but they didnt got installed. I got into manage apps. on settings and uninstalled all the HTC widgets. Restarted the phone three times. Nothing changed.
Any advices?
I decided to recovery but have some questions about recovery.
Will it roll the rom back to 2.1?
What will it erase? Apps, contacts, messages? What kind of settings will it reset? Ringtones, home layout and wallpapers?
Regards.
Sent from my HTC Wildfire using XDA app while pooping
Try clearing Dalvik Cache and also Format Cache in Clockworkmod. What do you mean by recovery? Nandroid? It is a 1:1 backup of whenever you made it. Or factory reset? Regardless, yes you will loose sms and contacts and etc so backup with HTC sync first.
Sent from my HTC Wildfire using Tapatalk
jonusc said:
Try clearing Dalvik Cache and also Format Cache in Clockworkmod. What do you mean by recovery? Nandroid? It is a 1:1 backup of whenever you made it. Or factory reset? Regardless, yes you will loose sms and contacts and etc so backup with HTC sync first.
Sent from my HTC Wildfire using Tapatalk
Click to expand...
Click to collapse
I meant anything that rescue me from my problem If the recovery in HBOOT screen is Nandroid, yes I meant it. I don't know how to clear Dalvik Cache or what it is But searched it and figured something. Now trying. I'm gonna update you.
Thanks.
Edit: And uh, what abput apps? will they erased?
Update: I was trying to Clear Dalvik via adb but it says: rm failed for -rf, Read-Only file system . What should I do?
Update2: I figured something and cleared Dalvik Cache but nonhing changed.
Update3: Performed a factory reset and solved thanks again jonusc for your attention
First question: I notice that a fair % of the time when I try to do a restore from CWM, it tells me there's a MD5 mismatch. Is this just a symptom of a bad SD card -- that the backup did not save properly to the card?
Since it's no good to find out the backup is bad when I actually need it, I came up with a work-around, which was to try and immediately restore from the backup immediately after making it. If it gives me an MD5 error, then I make a new backup. Eventually I don't get an MD5 error and the restore works, and in theory it should be restoring the phone to the state it was in just a few minutes earlier -- i.e. nothing is changed.
However, after a successful restore and reboot, I tend to get a slew of FC's at startup from background apps. I'm wondering what I'm doing wrong -- is there some extra step I need to do after a restore using CWM?
Sounds like when you backd up you had some data issues that are being restored too your phone each time you restore. Bite the bullett reflash your rom don't restore. But before you do that try fixing permissions in cwm.
I would clear cache and dalvik before doing the backup...
Sent from my SPH-D700 using XDA App
If you're using SRF, just reflash srf 1.1.1 right over it. It will repair your framework but save your personal data.
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Did not know that. You get a thanks.
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
kennyglass123 said:
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Click to expand...
Click to collapse
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
if you arent properly shutting down you will almost always get FCs on reboot if you have a no journal rom...
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
ummmm
Nerva said:
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
Click to expand...
Click to collapse
that would be not shutting down properly like pulling the power cable out of your comp and turn it back on not goood to do alot wil be ok in light doses
Corrupt data is 100% the cause. The only problem now is trying to determine where the problem came from. It can be from many things, but to be safe, i'd reformat the SD card (backup all ur data first on a computer). And recreate a backup from the rom previously. I use "my backup root" from the market and it works like a charm when switching from rom to rom.
Sent from my SPH-D700 using XDA Premium App
yep
i use the very same thing........... i read that somewhere lol
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
The 4 finger will cause corruption on ROMs without journaling, so yes. There is also a Quick Boot app that boots into recovery, same thing can happen. So for backups and restores, always power down then 3 finger into CWM.
I had Virtous Sense 1.29, which was working fine. Upgraded to 2.35 then this issue started. Screen times out and the MT4G restarts. Tried 2.37 today and the issue is still there. I wipe every time I flash. Any suggestions?
My guess is that need to wipe eveything to start a fresh rom.
That fix a lot issues..
But do not forget to nandroid, just to make sure if something goea wrong..
Sent from my HTC Glacier using XDA Premium App
Freeze and restarts ? you might what to read the important notes on the thread and flash the file they provided if your having that problem
Sent from my HTC Glacier using XDA App
I did do a full wipe in recovery multiple times. Wipe data/factory reset, wipe cache partition and wipe dalvik cache. No success.
I just flashed the patch under important notes as well. Screen timed out and then the MT4G restarted once again.
I change the screen time out setting to never and no restarts all at work today. It would be nice if my screen can time out on its own and not having to manually to do everytime. Thanks for your suggestions so far guys.
After doing a full wipe, I installed CM10 and the keyboard keeps crashing the home button doesn't work, browser won't work either. I've tried numerous tunes too do factory reset and wipe and nothing works
Sent from my SCH-I535 using xda app-developers app
did you install gapps?
yiannit said:
After doing a full wipe, I installed CM10 and the keyboard keeps crashing the home button doesn't work, browser won't work either. I've tried numerous tunes too do factory reset and wipe and nothing works
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You installed the wrong version of gapps. It needs to be gapps-jb-20121011-signed.zip.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
I did install the wrong ones, then I did a factory reset again and installed CM10 without gapps and it still does it
yiannit said:
I did install the wrong ones, then I did a factory reset again and installed CM10 without gapps and it still does it
Click to expand...
Click to collapse
Factory reset is not enough to get rid of them. That only wipes /data and /cache. You need to wipe /system before you install the CM10 again.
Sent from my Nook HD+ using XDA Premium
More on the keyboard issue
Ive run into the same problem also with the keyboard, home button, and browser not working. Ive read that this has been an ongoing issue with apparently the only solution is to reinstall CM10 and gapps. My question is, what versions of each are used. The latest nightly I was able to get was from 02/24. I also used the gapps from 10/11/2012. It was a no go. As soon as gapps gets installed, the problems begin. I tried the latest gapps from 12/12 and again, the same problems. What is the correct combination to use? Every time that Ive done it, Ive completely wiped my nook: system, data, dalvik, cache, etc.....
If I use the nightly from 02/24, for example, what gapps am I supposed to be using? Any help would be greatly appreciated.
G
pnkflyd101 said:
Ive run into the same problem also with the keyboard, home button, and browser not working. Ive read that this has been an ongoing issue with apparently the only solution is to reinstall CM10 and gapps. My question is, what versions of each are used. The latest nightly I was able to get was from 02/24. I also used the gapps from 10/11/2012. It was a no go. As soon as gapps gets installed, the problems begin. I tried the latest gapps from 12/12 and again, the same problems. What is the correct combination to use? Every time that Ive done it, Ive completely wiped my nook: system, data, dalvik, cache, etc.....
If I use the nightly from 02/24, for example, what gapps am I supposed to be using? Any help would be greatly appreciated.
G
Click to expand...
Click to collapse
CM10 always needs 20121011 (nightlies are CM10, you only get CM10.1 from here). Never use 20121212 on CM10, since it is hard to get rid of. If you ever installed the 20121212 gapps, both CM10 and the right gapps have to be re-installed on a wiped /system. If you are running on SD, reburning is not enough. That does not wipe it. It has to be wiped with CWM or TWRP.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Factory reset is not enough to get rid of them. That only wipes /data and /cache. You need to wipe /system before you install the CM10 again.
Sent from my Nook HD+ using XDA Premium
Click to expand...
Click to collapse
i too had the same problem .. as u said i followed the steps but now aal the buttons are working except HOME button ..
i use lg optimus one p500... installed ROm -cm--20130108-UNOFFICIAL-p500 .... and gapps-jb-20121011-signed.
thnxx in advance
Hello,
I have flashed Omega rom in my galaxy s4, however sometimes when I restart my device im stuck in the logo boot up. So my solution is to wipe the /data in recovery mode and it will start again.
But i don't want to wipe it every time i boot my device.
What do you think is the problem here? and how can i fix it?
rymngh said:
Hello,
I have flashed Omega rom in my galaxy s4, however sometimes when I restart my device im stuck in the logo boot up. So my solution is to wipe the /data in recovery mode and it will start again.
But i don't want to wipe it every time i boot my device.
What do you think is the problem here? and how can i fix it?
Click to expand...
Click to collapse
Try to wipe system, data, and cache again. Then reinstall the omega rom and see if that solves the problem.
Flowed from my GT-I9505 using xda-developers app
joelvn said:
Try to wipe system, data, and cache again. Then reinstall the omega rom and see if that solves the problem.
Flowed from my GT-I9505 using xda-developers app
Click to expand...
Click to collapse
i've done that 4 times already. and it is still not working..
last week, i flashed a rom and while flashing it the battery fell off because i removed the back cover while flashing it last week. maybe thats the problem why my data is not working properly?
rymngh said:
i've done that 4 times already. and it is still not working..
last week, i flashed a rom and while flashing it the battery fell off because i removed the back cover while flashing it last week. maybe thats the problem why my data is not working properly?
Click to expand...
Click to collapse
That probably isn't the problem. I recommend you to download the stock firmware of your phone and install that using Odin. Then if it works you can root it again, install a recovery and try it all again.
Flowed from my GT-I9505 using xda-developers app