Develop Bugs

Problem In Flashing PARANOIDANDROID

Hi Guys! I've got a problem in flashing PARANOIDANDROID ROM Port by Yasir.
Every time I try to install the ROM i get this error after few minutes:
Creating symlinks
Symlink: some symlinks failed
E: Error in /sdcard/PARANOID... .zip
(Status 7)
Installation aborted.
I'm using latest 4EXT touch recovery, JellyHboot as recommended, already tried with full wipe, SD format ( also EXT etc...);
I thought it could be a bad download so downloaded again and got same error.. The strange thing is that I get this error ONLY when i try to flash PARANOID ROM.. With the other AOSP (CM9, 10) , SENSE ROM i don't get any error, just flash fine... so, what can I do!?
Thanks in advance and sorry for my bad english!

that happened to me the first time, all i did was after wipe/factory reset, wipe cache + dalvik then format all partitions except sdcard n it worked. strange coz i do that anyway but with that rom i had to do it twice.
Sent from my HTC Desire

jmcclue said:
that happened to me the first time, all i did was after wipe/factory reset, wipe cache + dalvik then format all partitions except sdcard n it worked. strange coz i do that anyway but with that rom i had to do it twice.
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for your reply Jmcclue ! I've done a factory reset, wipe cache, Dalvik etc (like every time I flash a ROM) but nothing! It just seems that this ROM has some problems with me Jokes apart the strange thing is that when Yasir released PARANOID v1 I've installed it without problems but now with v3 got this problem.. I also tried to flash it on Stock Hboot, just for try..nothing! Really strange.. By the way thanks again!

Mat08.cc said:
Thanks for your reply Jmcclue ! I've done a factory reset, wipe cache, Dalvik etc (like every time I flash a ROM) but nothing! It just seems that this ROM has some problems with me Jokes apart the strange thing is that when Yasir released PARANOID v1 I've installed it without problems but now with v3 got this problem.. I also tried to flash it on Stock Hboot, just for try..nothing! Really strange.. By the way thanks again!
Click to expand...
Click to collapse
you r correct. download the "mirror" of v3. i checked md5sum and its correct and i just installed no probs.

jmcclue said:
you r correct. download the "mirror" of v3. i checked md5sum and its correct and i just installed no probs.
Click to expand...
Click to collapse
Finally I've got it! Wiped everything about 10 times lol but in the end.... I've flashed the one from the mirror as You said! Thanks man!

I've managed to install this rom. It works well (smooth and fast). But I am unable to install all my apps due to memory space problem. I managed to install about 10 apps only.
Anybody has a good idea on how i could install most if not all of my apps?
The rom is good, dont want to revert to my previous rom.
Thank you in advance.

absurd21 said:
I've managed to install this rom. It works well (smooth and fast). But I am unable to install all my apps due to memory space problem. I managed to install about 10 apps only.
Anybody has a good idea on how i could install most if not all of my apps?
The rom is good, dont want to revert to my previous rom.
Thank you in advance.
Click to expand...
Click to collapse
go to desire android development and read the thread of this rom and go to the last post
Sent from my HTC Desire

jmcclue said:
go to desire android development and read the thread of this rom and go to the last post
Sent from my HTC Desire
Click to expand...
Click to collapse
By the way thanks.This was solved already by int2sd, but i had no time to get back to this.
Good day.

Hey guys. I'm trying to flash PARANOIDANDROID v3.00+ and having exact same problem. wiped & formatted more than 10 times! no salvation so far! Is there any absolute solution?
P.S: I downloaded the Rom from "goo" instead of "mega" (having problems with this host). here is the "goo" post:
http://forum.xda-developers.com/showthread.php?t=2131790&page=19

mb88_peace said:
Hey guys. I'm trying to flash PARANOIDANDROID v3.00+ and having exact same problem. wiped & formatted more than 10 times! no salvation so far! Is there any absolute solution?
P.S: I downloaded the Rom from "goo" instead of "mega" (having problems with this host). here is the "goo" post:
http://forum.xda-developers.com/showthread.php?t=2131790&page=19
Click to expand...
Click to collapse
Make sure ur on stock hboot, format all partitions except sdcard twice, reboot recovery, flash rom, flash gapps, reboot, open terminal emulator n type "a2sd install" grant permissions then type "y" "n" "y"
Sent from my HTC Desire
RSK Sattelite SuperSense4.1

[Q] problems installing Revolution HD 14.2

after performing superwipe in recovery i get everything okay but then when i try to open ARHD 14.2.zip it gives an error just saying - (bad). what does it mean? what should i do to resolve it?

morfey_ua said:
after performing superwipe in recovery i get everything okay but then when i try to open ARHD 14.2.zip it gives an error just saying - (bad). what does it mean? what should i do to resolve it?
Click to expand...
Click to collapse
Redownload the ROM, place that on the SD Card from recovery and then try to flash that.
In Recovery go to Advanced (I think), then Mount SD Card, make sure you Unmount it after the file transfer.
Should help I think. Let me know how you get on.

Yes it solved the issue! thank you! such a small thing caused so much problems! incredible! double super wipe even crashed my CWM!

