Hi, i'm new on this thread, today i get this from my brother with Android 2.1 and he ask me for and update to 4.3 or 4.4.
Using this tutorial i install success 4.0,
https://www.youtube.com/watch?v=rqxearzXrVY
and using this rom update to 4.4
http://forum.xda-developers.com/showthread.php?t=2535547
to this point all well...but i get the error about Invalid IMEI....i back to 2.1, backup efs, update againt to 4.0.
Now when i try install 4.4, the CWM can't install 4.4. I try many roms but it's the same problem...
When try install 4.4:
----------------------------Try 1----------------------------
1.Clean chache partition......OK
2.Clean dalvik-cache............OK
3.Istall ROM...........................Error Status 0....or Error Status 7
----------------------------Try 2----------------------------
1.Clean chache partition......OK
2.Clean dalvik-cache............OK
3.Format /system..................OK
4.Install ROM.........................Reboot -> CWM -> reboot -> CWM (BOOTLOOP)
----------------------------Try 3----------------------------
1.Clean chache partition......OK
2.Clean dalvik-cache............OK
3.Format /system..................OK
4.Restore CWM backup......Reboot -> CWM -> reboot -> CWM (BOOTLOOP)
when i get a BOOTLOOP whit this kernel
http://forum.xda-developers.com/showthread.php?t=2330998
and the option "AROMA", check the /SYSTEM and this is empty (0 files)
I never had a similar problem. Help me please :crying:. Any idea
Solved
solved, only format all directories including boot.
ZeroDrako said:
solved, only format all directories including boot.
Click to expand...
Click to collapse
I'm having similiar problems. How do you 'format' all directories?
Jut Flash this kernel GearKernel - Universal
-Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
Then go to mounts and storage and format all directories....except the sdcard
that's all....
Related
i dont know much about roms i wanted to install miui rom i downloaded it from offical site and in cwm i selected miui rom and complete then i selected restart it stucked first screen and it automatically restart again and again why i couldnt install do you have an idea please help me !!!
http://forum.xda-developers.com/showthread.php?t=1130951
WARNING!!! USE IT AT YOUR OWN RISK!
nstall instructions:
- Reboot to CWM
- if you are coming from other rom (full wipe): wipe /system, /cache, /data and Dalvik-cache
- upgrade: wipe /system
- install zip from SD-card, select MIUI-1.X.X-beta.zip
jje
Hi all,
for now I'm still on a GS2, but I am considering buying a GNote your rom and I like a lot. So I plan to install it on my S2 to go to.
A question: I am in CM9 for now, with your rom (which is based on CM9) can I do the update with the available Nightly of CM9 ?
Or maybe I did not understand (which should not wonder ) and it can not work like that?
Thank you in advance for the answer.
If you are on PARANOIDANDROID v1.0 and update to a nightly from CM9. You will then be on CM9 not PARANOIDANDROID.
Even tho it is based on CM9 it is two different things.
Updates that get put in to CM9 nightlys will be put in to PARANOIDANDROID when they want and their rom will be updated, so will there thread and the OTA updater.
To sum up, if you flash a CM9 Nightly then you will lose your PARANOIDANDROID rom.
Also make sure you use the extended steps to install a new rom.
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
1.Reboot into recovery
2.Wipe Data / Factory Reset
3.Wipe Cache Partition
4.Install the Main ROM
5.In recovery go to Advanced
6.Wipe Dalvik Cache
7.Fix Permissions
8.Wipe Cache Partition
9.Reboot
10.If at the first boot you can't do the configuration of the google account, skip this step and continue
11.When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
12.When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
13.This is the moment for install all the extras like themes, fix's, kernels, etc.
14.Enjoy!!!
Thank's all.
Still Confused....
dwightvanbentem said:
Also make sure you use the extended steps to install a new rom.
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
1.Reboot into recovery
2.Wipe Data / Factory Reset
3.Wipe Cache Partition
4.Install the Main ROM
5.In recovery go to Advanced
6.Wipe Dalvik Cache
7.Fix Permissions
8.Wipe Cache Partition
9.Reboot
10.If at the first boot you can't do the configuration of the google account, skip this step and continue
11.When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
12.When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
13.This is the moment for install all the extras like themes, fix's, kernels, etc.
14.Enjoy!!!
Click to expand...
Click to collapse
I have rooted my GT N7000 with Stock ICS ROM from SAMSUNG [India]
BaseBand Version : N7000DDLP4
Kernel : 3.0.15-N7000DDLP8
How do I go about?
Do I need to first downgrade it to GB Stock India
N7000DDLC1---------2.3.6---------2012 March---------N7000ODDLC1-----------India--------------------------------------
OR
Do I downgrade it to SGN_XX_OXA_KJ1_FACTORYFS ???
please guide what to do...
Issue installing
http://forum.xda-developers.com/showthread.php?t=1729331&fb_source=message
Can someone help me. Tried to post a question in that post itself but need to have 10 comments or something.
Anyways, followed the following instruction which said to (i think)
boot into cwm
wipe data/factory reset
wipe cache partition
wipe dalvik cache
then i tried to install the file that i get from mediafire using install zip from sdcard
Find the file (in the download folder is where i saved it) but as soon as it starts to install it, stops ..calling out to an error (something 7)
Could someone see if i did it correctly or there is some other issue?
Currently running broodrom rc5
Hey, I am installing a custom ROM (Omega V43.3) through Mobile Odin Pro and during installation when it's copying selected files it froze on PolarisViewer for some reason! Now I have no idea what to do, it has been frozen for 15min!
The omega installar has already: wiped preload, dalvik cache, cache, formated system, copied system files,and is now on copying selected files.
Any ideas?
Update: Rebooted and landed in Android system recovery <3e>
you mean you dont have CWM recovery?
emil2394 said:
Hey, I am installing a custom ROM (Omega V43.3) through Mobile Odin Pro and during installation when it's copying selected files it froze on PolarisViewer for some reason! Now I have no idea what to do, it has been frozen for 15min!
The omega installar has already: wiped preload, dalvik cache, cache, formated system, copied system files,and is now on copying selected files.
Any ideas?
Update: Rebooted and landed in Android system recovery <3e>
Click to expand...
Click to collapse
BHARGAV33 said:
you mean you dont have CWM recovery?
Click to expand...
Click to collapse
Yes I was under the impression that you could just use Mobile Odin to flash your ROM's..
Do you also need to have CWM recovery?
BTW, I'm flashing stock firmware now..
Problem fixed. just had to choose 'Full Wipe' in the installation process of Omega..
Edit
mtyran said:
So I've decided to switch from JB to CM, but after using cyanogen installer I noticed that few things (apps, folders from JB) are still there. I tried factory reset but it didn't change anything, so I've found perfect command format /system. All I can do now is access CWM - I put JB.tar.md5 on microSD but no files are being found. Same happened after applying this PhilZ-cwm6-XWMS1-NEE-5.15.9-signed.
I'm out of ideas. Any help?
edit: Ok using CWM I wiped everything (factory reset, cache, format system, dalvik cache) and installed CM10.1/Gapps - system is back!
But the thing is I still have android stuff and my old files. So the question is how to do clean install?
Click to expand...
Click to collapse
md5 files are for odin (flash from pc), zip for cwm (from phone recovery)
Look up ROM wipe/nuke scripts by hawkerpaul.
running on 4.2.2 stock rom GT-i9060 rooted, twrp 3.02 and unlocked bootloader with ez-unlock (fastboot isnt working)
steps I used to flash the ROM:
1. flashing stock rom and getting root
2. enable USB debugging and unlocking bootloader
3. wiping cache, dalvik cache and data, 2nd time tried wiping cache, dalvik cache, data and system, 3rd time wiped cache, dalvik cache, data and added format script to update-script before mounting and extracting files (internal storage was never included because it doesn't make a difference)
4. flashing both of the ROM and gapps
the rom is made for my phone and i'm certain of it if i'm gonna be asked about it (GT-i9060 Baffinlite)
5. Wiping dalvik cache, cache and data
been more than a week working on flashing this rom but all goes back to the bottom
tried removing the assert line
added execute permissions to the zip, didn't make a difference
recovery version is 3.0.2 and tried twrp 2.7, twrp 2.8 and cwm 5.06 but the one the rom developer asked to use wasn't booting but kept powering the phone off after showing device logo, it's on the attachements
after getting error 7 couple of times without editing anything then i tried editing updater-script myself by changing the mount order but i guess the previous is the one used on every lineage rom so that failed too
there's a cm11 rom for the dvice working but full of bugs so what i'm not getting is why the lineage 16 one isn't mounting at all although the other one do
"detected filesystem ex4 for /dev/block/mmcblk0p17
mount: failed to mount /dev/block/mmcblk0p17 at /system"
that comes right after the extracting packages script (system.new.dat.br
ticking the system on twrp gives on log: can't mount system (invalid argument)
there is enough space on system for the rom too
i'm also sure that the system block is "mmcblk0p17" because it worked with the other ROM
the gapps mentioned that the android veriob I am using after installing the ROM is 5.1 (SDK 22) not 9.0 but I ignored it after checking the build.prop inside the system img
im ready for testing if there's a dev getting a solution
I know there would be lots of bugs by running pie on that phone because of the specifications but im okay with it
if someone could fix the mounting ROM bug or tell me if there is something i missed about flashing
Rom by knuxfanwin8
(androidfilehost.com/?fid=6006931924117889489)
Recovery by made_in_androland
(androidfilehost.com/?fid=457095661767119752)
NOT-Working recovery by knuxfanwin8
(androidfilehost.com/?fid=6006931924117902394)
I have the same problem, please give we a solution!
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Azureus. said:
running on 4.2.2 stock rom GT-i9060 rooted, twrp 3.02 and unlocked bootloader with ez-unlock (fastboot isnt working)
steps I used to flash the ROM:
1. flashing stock rom and getting root
2. enable USB debugging and unlocking bootloader
3. wiping cache, dalvik cache and data, 2nd time tried wiping cache, dalvik cache, data and system, 3rd time wiped cache, dalvik cache, data and added format script to update-script before mounting and extracting files (internal storage was never included because it doesn't make a difference)
4. flashing both of the ROM and gapps
the rom is made for my phone and i'm certain of it if i'm gonna be asked about it (GT-i9060 Baffinlite)
5. Wiping dalvik cache, cache and data
been more than a week working on flashing this rom but all goes back to the bottom
tried removing the assert line
added execute permissions to the zip, didn't make a difference
recovery version is 3.0.2 and tried twrp 2.7, twrp 2.8 and cwm 5.06 but the one the rom developer asked to use wasn't booting but kept powering the phone off after showing device logo, it's on the attachements
after getting error 7 couple of times without editing anything then i tried editing updater-script myself by changing the mount order but i guess the previous is the one used on every lineage rom so that failed too
there's a cm11 rom for the dvice working but full of bugs so what i'm not getting is why the lineage 16 one isn't mounting at all although the other one do
"detected filesystem ex4 for /dev/block/mmcblk0p17
mount: failed to mount /dev/block/mmcblk0p17 at /system"
that comes right after the extracting packages script (system.new.dat.br
ticking the system on twrp gives on log: can't mount system (invalid argument)
there is enough space on system for the rom too
i'm also sure that the system block is "mmcblk0p17" because it worked with the other ROM
the gapps mentioned that the android veriob I am using after installing the ROM is 5.1 (SDK 22) not 9.0 but I ignored it after checking the build.prop inside the system img
im ready for testing if there's a dev getting a solution
I know there would be lots of bugs by running pie on that phone because of the specifications but im okay with it
if someone could fix the mounting ROM bug or tell me if there is something i missed about flashing
Rom by knuxfanwin8
(androidfilehost.com/?fid=6006931924117889489)
Recovery by made_in_androland
(androidfilehost.com/?fid=457095661767119752)
NOT-Working recovery by knuxfanwin8
(androidfilehost.com/?fid=6006931924117902394)
Click to expand...
Click to collapse
I have The same problem, please help me.
I have the galaxy grand neo and i try to install lineage os 16.0 but not work, i have read in a thread that the problem will be the bootloader (its version is too old)
In the post it was written to update the bootloader but for the galaxy grand neo the only one verison of android is 4.2.2.
Maybe i'm wrong, i'm not a pro but i can understand somethings.
Hey any one there?????¿?
Please post a quick reply to help three of us from this drastical problem..........??????
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
kouseralamin said:
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
Click to expand...
Click to collapse
Tried but nothing
kouseralamin said:
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
Click to expand...
Click to collapse
Androcomtweaker said:
Tried but nothing
Click to expand...
Click to collapse
TWRP doesn't give you option Resize Partition but only option Resize File System - what is nothing else than expanding the related FS to reclaim wasted space.