Related
i have just installed the new radio and new radio's recovery.
i just put the cusorsense32A 1.2.6.1 on but everytime i turn it on it goes up to the start where you select language then freezes and goes back to the waving android startup screen.
Dragon365 said:
i have just installed the new radio and new radio's recovery.
i just put the cusorsense32A 1.2.6.1 on but everytime i turn it on it goes up to the start where you select language then freezes and goes back to the waving android startup screen.
Click to expand...
Click to collapse
try wipe everything then reflash 1.2.4 then apply 1.2.6.1 without wipe rename 1.2.4 to update.zip and keep the origional file name of 1.2.6.1
i am using the ra-magic32a-6.35-v1.5.2 recovery
so do i just do the wipe data/factory reset or everything as well
so like wipe dalvik-cache, wipe sd:ext partition, wipe battery stats, wipe rotate settings aswell?
Dragon365 said:
i am using the ra-magic32a-6.35-v1.5.2 recovery
so do i just do the wipe data/factory reset or everything as well
so like wipe dalvik-cache, wipe sd:ext partition, wipe battery stats, wipe rotate settings aswell?
Click to expand...
Click to collapse
use this guide, you have radio and spl flashed but flash the recovery in this post http://forum.xda-developers.com/showthread.php?t=605239
The Amon_RA Hero Recovery (thats the one i use and it works for me
Dragon365 said:
i am using the ra-magic32a-6.35-v1.5.2 recovery
so do i just do the wipe data/factory reset or everything as well
so like wipe dalvik-cache, wipe sd:ext partition, wipe battery stats, wipe rotate settings aswell?
Click to expand...
Click to collapse
i just wipe the two first ones thats was enough for me
i tried it but 1.2.4 does the same thing
if i flash 1.2.6 now will it work normal or still the same?
Dragon365 said:
i tried it but 1.2.4 does the same thing
if i flash 1.2.6 now will it work normal or still the same?
Click to expand...
Click to collapse
did you change the recovery to the one i posted?
yeh i updated to that one before after i updated my radio coz my old recovery didnt work
Dragon365 said:
yeh i updated to that one before after i updated my radio coz my old recovery didnt work
Click to expand...
Click to collapse
you need to flash this recovery into it http://forum.xda-developers.com/showthread.php?t=561124
in this post you need this recovery file Download
Latest :
•recovery-RA-hero-v1.5.3.1.img - MD5Sum: 7df9967233e414875257b1f1bf4c574d
is this the recovery you use :s
Dragon365 said:
is this the recovery you use :s
Click to expand...
Click to collapse
yup check your messages too
OMG DUDE YOUR A LEGEND =D
the recovery thing worked
thanks for all the help today
Dragon365 said:
OMG DUDE YOUR A LEGEND =D
the recovery thing worked
thanks for all the help today
Click to expand...
Click to collapse
no problem
nah i am not a legend, cursordroid is the one who is to thank for his great guide
hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett
I believe that those ROMs both require ENG S-OFF. Open simple root on your computer, click Fixes, then apply the fix there. Also, did you make sure you cleared your Dalvik cache before flashing? Always do a factory reset AND clear dalvik cache when changing ROMs.
make sure you have wifi off in your first boot
ardynine said:
make sure you have wifi off in your first boot
Click to expand...
Click to collapse
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
EtherealRemnant said:
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
Click to expand...
Click to collapse
Thanks ER. I'll try your method this evening.
I'll report back.
thanks!
brett
EtherealRemnant said:
I believe that those ROMs both require ENG S-OFF.
Click to expand...
Click to collapse
I can say with no doubt whatsoever, no.
id10terrordfw said:
I can say with no doubt whatsoever, no.
Click to expand...
Click to collapse
any suggestions then???????
I tried doing the ENG-off and still the same hang up on the front screen.
Any help please?
thanks,
brett
what method do you use to flash cm7? what exactly do you do.
to clarify what is your exact process for flashing the rom?
mudknot2005 said:
what method do you use to flash cm7? what exactly do you do.
Click to expand...
Click to collapse
Hi. Thanks.
I use rom manager to boot to recovery. Then I install zip from sd card. I go through the process until it says reboot. It's when I reboot that I get stuck in the bootloop. It just cycles from the CM7 circular arrow to blank and then to the arrow thing again. MIUI does the same between the gingerbread guy and the status bar and back.
I then take the battery out, take out the sdcard, down volume & power, reinsert sdcard and do a restore so I can use my phone again in clockworkmod 3.0.0.6.
thanks,
brett
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
bdws1975 said:
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
Click to expand...
Click to collapse
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
EtherealRemnant said:
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
Click to expand...
Click to collapse
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
bdws1975 said:
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
Click to expand...
Click to collapse
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
I'll give it a shot and then get back to you.
I do believe, however, that the restore I'm doing is the backup I did right before I did the original cm7 flash. I'll try.
thanks!
If you toggle wifi on after the first boot it goes into a bootloop. This is a know bug not a hunch.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
DUDE!!!! You freaking rock. I got it!
I installed MIUI and it's amazing. Thank you very much.
Brett
Mustang302LX said:
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
thank you!!!!! I really appreciate your help!
Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
RampageRR said:
Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
Click to expand...
Click to collapse
you got it. i dont think you have to flash the script everytime and you will not have to flash gapps everytime. btw you dont have to wipe between nightlys just simply flash over
Thanks, I appreciate the quick reply. So I shouldn't bother to wipe cache and dalvik cache? I thought that was pretty much recommended before flashing the majority of stuff. Ok, so I'm off to flash this nightly.
I never wipe between nightlys. But if you ever do encounter problems, then wipe cache, dalvik cache then reflash
Sent from my Desire HD using XDA Premium App
I've always wiped cache and dalvic between nightlies. I don't know if it's needed but I've never had any problems with installs. It only takes a few seconds and it's never hurts to be safe.
Sent through the power of Cthulhu!
I flashed 144, no issues so far. Thanks to all of you for the replies. I ended up wiping cache and dalvik cache just to be safe. I know there's a change log, but has there been any changes of consequence over 7.1 RC that are noticeable?
I know the most easily noticeable is if you put a lock screen on you can disable the lockscreen. Plus from 143 on is now on 2.3.5 if I'm not mistaken which does have some slight tweaks.
Sent through the power of Cthulhu!
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
Im running sparksco cm7.2 and everything was going well, until I tried to backup. The system backed up but now im stuck on bootloop! Can anyone help with this? ive tried wiping and restoring and no luck. Stuck on bootloop, Damn!!!
letmeputdatipin said:
Im running sparksco cm7.2 and everything was going well, until I tried to backup. The system backed up but now im stuck on bootloop! Can anyone help with this? ive tried wiping and restoring and no luck. Stuck on bootloop, Damn!!!
Click to expand...
Click to collapse
Have you tired a fresh flash or flashing another rom/back up
Sent from my PG06100 using Xparent Blue Tapatalk
Boot CWM, wipe /system, /cache (cache), dalvik cache, reflash rom, reboot.
All good thank u! Just restored back to cyclonic! Let's Go Giants!!!
First time I've heard of something like this, maybe next time ask the developer of the rom?
VICODAN said:
Boot CWM, wipe /system, /cache (cache), dalvik cache, reflash rom, reboot.
Click to expand...
Click to collapse
That should work, but the roms do wipe cache and dalvik-cache for you already so it's going to take a long time to boot up. Also every aosp rom already wipes system before installing just a fyi.
sparksco said:
That should work, but the roms do wipe cache and dalvik-cache for you already so it's going to take a long time to boot up. Also every aosp rom already wipes system before installing just a fyi.
Click to expand...
Click to collapse
Actually not all roms wipe /system.. key ingredient here.
VICODAN said:
Actually not all roms wipe /system.. key ingredient here.
Click to expand...
Click to collapse
I didn't say all roms, you mis-read again, but it seems to be a typical thing for you to do.
sparksco said:
I didn't say all roms, you mis-read again, but it seems to be a typical thing for you to do.
Click to expand...
Click to collapse
You said every AOSP ROM wipes /system.
VICODAN said:
You said every AOSP ROM wipes /system.
Click to expand...
Click to collapse
Yes that's what I said. Can you show me one that doesn't? And it should be a mainstream rom too like cyanogenmod, miui ect. Just show me one mainstream aosp rom that does not wipe system.
sparksco said:
Yes that's what I said. Can you show me one that doesn't? And it should be a mainstream rom too like cyanogenmod, miui ect. Just show me one mainstream aosp rom that does not wipe system.
Click to expand...
Click to collapse
Oh Sparksco. I love you.