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.
Related
simple thread, not much to say..
if you have troubles installing "Hyperbeam new time" or any other rom just follow this instructions:
First of all wipe data,cache,dalvik cache and format system
then flash the rom.
if the rom has an addon (su fix, lockscreen,etc) flash it after one boot! and you wont get bootloop. simple solution for roms like hyperbeamnewtime that has over +100 cmments telling that rom bootlooped.
-----
another tip for rom makers, if you are creating a rom, and to get system folder you use terminal emulator. NEVER EVER DECOMPRESS it with WINRAR, why? because it will "kill" lots of files such as busybox applets or SH files.
goodluck :good:
sorry for the bad english
Just an advice but format system is not necessary in all the ROMs and sometimes give status7 error. So if u can so just write that if it's mentioned then only wipe.
Press THANKS if I helped,
Best Regards,
AJ
alokbina said:
Just an advice but format system is not necessary in all the ROMs and sometimes give status7 error. So if u can so just write that if it's mentioned then only wipe.
Press THANKS if I helped,
Best Regards,
AJ
Click to expand...
Click to collapse
Status 7 error isn't due to format system...
Status 7 error is regarding build.prop and updater script.
And to the OP...
format system is not recommended for many ROMs (like CM based) and even if its recommended its not necessary to format system.
I never format my system and ROMs run fine... Just fine
Format data/factory reset is must when switching between ROMs
PS: It better to avoid format system.
PREDATOR95 ->->->->a.k.a. ->-> predatOr
predatOr said:
Status 7 error isn't due to format system...
Status 7 error is regarding build.prop and updater script.
And to the OP...
format system is not recommended for many ROMs (like CM based) and even if its recommended its not necessary to format system.
I never format my system and ROMs run fine... Just fine
Format data/factory reset is must when switching between ROMs
PS: It better to avoid format system.
PREDATOR95 ->->->->a.k.a. ->-> predatOr
Click to expand...
Click to collapse
Nope dude I agree its because of updater script but in some ROMs for e.g. some people reported of getting status 7 error due to format system so just adviced him!
Best Regards,
AJ
Hi, why do you recommend to don't format /system when flash a new rom? In every rom I read to do it.
AW: You got a bootloop and you followed instructions? (ROM INSTALLATION) (ROM MAKER)
XDynamite said:
Hi, why do you recommend to don't format /system when flash a new rom? In every rom I read to do it.
Click to expand...
Click to collapse
You can get a status 7 error (getprop) because the installation zip can't read from the /system/build.prop which device you are using. Then you are unable to flash the rom and you have no system installed
Sent from my Nexus 7 running Android 4.2.2
quaryone have
mihahn said:
You can get a status 7 error (getprop) because the installation zip can't read from the /system/build.prop which device you are using. Then you are unable to flash the rom and you have no system installed
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
So is it safe don't format the system directory? Aren't there risks to make trouble between the two roms (maybe because some files of the old rom)? In many roms with Aroma you can choose wich device are you using.
AW: You got a bootloop and you followed instructions? (ROM INSTALLATION) (ROM MAKER)
XDynamite said:
So is it safe don't format the system directory? Aren't there risks to make trouble between the two roms (maybe because some files of the old rom)? In many roms with Aroma you can choose wich device are you using.
Click to expand...
Click to collapse
No there are no risks, because the updater-script should format /system automatically. So don't format it by yourself, only wipe data/factory reset, wipe cache, (wipe dalvik-cache)
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
No there are no risks, because the updater-script should format /system automatically. So don't format it by yourself, only wipe data/factory reset, wipe cache, (wipe dalvik-cache)
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Ok, thank you for the information.
---------- Post added at 03:16 PM ---------- Previous post was at 03:04 PM ----------
However in the past I had a bootloop issue with Optimax 3.0 rom (phone stuck on Sony logo). Flashing process went well and I could use the phone for some day with no problems. With no apparent reasons while I was using the phone it has restarted by itself and then occurred the bootloop issue. I had to flash the stock rom with Flashtools.
Sometimes wiping system is important but do only if it stucks in bootloop or is mentioned in the thread
Best Regards,
AJ
The most import thing is to just READ the OP very carefully for installation instructions. Just follow each step closely and you should never have any problem.
Sent from my GT-P3100 using xda app-developers app
Hi,
My device is a GT-I9300, i have rooted with the toolkit by mskip and have TWRP. and yeah, am new to custom ROMs.
i successfully flashed the 3.15 version of PA earlier today.
But when i try to install the 3.65 version i get the following error in the log:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Formatting Cache using make_ext4fs...
Updating partition details...
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
Cleaned: /cache/dalvik-cache...
Cleaned: /cache/dc
-- Dalvik Cache Directories Wipe Complete!
Updating partition details...
Installing '<path to the ROM>'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.build.product.device") == "
getprop("ro.build.product") == "m0"
E:Error in <path to the ROM>
(Status 7)
Error flashing zip <path to the ROM>
Updating partition details...
I tried to download the ROM from two sources:
androidfilehost[INSERT DOT HERE]com/?fid=23032113221600425
goo[INSERT DOT HERE]im/devs/paranoidandroid/roms/i9300/pa_i9300-3.65-07JUL2013-gokussjx.zip
What i allso find strange, is that after i have tried this a couple of times now, and i have also taken "format data" 2 times - if i select "reboot system" after the failed flash of 3.65 - im loaded back into 3.15... how is that even possible..?
Any one else seens this?
What if you format system first?
Sent from my GT-I9300 using Tapatalk 4 Beta
No luck that either. tried both to format data - then immediately flash the ROM, and ive tried to format data, reboot, and then flash. neither work..
Formatting system removes the rom so if you've tried that and it worked, it wouldnt be booting into your previous rom. Also, format system doesn't touch data.
This error is nothing to do with data either. The error can't match the rom device "m0" with your device. I'm not sure where it looks for this info. I know ro.build.product=m0 (that its looking for) is in /system/build.prop of you'r current tom (or it should be) but whether that's what it matches or not I don't know. But if it does and its different, this error is what you'd get. Thats why I thought format system could help. It would remove the build.prop and at least rule out the product mismatch there.
Of course you could also just check the line manually.....
Sent from my GT-I9300 using Tapatalk 4 Beta
So how is it possible that i get 2 successful format data and the prev. ROM is still there?
The rom is in the /system partition. Your user apps and data are in the /data partition. "Wipe data" is obviously nothing to do with /system.
I think you're getting confused. This is a basic level of understanding you need to have before getting carried away flashing roms
Sent from my GT-I9300 using Tapatalk 4 Beta
System Format didnt do the trick either.
I actually read "format data" in your posts when you said "format system" - sorry for that
sponsen said:
System Format didnt do the trick either.
I actually read "format data" in your posts when you said "format system" - sorry for that
Click to expand...
Click to collapse
Maybe try a different ROM just to see if the problem is in the ROM zip or your phone. Try something like slim or PAC
Finally i got it working! THAT FEELING!
I stubled upon some posts regarding "Status 7" - and it suggested that it was because the recoverytool was outdated. I had TWRP 2.3.3.0 (came with the toolkit....).
So i had to re-flash the 3.15 Paranoid Android and update TWRP from GooManager to 2.6.0.0. That made the difference!
Have learned so much the last couple of days ^^
sponsen said:
Finally i got it working! THAT FEELING!
I stubled upon some posts regarding "Status 7" - and it suggested that it was because the recoverytool was outdated. I had TWRP 2.3.3.0 (came with the toolkit....).
So i had to re-flash the 3.15 Paranoid Android and update TWRP from GooManager to 2.6.0.0. That made the difference!
Have learned so much the last couple of days ^^
Click to expand...
Click to collapse
Interesting, thanks for feeding back.
First of all, this is my first post on this forum, so I'd like to say hello to everybody.
I made a bit of a mess with my father's phone (it was mine before he had it, so it was already modded), and the explanation will be somewhat long because I tried everything before coming here for help.
This phone had Android 5.1.1 Lollipop, installed through the official Cyanogenmod 12.1 Nightlies. It was working perfectly, but I wanted to install more Gapps on the /system partition and switch some of the original Cyanogenmod apps with the corresponding Google apps. I used Deltadroid's modular Gapps (Thread here: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368) to install everything I needed on the /system partition, but I only did a factory reset+cache wipe instead of wiping the /system partition too and starting from scratch, because I couldn't find the option to wipe the /system partition in the "stock" Cyanogen Recovery. Now the phone will boot, enter recovery mode and even get to the setup screen, but as soon as the Google Play Services are needed, they crash and the setup won't go on. I tried installing the CWM but the signature check fails every time, I tried using ADB but I'm no expert and I don't know how to make it work, I tried reinstalling the ROM and wiping /data and /cache once again to no avail, I tried basically everything but it seems the only thing that can be done is wiping the /system partition and reinstalling both the ROM, the Gapps and the add-ons.
The problem is, I have no idea how to wipe the /system partition, so I was wondering if anyone here could help.
Thanks in advance.
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
noppy22 said:
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
Click to expand...
Click to collapse
First of all, thank you for answering!
I tried many "-signed" .zips, but none of them worked, so I'll assume I used non-compatible ones. There was space for the Gapps on the /system partition, mainly because I made sure of getting only the Gapps and the few addons I needed, so the MB count was very low.
I'll try your recovery right now and let you know in a moment, hopefully this solves the problem and I can have the phone working again.
Managed to install the recovery, format the /system, /data and /cache partitions, install the rom, the Gapps and the add-ons. It worked, but the phone still gives me an "Unfortunately, Google Play Services has stopped". How can I get the apps to work? What could the problem be?
I solved the problem, finally...I changed the Gapps package (I used TK's Gapps) and managed to install it and make everything work.
Thanks for all your help! I think the thread can be closed now.
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
alexounet2 said:
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
Click to expand...
Click to collapse
Hey i had this issue and finally pinned it down to the TWRP I was using. It turns Official TWRP has this issue. This can easily be resolved if u flash Squid's TWRP
Download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
That was the problem apparently. Thank you!
Thank you! I was having this problem as well and that fixed it.
Thanks very much for your help!!!
I was scared of loosing my phone...
Thanks.
I have a US Cellular XT1526 and was unable to install GApps on CM13 without this. CM13 installed fine, and GApps looked like it installed, but on reboot nothing was there; GApps failed to install. Using Squid's TWRP fixed it; thanks!
ayush rao said:
hey i had this issue and finally pinned it down to the twrp i was using. It turns official twrp has this issue. This can easily be resolved if u flash squid's twrp
download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Click to expand...
Click to collapse
thank you so much :d
thank you buddy.....
my mother is using Motorola E 2nd gen LTE and i flashed it with cyanogenmod 13 used officialTWRP recovery... and i faced the same problem. thank you very much for your answer and also the other guy for asking the question.
Should I select boot or recovery as partition when flashing this img
cannot restore system mounted read only
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Djoul33 said:
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Click to expand...
Click to collapse
In TWRP, go to mount and see if data is mounted.
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Djoul33 said:
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Click to expand...
Click to collapse
I have flashed things that did not properly unmount a partition afterwards so I could not mount it in twrp. Try flashing something that mounts data, if not mounted, then unmounts data properly.
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
2016...
Djoul33 said:
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
Click to expand...
Click to collapse
Try that first.
Hi,
My TWRP was too old, deprecated. It is OK now.
Thanks.