I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help
as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps
birdr said:
I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help
Click to expand...
Click to collapse
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
chrisknife said:
as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps
Click to expand...
Click to collapse
That's not true and it's not why anyway. It's a problem with the recovery.
do you have any nfo ( workaround) how the update procedure can be done?
3bs11 said:
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
That's not true and it's not why anyway. It's a problem with the recovery.
Click to expand...
Click to collapse
ok sorry then...
i thought it's the same like on aokp nightlies.
for me it helped to delete preload and system...
had this error before too. after formating this it worked.
Thanks all. I got this working based on the advice given.
Precisely:
1. I extracted the nightly using ES file explorer.
2. I used a text editor to remove the line
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
from
/META-INF/com/google/android/updater-script
3. Then I re-zipped using ES file explorer.
4. Then i flashed as normal with philz recovery, wiped cache and rebooted.
Worked first time and everything upgraded as expected.
Thanks again for the help.
Related
DISCLAIMER: These scripts have worked for me without issue. It would behoove you to ensure you have a solid back up to recover from in the event that something goes horribly wrong. These scripts should be considered a WIP. I will edit them and provide information as needed if something does not work as it should. Please feel free to post here or PM me if you have issues and bear with me if they do not work properly for you. END DISCLAIMER
To be honest, I am lazy. I flash CM nightlies and sometimes themes, and I didn't like having to navigate through recovery over and over again to wipe cache and dalvik-cache. So, I decided to write a script that would just do it for me. Then I got even lazier. I found that I had written several scripts and now I was tired of having to flash them all in a certain order. Which is why I wrote one all inclusive script.
Here I will provide you with two separate scripts. The first does just enough and the second does that much and a few more personal tweaks.
The first script is a rather simple one. It formats your /cache partition and deletes /data/dalvik-cache.
Wipe_Cache_Dalvik.zip
Edify version to work with Clockword Mod Recovery
1. Back up your current rom
2. Flash Wipe_Cache_Dalvik.zip
3. Flash your nightly/theme of choice
4. Reboot
The second script is where my personal preferences come into play. This script is meant to be flashed after you install your nightly rom. This script will format /cache, delete /data/davlik-cache, delete certain system apps that I do not personally use, and then copy an edited build.prop into /system so that the DPI is set to 190 immediately after you reboot from installing the nightly rom. This script will more than likely have to be changed to suit your needs. I understand that people will want different DPI settings and would like to retain the use of apps that I do not use.
Wipe_Delete_Copy.zip
1. Edit the script if you so choose. (Directions will be given in the second post)
2. Back up your current rom
3. Flash your nightly
4. Flash Wipe_Delete_Copy.zip
5. Reboot
Many thanks to Omegasun and his BareBone App and Sense Removal Plus Community Tools Thread.
This was the thread that got me started writing scripts. I learned a lot from him. My script would not have been possibl without his.
Many thanks to unCoRrUpTeD and his unCoRrUpTeD Dual Boot V1 Thread. I did a lot of testing for unCoRrUpTeD on his dualboot setup. I learned a lot from him in regard to using updater-scripts and updater-binaries. Without him I would not have been able to write the second script.
A thank you also to Calkulin for his format_all.zip which was another source of inspiration for the first wipe script.
As always a giant thanks to Cyanogen, Team Douche, TeamWin, and the Snap Team. The information and aid that they have provided to me is second to none. Without them I wouldn't know half of what I do now. Their contributions are what make this community great.
Any gratitude that you may feel towards me for these scripts should be directed towards those mentioned above. I wrote these to benefit myself and now feel that I should give them back to you all. I hope they work as described and make flashing a little bit easier on you.
These are rudimentary directions for the time being. I will edit and make them more precise later tonight. Also included a few things for reference. Like I said, it is basic info for now and it will become more detailed and informative.
You will need a text editor to edit any of these scripts. I primarily use Notepad++ on Windows. If you are on a *nix box then I am sure you are more than able to find a text editor that suits your needs.
1. Unzip Wipe_Delete_Copy.zip
2. Navigate to *\META-INF\com\google\android\
3. You will see two files: updater-script and update-binary
4. Open updater-script with your favorite text editor. (In my case, I right click and choose "Edit with Notepad++")
5. Edit Away
6. Save
7. Rezip
For reference, these are the files deleted from /system/app:
ADW Launcher
Browser
Car Home Google
CM Wallpapers
Development
DSP Manager
Email
FM
File Manager
Google Quick Search Box
Genie Widget (News and Weather)
Live Wallpapers
Live Wallpaper Picker
Pro Tips (The CM Widget that appears after a clean install)
Sound Recorder
VoiceDialer
Notice "ADW Launcher." This means you will need Launcher Pro/ADW EX/etc before you flash this. Or you will need to remove this line from the script.
If you don't want to change your DPI settings:
1. Open up the script in your text editor
2. Delete
Code:
ui_print("");
ui_print("");
ui_print("");
ui_print("Copying build.prop to retain proper dpi");
show_progress(0.200000, 5);
package_extract_dir("system", "/system");
3. Save
4. Delete the "system" folder found in the original zip
5. Rezip
This will be very handy. Thank you, sir.
+1 for this when I get to mess around with it after work tomorrow. Great job
swyped from my cyanogenized and gingerbreaded EVO
i have been thinking about making a cache/dalvik wipe script forever, but never got the will. thanks for making my life easier karadore.
I appreciate the thanks. I know the basic script will work just fine. It is very straight forward. The second one is kind of tricky because it uses an updater/binary. I just recently started working with them and had a few issues to begin with. The more feedback you all give me on this the better. Hope they help.
i dont know how to write in edify, but i would like to. if you dont mind whipping up a little tutorial, that would be fantastic so all the peoplez can stop complaining that they get an error after flashing my zips on cwm 3+. it would help me and a lot of others as well.
dkdude36 said:
i dont know how to write in edify, but i would like to. if you dont mind whipping up a little tutorial, that would be fantastic so all the peoplez can stop complaining that they get an error after flashing my zips on cwm 3+. it would help me and a lot of others as well.
Click to expand...
Click to collapse
I may just do that. Would give me a nice little project in the next few days to help me procrastinate from school and work a little more
Anyway to update these to work on CW 3+ recoveries?
sminker said:
Anyway to update these to work on CW 3+ recoveries?
Click to expand...
Click to collapse
The second script should work because it is written in edify. I will update the first one so that it works. Leaving for work now but I should be able to do it all from my phone. Will post up the new version in a few.
sminker said:
Anyway to update these to work on CW 3+ recoveries?
Click to expand...
Click to collapse
Just did a quick edit from my phone. This new zip should work on all CW Recoveries. Let me know if there are more issues. Will update the op once I am off work.
http://db.tt/sBi95OV
Karadorde said:
Just did a quick edit from my phone. This new zip should work on all CW Recoveries. Let me know if there are more issues. Will update the op once I am off work.
http://db.tt/sBi95OV
Click to expand...
Click to collapse
Awesome. Haven't tested yet but thanks for updating.
All I ask is that you let me know if it works or not. No reason why it shouldn't, but the more R&D the better.
are you still planning on giving an edify tutorial? and if not do you have any helpful pages or just all-telling .zips i can look at? thanks a bunch karadorde
Wait you flash first and then wipe caches? I've always done it the other way around. Does it even matter? Guess not...
Sent from my PC36100 using XDA App
matt2053 said:
Wait you flash first and then wipe caches? I've always done it the other way around. Does it even matter? Guess not...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You can do it either way. I always used to wipe and then flash.
The reason I am wiping after flashing the nightly is because of the other code in the second script. The second script deletes all of those system apps that I don't use and copies my edited build.prop back into /system. If I flashed the script before the nightly, then those system apps would be reinstalled and I would lose my edited build.prop.
dkdude36 said:
are you still planning on giving an edify tutorial? and if not do you have any helpful pages or just all-telling .zips i can look at? thanks a bunch karadorde
Click to expand...
Click to collapse
I have started putting together the thread. I will be adding to it today. I will dig up some other threads for you as well. Here is a link to the one I just started in Evo General.
http://forum.xda-developers.com/showthread.php?t=994940
nice work.. definitely helps me with flashing nightlies.. i would always have to go and remove most of that stuff.. the only thing i wanted to keep was DSP so i went and simply edited script..
works.
Hey everyone - I figured this might help some folks. It is a CWM installable zip that will restore your system to a completely stock UEKHA (the US retail build for P7310). This includes the stock kernel and recovery image as well.
Heres the instructions:
1) Download this file: http://www.multiupload.com/1KRF1M4CQZ
2) Put the file on your internal storage.
3) Reboot into recovery
4) Execute the Wipe Data/Factory Reset option
5) Choose Install Zip from SD Card
6) Choose Choose Zip from SD Card
7) Select the P7310UEKHA_Restock_v1.zip
8) Sit back, wait about 5 minutes
9) Once the script completes and says "Done", reboot.
10) Welcome to a completely stock US Retail tab
Enjoy.
I just want to ask: Can we flash this on other 8.9s from other regions (namely, an Asian model)?
I'm used to how it is in Maemo where the only differences between firmwares is localization and some preinstalled programs.
Yes you could flash it onto another 8.9 as well, although it should be a P7310 (Wifi only). Just like Maemo, the only differences between regions are localizations and pre-installed apps.
This stock image would not support 3G functionality however, so it would be a bad idea to install it on a P7300.
That's great. Going to flash Clockwork and this once I pick up my P7310 on Tuesday.
Which reminds me - how are Samsung kernels built? I heard that they need to use an initrd (or can the modules be compiled straight into the kernel? or is there a kernel size limitation, which is why an initrd is needed?)
I am truly grateful for this as I rooted and debloated my Tab the very first day lol. This is a great step!
Just flashed my tab with the ROM, works great! Originally had asian ROM on the tab.
Thank you very much! I needed some of the stock original loadable modules after some prior tweaks .
Thanks for the good work!
I was checking the system script used, and I was wondering if this CWM preserve the file/folder permissions as out of the box state or is just 7777 state?
mramirezusa said:
Thanks for the good work!
I was checking the system script used, and I was wondering if this CWM preserve the file/folder permissions as out of the box state or is just 7777 state?
Click to expand...
Click to collapse
Permissions should be out of the box state...the system image was taken from my stock tab directly, and the extract script should leave all permissions in tact.
Hey alterbridge86, it's great to hear you have a GT 8.9 now, that's good news for us
Quick question, how did you dump the ROM and the recovery? I have a GT 8.9 3G from Orange France and I'd like to dump everything before installing CWM to be able to restore to stock if needed.
Thanks! And again, great work!
masterludo said:
Hey alterbridge86, it's great to hear you have a GT 8.9 now, that's good news for us
Quick question, how did you dump the ROM and the recovery? I have a GT 8.9 3G from Orange France and I'd like to dump everything before installing CWM to be able to restore to stock if needed.
Thanks! And again, great work!
Click to expand...
Click to collapse
I ended up dumping it using the CWM I posted in the other thread. The new clockworkmod stores its backups in .tar format, so it makes it really easy to manipulate. Simply create a backup, then if you're feeling adventurous, you can take this flashable zip, replace system.tar and boot.img with the ones created by your backup. The stock recovery is same on all devices, so you can leave the one that is in this package and itwill work for you
Sounds good, thanks I'll give it a try when I have a little more time to play
Hey guys, i did something really stupid today to my 8.9 p7310...I installed that Asia update to it and it placed the tab into a loop and crashes in the settings app when it first starts up. Cant access SD card to install this firmware. I need the Odin firmware to put back to stock I think. Any ideas?
shatty said:
Hey guys, i did something really stupid today to my 8.9 p7310...I installed that Asia update to it and it placed the tab into a loop and crashes in the settings app when it first starts up. Cant access SD card to install this firmware. I need the Odin firmware to put back to stock I think. Any ideas?
Click to expand...
Click to collapse
When you installed the Asian firmware at ODIN, did you remember putting the CSC, PIT, BOOTLOADER to their corresponding places along with the biggest file being at PDA? If you just used the PDA file and not the other files...there's your issue. Once you successfully ODIN, flash this specific CWM Recovery and then you can either choose Stock (this thread) or the Overcome ROM.
Yea just did the pda. The instructions only said the pda. Doesnt matter anyway i am back to stock used adb to load the stock zip to sdcard and loaded
shatty said:
Yea just did the pda. The instructions only said the pda. Doesnt matter anyway i am back to stock used adb to load the stock zip to sdcard and loaded
Click to expand...
Click to collapse
Good to know you made it. The same happened to another user. Those instructions aren't correct.
Sent from my GT-P7310
Help getting China based GT-7310 to US stock
Hello,
I recently bought a GT-7310 in China, and want to get this to stock US using your method. I had a question on step #2.
2) Put the file on your internal storage.
How do I get the file to the internal storage and where is that location? I don't see an /SDCARD folder anywhere when browsing the tab in Windows 7. I have the latest USB drivers installed. I tried to push the file to /SDCARD using ADB but Android SDK tools doesn't recognize my tab. Are there any other ways to get the file to internal storage?
Thanks.
zinzino said:
Hello,
I recently bought a GT-7310 in China, and want to get this to stock US using your method. I had a question on step #2.
2) Put the file on your internal storage.
How do I get the file to the internal storage and where is that location? I don't see an /SDCARD folder anywhere when browsing the tab in Windows 7. I have the latest USB drivers installed. I tried to push the file to /SDCARD using ADB but Android SDK tools doesn't recognize my tab. Are there any other ways to get the file to internal storage?
Thanks.
Click to expand...
Click to collapse
When you plug in the tab, it connects via MTP to Windows. Then you can only get to the internal storage, just drop it in there. You'll see all the default folders (music, videos, etc.) so you'll know your in the right place.
Thank you. I got the file to SD Card, went into recovery, executed the wipe data/factory reset option. After the wipe data/factory reset is complete, I selected the option "apply update from /sdcard". I selected that and I get the following error:
E:error opening /data/media: No such file or directory
Any ideas?
Thanks.
You need to use CWM recovery, not the stock recovery.
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
are you using any sound/volume mods? or any other flashable mods? i think awesomebeats dies this, at least others have complained about it wiping the dalvik after every reboot.
cdon2109 said:
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
Click to expand...
Click to collapse
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
CMNein said:
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
Click to expand...
Click to collapse
yes.. and it updates apps after delvic wipe.. but in my case whenever i restart I see the "Android is upgrading" box for about 3-5 sec.. no update app progress bar.. and when I wipe delvic this upgrading apps takes like a min or so with my 150+ apps.. but this "Android is upgrading" dialogue box appears only for 3-5 sec..
I am using PA 3.99 with franco kernel.. once booted every thing inside is running smoothly and no fc's...
Same here. No odex files in app folder. No wipe, no cache clearing. Plain reboot. And Android is upgrading message on every boot. (Starting apps)
No optimizing apps message though.
Sent from my Nexus 4
Wouldn't it be related to "zipalign apk on each boot" parameter ? or an other init script put in place by a dirty flash (no /system or /data format) or a kernel... ?
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
anandbibek said:
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
Click to expand...
Click to collapse
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
benbugohit said:
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
Click to expand...
Click to collapse
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
anandbibek said:
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
Click to expand...
Click to collapse
Did you try to re-flash your (stock) ROM (and the kernel after 2 reboots) with wiping only /cache and dalvik-cache ? with latest 2.6.2.0 TWRP ?
happens to me too
Sent from my Nexus 4
I've seen people get this with stuff like V6 Supercharger by Zepplinrox and similar scripts.
Edit : @Dungeon47: thanks for this information that users can't provide...
HeyyMyNameIs said:
happens to me too
Sent from my Nexus 4
Click to expand...
Click to collapse
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
benbugohit said:
Edit : @Dungeon47: thanks for this information that users can't provide...
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
Click to expand...
Click to collapse
im sorry, just wanted the OP to know that he is not the only one with this "problem" by the way im rooted stock rom and kernel, some apps start up when i boot like nova launcher, lucky patcher sidebar and udn. But i am not looking for a fix for this as this does not take that long and i just said that to let the OP know that he is not alone with this "problem"
Sent from my Nexus 4
Ok guys,
Here's the solution. Don't flame me for talking about unholy stuffs. I'm posting this only because it is the cause of the problem.
If you are using LP or such tools to create .odex files of some app in /app folder. It won't cause any boot msg.
But after you dirty flash a ROM, that .odex files somehow gets backdated and causes the UPGRADING msg.
Fix is, delete the odex files, and re create them if needed. Once after every dirty flash.
Sent from my Nexus 4
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachment for help.
:good:Hits Thanks If I helped u:good:
Hello, I'd like to flash Cyanogenmod 10.1.3 to my Sprint Galaxy S4. SPH-L720. I've installed TWRP. I understand Nandroid is the recommended backup. I've installed nandroid, busybox, granted SU permissions etc. Now before backing up via Nandroid I have a couple questions.
1.) Is it acceptable to save my Nandroid backup to dropbox?
2.) There are 3 options I can select Yaffs2 as Tar. Exclude Dalvik Cache. Exclude Google Music Files. I am guessing I don't need to save Google music files because I don't have anything in there as of now but I don't know what the first two options do. Could someone explain to me the purpose of these options and whether I may want to check them? Do I want to disable MD5 generation or compress the backup?
3.) After saving the backup am I ready to flash Cyanogenmod?
4.) To flash the ROM I just boot TWRP and tap to install the zip then let the phone work its magic? The ROM I will be installing is the Stable option on this page.
^^ I suppose it won't let me post the url but it's the jfltespr stable ROM from Cyanogenmod
Thanks in advance for the help!
2 Days later
Dalisword said:
Hello, I'd like to flash Cyanogenmod 10.1.3 to my Sprint Galaxy S4. SPH-L720. I've installed TWRP. I understand Nandroid is the recommended backup. I've installed nandroid, busybox, granted SU permissions etc. Now before backing up via Nandroid I have a couple questions.
1.) Is it acceptable to save my Nandroid backup to dropbox?
2.) There are 3 options I can select Yaffs2 as Tar. Exclude Dalvik Cache. Exclude Google Music Files. I am guessing I don't need to save Google music files because I don't have anything in there as of now but I don't know what the first two options do. Could someone explain to me the purpose of these options and whether I may want to check them? Do I want to disable MD5 generation or compress the backup?
3.) After saving the backup am I ready to flash Cyanogenmod?
4.) To flash the ROM I just boot TWRP and tap to install the zip then let the phone work its magic? The ROM I will be installing is the Stable option on this page.
^^ I suppose it won't let me post the url but it's the jfltespr stable ROM from Cyanogenmod
Thanks in advance for the help!
Click to expand...
Click to collapse
Since nobody replied I worked it out by trial and error. Here's what I came up with.
1.) You can save nandroid to dropbox but it takes FOREVER. it was much quicker to just copy the whole TWRP save file over to my desktop. Think 4 mins vs 4 hours quick. P.S. Something I couldn't find ANYWHERE was whether the Nandroid files should be separate. I expected a zip. My Nandroid manager recognized them as separate files as a backup so we're good to go.
2.) I didn't select Yaffs2 as Tar. I didn't exclude the Dalvik Cache, but I did exclude Google Music Files because it was empty anyway. I did not disable MD5 generation. A friend suggested I keep it. Also the backup was not compressed. I did a compressed and an uncompressed, the difference was only maybe a half a gig. If you have the storage space don't compress.
3&4.) With the backup saved safely off the phone I navigated to TWRP and installed the zip. It didn't work so I wiped the Dalvik and tried again without MD5 and it flashed right on. The first time It got stuck on the loading screen so I reinstalled the zip after wiping the Dalvik again and now it works like a charm.
**Something you may want to be aware of is not all ROM's come with Google services which is something I wanted, so you may have to do some digging to find the right google zip to flash but you flash that the exact same way you flashed the other zip.
**I'd be happy to do an actual writeup or help anyone with their issues on a Sprint SG4 since it appears that help in this part of the forum is kinda missing. Feel free to PM me!
~Dalisword
Watch "Install CyanogenMod on your Android Device with the CyanogenMod Installer" on YouTube
https://www.youtube.com/watch?v=ViVi4GAI0Sk&feature=youtube_gdata_player
Sent from my SPH-L720 using xda app-developers app
joshuadub said:
Watch "Install CyanogenMod on your Android Device with the CyanogenMod Installer" on YouTube
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
The one click installer wasn't working due to driver issues. I figured out the manual install.
Hi everyone, I have installed in my Jiayu S3 the mentioned AOSP N 7.1, and that process was seamless.
Now, to update to 7.1.1 I read from the ROM thread:
Update for 7.1.1
Q: Can't install rom, TWRP says "Updater process ended with ERROR 7
A: Since 7.1.1 Update, you'll need to unmount /system first , then you can proceed with rom install.
Click to expand...
Click to collapse
I have tried many different ways to do that but I always get the ERROR 7 message and I cannot update.
For example, this is what I have done in one of my trials:
- Restart in Recovery
- From Recovery,
-- Wipe cache, dalvik, data & system
-- Mount section, deselect "system" and leave only cache, data, micro sdcard (deselected "mount system partition read-only")
-- Install section, select the update 7.1.1 zip file and install it.
-- Here is where the process stops and I get the error.
I have tried other ways (like wiping only cache, dalvik & data), mounting the system read only or combinations of those, but I cannot get it to work.
Any help is much appreciated! Can someone explain in a more detailed way how to install?
Thanks a lot in advance.
Ps. I would have asked in the ROM thread but I do not have sufficient permission for that.
Ps2. Here is a log of my problem: https://www.zerobin.net/?f8e33fec02b06703#Gn8wb81G+6zF7mssoMRDS2PK60GAfKnQerhfsJW3Myc=
EDIT: I managed to fix the problem, see my answer in the comments.
marabelec said:
Hi everyone, I have installed in my Jiayu S3 the mentioned AOSP N 7.1, and that process was seamless.
Now, to update to 7.1.1 I read from the ROM thread:
I have tried many different ways to do that but I always get the ERROR 7 message and I cannot update.
For example, this is what I have done in one of my trials:
- Restart in Recovery
- From Recovery,
-- Wipe cache, dalvik, data & system
-- Mount section, deselect "system" and leave only cache, data, micro sdcard (deselected "mount system partition read-only")
-- Install section, select the update 7.1.1 zip file and install it.
-- Here is where the process stops and I get the error.
I have tried other ways (like wiping only cache, dalvik & data), mounting the system read only or combinations of those, but I cannot get it to work.
Any help is much appreciated! Can someone explain in a more detailed way how to install?
Thanks a lot in advance.
Ps. I would have asked in the ROM thread but I do not have sufficient permission for that.
Ps2. Here is a log of my problem: https://www.zerobin.net/?f8e33fec02b06703#Gn8wb81G+6zF7mssoMRDS2PK60GAfKnQerhfsJW3Myc=
Click to expand...
Click to collapse
I just found this post:
https://forum.xda-developers.com/showthread.php?t=2522762
I will try to do what it says and report on the result.
As a request to the developers, it would be nice if the necessary change is already included in the ROM itself, but whatever.
Ciao!
marabelec said:
I just found this post:
https://forum.xda-developers.com/showthread.php?t=2522762
I will try to do what it says and report on the result.
As a request to the developers, it would be nice if the necessary change is already included in the ROM itself, but whatever.
Ciao!
Click to expand...
Click to collapse
Indeed, the post I refer up there was the solution to the problem.
I paste here my steps:
Download the ROM zip file and unpack. I used the file "aosp_7.1.1_s3_h560_20170213.zip"
Open in a text editor the file META-INF/com/google/android/updater-script
Remove the line starting with "assert". In this case the line was number 2. (Remember, even if in your editor it shows in several lines, you have to delete until the semi-colon.)
Save file.
Repack everything into a new .zip file, e.g. "aosp_7.1.1_s3_h560_20170213-FIX_ERROR7.zip".
Use that file to update your 7.1 to 7.1.1 from your TWRP.
Enjoy!
you need to unmount system first.