Do I have to wipe both caches be4 updating to the new radios? Also, can I flash the radios to any Rom? Sorry I've never flashed radios be4
-Rr!cAn 3v0
Yes, just backup before hand, wipe the cache and dalvik cache, then flash your radio; you can also flash any radio on any rom.
Luisit0 said:
Do I have to wipe both caches be4 updating to the new radios? Also, can I flash the radios to any Rom? Sorry I've never flashed radios be4
-Rr!cAn 3v0
Click to expand...
Click to collapse
Yes, it is recommended to wipe both cache and dalvik before flashing a Radio. It is also recommended to reflash the kernel after flashing the radios. When I flash radios, I nandriod my CM7 setup, full wipe, flash radios, flash sense, update prl, update profile, and then restore CM7 nandriod.
from sense ROM: nandroid, wipe caches, flash radios, restore nandroid, update prl, update profile.
Muellersirch said:
Yes, it is recommended to wipe both cache and dalvik before flashing a Radio. It is also recommended to reflash the kernel after flashing the radios. When I flash radios, I nandriod my CM7 setup, full wipe, flash radios, flash sense, update prl, update profile, and then restore CM7 nandriod.
from sense ROM: nandroid, wipe caches, flash radios, restore nandroid, update prl, update profile.
Click to expand...
Click to collapse
Ok I'll be sure to do exactly as u said, thanx for the quick reply bro
-Rr!cAn 3v0
Be sure to not pull the battery when you reboot after the flash. The screen you'll see is normal, it's not an error. Pulling the battery will permanently brick your phone.
Sent from my PC36100 using Tapatalk
My suggestion:
Back up.
Download all radios. Check my sig for a link.
Wipe cache and dalvik.
Flash radio. Reboot. (All reboots will take you back into recovery)
Update Wimax. Reboot.
Update PRI. Reboot.
Update NV. Reboot.
Flash a rooted Sense ROM, based on the Evo (this disqualifies MikG, Director's Cut, Synergy and other Sense 2.1 ROMs, because those are based on the Evo Shift (I've had issues with Shift-based ROMs not reprovisioning data). Update PRL. Reboot.
Go into EPST (Dial ##3282#, Choose edit mode), enter your MSL code (download and use MSL Reader from the Market to get it), Data Profile, hit the menu button and choose restore. Just sit there, your phone will reboot and everything will go back to default. Let it reprovision, but when it says "Updating PRL" hit cancel.
Wipe everything in recovery three times, flash ROM of your choice. Personally I always do fresh installs, you can use Titanium Backup or nandroid I guess. I just like a fresh start sometimes.
what does restoring through epst do that setting everything to factory def not do?
thanks...
cipher77 said:
what does restoring through epst do that setting everything to factory def not do?
thanks...
Click to expand...
Click to collapse
EPST deals with the cellular data and connection. What I described reprovisions your phone on the network, usually for better data speeds. Factory reset deletes all caches and downloaded apps.
Related
I tried to dial that and nothing happened after it was entered. What did I do wrong? Thanks.
Sent from my PC36100 using Tapatalk
why are you trying to dial that?
*This was posted from my Evo 4G*
To fix my 4g
Sent from my PC36100 using Tapatalk
heard some roms don't support the codes. custom rom?
If you have a custom ROM, it might not support dial-codes such as ##DATA#, *#*#4636#*#*, etc. This is a known issue. You can always flash a rooted stock ROM, apply the baseband fix, and then re-flash your ROM.
That makes perfect sense! I'm using baked snack rom.. I guess that's why it's not working... I guess I can't fix my 4g yet...
Well, you can do a Nandroid backup, then wipe your data, cache, and dalvik cache, then flash a rooted OTA (stock w/ OTA) ROM, adjust the settings in ##DATA#, then re-flash your (right now) current ROM, followed by a Nandroid restore.
In other words:
1) Download OTA (1.47) rooted ROM.
2) Copy it to /sdcard then reboot into recovery
3) Do a Nandroid backup
4) Wipe everything in data, cache, dalvik (aka, factory reset)
5) Flash OTA rooted ROM
6) Boot into Android, bring up Phone dialer, punch in ##DATA#, type in MSL, adjust settings.
7) Reboot
8) Reboot into recovery
9) Wipe data, cache, dalvik, flash your old ROM
10) Reboot into Android, then reboot into recovery
11) Nandroid restore.
12) Reboot into Android, and you should have everything back.
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
danootz said:
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
Click to expand...
Click to collapse
No sometimes recovery doesn't wipe everything correctly... downlload caulks format all and then flash sense rom. Should fix your problem!!
Sent from my PC36100 using XDA App
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
danootz said:
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
Click to expand...
Click to collapse
radios have nothing to do with it. they base roms off new ota so that you can get the benefits of the changes not the radios. You can flash the original radio that came with the evo and it would not affect the rom. The radio controls your signal strength and wimax strength. which is why there is a thread with all the different radios because each phone reacts different to each radio.....
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
About a month ago I went from myns 2.2 to CM7 and eventually cm7.1 well I had terriable 3g 4g wifi and gps connection issues with CM and I flashed a bunch of kerenel and radio driver combos trying to fix the problem. Well out comes the synergy and I decide to try that and give up on CM. I did the usual wipe dalvic data ect twice and flashed synergy which got stuck on the white evo splash screen and won't go past that. Additionally when I flash any other rom's either myn's, cm, ect I get the same problem. I have tried wiping several times with both the Clockwork and RA recoveries with no success. As it stands now I can only recover previous nandroid backups or run the pc186img. Anyone have any ideas??? Help would be appreciated.
Thanks
Frankie
Go to the bootloader, do a clear storage [factory reset], then from recovery, do the full wipe, and only flash a rom, then boot; flash the kernel [if any] afterwards.
Frankie_Bones said:
or run the pc186img.
Frankie
Click to expand...
Click to collapse
hope thats an typo
dased14 said:
hope thats an typo
Click to expand...
Click to collapse
yeah pc36img
teh roxxorz said:
Go to the bootloader, do a clear storage [factory reset], then from recovery, do the full wipe, and only flash a rom, then boot; flash the kernel [if any] afterwards.
Click to expand...
Click to collapse
Worked, thanks. I had myself worried for a minute there.
After flashing QuadraSense 1.2(ICS 4.0.4) over a Sense 2.1 ROM, Synergy, my Bluetooth settings got screwed up. No matter what I do, new pairings end up being removed, and when I unpair devices, they reappear on the list after a reboot. Is there any way to fix this manually by deleting files? Or will I have to re-flash?
Don't flash over, do a full wipe before flashing the new ROM.
biohazrd51 said:
Don't flash over, do a full wipe before flashing the new ROM.
Click to expand...
Click to collapse
^ This
You do not flash one rom on top of another, thats almost ALWAYS garuanteed to screw up the operating system, especially if going from one major android version to another.
ALWAYS do a factory reset / wipe cache/dalvik / etc before flashing a brand new rom on the phone.
Yeah, I'm almost a complete noob at this; was a bit too hasty, I guess. However, after wiping System, Cache and Dalvik, then re-flashing the ROM, my Bluetooth problems still remain. :/
Just did a full wipe, then Titanium-restored everything, problem gone. I guess some settings in the data partition were conflicting with ICS settings.