Database Develop

unable to install any rom

There is some problem in my phone i m only able to install rom which is less than 68mb and and whenever i install cyanogen rom gapps wont install currently i am using stock rom so plz help i want to install cyanogen's 6.1 thanks

Stock ROM isn't less than 68MB. It's ~70-80MB.

Jack_R1 said:
Stock ROM isn't less than 68MB. It's ~70-80MB.
Click to expand...
Click to collapse
lol ok 70 mb but how do i fix this, should i give it to htc for repair?????

What makes you think you have this problem? Can you provide details?
Sent from my Nexus One using XDA App

when i try to install these are the follwing errors:
enoms:set_perm_recursive 0 2000 0755 0755
Can't chown/mod /system/xbin error
cyanogenmod 6:after flashing rom and gapps i wont wont get gapps there will be no youtube no market no gmail&chat.
eViL's NXSense HD v.0.8:unable to flash i forgot the error
RoDrIgUeZsTyLe CM6 Final LimeMOD R5:flashes properly after a reboot i dont get that usuall green cyanogen boot screen, I dont know how now i get android writted in bold letters and its blinking and after that i get google setup wizard then soft and hard keys are not responsive and keyboard wont allow me to numbers neither dial pad works.
Kang-o-rama-1.0-b2:same as above
MicroMod v2.8.0 :flashes but does not boot.
LeoFroYo 2.0.0:working properly but its outdated
stock frg83 works
tried flashing with both recoveries amon's 1.7.0.1, 1.9 and clockwork mods recovery 2.5.1.0.i even did try installing from rom manager no luck
i even changed the radio and tried now its Korean OTA 32.50.00.32U_5.12.00.08.
i did wipe cache and cache sd ext everything properly
is there another way to install rom or what should i do to fix this error i m really frustrated now i dont know what to do please help thanks:mad

Did you wipe?
Sent from my Nexus One using XDA App

danger-rat said:
Did you wipe?
Yes I did with both the recoveries
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App

Interesting...
What did you wipe, and how?
Sent from my Nexus One using XDA App

I wiped from recovery wipe data and cache wipe dalvik cache and wipe sd ext.I hope so this is the meathod to wipe
Sent from my Nexus One using XDA App

Yup, that should've done it.
Not sure what is going on, all I can suggest a factory reset, or revert to stock and start again...
Sent from my Nexus One using XDA App

factory reset as in stock recovery and and stock rom?

That's about all I can suggest. You can back up before, and you can always root again...
Or wait for some other advice, I'm sure there's better ideas floating around, and honestly, I've never heard of this issue before...
Sent from my Nexus One using XDA App

So do I never heard or read about this kind of problem
Sent from my Nexus One using XDA App

i prefer u format ur sdcard on the pc, i have feeling saying this from the sdcard. Try and let us know

finally some reply some hope yea even i thought some thing must be wrong with the partition or the sd card.So i had a spare 2 gb nokia class 2 sd card i formatted it and tried flashing cyanogen 6.1.0 it flashed but againg the same problem Gapps are not installing soo i tried Gapps-Mdpi-tiny-20101020-signed and i got market and youtube but still its not a permanent fix so please suggest what should i do i m completly frustated .....

[Q] bootloops after flashing rom

I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.

nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.

I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app

nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One

Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium

Unfortunately, I've tried flashing manually via recovery too...still bootloops

Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium

yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.

Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium

I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?

I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium

well, did a factory reset last night but i'm still having the same problem. I'm at a loss.

[Q] 10.2 failed. Phone switched off

Hi,
I was using cynogenmmod 10.1 nightly, today i updated it to 10.2 through manual update under about phone option in setting and installed it.
I downloaded gapps for 10.2 and wanted to install it.
Later i tried to get into recovery mode through vol up+power+home but i was not able to get into recovery mode and screen was black.
Then i started my phone and manually updated to 10.1 which i downloaded earlier through about phone-update option and phone updated and after reboot was not starting.
Now my phone is not getting into recovery mode and neither it is starting.
Kindly help.

Can you get into download mode?
Sent from my GT-N7000 using XDA Premium 4 mobile app

M able to get into download mode. I flashed it with N7000DDLSC_N7000ODDLSC_INU.zip
But phone is only showing samsung start screen and not moving ahead.
Kindly help

Flash a three file stock rom.

Thanks. Kindly provide link for the same of stock rom.
Also let me know which is better and stable custom rom which i like to upgrade after flashing with the stock rom.

Dr Ketan's thread has all the older 3 part roms, and we don't do best roms, just try them all and decide for yourself
Sent from my GT-N7000 using XDA Premium 4 mobile app

Get into download mode and flash some kernel via odin, so the cwm is flashed.
Then enter recovery, wipe data, system and flash your rom
Sent from my GT-N7000 using xda app-developers app

I am able to get into recovery mode through vol ip+home+power key
Can i install PhilZ-cwm6-DDLSC-ODD-5.08.5-signed (which is kernel i think)
then ill update in recovery mode with cm-10.1-20130727-NIGHTLY-n7000.
Will the above method will solve my problem?? Kindly reply at earliest.

The method mentioned in my previous is not working.
Help me with a link where i get how to update kernel and plz help me to start my phone.
M getting mad!!!

