Shinj1EVA reported that koush's web builder is now producing boo table CWM Touch images. I have built one and added it to the download page. I have not updated the regular CWM to 6.0.2.3 since there are no commits that affect how it works since I last built 6.0.2.1
12/20- All recoveries are functionally up to date as of this day.
I have seen most of the guides recommend flashing the 'grouper' recovery image. Don't do this. This is why your OTAs and update.zips are failing with 'Status 7'. Those zips have an assert check that ensures you are flashing your zips to the correct device. This is failing if you have a recovery image that was made for a different device.
Those assert checks are there for your protection and you should not get in the practice of working around them. Using grouper recovery.imgs is ill-advised and conceivably dangerous. 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.
I have ported TWRP and compiled a CWM-based (Touch and non-touch) recovery image, made from CM10.1 tilapia source. You will need fastboot, at minimum, to write this recovery. To root, you will need the CWM-flashable zip of SuperSU by chainfire..
Instructions
Boot into the bootloader (2 choices)
Turn the device on while pressing volume down; or
Code:
adb reboot bootloader
Unlock your bootloader
THIS WILL WIPE ALL OF YOUR DATA! No way around it...
Code:
fastboot oem unlock
With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
Mount system in the 'mounts' menu
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
To Root (With /system still mounted):
Code:
adb push CWM-SuperSU-v0.98.zip /sdcard/
Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
Reboot System
Congratulations, you now have the proper tilapia custom recovery and can flash roms and OTAs. Anytime you get a 'status 7' from now on, you know that rom was not made for your device. CWM will have instructions that gives you the option of preserving custom recovery and maintaining root.
If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
If you want to keep tilapia recovery but have a grouper rom you want to try, you will have to change the updater-script of that rom. It takes two seconds. Look at the third post for instructions.
Downloads
Recovery (just pick one)
CWM Recovery (Touch/Non-Touch) (6.0.2.1)
TWRP 2.3.2.1
Root (Get the CWM flashable zip)
SuperSU
ClockworkMod is the work of the estimable koush and TWRP is from the good men of Team Win.
a mirror please?
How to use grouper roms w/tilapia recovery
Use an archive manager like 7zip and open your rom without unzipping.
Open META-INF/com/google/android/updater-script
Look for the line (usually the first) that says something like this:
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper");
[*]
Change 'grouper' to 'tilapia'
Save and flash!
Hopefully soon, devs will make two versions of their roms, although that may not happen until we finish porting the GSM stack. A solution for the meantime would be to edit the above assert to (off the top of my head):
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper") || (getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia")
For anything meant to service both devices. The devs should not be expecting users to run another device's recovery in my opinion, even if it is working. Because, as we know, it breaks other things, like OTAs and other update.zips.
My expectation would be that they will begin to build separate roms, as that is best practice and doesn't make use use the grouper fstab stuff. Not the most efficient use of bandwidth, I concede...
Ather said:
a mirror please?
Click to expand...
Click to collapse
Sure. Is techerrata/Goo a non-working option for some people? I use it for a project that is has mostly international users and haven't had any complaints. What/where would be helpful to you?
Update: Since I am here...I will post CWM Touch eventually. CWM Touch still has closed source elements, so the only way I know of to compile it is to use koush's web builder. But the result of that build is not booting. I ported Touch by hand, but it is too buggy to release, something needs to be modified in the recovery.fstab, I guess.
Mirror:
http://core.routed.com/nexus7/
If this is installed, will I be barred from installing grouper roms? I currently have multirom running, with stock as the main rom and PA as the alternate. PA doesn't get 3G but it works fine. Other grouper roms still work too, just no 3G. This is holding me over until they get the "tilapia" roms up. I just installed the OTA manually through fastboot.
Xentar712 said:
If this is installed, will I be barred from installing grouper roms? I currently have multirom running, with stock as the main rom and PA as the alternate. PA doesn't get 3G but it works fine. Other grouper roms still work too, just no 3G. This is holding me over until they get the "tilapia" roms up. I just installed the OTA manually through fastboot.
Click to expand...
Click to collapse
You will have to hack the grouper roms to change their assert to read tilapia rather than grouper (assuming they have them, and it is REALLY easy to do either way, easier than flashing an OTA in fastboot easy). I tend to be of the opinion that it is better to have a hack like that when you know you are doing something dangerous as opposed to the reverse.
Not that it is all that dangerous with the Nexus devices. But if you are flashing a rom from a different device onto your tablet, I think that you should have to indicate you are aware you are doing it.
The best thing would be for roms that are able to work on both devices should have updater-scripts that reflect that. You shouldn't be required to run recovery not for your device. But personal choice, as always.
Edit: As indicated on the OP, grouper and tilapia have different layouts. Look at the recovery.fstab, tilapia has this line:
Code:
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
That file is used in making and configuring recovery...the rom makers will have to be able to work with tilapia recovery if they ever hope to have the GSM stack work, I would guess.
mateorod said:
You will have to hack the grouper roms to change their assert to read tilapia rather than grouper (REALLY easy, easier than flashing an OTA in fastboot easy). I tend to be of the opinion that it is better to have a hack like that when you know you are doing something dangerous as opposed to the reverse.
Not that it is all that dangerous with the Nexus devices. But if you are flashing a rom from a different device onto your tablet, I think that you should have to indicate you are aware you are doing it.
The best thing would be for roms that are able to work on both devices should have updater-scripts that reflect that. You shouldn't be required to run recovery not for your device. But personal choice, as always.
Click to expand...
Click to collapse
Cool, I'll give it a go once you get TWRP up and running. Maybe Tassadar, over in the MultiROM forum, can tweak it for MultiRom as well. I'm really liking MultiRom - IMHO it's less risky when toying with unknowns. It's probably more risky in reality though, and I'm just crazy
I've flashed this recovery to get 4.2.1 on my Nexus 7 3G, but it seems that I can't go into recovery mode anymore. The screen shows me picture of an android lying down with its front open.
The only way I'm able to go into recovery is to reflash, or do a
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
This works for that 1 boot, after which I get the same issue.
superc0w said:
I've flashed this recovery to get 4.2.1 on my Nexus 7 3G, but it seems that I can't go into recovery mode anymore. The screen shows me picture of an android lying down with its front open.
The only way I'm able to go into recovery is to reflash, or do a
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
This works for that 1 boot, after which I get the same issue.
Click to expand...
Click to collapse
Okay. After I flashed the OTA, CWM asked me if I wanted to make it permanent, but maybe that by itself us not enough. I had already done the following step.
flash recovery and boot into it. Mount system, and then:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
CWM asked me if i wanted to prevent the updates from flashing stock recovery and if I wanted to secure the root (su binary). But maybe that doesn't work right out of the box.
mateorod said:
Okay. After I flashed the OTA, CWM asked me if I wanted to make it permanent, but maybe that by itself us not enough. I had already done the following step.
flash recovery and boot into it. Mount system, and then:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
CWM asked me if i wanted to prevent the updates from flashing stock recovery and if I wanted to secure the root (su binary). But maybe that doesn't work right out of the box.
Click to expand...
Click to collapse
Yup, I renamed recovery-from-boot.p to recovery-from-boot.p.bak using ES File Explorer and it's all good now. I'm now able to use CWM. However, CWM always asks me if I want to prevent updates from flashing stock recovery and I always chose no (since it warns that this is irreversible).
Strange though. I assumed that even if CWM doesn't stick without renaming recovery-from-boot.p, the N7 3G would flash stock recovery and it would still be functional.
installed last night, works great..frankly i prefer the non-touch, dunnow why but its much better...i tried to rename the files, but there werent any files in the /system , flashed the CWM package, took a nandroid..all works great
Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.
gwisch said:
Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That error message has absolutely nothing to do with the recovery image.
This special talapia version of CWM isn't some magic pill that will make every other problem go away. It's simply designed to accurately reflect the hardware for the tablet you own (talapia vs grouper) so you don't run into as many problems down the road installing OTA updates and custom ROMs that check.
However, you still need to meet ALL the other requirements of the updates. So if you made changes to your /system files, kernel (not in this case, but in general), build.prop, etc., the OTA update will still abort and explain why.
Did you even read the error message?
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk".
It's pretty clear that you modified the framework file. You will need to revert that back to stock and flash the OTA again afterwards. Any other tweaks/modifications/freezes/removals/etc. of system apps will most likely result in the same thing.
TWRP is up...
I compiled a TWRP image for tilapia as well.
This actually took a little doing...my intention here was to simply compile some images, but since tilapia is only Android 4.2, and we don't have CM10.1 (officially), I actually endied up having to port TWRP whole cloth. This is compiled from TWRP source code, with a few tweaks.
There are a couple things about the port I would like to eventually tweak, I had to copy the sbin folder over by hand, and due to the intertwined nature of grouper/tilapia, settings derived from common files in the source code are named grouper still, (i.e. ueventd.grouper.rc instead of ueventd.tilapia.rc) but that is quibble stuff and may end up staying that way regardless, since many of the tilapia make files are merely pointers to the grouper files. It certainly doesn't hurt anything.
The TWRP image has been confirmed working with the OTAs.
I thought long and hard about possibly modifying these recovery images to allow users to flash grouper roms as well. I know it is unlikely that everything will be made available in two versions, even though it should be.
Any thoughts on this? It is a demonstrably better idea than having people use the grouper images, but I still think the developers/modders should be the ones handling this problem. People are going to NEED this recovery image once the nightlies of AOKP/CM10.1 and whatever start coming down, but I know that grouper zips will still be tempting to many.
Under the instructions in the first post, it says:
OR: If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
fastboot boot recovery recovery-CWM-tilapia-regular.img
Click to expand...
Click to collapse
So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?
When I try to do this, it doesn't work, and I just get this:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'
I also tried to follow the main instructions and it fails on step 2 with:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s
I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?
manekineko said:
Under the instructions in the first post, it says:
So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?
When I try to do this, it doesn't work, and I just get this:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'
I also tried to follow the main instructions and it fails on step 2 with:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s
I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?
Click to expand...
Click to collapse
Yep. My bad.
I originally just posted the images as an alternative to the recoveries for the regular Nexus 7 (non-3g) images people were using. I later realized that some new people would come by so I threw rooting instructions as well. I didn't go back far enough, sorry. I will fix it now.
What you need to do is easy though, just like you mentioned you need to unlock your bootloader. So once you boot into the bootloader,
Code:
fastboot oem unlock
This will wipe all of your data, and there is no way around this, sorry. It is a security measure of some sort. There will be a screen where you acknowledge this and then the bootloader will unlock. You can then follow the rest of the instructions. Sorry for the confusion.
Update: Fixed and streamlined OP. Glad you got me to do this, I think it is better now.
In the rooting instructions, this line wasn't working for me, as /sdcard/ was for some reason a directory containing 3 folders (0, odb, legacy), where 0 had the normal contents of /sdcard/:
adb push CWM-SuperSU-v0.98.zip /sdcard/
Click to expand...
Click to collapse
Instead, I had to do:
adb push CWM-SuperSU-v0.98.zip /sdcard/0/
After that change, I was able to flash the zip and root successfully.
Hi OP,
I followed your instructions and managed to root my nexus 7 3G running stock Android 4.2.1. Thanks.
However there are some extra "incidents" which is not captured in your instructions and somehow it happen on my side, so I just detailed down what happen in case it can be of help to others:
Below is the full OP's original instruction and some extra "incidents" during rooting
Instructions
1. Boot into the bootloader (2 choices)
Turn the device on while pressing volume down; or
Code:
Code:
adb reboot bootloader
2. Unlock your bootloader
THIS WILL WIPE ALL OF YOUR DATA! No way around it...
Code:
Code:
fastboot oem unlock
My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to
2a. Reboot into bootloader
Code:
adb reboot bootloader
3. With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
Code:
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
4. To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
Mount system in the 'mounts' menu
Code:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
5. To Root (With /system still mounted):
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.
Code:
Code:
adb push CWM-SuperSU-v0.98.zip /data/media/
Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
Code:
Reboot System
5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.
COLOR="Red"]My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to
Click to expand...
Click to collapse
I can't speak as to how Windows works exactly, but I can tell you that fastboot code does nothing to the 'host' PC. Not saying it didn't happen, but it wasn't fast boot.
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.
Click to expand...
Click to collapse
The person above you reported that they had to push to /sdcard/0. I checked my original instructions and they work for me. I haven't decided what to put yet. They have been playing around with the standard nomenclature for emulated storage, but I have yet to see anything that explains the varied experiences. I haven't looked yet really, either
5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.
Click to expand...
Click to collapse
I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.
Thanks for your feedback.
I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.
Click to expand...
Click to collapse
Hi,
In fact I am also confused about the warning. Not sure does choosing "Yes" means retain CWM or not. So I just choose "Yes" and saw that CWM is still the recovery after reboot.
So do you mean after this step:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
It does not matter whether I choose "Yes" or "No" in the final phase, and I will still have CWM as my recovery?
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: // clashin.com/
zhudachang said:
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: / / justcoolthings.net
Click to expand...
Click to collapse
Just want to say thank you for these steps! It fixed my phone as well and saved my sanity! LOL
5.1 OTA Update Screwed My Nexus 5
zhudachang said:
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: // clashin.com/
Click to expand...
Click to collapse
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
I would suggest you do a "flash-all" to your device.
1) Download the factory image ("hammerhead-lmy47i") from https: // developers.google.com /android/nexus/images
2) Boot your device into bootloader mode and run "flash-all.sh" to flash the 5.1 factory rom. It should fix all your errors.
Good luck.
Yu
liquanize said:
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
Click to expand...
Click to collapse
liquanize said:
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
Click to expand...
Click to collapse
Keep in mind that STOCK recovery does NOT let you connect to normal ADB, a custom recovery does. Also, you need to be root to 'mkfs.ext2', and the target partition must not be mounted, I believe.
Before attempting the steps @zhudachang posted below, i.e. To flash a factory image, you need to unlock your bootloader.
zhudachang said:
I would suggest you do a "flash-all" to your device.
1) Download the factory image ("hammerhead-lmy47i") from https: // developers.google.com /android/nexus/images
2) Boot your device into bootloader mode and run "flash-all.sh" to flash the 5.1 factory rom. It should fix all your errors.
Good luck.
Yu
Click to expand...
Click to collapse
I sideloaded the 8.1 OTA yesterday. However, I'm having issues with my finger print sensor and want to do a clean flash of the whole image. I downloaded the Walleye .011 image file from Google's site this morning. When I attempt to flash the image using the flash-all command, I receive the following error:
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
mke2fs failed: -1
error: Cannot generate image for userdata
I have my bootloader unlocked but am not rooted. The phone is currently on the .011 build but it will not let me flash the image. Any ideas? I've also downloaded the latest platform tools in case that was an issue.
Thanks,
Rick
C5Longhorn said:
I sideloaded the 8.1 OTA yesterday. However, I'm having issues with my finger print sensor and want to do a clean flash of the whole image. I downloaded the Walleye .011 image file from Google's site this morning. When I attempt to flash the image using the flash-all command, I receive the following error:
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
mke2fs failed: -1
error: Cannot generate image for userdata
I have my bootloader unlocked but am not rooted. The phone is currently on the .011 build but it will not let me flash the image. Any ideas? I've also downloaded the latest platform tools in case that was an issue.
Thanks,
Rick
Click to expand...
Click to collapse
Are you running it from the directory where the image is?
C5Longhorn said:
I sideloaded the 8.1 OTA yesterday. However, I'm having issues with my finger print sensor and want to do a clean flash of the whole image. I downloaded the Walleye .011 image file from Google's site this morning. When I attempt to flash the image using the flash-all command, I receive the following error:
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
mke2fs failed: -1
error: Cannot generate image for userdata
I have my bootloader unlocked but am not rooted. The phone is currently on the .011 build but it will not let me flash the image. Any ideas? I've also downloaded the latest platform tools in case that was an issue.
Thanks,
Rick
Click to expand...
Click to collapse
I had the same issue with my 2 XL and it was driving me crazy.
The only way I was able to get the factory image to flash is by removing the -w flag near the bottom of the script. I couldn't figure out what was going wrong and have never needed to modify the script for a factory image to flash.
your problem could be easily solved by restoring factory settings.
have you compared the SHA-256 Checksum hashes? It may/might explain or expose if something is missing...
I mean it's doubtful that you've gone this far where it would be something like that, but you never know... small but won't hurt to try and if that ends up being it, then it's a small thing and keeps you from going all too far...
Thanks for all the replies. I have not compared a checksum yet, but will validate they are the same.
I wanted to flash the whole image as a way to completely clean install the system and my apps. Wouldn't a factory reset only remove my data and configuration settings? If there was an issue with the system files, those wouldn't be fixed, correct?
Thanks,
Rick
Sent from my Pixel 2 using Tapatalk
osi13 said:
I had the same issue with my 2 XL and it was driving me crazy.
The only way I was able to get the factory image to flash is by removing the -w flag near the bottom of the script. I couldn't figure out what was going wrong and have never needed to modify the script for a factory image to flash.
Click to expand...
Click to collapse
How I can do that ( removing the -w flag near the bottom of the script ) pls help
zetareticuli said:
How I can do that ( removing the -w flag near the bottom of the script ) pls help
Click to expand...
Click to collapse
You want to remove the -w flag from flashall.sh or flashall.bat.
osi13 said:
You want to remove the -w flag from flashall.sh or flashall.bat.
Click to expand...
Click to collapse
problem solved i found the (-w) but the problem now is i can't flash or install one ROM to start the process to go out of the bootloop problem.. no recovery mode, i can't install TWRP, the phone are connecting with my comp and i has tryied flash many stock rom's and flash the 4 core.img, but nothing works can you help me??
Hello guys, some time ago this device had more support from developers, someone could extract the recovery.img in order to keep it updated.
I wonder if anyone would know what the procedure is for extracting.
My device is the ZE552KL (Z012D).
I followed the steps in this tutorial, however, I did not succeed: https://tinyurl.com/yd3w4pxa
I followed all the steps and tried to extract recovery.img from the Zenfone 3 ZE552KL (Z012D) Asus firmware, however, there was a problem after applying the applypatch directive.
Error: patch boot.img: Only patches to EMMC targets are supported.
And I can not solve it.
install-recovery.sh (original extraction): https://hastebin.com/lupoqovila.bash
install-recovery.sh (change): https://hastebin.com/ofuqofezat.bash
Apllypatch directive used at the prompt: applypatch -b recovery-resource.dat boot.img recovery.img 28e9d4088f51c9dafb9189eb15f061c78be55a57 18791676 4a9f7c48e01aed3a46ac8d06618239dff9834caf: recovery-from-boot.p
Error:
https://imgur.com/a/JWfyr
I also asked for help at Zentalk, but so far no one has spoken.
https://www.asus.com/zentalk/tw/thread-147621-2-1.html
Please, I'll be grateful if anyone can help.
The recovery partition is #59, therefore to back it up you can use terminal emulator and type;
Su
dd if=/dev/block/mmcblk0p59 of=/sdcard/recovery.img
To flash, go to fastboot and type
Fastboot flash recovery recovery.img
Fastboot reboot
You need root for all this. You can convert the recovery image to be flashable via recovery but it only works with twrp, not stock.
wang1chung said:
The recovery partition is #59, therefore to back it up you can use terminal emulator and type;
Su
dd if=/dev/block/mmcblk0p59 of=/sdcard/recovery.img
To flash, go to fastboot and type
Fastboot flash recovery recovery.img
Fastboot reboot
You need root for all this. You can convert the recovery image to be flashable via recovery but it only works with twrp, not stock.
Click to expand...
Click to collapse
Thanks for taking note of my question, but what I really need to know is about recovery stock. It would not be logical for my use to perform custom recovery extraction, since it is already found in the .img format from the developer's available links (TWRP).
Following the tutorial steps of the links I indicated it is possible to make a kind of compilation using the official OTA file, processing on the device itself to generate the file recovery.img stock.
Again thank you for trying to help, any and all help is very welcome.
+1
Can someone post here stock recovery.img for ze520kl newest oreo firmware?
I'd like to know how to do this as well. I went through a lot of trouble to get Oreo installed after rooting and installing TWRP on my phone running Nougat, ended up having to go back to stock and install updates incrementally. As you noted, root is required to save the stock recovery.img, but since my device is not rooted now I can't root without installing TWRP first. That would put me in the same situation as the OP. The google translate of the link posted by the OP is a bit hard to understand, can someone else give an english explanation of how to extract recovery.img from firmware zip?
TIA
Update: I managed to follow the instructions in the OP's link, ended up with a similar applypatch command as he did and also encountered the same error with running the command over adb. I'm not sure if those instructions are for all asus devices, the one in the link is Asus P028 (Zenpad 10)
applypatch -b recovery-resource.dat boot.img recovery.img f448eeec56d4d87173858cd7aec25c36a7dfaaa7 18736380 9ebabd3eb6a59cfcaf0f4f048e2d8d6d870d7924:recovery-from-boot.p
ktl20 said:
Can someone post here stock recovery.img for ze520kl newest oreo firmware?
Click to expand...
Click to collapse
Here
Error
I keep getting
/sbin/sh: f448eeec56d4d87173858cd7aec25c36a7dfaaa7: not found
whenever i go through this. what am i doing wrong? T_T
wang1chung said:
The recovery partition is #59, therefore to back it up you can use terminal emulator and type;
Su
dd if=/dev/block/mmcblk0p59 of=/sdcard/recovery.img
To flash, go to fastboot and type
Fastboot flash recovery recovery.img
Fastboot reboot
You need root for all this. You can convert the recovery image to be flashable via recovery but it only works with twrp, not stock.
Click to expand...
Click to collapse
when I type su and enter, on adb shell show error "/system/bin/sh: su: not found". my device is unrooted. I did this for boot and recovery backup before rooting. I'm using Zenfone x00rd (Live L1)