morfey_ua said:
Yes it solved the issue! thank you! such a small thing caused so much problems! incredible! double super wipe even crashed my CWM!
Click to expand...
Click to collapse
The ROM may not have downloaded 100% or something may have glitched, glad it's solved for you.

[Q] CM10 Stable - Completely Unstable and Broken

Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.

Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip

Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium

Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.

dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?

Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.

You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.

i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset

If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...

goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.

BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.

Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).

goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.

Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works

wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.

Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end

wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?

Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.

Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway

CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?

You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"

CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.

Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.

A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!

Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?

cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't

So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.

Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).

So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!

cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.

Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?

Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

[PROBLEM][SOLVED!] CWM, TWRP and LEWA Recoveries not booting into system

I've been working around with my device. And created a custom ROM a while back. So I finally decided to test it and here's when the problem occured:
I was on v11 something, when I flashed CWM 6.0.28 and tested it. It booted alright, wiped things and then when I chose the option, reboot into system, it did so without any problems. Then I upgraded to v1.1.2.2 and reflashed CWM but this time the 6.0.48 version. It worked fine too. But then, when I chose to reboot into system, the screen froze. I had no choice but to pull out the battery and reboot it.
I tried and flashed Lewa Recovery as well as TWRP Recovery. Same thing happens. As soon as I choose Reboot--> System, the screen freezes.
I was hoping any of the professional devs look into this and find a cause,
FYI I'm on Null Kernel for 4.1.2, running Stock ROM with G-Apps.
Any help would be appreciated!
SOLUTION! :
Download the recovery in the attachments. It's Lewa Recovery. Flash it. It works like any other recovery.
Flash zips, create backups and when you are done, Just Click on Reboot. But DO NOT click on system. Instead choose Download. You will boot right back into system.
So no more pulling out covers. Cause it can seriously lose the cover. Enjoy devs.

all custom recovery currently got problem with freezing when choosing to reboot into system, reboot recovery or poweroff.
its a bug in the recoveries.

mdfzhi said:
all custom recovery currently got problem with freezing when choosing to reboot into system, reboot recovery or poweroff.
its a bug in the recoveries.
Click to expand...
Click to collapse
Then how do we get past it? Is there a way to reboot into system without having to pull out the battery? How do you guys do it?

no other way except pulling out battery.

mdfzhi said:
no other way except pulling out battery.
Click to expand...
Click to collapse
So, shouldn't you guys work on fixing these issues in the recovery? I'm afraid the back cover of my Nokia X would become loose.

yes someone should look into but its not going to be me. whole cm repo is too much for my slow internet speed to sync.

mdfzhi said:
yes someone should look into but its not going to be me. whole cm repo is too much for my slow internet speed to sync.
Click to expand...
Click to collapse
Man, why not you start cm11 for us?

mdfzhi said:
yes someone should look into but its not going to be me. whole cm repo is too much for my slow internet speed to sync.
Click to expand...
Click to collapse
Yo! I found the solution. Check out the thread again.

Dom3616 said:
Yo! I found the solution. Check out the thread again.
Click to expand...
Click to collapse
dont understand

sumondhk1 said:
dont understand
Click to expand...
Click to collapse
See again.

Dom3616 said:
See again.
Click to expand...
Click to collapse
Thanks for thr solution but I am already using it and it is much better than others.
When I press reboot system, it takes sometime but after all it boots.
Now gonna try your method.

Lewa recovery can't mount usb storage. At least for me it can't.

mdfzhi said:
Lewa recovery can't mount usb storage. At least for me it can't.
Click to expand...
Click to collapse
Yes, but I copy the files before I boot the recovery.

I Would never Suggest Lewa For anyone ! It is smooth...cool .... good
But you will get bored of those frogs instead of smilies...
I Really Hated the Lewa Recovery too...
Made my Dead...In SERVICE Center gonna get it back on 13th...i'll sell it to buy XL
I Will never install Lewa on it...I Will do install TWRP On it...And thn flash dhacker29's AOSP Rom...(Altough i love S5 Minirom...but i've heard buttons and camcorder doesn't work on it...It completely Works on X....Just gonna wait Hope he fix it before 13th )

Dom3616 said:
See again.
Click to expand...
Click to collapse
i don't have any problem about booting to system with my nokia XL

Dom3616 said:
I've been working around with my device. And created a custom ROM a while back. So I finally decided to test it and here's when the problem occured:
I was on v11 something, when I flashed CWM 6.0.28 and tested it. It booted alright, wiped things and then when I chose the option, reboot into system, it did so without any problems. Then I upgraded to v1.1.2.2 and reflashed CWM but this time the 6.0.48 version. It worked fine too. But then, when I chose to reboot into system, the screen froze. I had no choice but to pull out the battery and reboot it.
I tried and flashed Lewa Recovery as well as TWRP Recovery. Same thing happens. As soon as I choose Reboot--> System, the screen freezes.
I was hoping any of the professional devs look into this and find a cause,
FYI I'm on Null Kernel for 4.1.2, running Stock ROM with G-Apps.
Any help would be appreciated!
Click to expand...
Click to collapse
I was also facing this problem. but now I am doing one thing,after flashed all I need,I clear the dalvik cache.Then click the reboot and its rebooted the system smoothly.No freez screen.Hope it will help others..
I am using CWM 6.0.28 recovery and stock rom.