Develop Bugs

Constant Bootloop after flashing ANY kernel

Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.

DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App

Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.

How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.

Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.

najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.

najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.

Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.

Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.

Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App

You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App

Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!

Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.

Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.

When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App

Thanks I'll give it a shot later on.

[Q] Flashed nightly Mod7 build7 for my EVO4g HELP

Please be nice to me.....I am a newbie, very bold and out of the box and living dangerous with this rooting and ROM flashing. I am addicted but do not know a lot. I am not techno stupid but I get excited and dont think sometimes (was before I took my A.D.D. meds so I was being impulsive) anyhow for some stupid reason I didnt run a nandroid backup. I have a backup but for some reason it wont boot to it. What happened was after flashing 7 the other day, I loved it but market kept force closing all my apps and I couldnt figure it out so I restored back to mod6. was up all night playing around trying to learn all this lingo blingo ROM crudola...........anyhow saw the 7nightly so I flashed it while driving to work (bet yall think im really dumb now) LOL and it boots and gets to the Android screen where it says touch the Android to begin......NOTHING HAPPENS. Rebooted 3 times no worky. So I figure well go back to Mod6 and have a phone until 7 is stable. Cant do that so Im not sure what to do now. I tried flashing a Full Mod6 but to no worky I am at a LOSS. Figured I would ask the experts to please help with ideas. Hugs from Texas girl
Currently backing up my SD card in case I need to.

Have you been wiping in-between flashes? If not:
1. get into recovery
2. wipe everything except battery and rotate stats. Wipe it all again.
3. Flash the Rom of your choice.
4. ???
5. Profit (hopefully)

cm7 nightlys
nicolemiles said:
Please be nice to me.....I am a newbie, very bold and out of the box and living dangerous with this rooting and ROM flashing. I am addicted but do not know a lot. I am not techno stupid but I get excited and dont think sometimes (was before I took my A.D.D. meds so I was being impulsive) anyhow for some stupid reason I didnt run a nandroid backup. I have a backup but for some reason it wont boot to it. What happened was after flashing 7 the other day, I loved it but market kept force closing all my apps and I couldnt figure it out so I restored back to mod6. was up all night playing around trying to learn all this lingo blingo ROM crudola...........anyhow saw the 7nightly so I flashed it while driving to work (bet yall think im really dumb now) LOL and it boots and gets to the Android screen where it says touch the Android to begin......NOTHING HAPPENS. Rebooted 3 times no worky. So I figure well go back to Mod6 and have a phone until 7 is stable. Cant do that so Im not sure what to do now. I tried flashing a Full Mod6 but to no worky I am at a LOSS. Figured I would ask the experts to please help with ideas. Hugs from Texas girl
Currently backing up my SD card in case I need to.
Click to expand...
Click to collapse
Btw cm7 nightlys #7 is working fine I have no issues other than I think I might be having radio issues but that has nothing todo with cm7.
First you have to wipe and partition all data on your phone inrecovery mode. Cache dalve calche and do a full system wipe. Get yourself one of those minisd to sd card adapters to format your sd. Erase all data by formatting the sd the copy and paste your working rom zip back on the sd. Put it back in your fone and reboot into recovery. From there id do one more factory reset just to be sure then flash the zip. You should be good. Sounds to me you flashed to many roms on top of eachother without wiping prior installments.

Omg thanks
Wiping Data was the ticket.......DUH to me! you guys are awesome. Im in and just logged in and setting it up now. EXCITED!

tejasrichard said:
Have you been wiping in-between flashes? If not:
1. get into recovery
2. wipe everything except battery and rotate stats. Wipe it all again.
3. Flash the Rom of your choice.
4. ???
5. Profit (hopefully)
Click to expand...
Click to collapse
Gotta love the underwear gnomes

Rebooting issues

Ive installed a few different roms and when the phone boots up the animation, it reboots and just reboots at the HTC Evo white screen..
ive gone into the recovery and deleted the Cache and Davlik.. rebooted, and same thing... out of 10 boots, it booted 2 times successfully into the rom but then after 10mins, it reboots again and get stuck...
anyone know whats wrong or how to fix this..
thanx

gd6noob said:
Ive installed a few different roms and when the phone boots up the animation, it reboots and just reboots at the HTC Evo white screen..
ive gone into the recovery and deleted the Cache and Davlik.. rebooted, and same thing... out of 10 boots, it booted 2 times successfully into the rom but then after 10mins, it reboots again and get stuck...
anyone know whats wrong or how to fix this..
thanx
Click to expand...
Click to collapse
If your not running any scripts then I would try fresh download wipe all except sdcard battery and rotation and reflash don't flash any thing else until after you boot up then flash each additional item that you like one at a time rooting between each one that way you can find out what if anything is causing your problem hope that helps

ive used the wipe on EVERY options.. even wipe sdcard, battery and rotate screen option...
I dont flash any extras then the actual rom..

gd6noob said:
ive used the wipe on EVERY options.. even wipe sdcard, battery and rotate screen option...
I dont flash any extras then the actual rom..
Click to expand...
Click to collapse
Then I would try a fresh download you may have a bad copy

