Related
This is a modified OpenRecovery (Skrilaz_CZ) based on Androidiani Recovery (89luca89&Azhad) with some enhanced features for Milestone XT720.
Features:
Main OR menu streamlined
Most Androidiani menu options have been moved into OR > Other Utilities
Add ext3/4 support (thanks fjfalcon)
Added SD Card Utility (OR > SD Card Utility)
Added preference for display brightness in OR (OR > Settings > Brightness)
Added utility to reinstall orbootstrap (OR > "Other Utilities" > "Re-install orbootstrap")
New sh hijack binary will boot to fastboot bootloader if volume-down is held (OR > "Other Utilities" > "Re-install orbootstrap" to enable). This should be compatible with all ROMs and stock.
nandroid: removed ability to backup partitions that always fail (this means "Backup All" works now)
Fixed OR > "Wipe Dalvik Cache" bugs (previous OR/AOR don't clear them all)
Added OR > "Power Off" (helpful when phone is being stupid about charging)
Minor update to sdcard-info.txt output
XT720 basebands added (OR > Change Basebands)
Please note that although most Androidiani menu options have been included in the Other Utilities menu item, that does *not* mean I have tested them on XT720.
Installation:
Download link: http://www.multiupload.com/J8Q15SHP4S
Root the phone
Download OpenRecovery-XT720-01.zip (it contains /sdcard/OpenRecovery and /sdcard/OpenRecovery.zip)
Extract OpenRecovery-XT720-01.zip onto the SD card. This will create a /sdcard/OpenRecovery directory and an /sdcard/OpenRecovery.zip file.
Make sure you're not in USB access mode and install the bootstrap (using adb or Terminal):
Code:
su
cp /sdcard/OpenRecovery/orbootstrap/install_script.sh /tmp
chmod 755 /tmp/install_script.sh
/tmp/install_script.sh STR
Upgrading from OpenRecovery:
Download link: http://www.multiupload.com/J8Q15SHP4S
Make a nandroid and backup your sdcard
Download OpenRecovery-XT720-01.zip (it contains /sdcard/OpenRecovery and /sdcard/OpenRecovery.zip)
Rename the old /sdcard/OpenRecovery folder to /sdcard/OpenRecovery.bak
Extract OpenRecovery-XT720-01.zip onto the SD card. This will create a new /sdcard/OpenRecovery directory.
Optional: Move/copy all files from /sdcard/OpenRecovery.bak/updates to the new /sdcard/OpenRecovery/updates directory
Optional: Reboot into OR. Select "OR" > "Other Utilities" > "Re-install orbootstrap"
Github: https://github.com/Mioze7Ae/openrecovery_xt720
Thanks: skrilax_cz, 89luca89, Azhad, fjfalcon
Is this the same update that was posted in other topics?
No, it's not the same, its the next version. The biggest difference is this one merges Androidiani (the previous one was based on vanilla OpenRecovery). Maybe I should bold the new stuff.
Sorry about this but what does Reinstalling the Bootstrap mean? Don't we already use that for getting in the bootloader? Is it is it gets broken somehow?
Woodrube said:
Sorry about this but what does Reinstalling the Bootstrap mean? Don't we already use that for getting in the bootloader? Is it is it gets broken somehow?
Click to expand...
Click to collapse
If the bootloader gets broken, you won't be in OpenRecovery
Anyway, I see two reasons to use it. (1) to make 100% sure you can get back to OpenRecovery after you've flashed something experimental (say a Milestone A853 update-based ROM) or (2) you want to upgrade your bootstrap to the new version that lets you hold volume-down to boot directly into the fastboot bootloader. (i.e. in the new version volume-up==OpenRecovery, volume-down==fastboot)
Edit: that reminds me... I should make a version of the bootstrap that fixes volume-down to boot OR on Milestone XT720 running Motoroi 50R...
Mioze7Ae said:
If the bootloader gets broken, you won't be in OpenRecovery
Anyway, I see two reasons to use it. (1) to make 100% sure you can get back to OpenRecovery after you've flashed something experimental (say a Milestone A853 update-based ROM) or (2) you want to upgrade your bootstrap to the new version that lets you hold volume-down to boot directly into the fastboot bootloader. (i.e. in the new version volume-up==OpenRecovery, volume-down==fastboot)
Edit: that reminds me... I should make a version of the bootstrap that fixes volume-down to boot OR on Milestone XT720 running Motoroi 50R...
Click to expand...
Click to collapse
Very very nice... thx man
Ok so I may have run into a glitch. Hopefully it is just mine, but it has been awhile since I had updated many of the apps from the market and let me tell ya, there was a shopping list. Haha get it. Anyways, I updated them all and decided it has also been some time since I had made a backup as well.
So I went in and "tried" to make a backup of the usuals (system, data, cust, cache, cdrom and sd). I probably tried 3 or 4 times and it never backed anything up. I even deleted the openrecovery folder and re-unzipped and replaced it and tried maybe another 3 times. It would just hang on the system dumping part for 15+mins (which is way too long).
I rebooted and put the original MZor back in there (the one w/o all the AOR stuff in it-for reference). Booted into recovery and boom, made the full backup in normal time. I ran checks on sd and sd-ext several times throughout and never a problem.
Has anyone else encountered this? I had been using this since it first came out and some of the utilites and all worked fine, but now that I think of it, hadnt tried to make a back up until last night.
***Side question: Since the beginning when I first learned how to make a backup, I read that you should backup system, data, cust, cache, cdrom and sd(if neccessary). My question is why do we and does it matter if we back up the cust, cache and cdrom parts? Wouldn't these get repopulated anyways at first boot? Would everything work if we just restored system, data and sd (again if neccessary)
Woodrube said:
Ok so I may have run into a glitch. Hopefully it is just mine, but it has been awhile since I had updated many of the apps from the market and let me tell ya, there was a shopping list. Haha get it. Anyways, I updated them all and decided it has also been some time since I had made a backup as well.
So I went in and "tried" to make a backup of the usuals (system, data, cust, cache, cdrom and sd). I probably tried 3 or 4 times and it never backed anything up. I even deleted the openrecovery folder and re-unzipped and replaced it and tried maybe another 3 times. It would just hang on the system dumping part for 15+mins (which is way too long).
I rebooted and put the original MZor back in there (the one w/o all the AOR stuff in it-for reference). Booted into recovery and boom, made the full backup in normal time. I ran checks on sd and sd-ext several times throughout and never a problem.
Has anyone else encountered this? I had been using this since it first came out and some of the utilites and all worked fine, but now that I think of it, hadnt tried to make a back up until last night.
***Side question: Since the beginning when I first learned how to make a backup, I read that you should backup system, data, cust, cache, cdrom and sd(if neccessary). My question is why do we and does it matter if we back up the cust, cache and cdrom parts? Wouldn't these get repopulated anyways at first boot? Would everything work if we just restored system, data and sd (again if neccessary)
Click to expand...
Click to collapse
I don't backup cust or cdrom. I made a backup with Mz's new O.R. yesterday and good thing I backed up ext cause my XDA Special backup would not boot without it. Not much help for ya sorry bud Hope you get it worked out.
@Mioze7Ae
can you please compile a standalone APK installer version of the new open recovery for XT720?
after reading the instructions i noticed, it requires an existing open recovery already installed to apply the above updates
AllGamer said:
@Mioze7Ae
can you please compile a standalone APK installer version of the new open recovery for XT720?
after reading the instructions i noticed, it requires an existing open recovery already installed to apply the above updates
Click to expand...
Click to collapse
I tried but my re-compiled version of the OpenRecovery.apk just FC'd.
Thanks for this Mioze7Ae, this is really sweet!
Am I missing out something here? I don't seem to be able to get the additional OR menu to convert to EXT4. I flashed back to Singapore 2.1 and have rooted. Removed the previous Open Recovery folder but where do I get the OpenRecovery.apk? Do I use back the previous version?
You can use Dexter's OpenRecovery.apk to install Open Recovery & then follow Mioze7Ae's instructions in the OP to update it.
Not sure what effect it even has, but the set timezone seems to be backwards ... Selecting GMT-7 runs /bin/timezone.sh GMT+7 and selecting GMT+7 runs /bin/timezone.sh GMT-7
Hey guys, hope you can provide me with a clearer instruction. I have done exactly as per the instructions and now when I boot into recovery, I don't see the extra option to convert to EXT4. The only things I see in the menu is:
Motorola MILESTONE XT720 Open Recovery
Version 1.46
Created by Skrilax_CZ
Use Volume Up/Down to highlight:
Camera_Mode key to select.
Main Menu
Reboot Menu
Settings
USB Mass Storage Mode
Nandroid
Application Menu
Run Script
Apply Update
Wipe Dalvik Cache
Wipe Data / Factory Reset
Wipe Cache Partition
What am I doing wrong? The phone is still running 2.1 update 1 but it's rooted.
It looks like you're running the original OpenRecovery. You need to replace the OpenRecovery folder on the sdcard with the version from the OpenRecovery-XT720-01.zip.
I think I can see how the instructions about renaming might be confusing so I tweaked the phrasing a little bit.
Thanks for the reply Mioze7Ae but I followed exactly as your instructions. Here's what I've done:
-Flashed singapore_STR_U2_01.1E.0
-Rooted with SuperOneClick
-Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
-Ran OpenRecovery.apk
-Install Recovery System. Install Sucess.
-Recovery Boot and that's where it boots into the old OR.
It's the same if I use the OpenRecovery folder provided by hellmonger in The XT720 XDA Special Final RC2 "Hellmonger Edition"
ranggie4 said:
Thanks for the reply Mioze7Ae but I followed exactly as your instructions. Here's what I've done:
-Flashed singapore_STR_U2_01.1E.0
-Rooted with SuperOneClick
-Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
-Ran OpenRecovery.apk
-Install Recovery System. Install Sucess.
-Recovery Boot and that's where it boots into the old OR.
It's the same if I use the OpenRecovery folder provided by hellmonger in The XT720 XDA Special Final RC2 "Hellmonger Edition"
Click to expand...
Click to collapse
Change this:
Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
Ran OpenRecovery.apk
Install Recovery System. Install Sucess.
To this:
Transferred to SD the the original OpenRecovery.apk file.
Ran OpenRecovery.apk
Install Recovery System. Install Sucess.
Extracted and transferred to SD the new OpenRecovery folder, OpenRecovery.zip
R-D said:
Not sure what effect it even has, but the set timezone seems to be backwards ... Selecting GMT-7 runs /bin/timezone.sh GMT+7 and selecting GMT+7 runs /bin/timezone.sh GMT-7
Click to expand...
Click to collapse
I think it only affects the naming of the nandroid directories, but I'll give it a look. Nice catch!
Thanks Mioze7Ae. The last instruction made it clear. It works now. Thank you so much!!!!!!!!
Mioze7Ae said:
I think it only affects the naming of the nandroid directories, but I'll give it a look. Nice catch!
Click to expand...
Click to collapse
it was like this in all the versions of open recovery...
+++++++++
Mioze, can you also add a wipe battery stats in your modified openrecovery? comes in handy when we flash a new rom or restore a nandroid so we dont have to use the battery calibrating app.
THIS IS NOT CWM FLASHABLE. YOU MUST USE NVFLASH
Edit: It has come to my attention that the CWM is 5.5.0.2. This error has since been corrected. Sorry folks. I'm an idiot.
Hey, i hope this doesn't bother anyone but i compilied and easy zip for NVFLAshing the new CWM.
Thanks Fosser, Team DRH, and the BishopofTechnology (all of whoms work this is, i just put it in one place)
Included is the NVflashable info, the drivers for APX, and the new version of CWM.
Do this @ your own risk, i'm not responsible for any problems (i did test it three times, with each version of CWM, if that counts for anything)
Step 1) Get into APX mode (power + Vol-) [the screen will go black. that's what you want
Here's what the Bish says:
Step 2) Connect the GTab to the PC via the USB cable.
if your PC loads the USB driver and connects to the GTab, SKIP to the “Using NVFlash” section.
if the WINDOWS PC fails to load the driver, just click through Start/Control Panel/Device Manager and find “APX” listed in the devices with a yellow “!” (exclamation point) on the icon.
Select the APX item and find the “Update Driver” button and click it.
When it asks where to search, choose the “local computer” manual selection choice and tell it to Browse to the "Flash USB Drivers".
If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Click to expand...
Click to collapse
Step 3) Run the "nvflash_gtablet.bat"
A CMD prompt will pop up, let it do it's thing (don't stop or unplug during). Give it about a minute or until the CMD prompt disappears. You will the get a message that says "Entering NvFlash recovery mode / Nv3p Server"
At this point is should be okay to restart your tab. I'm running Flashback and had no problems staring up.
If you want to check the new CWM, hold the power + Vol+ when restarting and it should put you into recovery.
CONGRATS! You have the new recovery in preparation for ICS.
Once again, none of this is my work--i just put it into a convenient place.
Thanks again to all the Devs and enthusiasts. You make the Gtab worth having!
Edit 1:
Here is the MD5 check: 3DD468C48A3515E6E5A1C1236FF5068E
Edit 2:
The update recovery is with the normal sized Recovery.
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED
Alright. Download tested and verified. this is deff 5.5.0.4!
sorry again folks
Anyone that is interested in installing this via CWM, I created a CWM flashable verison from fosser2's download. Here is a link to the "normal font" version http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. If you want the "big font" version, all you have to do is open the zip, delete the recovery.img, rename the Team DRM/fosser2/plastikman supplied version to recovery.zip & then add it to the zip.
I have installed this on 2 of my gTabs (one gTab Comb v3.3, the other CCCv8) and did not had any issue installing it this way.
Just a few notes on this version; it does give you the ability to flash from both the internal sd & external sd but uses a different naming convention though..."sdcard" is the name used for the external microsd slot and "internal sd" is what we would normally call sdcard. This version also appears to have fixed the "reboot recovery" bootloop bug of cwm3.0.2.8 (or aleast bypassed it)...when I selected "reboot recovery" it did the same as "reboot system now" (as I was doing this I crossed my fingers hoping it wasn't going to bootloop me...yea..no bootloop).
CWMR is touch capable. You scroll/select in 3 different ways...you can either use the capacitive buttons (which have been remapped to...Search is "select", Home is "scroll up", Menu is "Scroll down" and Back is "back"), you can also use the on screen touch controls (back, up, down & return), or you can also swipe up and down to scroll up/down and swipe sideway to select.
Al
PS:
WARNING: This is the beta6 release. The op page over in the Slatedroid gTablet Laboaratory says that selecting repartition will only repartition the EXTERNAL SD. Two users have reported magic value mismatch after repartioning with this version. plastikman, who created it says he is looking into it.
So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App
why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x
Yes but beware of repartition bug
lsu205 said:
So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Yes you can. I installed on both mine from CWM 3.0.2.8.
Please note the warning I put on my previous post! It probably isn't a good ides to "repartition" with this version until plastikman finds the bug. If you need to repartition (which shouldn't be very oftern) you can always flash the old CWM (or stock recovery) via this version. The recoveries are so small that I keep a copy of each on the tablet just in case.
is the download ok i have try to unzip it and it gives me an error file is not a zip file
Alternate location
wuilly said:
is the download ok i have try to unzip it and it gives me an error file is not a zip file
Click to expand...
Click to collapse
You don't need to unzip it but it does need to be a vailid zip.
Yes, the download is OK from dropbox. I just redownloaded it to my PC & tested the archive. No erors found.
I also put it on mediafire...try this link http://www.mediafire.com/download.php?qg3n084hfu783i2 & see if it's any different for you.
Al
---------- Post added at 09:23 PM ---------- Previous post was at 09:15 PM ----------
jamcar said:
why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x
Click to expand...
Click to collapse
It shouldn't (and didn't for me). Are you sure you didn't select accidentally hit "reboot recovery" instead of "reboot system now" (since you were still in CWM3.0.2.8 untill you reboot)? If you did accidentally hit reboot recovery then it would have put you in a CWM bootloop.
There are 2 ways I've used to fixed a CWM bootloop (yes I've accidentally hit reboot recovery too)..one was is to use nvflash to format partition 7 (MSC) and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery. Formatting MSC is the fastest, but most people I suggest these fixes to choose to do the stock recovery route. If you want detailed instruction for either, let me know.
Al
Great work and thanks for putting in one spot. I'll probably wait till a ICS ROM is released with but must say that this is a great first step till we get it. Cant wait for 10" of ICS....my cappy luvs ICS...
J017373 said:
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED
Click to expand...
Click to collapse
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
aabbondanza said:
and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery.
Click to expand...
Click to collapse
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.
Just installed using CWM recovey and all is well. Just to test I took out my external sd card and when I went to update from sdcard it showed the content of the internal. So I am guessing that if one would decided to partition there internal sdcard they might need to pull there external out first. Then boot up recovery for there updates.
rajeevvp said:
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.
Click to expand...
Click to collapse
Just can't keep up with you raj...why did it take you 2 months to come up with the flashable msc format? Just kidding. I got the format msc from that very thread back in October. Everyone I've run into that is in a CWM loop I've given them the option of formating msc (via nvflash) or flashing stock recovery/then CWM. In every case they have always chosen to flash stock recovery & then flash 3028 (probably because most of the people I help are pretty new to the gTab). I think now they will choose the format via flash method. Thanks for the tip.
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop? I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing). But if that is correct then why does flashing stock recovery, doing a normal boot & then flashing CWM fix the problem too (so I'm guessing I am wrong about my guess)? In any case can you explain why it works that way?
Al
When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.
nobe1976 said:
When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.
Click to expand...
Click to collapse
There are a couple of problems that I noticed with this version of CWM, and which might be responsible for your problems.
1. Roebeet's gtablet.cfg file which almost everybody uses to nvflash back to the 1.2 stock ROM has a bug in the system.img size calculation:
Code:
$ [B]fgrep size= roebeet.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]259715200[/B]
size=0xFFFFFFFFFFFFFFFF
The second last line is the size of the "system" partition and it is misaligned. Every other partition is correctly rounded up to end at the gTablet's NAND flash erase size (128K). Compare with bekit's gtablet.cfg:
Code:
$ [B]fgrep size= bekit.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]209715200[/B]
size=0xFFFFFFFFFFFFFFFF
Here all the partitions--including the last which uses the remaining available space--are rounded up to a 128K boundary. Looks like roebeet just added 50M to bekit's system.img size without rounding it up. The correct value should've been (using roebeet's system.img size as NUM):
Code:
$ [B]( NUM=$((259715200)); echo $(( (NUM + ((1<<17)-1)) & ~((1<<17)-1) )) )
[/B]259784704
--which brings us to problem no. 2:
2. The CWM-5.5.0.4 Beta 6 has a "cmdline" file containing NAND flash partition sizes which overrides the user's partition sizes read from the Partition Table. This is fine if the sizes are the same, but, a bad idea otherwise. In this CWM, the cmdline file sets "system" to be what we calculated above (259784704) but, which disagrees with the size in the PT (259715200).
Use the zip file in the attachment to empty the cmdline file out. This will cause the partition sizes to be read from the PT on the NAND flash.
My recommendation is that:
1. Users nvflash to 1.2 using either
a) the attached gtablet.cfg which has all the partitions correctly ending at 128K boundaries or
b) bekit's original gtablet.cfg. (This option is what I recommend. The "cache" partition is used for OTA updates and if it is much smaller than the "system" partition--like in roebeet's gtablet.cfg, then, depending on the size of the image, automatic updates might fail.)
2. Install the new CWM-5.5.0.4 Beta 6, and then immediately flash the attached zip file to empty out the cmdline file.
aabbondanza said:
why did it take you 2 months to come up with the flashable msc format?
Click to expand...
Click to collapse
Didn't think adb was going to be difficult for people who have no problem with nvflash...
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop?
Click to expand...
Click to collapse
I looked at this sometime back and its complicated. I'll make a post on this later this weekend after I've looked at VS's newly posted 1.2 kernel patch.
I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing).
Click to expand...
Click to collapse
For "mysterious bit" substitute "string", but, you are correct.
Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al
CWMR5504 Fixed
aabbondanza said:
Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al
Click to expand...
Click to collapse
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al
aabbondanza said:
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al
Click to expand...
Click to collapse
Thank you. This worked well for me, since I was not inclined to do the nvflash thing. I was able to boot back into my Beasty+Clemsyn rom without incident. Tested by rebooting again and was able to boot into the rom with no issues.
aabbondanza said:
He switched from using pershoot's kernel (which required the command line) to using the stock kernel.
Click to expand...
Click to collapse
... and in the process also brought back the always-reboots-into-recovery problem, right? Whereas with the pershoot kernel "Reboot Recovery" would just reboot the tablet into the ROM?
BTW, the pershoot kernel doesn't need a cmdline file: craigacgomez's CWM-4.0.1.5 too has a pershoot kernel and its cmdline file is empty. As I mentioned before: if the cmdline file is empty, then the bootloader will construct a cmd line for the kernel.
to install the cwm recovery do I simply transfer the zip to the internal sdcard and flash zip from sdcard as if it were a rom?
Hi.
I need help i want to know how to install JELLYBLAST V3.0.3 on my galaxy y pro GT-B5510
i read on this post JELLYBLAST V3 that with some modification it can be installed on Galaxy Y Pro
THANKS
nedo113 said:
Hi.
I need help i want to know how to install JELLYBLAST V3.0.3 on my galaxy y pro GT-B5510
i read on this post JELLYBLAST V3 that with some modification it can be installed on Galaxy Y Pro
THANKS
Click to expand...
Click to collapse
1) download jellyblast + 4 OTA + CWM
2) open jellyblast zip ed delete "boot.img"
3) copy rom + 4 ota + CWM inside SD
4) reboot in recovery mode (vol up + home + power) and select CWM.zip
5) Backup your rom via CWM (backup and restore) [REQUIRED STEP! This take some time but you can restore previous rom and all you had before (apps, calls... everithing) in case of problems!]
6) Run " wipe data/factory reset" and " wipe cache partition" ("wipe data/factory reset" delete everithing from your device!)
7) Run "install zip from sdcard" > "choose zip"
8) Select jellyblast rom > "yes"
9) Than "reboot system now"
For ota:
1) Reboot in recovery mode (no need flash CWM again...)
2)Select "apply update"
4) choose first OTA
5) reboot
6) same for other ota (pass 1 to 5)
Install OTA update in number order (OTA 1, OTA 2...)
(Thanks to Roby293)
I tried this steps yesterday.
Full working for me, the rom is very smooth & fast.
Just some force stop to Phone process and PIN Dial pad not working.
Some people say fix this flashing "modem" & "csc" via ODIN.
But i'm not really sure.
Sorry for delay. Hope this help someone else.
Thanks
ciccione said:
1) download jellyblast + 4 OTA + CWM
2) open jellyblast zip ed delete "boot.img"
3) copy rom + 4 ota + CWM inside SD
4) reboot in recovery mode (vol up + home + power) and select CWM.zip
5) Backup your rom via CWM (backup and restore) [REQUIRED STEP! This take some time but you can restore previous rom and all you had before (apps, calls... everithing) in case of problems!]
6) Run " wipe data/factory reset" and " wipe cache partition" ("wipe data/factory reset" delete everithing from your device!)
7) Run "install zip from sdcard" > "choose zip"
8) Select jellyblast rom > "yes"
9) Than "reboot system now"
For ota:
1) Reboot in recovery mode (no need flash CWM again...)
2)Select "apply update"
4) choose first OTA
5) reboot
6) same for other ota (pass 1 to 5)
Install OTA update in number order (OTA 1, OTA 2...)
(Thanks to Roby293)
I tried this steps yesterday.
Full working for me, the rom is very smooth & fast.
Just some force stop to Phone process and PIN Dial pad not working.
Some people say fix this flashing "modem" & "csc" via ODIN.
But i'm not really sure.
Sorry for delay. Hope this help someone else.
Click to expand...
Click to collapse
Thanks my friend full working for me too
danhtien088 said:
helllo
Click to expand...
Click to collapse
this is not chatting site pal to say hello....ask q if u have any....
Hi! This rom works in GT-B5510 with all OTA Updates installed? Another question; I have a GT-B5510L You guys think the rom will work?
Suuichi said:
Hi! This rom works in GT-B5510 with all OTA Updates installed? Another question; I have a GT-B5510L You guys think the rom will work?
Click to expand...
Click to collapse
Yup it works with that device
Please press thanx if I am useful to you
ciccione said:
1) download jellyblast + 4 OTA + CWM
2) open jellyblast zip ed delete "boot.img"
3) copy rom + 4 ota + CWM inside SD
4) reboot in recovery mode (vol up + home + power) and select CWM.zip
5) Backup your rom via CWM (backup and restore) [REQUIRED STEP! This take some time but you can restore previous rom and all you had before (apps, calls... everithing) in case of problems!]
6) Run " wipe data/factory reset" and " wipe cache partition" ("wipe data/factory reset" delete everithing from your device!)
7) Run "install zip from sdcard" > "choose zip"
8) Select jellyblast rom > "yes"
9) Than "reboot system now"
For ota:
1) Reboot in recovery mode (no need flash CWM again...)
2)Select "apply update"
4) choose first OTA
5) reboot
6) same for other ota (pass 1 to 5)
Install OTA update in number order (OTA 1, OTA 2...)
(Thanks to Roby293)
I tried this steps yesterday.
Full working for me, the rom is very smooth & fast.
Just some force stop to Phone process and PIN Dial pad not working.
Some people say fix this flashing "modem" & "csc" via ODIN.
But i'm not really sure.
Sorry for delay. Hope this help someone else.
Click to expand...
Click to collapse
Hi friend
thanks for your help but i need it one more time
I do not get to use symbols, numbers on the keyboard only letters
to put numbers I have to use the onscreen keyboard but the screen is too small for typing with it so i would like fix it
do you have any idea??
i use it in spanish language
nedo113 said:
Hi friend
thanks for your help but i need it one more time
I do not get to use symbols, numbers on the keyboard only letters
to put numbers I have to use the onscreen keyboard but the screen is too small for typing with it so i would like fix it
do you have any idea??
i use it in spanish language
Click to expand...
Click to collapse
I'm having the same problem, and another ones... the customized keys (1 and 2), Backspace and Enter keys doesn't work, the camera can't be used in 3.15MP and most of apps doesn't install, just keep saying "downloading"
for problem with device/hardware keyboard, please copy keylayout and keychars from your stock rom into jellyblast (System/Usr)
dont delete the existing folder in jellyblast, just replace the existing files. the flash the modded jellybean rom again.
your keyboard will be working, overall keyboard function is ok, but i cant get symbol button working yet..
im using this, almost perfect but phone application looks bad because of the landscape view of our phone.
for camera, you can replace it with camera.apk from your stock rom. (system/app folder)
update: just wanna share, cant copy camera from stock rom, becuase stock is odexed. so, to get 3.2mp camera working, i downloaded ported jellyblast rom for galaxy mini pop plus, extracted it,copy camera.apk from system/apps and install on your phone.
suuchi, for 'apps doesnt install' problem, u need to remove a2sd or disable it before flashing the rom.
found today out position sensor not working properly..horizontal calibration wont help
update: got it working already, need to copy sensor file system/bin and system/lib folder from stock rom.
xshiro said:
for problem with device/hardware keyboard, please copy keylayout and keychars from your stock rom into jellyblast (System/Usr)
dont delete the existing folder in jellyblast, just replace the existing files. the flash the modded jellybean rom again.
your keyboard will be working, overall keyboard function is ok, but i cant get symbol button working yet..
im using this, almost perfect but phone application looks bad because of the landscape view of our phone.
for camera, you can replace it with camera.apk from your stock rom. (system/app folder)
update: just wanna share, cant copy camera from stock rom, becuase stock is odexed. so, to get 3.2mp camera working, i downloaded ported jellyblast rom for galaxy mini pop plus, extracted it,copy camera.apk from system/apps and install on your phone.
suuchi, for 'apps doesnt install' problem, u need to remove a2sd or disable it before flashing the rom.
Click to expand...
Click to collapse
I solved the symbol's problem using an app called 'Game Keyboard'. With the compatibility options the buttons will work properly. Can you upload the camera.apk? Thanks a lot!
Suuichi said:
I solved the symbol's problem using an app called 'Game Keyboard'. With the compatibility options the buttons will work properly. Can you upload the camera.apk? Thanks a lot!
Click to expand...
Click to collapse
ooh..thanks bro
i have attached camera apk here
xshiro said:
found today out position sensor not working properly..horizontal calibration wont help
update: got it working already, need to copy sensor file system/bin and system/lib folder from stock rom.
Click to expand...
Click to collapse
Hi! I've been using this rom for 3 days, it works really fast and smooth. I just need to fix the sensor's problem. Can you tell me which files I need to copy? Thanks!
Suuichi said:
Hi! I've been using this rom for 3 days, it works really fast and smooth. I just need to fix the sensor's problem. Can you tell me which files I need to copy? Thanks!
Click to expand...
Click to collapse
im not sure which sensor file that responsible for screen position, so i just copied all sensor related file ..hehe...
the files are
system/bin
- atx
-memsicd
system/lib
-libacc.so
-libsensorservice.so
-libaccsensorcal.so
-libaccelcal.so
-libaccsensorcaltest.so
what i did was, using the root explorer (setting - mount / and /system as writable is checked) delete all the existing sensor file, then copy paste, because the explorer cannot replace the existing files.
then i set the permission back..to enable 'read write exec' for all user group...
then restart the phone..
you will notice horizontal calibration app wont show the correct position (maybe you need to replace horizontal calibration app also), but your sensor is working by using sensor diagnostic (dial *#0*#)
bro do have any solution for dialer/phone app not displayed correctly?
xshiro said:
im not sure which sensor file that responsible for screen position, so i just copied all sensor related file ..hehe...
the files are
system/bin
- atx
-memsicd
system/lib
-libacc.so
-libsensorservice.so
-libaccsensorcal.so
-libaccelcal.so
-libaccsensorcaltest.so
what i did was, using the root explorer (setting - mount / and /system as writable is checked) delete all the existing sensor file, then copy paste, because the explorer cannot replace the existing files.
then i set the permission back..to enable 'read write exec' for all user group...
then restart the phone..
you will notice horizontal calibration app wont show the correct position (maybe you need to replace horizontal calibration app also), but your sensor is working by using sensor diagnostic (dial *#0*#)
bro do have any solution for dialer/phone app not displayed correctly?
Click to expand...
Click to collapse
Thanks! You are awesome! I tried to modify or replace the phone.apk, but didn't work... If I find a solution, I will post it here!
Suuichi said:
Thanks! You are awesome! I tried to modify or replace the phone.apk, but didn't work... If I find a solution, I will post it here!
Click to expand...
Click to collapse
ok,..currently using exdialer
now occasionally will have problem with flickering screen with some apps...suspect power management issue...
HELP PLZ
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
---------- Post added at 03:25 AM ---------- Previous post was at 02:47 AM ----------
xshiro said:
ok,..currently using exdialer
now occasionally will have problem with flickering screen with some apps...suspect power management issue...
Click to expand...
Click to collapse
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
Wondering if a clockwork back up could get me back the kernel?
zip not opening
brothers whenever i try to install zip fro cwm , it gives error like zip opening failed.
i hv installed the zip package of jelly blast without deleting boot.img nd it didnt give any error while opening zip but after installation i was facing half screen error.
so i m assuming that when i delete boot.img nd re zip the file at that point i m doing some mistake.
is thr some specific zip format or compression ratio which i should have to consider while zipping it?
far4z said:
brothers whenever i try to install zip fro cwm , it gives error like zip opening failed.
i hv installed the zip package of jelly blast without deleting boot.img nd it didnt give any error while opening zip but after installation i was facing half screen error.
so i m assuming that when i delete boot.img nd re zip the file at that point i m doing some mistake.
is thr some specific zip format or compression ratio which i should have to consider while zipping it?
Click to expand...
Click to collapse
When you download the Rom zip do not unzip it... Open the rom zip in winrar or 7zip and then delete the boot.img file from the compressed zp
Mariofrith said:
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
---------- Post added at 03:25 AM ---------- Previous post was at 02:47 AM ----------
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
Wondering if a clockwork back up could get me back the kernel?
Click to expand...
Click to collapse
yes you can. if you have backup your stock rom using cmw, you know the combination key to recovery? press vol up + home + power on
then select update zip from sdcard, select cmw.zip -> restore
or you can take out your sdcard copy the correct jellyblast zip, with deleted boot.img. reflash again, bro make sure you have disable/removed a2sd for smooth installation
TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18
Thanks!
is it functional for backing up our system in TWRP?
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive
Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...
Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.
Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!
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.