Database Info

[Q] New Cyanogen 7 update for Thunderbolt

Hey Guys,
So I just rooted my Thunderbolt the other day with Cyanogen 7 Mod version 7.0.0. Today a new update came out (version 7.0.1) and I was trying to figure out if I needed to wipe my data and cache in order to update to this version. Hopefully someone has the answer. I am new to android and am looking for advice. Thanks in advance!

Wipe data
Wipe cache
wipe dalvik cache in the advanced portion of CWR
then install the ROM
Do all three at least 3 times just to be sure.
Make sure your battery is fully charged.
Anytime you install a new ROM follow this. If a small modification like new market, pull down menu. just wipe cache
Hopes this helps

hackercity said:
Do all three at least 3 times just to be sure.
Hopes this helps
Click to expand...
Click to collapse
Lol, reminded me of the website is down vid....did you reboot? Yea man I rebooted three times, I always reboot three times like you told me!
-sent via 1.21 giggawatts of android.

wipe 3 times? excessive much? once is sufficient and additional wipes wont do anything more.

mbh87 said:
wipe 3 times? excessive much? once is sufficient and additional wipes wont do anything more.
Click to expand...
Click to collapse
+1 to wiping just once.
Also, OP, keep in mind CM7 for TB is pre-alpha and does have bugs. If you're looking for a daily driver, since you're new to Android, perhaps you would want to try a more stable ROM to get your feet wet, and once you get the hang of things, perhaps trying CM7 or a leaked ROM.
Good luck!

Wipe 3 times Anal retentive much? ...haha anyway
Wipes of caches sure but ....
Flashing CM7 7.0.1 over 7.0.0 there is no need for data wipe .
If an issue does arise you can wipe it after but why reinstall all your apps really?
This has been my daily driver
No 4G here yet & I use do not use wifi regularly.

are there still issues with CM7 not being able to use phone information (EPST) or ##778# to manage / edit modem settings?
i think i'm stuck on 3g...

there's an app called network that lets you pick which radio you want to use..I used it to switch from 3g/4g to 3g only...it has 4g only.

I always wipe 2-3 times ever since the OG Droid days. It takes you 30 more seconds, whats the big deal. If it somehow bricks because the wipe wasn't successful or you have to reflash a rom it will take you another 10-20 minutes.
Better be safe than sorry.

I've followed the steps outlined in the following thread but i can't get data to stick. It frequently drops even the 3G connectivity.
Also noticed that bluetooth isn't workinig.
http://forum.xda-developers.com/showpost.php?p=13881413&postcount=2616
Any tips on what I can try to get data to stick.

PUR3AO5PTH3ORY V1.0 problem

my phone resets itself. It gets loaded all the way to the main screen then when I go to click on something it locks up and rebootself. any help?!

justavillain said:
my phone resets itself. It gets loaded all the way to the main screen then when I go to click on something it locks up and rebootself. any help?!
Click to expand...
Click to collapse
Did you wipe EVERYTHING?
Sent from my ADR6400L using XDA Premium App

yes i did wipe everything 3 times. it seems the cpu hits a wall and just resets

justavillain said:
yes i did wipe everything 3 times. it seems the cpu hits a wall and just resets
Click to expand...
Click to collapse
Make sure to wipe dalvik cache and battery stats too.
If that doesn't work. Make sure to check your MD5 sums and do a fresh install.
Sent from my ADR6400L using XDA Premium App

i just did another fresh install. i let it sit for about 10 min or so now. if i get the problem ill check taht out

justavillain said:
my phone resets itself. It gets loaded all the way to the main screen then when I go to click on something it locks up and rebootself. any help?!
Click to expand...
Click to collapse
Format system.. And there is 1.1 just released too
Sent from my ThunderBolt using XDA Premium App

wipe dalvik, cache/system, factory reset, format /system, wipe battery
i use that latest 6275 radio
the initial bootup where it keeps showing the droid pop up will do that for awhile. i was starting to think "god why!!!... whats wrong?!" and then it loaded.