I had the same issue on a replacement Evo, it had never been rooted. Eventually it wouldn't boot up at all, even after 20+ tries. I took it into the Sprint store and they ordered a replacement (they did check for s-off).
I would try running an RUU. If the problem persists, then do whatever you have to do to get s-on so you can get a replacement. I'm not familiar with the new rooting and unrooting methods, haven't done it since FroYo. If running an RUU will revert you to s-on, then I'd use an easily rootable RUU in case it solves your problem. Good luck!

Like plainjane said. In case you need to unroot and have it replaced, I'd follow captain_throwbacks thread at the mik-mik to downgrade radios and hboot to froyo (radio 2.15.00.11.19 hboot 2.10) before your phone becomes completely unalterable, then you'll still be root, and if the unthinkable happens, you'll also be in good shape for sprint checking your setup. Look in the general sub-forum,... much talk and info about this. Look for info from Captain_Throwback.
Sent from my PC36100 using xda premium

If you wiped your SDCard, then you have nothing on there. Definitely run the RUU and see where you can go from there

Might wanna check ur permissions ad well....not sure which rom ur running but the boot animations..are either in data....local....or says...media...resources ...if I'm remembering correctly ....long press and check ur permissions once you've found them
Sent from my Expressed out eVo using xda premium

how long have yo let it go? Iv had a similar problem when i boot to a new rom for the first time. it goes through the splash screen, then to bootanimation, then back to splash then animation again. this usually happens 1-2x then once its all up, settled in and i have my settings and apps reapplied it doesnt happen again. Just my experience.

the only problem is....
Im not on sprint.. heck im not even in the U.S.
Im up in Canada. I bought this phone for my media player instead of an ipod, which is more (got this phone for $50) and for taking pictures... If its dead (i hope its not) then its no big deal...
also, i have a habit of backing up my important info and wiping my SDcard when install a new rom..

im kinda getting fed up with this constent reboots..
im thinking if I flash the stock RUU, this would unroot my phone.. then I will reroot it.. would this be a good idea??
I read that the lastest RUU cant be unlocked yet.. so which is the latest version that can be unlocked and s=ff?

gd6noob said:
im kinda getting fed up with this constent reboots..
im thinking if I flash the stock RUU, this would unroot my phone.. then I will reroot it.. would this be a good idea??
I read that the lastest RUU cant be unlocked yet.. so which is the latest version that can be unlocked and s=ff?
Click to expand...
Click to collapse
I'm surprised no one's asked you this yet, but what recovery are you using?

Amon RA, from the following link. Flash it via hboot using PC36IMG.zip
http://forum.xda-developers.com/showthread.php?t=705026
IIRC, after i flashed this recovery, i started having these issues... before I was on the revolutionary recovery and didnt have any issues..

(Fix) JB/ICS extreme lag and non booting issues

I recently have spent a decent amount of time trying to get my inc2 to boot JB without extreme lag(maxed out CPU). I've ran JB quite a few times until one day I overclocked to 1.5GHz and my phone boot looped and could never get JB or ICS to run properly. Its been reported that over clocking over 1.3GHz can break the partition on your phone and even lose root. If u have similar problems this is what I did -
Put the stock ruu GB 2.3.4 on the root SD card as pg32img.zip
Boot into boot loader and click vol up to accept update.
you are now on the latest stock gb without root but s-off will b preserved
download super one click and htc drivers to gain root.
reboot
I flashed twrp thru goo manager cuz that it's what I prefer. Wipe and flashed dkstunna's build 3 with 4.2 gapps and boom BACK TO FAST JB in under 30 min.
hope this helps someone! hit thanks if it did
next I hope to help on the main thread one day, Ive flashed almost every ics jb Rom and would luv to help
Sent from an incredibly running JB inc2

Can anyone verify this works? Not that I doubt you OP, just wondering if this has worked for anyone else?

Quick question.
I have been rooted for so long I've almost forgotten how it is done but I don't remember Super One Click supporting the DInc2. Does this mean it does root 2.3.4?

yes super one click works for inc2, and yes it will root 2.3.4. s off is the hard part on 2.3.4 if ur not already, so be s-off. I'm sure this will work differently for everyone cuz god knows why ics jb stopped working right in the first place. I bet kernel source would fix this too...

Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!

I'm running PA for months now and it hasn't locked up or lagged. I came from Venom before. I wiped everything except SD card, installed CM10 10/3, booted, flash PA, booted, flashed gapps and kernel. It booted up just fine for me.
I also flashed the firmware in the Venom thread. I don't use v6supercharger, 1024MHz smartassv2, and I undervolt -50.

TheAtheistReverend said:
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
Click to expand...
Click to collapse
I was in a bit of a panic cause i was using viper, went to aeroevans 11/13 jb, it worked for about 6 hours and then the massive lag and boot loops started. I couldn't flash any ics/jb aosp rom, I tried mimicry, dkstunna, and aeroevean's cm9/10. all non usable, crazy lag and boot loops. viper seemed to flash fine though.
I did try the solution in this thread and it didn't seem to work so I reflashed viper formatting using aroma. I let it boot and settle. then i formated all partitions in 4ext and reinstalled viper without formatting in aroma and i let it boot and settle, finally i reformatted all partitions in 4ext, installed aeroevan's 11/13 with latest jb gapps and all has been great for the past few days. fingers crossed.

