Develop Bugs

CM7 problems?

I'm making this thread to try and solve issues and problems with cm7 for problems that you can probably solve instead of posting 10 times and making a repeated question in the official thread of cm7 development thread
If you have any issues we can help each other, to start with I got the blue then green light on my first restart, but after wiping data and cache AGAIN (I already did it before installing from zip) it worked!
I had problems with the notification widgets, but after a few restarts it didn't dissapeared. So that problem solved by itself
I currently have the flash notification widget not working (and it works on camera but not on video recording) I don't know if it is a common problem from the beta 3 version (If someone knows I would be thankfull***) but meanwhile you can get the flash to work with this widget https://market.android.com/details?id=com.advback.ledflashlight&feature=search_result
The Wifi is working OK but it seems like the refreshing time of signal is too low (I get close to the wifi router and maybe there are 1min. until the small widget at the top fills up) and viceversa I get away from signal and it is remained full until 1 min or so.
edit:
For Gps small fix you can find in the page 123 this from AkkiandDefy:
1.Search FasterFix in the market and install!
2.Open it and choose your region the
3.Now theprogramm will install the right Config
4.And then install GpsFix and let him search
Don't be afraid..let him search longer(till he tell the right adress). Once fixed he will find it always faster.
Admin or mods if there is any problem with my thread let me know, I'm just trying to help

good Idea

just trying to help hehe my idea is to get the important information in the first post just done the flashing of the test2 for gps going to try right now

I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
EDIT: OK, so I tried another data/cache wipe and installing CM7 again as update.zip, but have to use the default bootloader now and it says "signature verification failed". :S

did you instal the nordic version? 3.4.3 11 (the last one) flash this, then install superuser (with superoneclick) afterwards instal the clockwork (I used the same one as you) then wipe data, cache install beta 3, gapps and gps test 2 and reboot it should work

Viridis said:
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
I had the same error - i reflashed the 3.4.3.11 sbf with rsd lite
after that, rooted , instaled clockworkrecovery and booted into recovery mode to instal CM7
After installing CM7, i allowed to boot itself (2init is set on automatic) then just reboot and enter into custom recovery via pressing vol down right after blue notification light appears - frome here you can acces custom recovery and install addons like gapps and gps fix.
Warning - entering from Clockwork recovery after CM7 installed will get you in bootloop and need to reflash the main sbf again.
Click to expand...
Click to collapse

really? I think I did it and it didn't happen that, but anyway my recomendation for those we don't know so much is to install from clockwork the beta, gapps and any fixes (gps etc) at the same time without rebooting so we don't have to use it anymore (in this logical order, 'cause maybe it doesn't mind but maybe it can prevent us from getting any error)

Thanks for the replies everyone.
Right now I've flashed 3.4.3.11 on with RSD Lite, that went fine. I've rooted with Superoneclick and installed the custom recovery app from before, and I can get into Clockwork recovery with that.
Now though when I try to do a wipe it says "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!". I took out my SD card and formatted and partitioned it with 500mb ext, 50mb linux swap and around 1.5GB FAT to see if that would help, but it hasn't. I did this with my PC, however I did use the one on the recovery before that, which was probably a bad idea. I didn't think to much of it since it should have only affected the SD card.
I think now I need to use ADB or something to fix this, I've also unrooted and rooted again. I also tried installing cyanogenmod before the mount errors when only an "app2sd" error was coming up on the wipe, but it didn't actually do anything, it just started up with the stock 2.2 froyo again.
EDIT: I tried just wiping and installing cyanogenmod.zip and gapps.zip anyway, but it just comes reboots with stock blur/froyo. I don't have any "update.zip"s or anything.

try wipe from stock. do: vol down + power and then when the ! appears with the android guy press vol down + vol up
afterwards you will get stuck in the moto logo. get out the battery, put it again and flash the nordic version 3.4.3 11 then enable adb and with superoneclick install root
IMPORTANT: NOW GET OUT ADB AND REBOOT
after reboot install clockwork and get the beta 4 and gapps into the sdcard,
then wipe data and wipe cache
install from zip first beta then gapps (if an error of line X appears and says installation aborted just try again it will work, happened to me several times) and reboot!

Hey, thanks for the thread.
I have a problem with FasterFix. Mine asks for root permission but it just won't load. Remains in black screen and does nothing. GPSFix opens, but don't sync.
Any ideas?
@Quarx
Thank you for the CM7 mod, I'm loving it.
Will post it to the original forum post once I'm able to.
And will buy you a beer

you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!

mariosanoguera said:
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
Click to expand...
Click to collapse
I hope someone post this on the main thread.

I just applied the *.zip(s) and the am loading in for setup, it seems to be working so far. The boot screen is AWESOME as always... setup seems a bit twitchy but hopefully I'll get it to work here soon. *crossed fingers*