Try a0sp 1.1.1

i went to 1.1 and same problem. i went to run quadrent and it locks every time. ill try 1.1.1, im guessing he fixed the market problem

Hmm interesting, did you once you installed it (after wiping) let it sit for 10 min before rebooting it?

while still in clockwork recovery, wait 10 min? im not kne to rooting just the whole rom/kernel part.

justavillain said:
while still in clockwork recovery, wait 10 min? im not kne to rooting just the whole rom/kernel part.
Click to expand...
Click to collapse
Nope in clockwork wipe, do a factory reset, wipe cache, then do dalvik and system too.
After that, flash your ROM and reboot once complete. While it is rebooting go find something to do. Basically, leave it alone for a few minutes (2-5 is usually sufficient). That allows the kernel/rom to settle.
For extra credit, before wiping, go ahead and use something like titanium backup to backup your apps. The you can restore your apps (not the system data though). Thats how I usually do it.

saintfurion said:
Nope in clockwork wipe, do a factory reset, wipe cache, then do dalvik and system too.
After that, flash your ROM and reboot once complete. While it is rebooting go find something to do. Basically, leave it alone for a few minutes (2-5 is usually sufficient). That allows the kernel/rom to settle.
For extra credit, before wiping, go ahead and use something like titanium backup to backup your apps. The you can restore your apps (not the system data though). Thats how I usually do it.
Click to expand...
Click to collapse
I did all that a few times now and nothing doing....it's starting to make me mad so I'll just flash back to CM7 and keep it that way.

Could just be a bad download...

[Q] HELP flashing kernel PLEASE

I have just recently begun modding my G2x. I can install ROMs without any problems but I've since been interested in flashing a custom kernel. Information is sort of everywhere and what I do manage to find I am worried about it being out-of-date. Anyway, I flashed cm7.1 (the stable release) and it worked fine until it started fc-ing everything google related (something to do with sync?). I decided to try flashing kernels (wiping caches as instructed) and could never get one to work. I've since flashed the latest cm nightly (201 I think) and tried trinity with it. Still nothing. I've since read that I should let the phone sit for 10-20 minutes but after about 20 minutes it is just a black screen and nothing ever happens. It does get really hot however. Anyway I have tried flashing kernels multiple times and nothing has ever worked, same story every time. Any way somebody could tell me what I'm doing wrong? Tell me what's compatible (as maybe sorta stable) with the ROMs I'm using? HAHA and if it's not asking too much...maybe some links too? Sorry, just very new to this and very eager to learn. I just have a bit of trouble figuring out what's supposed to be compatible and where to find it. THANKS!

Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!

fcisco13 said:
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Thanks will give it a shot in the morning. Too much of a headache all day. Back in a useable state and I want to keep it that way for a bit haha. Will post results.

I still haven't tried to flash a new kernel... that is coming in a bit. I do have a question though... I'm interested in getting my phone in the cleanest state possible before doing anything further. I basically want my external sd cleaned up (I want to just reformat it) before flashing a rom again. What files/directories are absolutely essential to keep? As I said, I want to just wipe it clean but I'm not sure I can do that.
Sent from my LG-P999 using XDA App

So just to be thorough I can safely remove the cwm directory as well? Just delete it all put my rom and kernel zips back and I'm good?
Sent from my LG-P999 using XDA App

Make sure you flashed recovery through nvflash
NVIDIA NEVER AGAIN!

Tried to just flash 0.4.7 and it did the same thing as before. Waited 20 minutes before taking out the battery then tried to boot it again. Waited 20 more minutes and all it ever did both times was get hot. Same results as before.
Sent from my LG-P999 using XDA App

OK that's what I was missing. Needed to be running SV. Anyway it's working now just fine. Muuuch appreciated.
Sent from my LG-P999 using XDA App

