Related
Ok, so there seems to be some issues with installing the recent 4.2.1 OTA update with custom recoveries (ie: CWM or TWRP). I ran into this issue myself, and I've seen many other posts with similar problems. I've found the solution and explained it in multiple threads, but due to the nature of the issue, I thought it deserved it's own thread to make sure everyone is aware of the problem and the workaround.
Details:
The 4.2.1 OTA update comes in two flavors - nakasi and nakasig. The former is for WiFi devices (8, 16, 32), and the latter is for 3G devices. In turn, they each have their own device types - grouper and talapia, respectively. While the hardware differences between the WiFi and 3G models is negligible, and most things are interchangeable (ie: kernels, recoveries, etc.), the updates are NOT, and you need to pick the correct one for your platform. For the 3G models, this means the 'nakasig' version.
However, the first thing the OTA update does is validate the integrity of the system. In addition to checking about 200 files in the /system partition, it also looks at the device itself. Specifically:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2/JOP40C/527662:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2.1/JOP40D/533553:user/release-keys");
assert(getprop("ro.product.device") == "talapia" ||
getprop("ro.build.product") == "talapia");
While the first part checks the build.prop file to see what the "ro.build.fingerprint" has defined, the latter (bolded) assert examines what the RECOVERY says the system is. This is where the problem lies. AFAIK, there are no 'talipia' versions of CWM or TWRP. All 3G users running custom recoveries are using the 'grouper' (ie: Wi-Fi only) version. And this is fine 99% of the time. But this is the 1% of the time when they are not compatible. As a result, when the updater script checks recovery, and is told that the system is 'grouper', it aborts the update.
I ran into this issue on both the latest versions of TWRP and CWM. I wasn't sure why, since I thought it just looked at build.prop which was OK. After speaking with oldblue910, he explained that it is getting that information not from build.prop, but from the custom recovery, which is why the update was failing (thanks to oldblue910 for the info!).
SO, I was left with one of two options. I could either restore the stock talipia recovery or modify the update zip to ignore this information. I chose the latter. I'm not sure why Google decided to even but this redundant check in place, since the build.prop fingerprint check should suffice to validate the hardware. Not to mention that the next part of the update is to assert check the majority of files in 'system' anyway, which would fail if it wasn't a 3G device. In any case, by removing the above bolded lines out of the updater-script, my tablet was able to be successfully updated to 4.2.1.
Since many other XDA users run custom recoveries, it is safe to say many other users will run into this issue as well. So I put my custom update online for anyone else to use.
You can download it here:
http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
MD5SUM: b0adff6a04ca2ca6234a9678476d329e
A couple notes:
1) This update zip is completely identical to the Google version, outside of the talipia check removed.
2) This update should ONLY BE USED ON 3G NEXUS 7 MODELS. It will NOT work on Wi-Fi only versions.
3) All the other asserts are left in-tact, as they should be. So your 'system' needs to be mostly stock. It checks and patches about 200 files, and if any of them are modified, removed, frozen, etc., the update will fail.
4) The OTA update does NOT check or update the bootloader or kernel, so modifications or non-4.2-stock versions in those areas are fine. However, as stated in #3, mostly everything else should be stock.
5) If the update fails on a specific assert, it will explain what the problem is (ie: the specific apk or odex file). You will need to fix that before proceeding. If you run into an issue and require assistance, you will need to explain the exact error message.
6) As this is almost completely stock OTA update, you WILL lose root/custom recovery unless you take precautions to prevent them from being overwritten. To preserve root, you can use RootKeeper or a similar app to back it up. The latest version of CWM also will warn you if root is lost and apparently restore it for you. For the recovery side of things, the update puts that recovery-recovery file on the system. You can either manually remove it via adb shell (BEFORE REBOOTING AFTER THE UPDATE), or in CWM (and possibly TWRP's case), it should warn you that you might lose custom recovery after the update and ask if you want it to fix it for you (say yes).
Hopefully this helps others who ran into the same error as me. Enjoy!
phonic said:
Ok, so there seems to be some issues with installing the recent 4.2.1 OTA update with custom recoveries (ie: CWM or TWRP). I ran into this issue myself, and I've seen many other posts with similar problems. I've found the solution and explained it in multiple threads, but due to the nature of the issue, I thought it deserved it's own thread to make sure everyone is aware of the problem and the workaround.
Details:
The 4.2.1 OTA update comes in two flavors - nakasi and nakasig. The former is for WiFi devices (8, 16, 32), and the latter is for 3G devices. In turn, they each have their own device types - grouper and talapia, respectively. While the hardware differences between the WiFi and 3G models is negligible, and most things are interchangeable (ie: kernels, recoveries, etc.), the updates are NOT, and you need to pick the correct one for your platform. For the 3G models, this means the 'nakasig' version.
However, the first thing the OTA update does is validate the integrity of the system. In addition to checking about 200 files in the /system partition, it also looks at the device itself. Specifically:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2/JOP40C/527662:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2.1/JOP40D/533553:user/release-keys");
assert(getprop("ro.product.device") == "talapia" ||
getprop("ro.build.product") == "talapia");
While the first part checks the build.prop file to see what the "ro.build.fingerprint" has defined, the latter (bolded) assert examines what the RECOVERY says the system is. This is where the problem lies. AFAIK, there are no 'talipia' versions of CWM or TWRP. All 3G users running custom recoveries are using the 'grouper' (ie: Wi-Fi only) version. And this is fine 99% of the time. But this is the 1% of the time when they are not compatible. As a result, when the updater script checks recovery, and is told that the system is 'grouper', it aborts the update.
I ran into this issue on both the latest versions of TWRP and CWM. I wasn't sure why, since I thought it just looked at build.prop which was OK. After speaking with oldblue910, he explained that it is getting that information not from build.prop, but from the custom recovery, which is why the update was failing (thanks to oldblue910 for the info!).
SO, I was left with one of two options. I could either restore the stock talipia recovery or modify the update zip to ignore this information. I chose the latter. I'm not sure why Google decided to even but this redundant check in place, since the build.prop fingerprint check should suffice to validate the hardware. Not to mention that the next part of the update is to assert check the majority of files in 'system' anyway, which would fail if it wasn't a 3G device. In any case, by removing the above bolded lines out of the updater-script, my tablet was able to be successfully updated to 4.2.1.
Since many other XDA users run custom recoveries, it is safe to say many other users will run into this issue as well. So I put my custom update online for anyone else to use.
You can download it here:
http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
MD5SUM: b0adff6a04ca2ca6234a9678476d329e
A couple notes:
1) This update zip is completely identical to the Google version, outside of the talipia check removed.
2) This update should ONLY BE USED ON 3G NEXUS 7 MODELS. It will NOT work on Wi-Fi only versions.
3) All the other asserts are left in-tact, as they should be. So your 'system' needs to be mostly stock. It checks and patches about 200 files, and if any of them are modified, removed, frozen, etc., the update will fail.
4) The OTA update does NOT check or update the bootloader or kernel, so modifications or non-4.2-stock versions in those areas are fine. However, as stated in #3, mostly everything else should be stock.
5) If the update fails on a specific assert, it will explain what the problem is (ie: the specific apk or odex file). You will need to fix that before proceeding. If you run into an issue and require assistance, you will need to explain the exact error message.
6) As this is almost completely stock OTA update, you WILL lose root/custom recovery unless you take precautions to prevent them from being overwritten. To preserve root, you can use RootKeeper or a similar app to back it up. The latest version of CWM also will warn you if root is lost and apparently restore it for you. For the recovery side of things, the update puts that recovery-recovery file on the system. You can either manually remove it via adb shell (BEFORE REBOOTING AFTER THE UPDATE), or in CWM (and possibly TWRP's case), it should warn you that you might lose custom recovery after the update and ask if you want it to fix it for you (say yes).
Hopefully this helps others who ran into the same error as me. Enjoy!
Click to expand...
Click to collapse
I compiled a CWM image for tilapia, so now users can flash updates and roms for their device without trying to by-pass the safety checks. With everyone recommending flashing grouper recovery, people are going to keep flashing grouper roms and wonder why things aren't working correctly.
The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
Better to have proper recovery for our (unique) device instead of a grouper port. The CWM image is not touch, the touch sources are not open source and koush's online builder is not producing a working image at this time. I ported one by hand, but it is too buggy to release.
I'll add twrp to the post sometime later.
mateorod said:
I compiled a CWM image for tilapia, so now users can flash updates and roms for their device without trying to by-pass the safety checks. With everyone recommending flashing grouper recovery, people are going to keep flashing grouper roms and wonder why things aren't working correctly.
Better to have proper recovery for our (unique) device instead of a grouper port. The CWM image is not touch, the touch sources are not open source and koush's online builder is not producing a working image at this time. I ported one by hand, but it is too buggy to release.
I'll add twrp to the post sometime later.
Click to expand...
Click to collapse
Thanks, that's definitely a better solution versus a work around.
Though the safety check bypassed in the OP wouldn't cause any issues since it was redundant and unnecessary. The OTA update already checks build.prop for the model info and all the apks/odexes it updates, so it would be impossible to flash it on a non-compatible device. But you raise a very valid point about incorrect ROMs and other things. The 3G unit probably needs it's own forum.
Did you have to make any real modifications to CWM outside of changing grouper to talapia?
The 3G unit probably needs it's own forum.
Click to expand...
Click to collapse
Its already done here; http://forum.xda-developers.com/forumdisplay.php?f=2022
Ather said:
Its already done here; http://forum.xda-developers.com/forumdisplay.php?f=2022
Click to expand...
Click to collapse
Woohoo! Thanks.
I had some issues when I did the update. It gave me some errors, and aborted, but then I found a link that had the update and I got it to update. This happened on my n4 and n73g. Well, for some reason, the recoveries got deleted so I had to reinstall them. I was able to use the goo manager to restore TWRP on my N4, but it wasn't working on my N7 so I had to side load it. After this, I noticed that google now wasn't working on my n4, and the volume rocker on my n7 had some issues. I went in and wiped the cache and dalvik cache and rebooted. Google now works on my N4, and while the volume gets adjusted on my N7, it won't make the beep every time I push up or down on the rocker indicating the volume level. I haven't noticed any other issues, but I haven't really delved into my devices. I may try to do a factory wipe and return everything to stock just to see what went wrong in the first place and to see if I can do anything different I still can't figure out how to get ADB running on my computer, so yes I used one of the tool kits to load everything. I know the OP's position on tool kits, but I just can't figure out how to get ADB running manually, AND it takes so long to download and install everything unless I am installing things I don't even need.
Nexus 7 takju firmware update
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Do you have the Galaxy Nexus or Nexus 7? If Galaxy Nexus, you of course would want to check those forums. As for the updates, you should normally see a notification alerting you of the update, but you can also check for it in settings/about phone/system updates. Otherwise the appropriate forum for your device will have links to the update files. Good luck!
lil help please
I updated to 4.2.1 with the OTA zip file using TWRP and voodoo root keeper installed. It flashed just fine. Rebooted with update. My root access is funky though. SuperSU is still there and I can access root file threw root explorer but I can't mount it as writable and when I install a new app that needs root access it never asks for it. Does superSU need to be updated? There is no update available for it.
Vlad7777 said:
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Click to expand...
Click to collapse
Is your device rooted? Is this your first android device? You will get a little notification in the notification bar at the top saying your deivce has an update.. If you have not rooted, you will receive the first OTA in a day or two that will go from JVP15S to JOP40C. Then later, you will receive the update for JOP40D. Some people have had success at forcing the update by going to settings, apps, all, google framework services, and selecting force stop then clearing the data. You then go back into settings, about device, check for updates and check for update.
Vlad7777 said:
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Click to expand...
Click to collapse
The N73G ships with an interim 4.2 build, which is JVP15S. There are some significant differences between this and JOP40C, which is the first update you will get out of the box. I imagine 4.2 wasn't fully finalized prior to hardware production, and they didn't want to hold it up until they were ready (wise choise!). In my case, within an hour after opening my N73G and turning it on, I had the 40C update notification. I applied this prior to rooting/modding/etc. ONLY after you are on 40C can you get the upgrade to 40D (4.2.1). Google pushes out incremental patch updates, so you can't skip a version.
So you have two options:
1) Apply update #1 and wait for #2 and then root/etc.
2) If you don't want to wait, and your device is still basically brand new and not setup (too much), AND assuming you want to root, customize, etc., just download the 4.2.1 system image from Google and fastboot flash it. You'll need to unlock the bootloader anyway, which will wipe your system, so now's a perfectly good time to do everything at once. Unlock bootloader, flash 4.2.1 stock (40D FULL IMAGE), flash custom recovery, install su zip, install any other mods (which is limited really to basic stuff and a custom kernel right now), enjoy.
Andoid 4.2.1 update
adamhlj said:
Is your device rooted? Is this your first android device? You will get a little notification in the notification bar at the top saying your deivce has an update.. If you have not rooted, you will receive the first OTA in a day or two that will go from JVP15S to JOP40C. Then later, you will receive the update for JOP40D. Some people have had success at forcing the update by going to settings, apps, all, google framework services, and selecting force stop then clearing the data. You then go back into settings, about device, check for updates and check for update.
Click to expand...
Click to collapse
Thanks!
It is my first Android device.
I am trying to root it (unsuccessfully).
I was able to get the FASTBOOT unlock - but cannot root because of the drivers interface...
I did update the firmware by forcing via framework system. Had to do in two steps as it only upgrades one generation at a time.
By the way - I had the "takju" - now it is "tilapia" after "official OTA update.
I hope to get the rooting problem resolved - all instructions on the net are for older ROMs and I already screwed up my work laptop installing obsolete PDANET drivers which replaced the original drivers - so my device manager which originally saw my Nexus 7 as "Nexus 7" now sees it as "Android Phone Device". I do not know how to recvert back.
So now I am going to try my other laptop for rooting.
Hopefully I could find just a "professional step by step procedure - unlike many that I found on the net. Many people just happy to get on YouTube to show themselves off but the advice is half ass.
Thanks again for your help though I am half way through.
Best regards
Vlad7777 said:
Thanks!
It is my first Android device.
I am trying to root it (unsuccessfully).
I was able to get the FASTBOOT unlock - but cannot root because of the drivers interface...
I did update the firmware by forcing via framework system. Had to do in two steps as it only upgrades one generation at a time.
By the way - I had the "takju" - now it is "tilapia" after "official OTA update.
I hope to get the rooting problem resolved - all instructions on the net are for older ROMs and I already screwed up my work laptop installing obsolete PDANET drivers which replaced the original drivers - so my device manager which originally saw my Nexus 7 as "Nexus 7" now sees it as "Android Phone Device". I do not know how to recvert back.
So now I am going to try my other laptop for rooting.
Hopefully I could find just a "professional step by step procedure - unlike many that I found on the net. Many people just happy to get on YouTube to show themselves off but the advice is half ass.
Thanks again for your help though I am half way through.
Best regards
Click to expand...
Click to collapse
I think you are either looking at really bad guides or simply making the rooting process much harder on yourself.
While some Android devices have more complicated unlocking/rooting/etc. requirements, that is not the case with Nexus devices - certainly not the Nexus7. The process couldn't be more simple. If you've already unlocked the bootloader, you are 1/3 of the way there. All you need to do is copy over a compatible "su" app zip to the device, install or run a custom recovery, install the su zip and voila - rooted.
If you already have fastboot running, that's the only tool you need. Download a custom recovery (CWM or TWRP) from a thread in this forum that is compatible, reboot into bootloader mode and install it:
fastboot flash recovery <recovery.img>
Then reboot into recovery mode (you can do this from bootloader), and you should be in CWM/TWRP. Then you simply install the SU zip using the menu on the screen.
It's a very simple process and does not require a special toolkit or anything like that.
phonic said:
I think you are either looking at really bad guides or simply making the rooting process much harder on yourself.
While some Android devices have more complicated unlocking/rooting/etc. requirements, that is not the case with Nexus devices - certainly not the Nexus7. The process couldn't be more simple. If you've already unlocked the bootloader, you are 1/3 of the way there. All you need to do is copy over a compatible "su" app zip to the device, install or run a custom recovery, install the su zip and voila - rooted.
If you already have fastboot running, that's the only tool you need. Download a custom recovery (CWM or TWRP) from a thread in this forum that is compatible, reboot into bootloader mode and install it:
fastboot flash recovery <recovery.img>
Then reboot into recovery mode (you can do this from bootloader), and you should be in CWM/TWRP. Then you simply install the SU zip using the menu on the screen.
It's a very simple process and does not require a special toolkit or anything like that.
Click to expand...
Click to collapse
Thank you for your reply and advice.
How do I place the "su zip" in the device and into which directory - I can try download directly to Nexus but needs to know where to place it.
Also what are "CWM" or "TWRP" And where do I place them for custom recovery procedure.
I apologize for my ignorance but Android is a complete new experience for me.
Vlad7777 said:
Thank you for your reply and advice.
How do I place the "su zip" in the device and into which directory - I can try download directly to Nexus but needs to know where to place it.
Also what are "CWM" or "TWRP" And where do I place them for custom recovery procedure.
I apologize for my ignorance but Android is a complete new experience for me.
Click to expand...
Click to collapse
You can place the "su zip" anywhere you like on the internal storage. When you get into custom recovery (CWM or TWRP), you can select "Install ZIP" (or something along those lines) and it will bring up a file system explorer that will let you select the one you want to install.
CWM and TWRP are both custom recoveries. They replace the stock, and very useless, recovery and give you many more advanced features. Things like flashing zip files, making nandroid backups, etc. You need to flash them to your "recovery" partition. It's a very easy process, but will require some specialized software. There are many guides and toolkits (if that's what you want to use) online. Just make sure you use the Talipia recovery (which exists now in the 3G forum).
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Hardley97 said:
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Click to expand...
Click to collapse
Here's my advice, go back to stock again,the LG flash tool. When that completes, use Freedom Tools (its in Development) and use ioroot25 (link is in the aforementioned thread) to root device. Then use Freedom Tool to install twrp. I've used it many times and never had a problem. Re-download cm rom (perhaps bad download) and flash in twrp. I would suggest using a more current twrp (start with 2.7, DL newest twrp, flash, reboot recovery) then flash cm. Let me know how it goes!
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Hardley97 said:
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Click to expand...
Click to collapse
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
njstein said:
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
Click to expand...
Click to collapse
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Hardley97 said:
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Click to expand...
Click to collapse
Dude, I'm sorry for not reading closer to begin with, but ya, you're trying to flash a JB rom with a KK recovery. 2.7 and up are for kk only. I'm so sorry...
Did you flash a gapps zip with Beanstalk? Did you do a completely clean install?
If you still want to flash a 10.2 cm you're going to have to find the appropriate recovery, and there I'm of no use since I entered this phone on kk and don't know anything about its jb history. Also don't know about the USB tether part either (I don't use it) so you're probably going to have to do some searching, flashing, and experimentation.
But bright side is we've figured out why you couldn't flash the cm rom. Either stay on kk or above, or start scrolling through the dev section looking for jb recovery...
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Hardley97 said:
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Click to expand...
Click to collapse
So glad it worked for you and you're up and running!
Nah, bro, I'm good. Give it to the devs, they deserve it. Giving knowledge through experience is what xda is all about, pass it on when you can. Thank you, though!
Afternoon all!
Have been pulling my hair out for almost a week now trying to get this TF701 updated. I'm stuck trying to get the bootloader updated at this point. Curently version 10.6.1.14.10 I have been able to get the device unlocked and curently have twrp 2.8.7.2 installed. Before installing twrp I tried just about every rom update on asus website and the system wouldn't pick the file up as an update. Now that I have twrp installed I get an error "error executing updater binary in zip....." I am guessing that is because the bootloader is on an old version.
Can someone please give me a little guidance to get this updated.... any help is greatly appreciated.
Thank you.
sattech200 said:
Afternoon all!
Have been pulling my hair out for almost a week now trying to get this TF701 updated. I'm stuck trying to get the bootloader updated at this point. Curently version 10.6.1.14.10 I have been able to get the device unlocked and curently have twrp 2.8.7.2 installed. Before installing twrp I tried just about every rom update on asus website and the system wouldn't pick the file up as an update. Now that I have twrp installed I get an error "error executing updater binary in zip....." I am guessing that is because the bootloader is on an old version.
Can someone please give me a little guidance to get this updated.... any help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Installing TWRP should automatically update your ASUS boot loader to the latest version. Are you sure that you have the tf701 and not another version, tablet? Also, which flavor or region of the tablet do you have US, WW? I am guessing that you downloaded TWRP and forced it to install through fastboot mode...?
DOH!!! Boy do I feel like a total moron! Went to check/confirm model number and it is indeed a TF700, not a TF701 like I swear I seen at first. Anyways it does look like I have the latest asus updates so all is good. I was also able to just successfully install Zombi-pop 5.1.1 and it's booting now for the first time. I have the US sku and I did use fastboot to load twrp.
boy I can't believe this....thank you very much for pointing out what I've over looked for a week now.
Can you click on the thanks button, it helps, Thanks!
lost and confused......
sattech200 said:
Afternoon all!
Have been pulling my hair out for almost a week now trying to get this TF701 updated. I'm stuck trying to get the bootloader updated at this point. Curently version 10.6.1.14.10 I have been able to get the device unlocked and curently have twrp 2.8.7.2 installed. Before installing twrp I tried just about every rom update on asus website and the system wouldn't pick the file up as an update. Now that I have twrp installed I get an error "error executing updater binary in zip....." I am guessing that is because the bootloader is on an old version.
Can someone please give me a little guidance to get this updated.... any help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Hi. I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. If possible maybe direct me where I could get a step by step guide with the links to the correct downloads.
Kind Regards
Rob
Hello, my name is tito. I wanted to know how to install the xposed framework for Android 5.1. I've downloaded the apk, i've downloaded the zip files, i tried to use twrp recovery to flash the files but i cant install it. I choose the most recent version, then i go to install and it downloads the file, then it give's me a message saying: Ensure the partition listed below is the correct one for your device. If you do not verify this then you risk bricking. On some devices it is impossible to flash recovery while in android. If flashing doesn't work for you then please flash recovery a different way. /dev/block/bootdevice/by-name/recovery. And it give's me two options: NO-YES. If i choose no, it doesn't do anything, if i choose yes it says me: Please wait: Flashing and recovery or something like that. Then it give's me an error saying: Something is wrong: Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now? If i choose CANCEL it doesn't do anything, if i choose OK it reboots my device and it appears the android logo with a warning icon on him. I thought my phone was broken. I turned off it and it tried to turn on it again, and thanks god that it wasnt broken. I've tried a lot of things. My phone is an LG Leon (NOT LTE) (Its rooted) and i suspect that the reason of this is that this app makes me say to it what phone i have, and i pick LG Leon LTE because there isn't anyone that says only LG Leon. Please help me. I just want to have the Xposed installer. When i had kitkat it was pretty easy. I've never used this things of rom's and custom recoverys, i dont understand anything of that. I made a Nandroid Backup. I have BusyBox installed. Can this be happening because i dont have the bootloader unlocked? If it's that please explain me how can i unlock it, because there's not too many tutorials about my phone. If theres another way to install the Xposed framework, or there's another custom recovery i can use, please tell me.
Thank you all. Tito
do you use the right version? there are 3.arm, arm64, arm86. also do you have mounted your system?
kos25k said:
do you use the right version? there are 3.arm, arm64, arm86. also do you have mounted your system?
Click to expand...
Click to collapse
Yes, i've read a post that says that you must check your phone's proccessor so you can know what version you must choose,the .arm is for standard proccessors, arm64 is for 64bit proccessors, and arm86 is for intel proccessors or that's what i understood, the proccessor is ARM7v 32bits, thats what i wanted to install, but that's not the problem. The problem is that i can't install the TWRP Manager to flash the previously mentioned files, because of an error, if i fix it, i could know if the rest of the proccess is right. About that "mounted system" i dont know what you are talking about, sorry, im new in this, an also the english is not my own language, so, sorry if something is wrong.
Ok, so let me start this off by saying I feel kind of dumb right now. I am really new to all this.
I bought a motog5s, and rooted it with super su.
I tried to add a different OS rom (several actually).
I ended up messing up somehow and deleting my backup of the stock rom which I nandroid saved on twrp-3.1.1-sanders.img
I now have a phone with no Operating Sytem. I had twrp-3.1.1-sanders.img and tried to upgrade to twrp-sanders-r2.img which worked but, deleted my backup of stock rom install when i deleted the internal storage like a moron, also didn't help me install a rom w/o error messages so then I upgraded to twrp-sanders-r16.img, which worked also. But now I get error 7 every time I try to install any rom.
Right now my phone has just twrp-sanders-r16.img and no operating system.
How do I resolve the error 7 and error 255(i was getting earlier but now just error 7), and install an operating system? I wanted to get pixel experience working which was what got me all turned around in the first place. I also tried Cosmic, Arrow, AOSPext all of which where in the XDA roms forum(for Moto G5S, Sanders) but kept getting error 255 then I tried to do a fix (deleted assert command from a file in the rom with text editor, but kept saying my ZIP files weren't the proper format, I have ubuntu linux on my computer...which should work) and it stopped giving error 255 and now gives error 7.
I have tried sidebooting, and also many different roms and all give errors. I also had lots of trouble with Open Gapps/larger files/Roms when trying to download on my cpu and then move/copy to my phone's internal storage so I don't know how to resolve that either.
I now want to get a solid rom OS on here ( that's noob friendly) and root with magisk of which i have DL'd 16.0 & Magisk Manager 5.8.3 (last stable release i think)
How do I fix this? Please help!
thank you very much for any help in advance.
First off make sure you have a Moto G5s Plus not the smaller variant. If it's a Plus, than fastboot flash this twrp recovery and try downloading a fresh ROM, gapps, and also Magisk. Flash those guys and you should be good.
Sent from my XT1806 using Tapatalk
treyweez11 said:
First off make sure you have a Moto G5s Plus not the smaller variant. If it's a Plus, than fastboot flash this twrp recovery and try downloading a fresh ROM, gapps, and also Magisk. Flash those guys and you should be good.
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
when i try to flash the rom i get error 7 and it won't install.
mr_moneroj said:
when i try to flash the rom i get error 7 and it won't install.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=890129502657595739
Sorry meant to put this link to update twrp. See if this version will clear you of the error
Sent from my XT1806 using Tapatalk
treyweez11 said:
https://androidfilehost.com/?fid=890129502657595739
Sorry meant to put this link to update twrp. See if this version will clear you of the error
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
Awesome, I will give it a go. Appreciate your help. Thank you.
treyweez11 said:
https://androidfilehost.com/?fid=890129502657595739
Sorry meant to put this link to update twrp. See if this version will clear you of the error
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
Ok I flashed TWRP R20 and it's now on my phone.
I tried flashing Lineage OS, got error 7.
Tried flashing the version of Lineage OS where I deleted the assert code from the beginning of the Updater-Script (which was supposed to fix it.) Instead, I get an error saying it's an improperly formatted zip file.
What solution can I try for resolving this error 7? It happens with every single rom I try.
mr_moneroj said:
Ok I flashed TWRP R20 and it's now on my phone.
I tried flashing Lineage OS, got error 7.
Tried flashing the version of Lineage OS where I deleted the assert code from the beginning of the Updater-Script (which was supposed to fix it.) Instead, I get an error saying it's an improperly formatted zip file.
What solution can I try for resolving this error 7? It happens with every single rom I try.
Click to expand...
Click to collapse
Just try a fresh downloaded room
Sent from my XT1806 using Tapatalk
kinda' haven't rooted except for other ppl much in the past decade, but i just did this phone and from what i understand, first of all flashing magisk on top of supersu seems like a bad idea since they alter complely different directories. pretty sure you'd want to stick with one or the other unless you reverted to stock first. other than that, did you reformat your system partition on the first try? did you wipe before trying other roms?
stuck with same error.
stuck with exact same error 7, did you got any solution, plz send if any, thank you
xt1804
mr_moneroj said:
Ok, so let me start this off by saying I feel kind of dumb right now. I am really new to all this.
I bought a motog5s, and rooted it with super su.
I tried to add a different OS rom (several actually).
I ended up messing up somehow and deleting my backup of the stock rom which I nandroid saved on twrp-3.1.1-sanders.img
I now have a phone with no Operating Sytem. I had twrp-3.1.1-sanders.img and tried to upgrade to twrp-sanders-r2.img which worked but, deleted my backup of stock rom install when i deleted the internal storage like a moron, also didn't help me install a rom w/o error messages so then I upgraded to twrp-sanders-r16.img, which worked also. But now I get error 7 every time I try to install any rom.
Right now my phone has just twrp-sanders-r16.img and no operating system.
How do I resolve the error 7 and error 255(i was getting earlier but now just error 7), and install an operating system? I wanted to get pixel experience working which was what got me all turned around in the first place. I also tried Cosmic, Arrow, AOSPext all of which where in the XDA roms forum(for Moto G5S, Sanders) but kept getting error 255 then I tried to do a fix (deleted assert command from a file in the rom with text editor, but kept saying my ZIP files weren't the proper format, I have ubuntu linux on my computer...which should work) and it stopped giving error 255 and now gives error 7.
I have tried sidebooting, and also many different roms and all give errors. I also had lots of trouble with Open Gapps/larger files/Roms when trying to download on my cpu and then move/copy to my phone's internal storage so I don't know how to resolve that either.
I now want to get a solid rom OS on here ( that's noob friendly) and root with magisk of which i have DL'd 16.0 & Magisk Manager 5.8.3 (last stable release i think)
How do I fix this? Please help!
thank you very much for any help in advance.
Click to expand...
Click to collapse
I think ! you should trying " Back to Stock Rom by XDA"
regarding back to stock rom
Sanjay.it said:
I think ! you should trying " Back to Stock Rom by XDA"
Click to expand...
Click to collapse
is back to stock rom have anything do with recovery changes
i made some changes in team-win recovery and while flashing some commands giving errors is that a problem with my pc system
and can i downgrade to 7.1.1 firmware, previously i was on 8.1 june 2018
any reply is appreciated, thank you
I had a similar problem. While trying to flash liquid_remix ROM I kept getting error 7. I checked and saw that my system partition was not mounted in TWRP. After mounting it the ROM flashed fine.
solved this issue on my moto g5s plus
mr_moneroj said:
Ok, so let me start this off by saying I feel kind of dumb right now. I am really new to all this.
I bought a motog5s, and rooted it with super su.
I tried to add a different OS rom (several actually).
I ended up messing up somehow and deleting my backup of the stock rom which I nandroid saved on twrp-3.1.1-sanders.img
I now have a phone with no Operating Sytem. I had twrp-3.1.1-sanders.img and tried to upgrade to twrp-sanders-r2.img which worked but, deleted my backup of stock rom install when i deleted the internal storage like a moron, also didn't help me install a rom w/o error messages so then I upgraded to twrp-sanders-r16.img, which worked also. But now I get error 7 every time I try to install any rom.
Right now my phone has just twrp-sanders-r16.img and no operating system.
How do I resolve the error 7 and error 255(i was getting earlier but now just error 7), and install an operating system? I wanted to get pixel experience working which was what got me all turned around in the first place. I also tried Cosmic, Arrow, AOSPext all of which where in the XDA roms forum(for Moto G5S, Sanders) but kept getting error 255 then I tried to do a fix (deleted assert command from a file in the rom with text editor, but kept saying my ZIP files weren't the proper format, I have ubuntu linux on my computer...which should work) and it stopped giving error 255 and now gives error 7.
I have tried sidebooting, and also many different roms and all give errors. I also had lots of trouble with Open Gapps/larger files/Roms when trying to download on my cpu and then move/copy to my phone's internal storage so I don't know how to resolve that either.
I now want to get a solid rom OS on here ( that's noob friendly) and root with magisk of which i have DL'd 16.0 & Magisk Manager 5.8.3 (last stable release i think)
How do I fix this? Please help!
thank you very much for any help in advance.
Click to expand...
Click to collapse
hii, mr_moneroj
i was having the same error
and back to stock rom worked for me,
let me find links that could lead you to solve problem
https://forum.xda-developers.com/mo...ockrom-android-8-1-oreo-oficial-twrp-t3804750
means i did this, hope works for you
first i restored my phone through this backup
then my network and fingerprint were not working well
so used this you tube video
follow this instructions after above link restore
https://youtu.be/iu3BOs7nMuA
very well explained, follow them
i did this and back to stock also i got official 8.1 right now, upgrading
bye....