I think Im starting to have the earphone piece problem

Quarx posted another version to the main thread. Downloading now. Seems like it doesn't need to wipe. Lets see...
It seems a little buggy for those who have green lens. I'm waiting with 4.0.

Can I delete this post?

Problems to edit the contacts
Hello.
I've had problems to edit the contacts, in my phone book.
I syncronized my contacs with the Facebook contacts. Have all of then in my contact list, but when i need to add a phone number to the contact, it says that i can't edit Facebook contacts in that device. I need to create a new contact and put the phone number in that new one, and that pisses me cause i will need to have 2 contact from 1 person, duplicating my entire contact list. And all my contat that are in my SIM card don't show in the MOD. I have downgraded and all the contacts now have reapered.
Please, if someone knows how to help, since i was using the Blur, and had all my contacts from Facebook before, editing and merging then when they are duplicated.

It seems like the camera is not THAT working. When I zoom in too much it crashes and I lose access to the camera.
Is Quarx even knowing about this thread?
Edit: I was listening to a song in PowerAmp, opened an YouTube video and all sounds gone, some process forced close and no sound was played until restarted.
Edit2: it seems like that DSPmanager forced close when YouTube opened. Disabled for now.

I've updated to beta4 and the only issue I have is with GPS. Just tested camera, video and flash and all working.
Edit: also issue with video playback... it jumps.
Sent from my MB525 using XDA App

I can't play any videos at all. Guess I'll be back to froyo till this is fixed.
Sent from my MB525 using XDA App

[Q] Updating Android Revolution HD

Hi,
I am currently running Android Revolution HD 5.1.7 on my DHD
I was just wondering with the new 6.1.1 version out, to upgrade to it,
do I simply download the file and just flash that to the device or must I first wipe my device? Or some other way?
Thanks for any help!
P.s Really sorry if this has already been asked but I had a quick search and couldn't see anything to this specific situation!

Back up all your data then flash the superwipe script, then flash the ROM, restore data
Sent from my HTC Desire HD using Tapatalk

Thanks alot,
Also once I have flashed the rom to the phone,
Can I remove the file from my SD Card to free up some space?
Its something I have been unsure about from the first time I flashed my phone,
But I should imagine you can??
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!

Razza12003 said:
Can I remove the file from my SD Card to free up some space?
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Click to expand...
Click to collapse
1. You can but I would recommend that you keep a copy of a stable ROM on your sd card just in case you have to reinstall for some reason.
2. It seems like the ROM is corrupted.
Did you superwipe before you installed the ROM?
If you have:Check the md5 checksum of the rom you downloaded. It should be the same as the one posted under the ROM download link in the ARHD thread. If its the same you can try superwiping and reinstalling the rom.
If you havent: Download the superwipe script from the first page in the ARHD thread, superwipe and reinstall the ROM.
Also make sure to backup your phone data before superwiping because everything will be lost. Also don't install any mods untill your device has completed the first boot after installing the ROM.

to be honest i had issues with arhd 6.1.1 when i flashed it too. not the same as yours but constant. not everybody seems to have them though and others say it has something to do with the overclock daemon. i believe there´s a patch for it though on the 6.1.1 developers thread.
i didnt bother though i just moved on to virtuous unity 2.39 and have had no problems, really smooth sense 3.0 rom. i´ve been planning to try out a non sense rom next but i really like this rom so i´ve been putting it off for a while now. i even put the beats audio patch on it a few days ago and i gotta say its pretty good even on stock htc headphones

planing to update to arhd6.1.1 too, but have ardh3.3 and clockwork 3.0.0.6. which clockwork is ok (mean which of the newest)?

I did use superwipe and i checked the md5 and it was all good!
I re-flashed the rom and now its ok
I have found out what was causing it!
It starts happening again every time I install google+ 2.0
The new version of the app that has recently been leaked on androidpolice
(Would include a link but im not allowed yet)
And the reason it did it straight from the start the first time is because, before
doing anything else, I restored all my app via Titanium Backup!
If anyone else has this issue or could try to install the app and see if it happens
to them or could figure out how to fix it, it would be great!
(Don't worry about installing it, uninstalling it stop the force closes straight away)

did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems

Lewelynn said:
Also make sure to backup your phone data before superwiping because everything will be lost.
Click to expand...
Click to collapse
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?

ponk2k said:
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Click to expand...
Click to collapse
Yes i tried restoring just the app, that caused fc's too!
As did re-downloading the app!
jms-xda said:
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
Click to expand...
Click to collapse
Superwipe doesn't effect the radio, and yeah that order you said is the way I went about it, but I also think you can do radio before rom too!

Update from 5.1 to 6.1
Maybe I haven't looked hard enough or maybe I am simply too tired...
Are there any specific steps from updating ARHD from 5.1 to 6.1? I can't seem to find any info about it.
Also, flashing the 6.1 over the 5.1 will it reset the way my screens/widgets are set while on 5.1?
Thanks.

[Q]Desire Z keeps rebooting after few seconds on home screen

Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you

cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App

could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.

+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd

cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App

I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.

I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.

well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far

Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon

Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve

Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve

the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.

Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve

I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium

Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve

Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve

Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium

Virus???? Idk but phone is messed up

Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.

not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.

tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.

if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.

When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.

tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far

PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off

im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)

maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!

tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.

when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before

i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.

tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work

Can't solve this problem, curious to understand

Hello to all, I am asking for some help and advices and I think this might be an interesting problem for some of you. I can't really explain it very well, but I will try to provide as much info as I can, so let's start. Since the past 20 days, I have tried Mokee 5.1.1 Release after trying Resssurection as my first Lollipop experience and I liked it, it was stable, fluid and different. I had some bugs and issues with Ressurection which I couldn't accept, so Mokee surprised me nicely. So I arranged it all up, everything that I need and didn't face any bug or even crash for about 10 days or more. So one day I was upgrading or something like that and wiped dalvik cache and cache with TWRP 2.8.7.0. After flashing, there was that app optimization process which is normal, and after that the phone wasn't booting. It would show my wallpaper and background material for a moment or 2-3 seconds max and then rebooting again and again. So I have restored the nandroid backup and it was fine. I guess if I can remember well that I was using that backup for about a few hours and it was fine and then I did something and it couldn't reboot again and my background was blinking. So I was messing with all of that and decided to try CM12.1 R15 and Ressurection 5.3.4 i think. After wiping everything except external SD of course and flashing it, everything was fine while setting it up and restoring my apps and data. And then after some time I wiped dalvik cache and cache, for some reason I had to do it, probably to flash xcelerate kernel and boot image before it and then again the phone couldn't reboot with background blinking, so it's the same problem. But now it's even worse, when I make a nandroid backup, I can't restore it, it won't reboot which means the problem is present all the time. So I tried this :
1. Wiping everything except external SD and flashing the same or a different Rom works, but the problem appears again sooner or later after setting the ROM and apps. The last thing I tried is to wipe dalvik and other catches and rebooting few times after flashing fresh ROM without setting it up or doing anything, and everything was fine, phone rebooted every time. I am confused because I am pretty sure that the problem appeared for the first time after wiping catches and rebooting and then just remained.
2. I have tried to repair system in TWRP, didn't work. Tried wiping only system partition and catches, didn't work. So it doesn't work by wiping system, but it works after a fresh flash of a ROM. Now for the few days I am using Mokee without xcelerate and other kernels, so I guess it's not because of a kernel, which I used before when it started for the first time. I have also tried to boot without SD card, didn't work. Every time the background blinks for a few times and then it reboots from a Mokee logo, and again, and again, always the same process.
Some apps that I am using which I gave a root acess : System Tuner ( Using it only for Freezing things that I don't need, deleting things that I really don't need, managing startups, backing only apps without data and clearing cache ). For appdata I use Helium and it works every time, great program. I am 99% sure that I am not doing anything wrong with system tuner, I know what to freeze and what to delete and what to startup. And after all of that, the problem doesn't appear and appears mostly if I remember correctly after wiping Dalvik and catches. Other apps with root acess are greenify, ES file explorer, xbooster which I rarely use and maybe 1 or 2 other apps which I always use. Before I used Chainfire's SuperSU and Stericsson's Busybox too and everything was working very well till the problem appeared for some reason. I don't use xposed framework on lollipop yet if it matters. And another thing, for wallpaper I use some picture with 1600x1200 resolution or similar, but it's bigger than 1270x720. Can that be a problem ?
So, I apologize for such a long and repetitive text hehe, I am just asking what do you think why is this happening ? Should I flash a fastboot rom with MiFlash, will that fix it ? will I be able after doing that to install Mokee or another 5.1.1 rom with all my apps and settings without facing this again ? TWRP is 2.8.7.0., is this version stable enough, is that a source of a problem ?
Whatever answer I get, thanks in advance and cheers !

Hi again, I have realized what caused all of this trouble, it's a bit unusual. After flashing the stock rom via MiFlash and doing everything else, it was clear. It was all because of Apex launcher, without a custom theme. It seems that Apex was compatible with some older version of Mokee and other LP roms, but those last few updates couldn't support it anymore. Too bad, I really liked Apex, it was very practical for me with a lot of options to use, while being lightweight. Now I need to find another launcher which can offer me similar experience till Apex is updated if ever, but I am a bit sceptic. The thread can be closed, thank you.