[Q] P5110: Random Rebooting (CyanogenMod 10.1 - RC5)

My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!

jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,

jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.

Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.

Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium

Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?

Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.

Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium

Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.

Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.

Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.

jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app

After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.

Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?

All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app

Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1

I am Having the same prob with galaxy tab2 7.0(gt-p3100)

[Q] Updating PureWhite without Fwipe

Hi at all
I didn't reached 10 messages so I can't post my question on developer's thread, so I'm going to ask it here
I have a PureWhite L preview ROM updated to semptember release
yesterday the developer updated to a new version and I don't know if I can upgrade to a new version without a FullWipe
Thanks for the patience

If it doesn't say clean flash (full wipes) then you can try a dirty flash (no wipes).
If you have any issues at all after tho, you need to clean flash before reporting them, to see if that solves it.
Use titanium backup to back up user apps and data, and clean flash....that's the best way in my opinion. (obviously don't wipe internal SD)
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
Oh, when devs make major changes, they usually will tell us to clean flash....in that case, do it. ?

Thank you for the reply
I alreary use Titanium, I'm not a beginner but I don't want to soft brick my phone doing a dirty flash and the autor didn't mentioned if I can do it

Worst case usually if updating same Rom is some issues like force closing, or maybe a bootloop or something. If so, then just clean flash it.
I've never heard of a brick from dirty flashing a Rom update.
But, there's risk with everything we do as always. ?

sas46 said:
I'm not a beginner but I don't want to soft brick my phone
Click to expand...
Click to collapse
Hehe that's an oxymoron. No such thing as a soft brick. Only beginners believe it exists
Seriously though the reason for boot loops with dirty flash is incompatible data. Nothing more. Nandroid. Titanium. Flash. If it boot loops, wipe.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Hehe that's an oxymoron. No such thing as a soft brick. Only beginners believe it exists
Seriously though the reason for boot loops with dirty flash is incompatible data. Nothing more. Nandroid. Titanium. Flash. If it boot loops, wipe.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You are saying that, more than one year ago I bricked my gNex doing an update of PA without a full wipe (only cache, dalvik and format system)
That rom is a cooked rom from an unstable preview, so if the developer made some important changes it can cause some major problems with booting like happened with PA and my Gnex

sas46 said:
You are saying that, more than one year ago I bricked my gNex doing an update of PA without a full wipe (only cache, dalvik and format system)
That rom is a cooked rom from an unstable preview, so if the developer made some important changes it can cause some major problems with booting like happened with PA and my Gnex
Click to expand...
Click to collapse
Whatever caused your "brick" on your gnex, I 100% guarantee you that it was absolutely nothing to do with whether you wiped or not.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Whatever caused your "brick" on your gnex, I 100% guarantee you that it was absolutely nothing to do with whether you wiped or not.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not a developer, I'm an user that like, sometimes, to test some new roms and I really like thi one. I'm only reporting you my experience. I can't waste half a day to put my phone back working and that's why I asked there my think
When I'll reach 10 posts I will ask to the developer directly
Thank you for your patience

sas46 said:
I'm not a developer, I'm an user that like, sometimes, to test some new roms and I really like thi one. I'm only reporting you my experience. I can't waste half a day to put my phone back working and that's why I asked there my think
When I'll reach 10 posts I will ask to the developer directly
Thank you for your patience
Click to expand...
Click to collapse
I'm trying to help you. Your question is basic and any user who flashes ROMs should at least understand these basics. This is not a question you need to ask the developer. We've already answered. Its an answer we give a hundred times a day.
Try reading our sticky threads which you can get to via my signature. We've written everything you'd ever need to know
Sent from my Nexus 5 using Tapatalk

Guaranteed you didn't brick your gnex from a dirty flash.
You can't brick your phone from a dirty flash.
#stayparanoid

Honestly, if you are worried about needing time to fix the odd issue, flash stock and call it a day. This hobby can very often require some time when things don't work right.
That's just how it is. ?