Develop Bugs

Jellybean only boot loop

Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?

MARINERMOOSE241 said:
Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?
Click to expand...
Click to collapse
Download the file again. Sounds like a bad flash.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.

MARINERMOOSE241 said:
Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.
Click to expand...
Click to collapse
That's why I recommended downloading again. Sometimes packets are lost in cyberspace. I don't see how your device is the only one doing this. Gotta be something on your end. (Not trying to point fingers. Just saying it can be a million and 2 things )
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.

MARINERMOOSE241 said:
Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.
Click to expand...
Click to collapse
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium

Rememdium said:
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.

MARINERMOOSE241 said:
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.
Click to expand...
Click to collapse
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.

Digital1325 said:
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.
Click to expand...
Click to collapse
No they aren't. Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside

Digital1325 said:
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside
Click to expand...
Click to collapse
I read it on their website but i came across it in binarybishops nightly thread. And no the cache wipe is fixed. I use the touch version, tried TWRP and CWM 5 hell i tried them all! They all produced the exact same results for me as far as performance goes. But ive never had any issues with 6.0.1.1 i love it to death

Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.

MARINERMOOSE241 said:
Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.
Click to expand...
Click to collapse
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.

MARINERMOOSE241 said:
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.
Click to expand...
Click to collapse
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.

elesbb said:
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.
Click to expand...
Click to collapse
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.

MARINERMOOSE241 said:
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.
Click to expand...
Click to collapse
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?

elesbb said:
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?
Click to expand...
Click to collapse
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.

MARINERMOOSE241 said:
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.
Click to expand...
Click to collapse
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Formated the SD card ... used the external adapter to copy the flash to the SD same bootloop I also copied the file directly to internal storage removed the sd card and flashed same result... looks like no Jelly bean for me... so freaking odd as I can flash ICS any rom all day long just fine.

[Q] (status 7) some symlinks failed when installing ROMs.

when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Edit: Thanks for all the help guys. I'm still having this problem.
Things i have tried: go into mounts and remove the top X on the list.(TWRP)
flashing a stock kernel gets me stuck in a boot loop.
I am using the franco kernel and had this same issue using CWM before switching to TWRP.

You can try this...
simms22 said:
try booting out of recovery into the bootloader, then back to recovery to reflash.
Click to expand...
Click to collapse

If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium

qbanlinxx said:
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250

natheist411 said:
when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Click to expand...
Click to collapse
Are you using TWRP recovery? If you are that's the issue. The latest update has a flaw, you have to go into recovery, go into mounts and remove the top X on the list. They said they where working on releasing a correction for it. If your not on TWRP then I don't know what's going on.
Sent from my Galaxy Nexus

I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app

natheist411 said:
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus

I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
bk201doesntexist said:
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda premium

qbanlinxx said:
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have also seen something similar. What most people don't realize is the some kernels, including Franco, change things in /system as well, which messes with some things.
Sent from my Galaxy Nexus using Tapatalk 2

Okay, thanks. I was not aware of this. Will checkout some kernel zips to see what's going on.

edfunkycold said:
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I tried this. Still the same outcome. Thanks anyways.

Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.

Milamber said:
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Click to expand...
Click to collapse
no one here was help but i think i figured it out myself.
try this and see if it works.
when you go to install the rom, before doing so wipe data (factory reset) three times.
i was so frustrated about it i finally said **** it and didnt care if i lost everything, but i didnt loose anything so all is well.
let me know if that works

(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
I'm tryied many recoveryes and kernels, but the problem is in copying process(now all zip's have good CRC, and MD5). . Give me a beer

JeyLo said:
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
Click to expand...
Click to collapse
Huh? What is siyah 5.0b2???

I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.

Milamber said:
Huh? What is siyah 5.0b2???
Click to expand...
Click to collapse
He's on a different device.
Sent from my i9250

chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Wipe/Factory reset does not touch the system partition at all. This is normal. It only wipes the userdata partition.

chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Had a bad download and on initial install I formatted system however it failed. Went back and formatted system and cache manually and worked for me.

I'm not sure if this is related, but I read in the MMuzzy's Jelly Bean 4.2.1 thread (http://forum.xda-developers.com/showthread.php?t=1762846, first post specifically) that unmounting /system fixes this problem, and sure enough it solved the problem for me when I tried to flash that ROM.

Why is this happening to my Gnexus?

Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.

I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD

Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.

4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway

nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..

crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2

Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app

plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens

Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!

lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.

Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related

Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.

Alright will do as suggested

How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!

update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.

nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..

Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far

So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.

Phone won't boot into recovery?

Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium

eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.

EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium

Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium

eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.

Nothing wrong with CWM.

Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)

The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.

Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.

OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium

eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.

EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium

eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.

EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium

eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?

EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium

(Q) Been Gone For Some Time...???

I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?

XxLostSoulxX said:
I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
Click to expand...
Click to collapse
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium

LuigiBull23 said:
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working

XxLostSoulxX said:
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
Click to expand...
Click to collapse
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium

LuigiBull23 said:
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there

XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Click to expand...
Click to collapse
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium

LuigiBull23 said:
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file

XxLostSoulxX said:
Click to expand...
Click to collapse
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
XxLostSoulxX said:
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file
Click to expand...
Click to collapse
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium

LuigiBull23 said:
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.

XxLostSoulxX said:
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
Click to expand...
Click to collapse
No AOSP ROMs at all? I would go back to complete stock, update to MA7 or MC2 then reroot and try flashing again.
Sent from my Nexus 4 using xda premium

XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
Click to expand...
Click to collapse
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.

Skripka said:
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Click to expand...
Click to collapse
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation

XxLostSoulxX said:
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
Click to expand...
Click to collapse
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.

Skripka said:
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Click to expand...
Click to collapse
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check

okay i used Toolkit 4.1.0 and chose to flash to stock and it didnt work because i still have root and still on ljc, and same setup as before, i cant update to ma7, however i chose to install stock recovery, but i know if i do update it will fail.
EDIT: **** it wont even reboot to install the update. says rebooting now and nothing. F THIS PHONE.
I CANT EVEN UNROOT

XxLostSoulxX said:
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
Click to expand...
Click to collapse
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium

LuigiBull23 said:
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.

XxLostSoulxX said:
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
Click to expand...
Click to collapse
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium

LuigiBull23 said:
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
correct yeah because i restored so i can atleast use my phone to try to fix it using toolkit
EDIT: Hooray i finally got it that did the trick this time. however basband is still LJC but is 4.2.2 because i went through setup this time and was able to boot up