deep-j4u said:
The method mentioned in my previous is not working.
Help me with a link where i get how to update kernel and plz help me to start my phone.
M getting mad!!!
Click to expand...
Click to collapse
Are You wiping Your data and formatting system before installing new ROM? That's quite important, or it won't boot

Thanks everyone for your support. I have deleted all data and installed 10.2 with new gapps.
Once again thanks!!!

deep-j4u said:
Thanks everyone for your support. I have deleted all data and installed 10.2 with new gapps.
Once again thanks!!!
Click to expand...
Click to collapse
Yep, always wipe Your data changing to other structure of ROM. And sometimes also system...

Thanks for the help buddy.
Also when we change version we should wipe cache but in same version when we update through about phone option that time cache wiping is necessary??
Where I can get themes for 10.2 CyanogenMod?

try search for HoloGlass Theme beta.. quite interesting for me..
Sent from my GT-N7000 using xda premium

[Solved] Recoveries not really working on CWM

Hi everyone!
I'm still a newbie arround here, so i will have to tell you all the steps i did until i got the problem.
So i did the following: I have stock rom (4.0.4) and BaseBand, i've rooted the phone using NVFlash method (using All-in-One Toolkit by SpyrosK) and i've replaced the Stock ICS BootLoader also using the AIO Toolkit. The phone was working great and all but after some weeks it started getting slow and i though about doing a factory recovery. So I tried the backup normally. Went to the menu then settings> backup and reset> factory data reset. After the reboot the normal LG logo showed and then the following: "Unfortunatly, the process com.android.phone has stopped" and behind this text box it has: "Encryptation unsuccessful
Encryptation was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone, you must perform a factory reset[...]" and it has a reset phone button but i can't acess it because the text window is on top.
After I got this I tough about giving a try to CWM(v6.0.2.5) recovery. So i tried the following: wipe cache partition, wipe cache partition, wipe dalvik cache and fix permissions and tried the reboot but the same problem still persists...
Can anyone help me? This doesn't seem like a brick to me and it was supposed to be a factory reset but isn't correctly working. What can I do to fix this?
Tell me if you have any question or if you need a picture of the screen i get when i boot the phone. Than you very much.
Edit: Already tried to change my recovery image, still have the same problem...Was thinking in installing the stock rom again via CWM. Is it a good ideia? Will it fix?

In CWM there is a factory reset too (something like wipe data/factory reset). That should do the trick (but I'm afraid you'll have to set up from scratch again). Otherwise you'll have to wipe everything (including format /system) and flash the ROM again...
Sent from my LG-P990 using xda app-developers app

oneearleft said:
In CWM there is a factory reset too (something like wipe data/factory reset). That should do the trick (but I'm afraid you'll have to set up from scratch again). Otherwise you'll have to wipe everything (including format /system) and flash the ROM again...
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Tried that wipe data/factory reset too. It did'nt work either. Maybe I'll go for the full wipe and try the stock rom again. Thank you for the help

I am sorry to hear. Why don't you try flashing another ROM, just to test? For example pengus' CM10 equivalent http://forum.xda-developers.com/showthread.php?t=2058231? It is very stable. Remember to update to last Kowalski kernel (by flashing after flash of ROM). May I suggest M1 norh (without ram hack)...
PS You need to be on new bootloader - see instructions in thread. If you have problems with the CM10 camera, you can flash CM10v3 by feav http://forum.xda-developers.com/showthread.php?t=2163473
Sent from my LG-P990 using xda app-developers app

Your partition is corrupt. Please reflash unlocked new Bl.
Thanks
Sent from my LG-P990 using xda app-developers app

Jishnu Sur said:
Your partition is corrupt. Please reflash unlocked new Bl.
Thanks
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Tried that with AIO by SpyrosK . Still didn't work. But thanks for the suggestion!

oneearleft said:
I am sorry to hear. Why don't you try flashing another ROM, just to test? For example pengus' CM10 equivalent http://forum.xda-developers.com/showthread.php?t=2058231? It is very stable. Remember to update to last Kowalski kernel (by flashing after flash of ROM). May I suggest M1 norh (without ram hack)...
PS You need to be on new bootloader - see instructions in thread. If you have problems with the CM10 camera, you can flash CM10v3 by feav http://forum.xda-developers.com/showthread.php?t=2163473
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Because I have no currently back up (coz of neglicence) I'll try a stock rom first. I'll give this a try after the stock rom. Thank you again :good:

Jishnu Sur said:
Your partition is corrupt. Please reflash unlocked new Bl.
Thanks
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Was probably this! When i wrote the reply i tried using the option of replacing the Stock locked to the new one and this did not fixed.
So after i tried the option "Repartition your device with preferred layout and bootloader. Had to get another rom after and got the stock rom again, but i'll give a try to the one oneearleft suggested. Thank you very much. I've learned a lot with this!
Cheerz and keep up the good work!

[Troubleshooting] (CM 10.2) Stuck at boot screen after reboot

Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app

I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?

knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.

SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.

jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason

knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?

No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000

It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?

nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.

I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?

nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.

tried without the external SD card inserted?

nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000

SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?

knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000

SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!

SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..

I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".

So...which Stock Rooted ROM using to flash?...

heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000