I have tried just about everything. I can't think of anything else to try. I wish we knew why some phones were doing this.
The first thing I remember not going as usual on my phone was MIUI was not installing properly. It would hang on "updating boot" during install. I couldn't for the life of me get it any farther than that. The next thing was a JB NAND wouldn't boot properly, and then it was all down hill.

Back on the same bull**** of bootlooping on cm10. There should be a warning on the viper thread to not install it if you ever want to use another rom.

I don't know why but I'm not having any problems after viper...
I'm so fresh you can suck my nits...

None of us know the answer and that's the only common denominator. I'm just lucky that Miui works or i'd be sol

Uhh so yeah, tried this and it didn't work. Never had any problems with the phone before I got rid of ViperInc. I was on the latest firmware, every ROM flash was a totally clean one, followed the instructions in the OP and CM10 Global is just sitting here bootlooping. I know the dev isn't responsible for what happens to our phones, but multiple cases of the same seemingly unsolvable problem says there's something wrong with that ROM, imho. ****ing bogus.

Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app

chillybean said:
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
It's not the cm10 devs' problem

Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app

after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem

chillybean said:
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I don't think it is ViperROM dev's problem, nor is their responsibility to help. They make it very clear they hold no responsibility for what happens to your device when you flash their ROM. They are also not making any money from the free rom they put out for us to enjoy, so their is no driving force really behind their desire for "fans" if you will.
That being said, it would be nice if they could help and did. Has anyone directly, and nicely asked Nitsuj or any of the Viper team for help?
fen0m said:
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
Click to expand...
Click to collapse
Doubt it. I went all the way except for S-off and re-rooted but it still will not load any JB rom I try. But by all means, it might be worth trying if you're so motivated. Seems like some things work for some, but not for others at this point.

Just got back onto CM10. Was on Viper, did full wipe x2, formatted partitions to ext3 in 4ext Recovery, fix permissions, then formatted cache.
Then...here's the weird part....since Mimicry was the only non GB Rom I could get to at least boot, I tried a clean flash of it. Used only the baseline items in the Aroma installer (only things I installed were the jb animations, trebuchet, v6, and daemon). Booted into Mimicry and let it settle without signing in to Google. Profit!
Next phase was a full wipe x2, flash newest CM10, flash GApps, then format cache.....double profit! Hopefully this will hold up. Will report back once its had time to fully settle.
Sent from my Incredible 2 using xda premium

Sry didn't mean to say it like that but I know its not their responsibility..I just asked if they try to figure this out..I'm gonna try this mimicry method...I hope I profit like twice
Sent from my HTC Droid Incredible 2 using xda app-developers app

I wouldn't call it a method really....I think I may have just gotten lucky
Sent from my Incredible 2 using xda premium

[Q] Help needed- Bootlooping

HI,
I am facing a peculiar kind of a problem. I recently rooted my Desire Z following the cyanogen wiki to the letter. I have tried many ROMS but whichever ROM I install, I am facing this problem. For the first few days of Install, my phone works perfectly. But after a few days if I reboot, my phone gets stuck is a bootloop( i dont know if thts the right word, coz it boots and it starts the android but before the launcher is started it restarts again.
First I was using Flinny's CM10.1 test builds, and then I changed it cause I thought that was the problem. Now I am using Andromadus' Mimicry 1.5 which is also giving me same problem.
Everytime this happens I have to use the PCIMG10 file to restore it and then root it again and then install the ROM..
Is there any way to solve this problem.. I'll provide logs if u require... I am desperate..

yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)

demkantor said:
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
Click to expand...
Click to collapse
I have a logcat from when I was running Flinny's CM10.1 test builds.. I faced this many times with that ROM and so I took a log last time it happened.
BootLoopLog_CM10.1
The latest time since I was in a hurry to get my phone back to working condition couldnt get a log. But soon after, it happened again. I installed only "Explorer" and "What'sapp" when this happened again. I have captured the logs and here it is.
BootLoopLog_Mimicry1.5
And ya I did try and restore a previous backup, and I also tried wiping and installing the ROM, but in both the cases the Phone will hang at the boot animation screen or restart again. Here attached is a log of the phone restarting after a clean wipe and fresh install of the ROM.
BootLoopLog_Mimicry1.5-after reinstall
Code:
Bootloader screen info
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010,15:56:30
Please help me out... this is kind of frustrating.
P.S- I did see that thread.. but since my phone was not bricked, I didnt post it over there..

are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens

demkantor said:
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
Click to expand...
Click to collapse
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..

manujosephv said:
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
Click to expand...
Click to collapse
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..

manujosephv said:
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
Click to expand...
Click to collapse
Guess what... That worked... My phones been running without bootloop till now.. :good:
Everytime I reboot, my heartbeat increases.. but it comes through smoothly at the end.. thanks a lot..
P.S - Completely off the topic.. Mimicry ROM is giving me insane battery life.. Running the phone more than 1 day without charging.. :laugh: