Related
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card
rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996
I'm using an unpopular android device and am stuck on 3e recovery as there is no CWM for it. Should I be writing update.zip with amend or edify? Please advise.
Prasad007 said:
I'm using an unpopular android device and am stuck on 3e recovery as there is no CWM for it. Should I be writing update.zip with amend or edify? Please advise.
Click to expand...
Click to collapse
First of all, what device? You can't flash any custom zips in a 3e recovery. Does your device have its firmware released? If so, you can extract the recovery.img and use it to create a CWM recovery img at builder.clockworkmod.com. REply directly to my post so I get a notification please, because I have way too many subscriptions and I don't want even more. I'll try to help you out as much as I can.
Codename13 said:
First of all, what device? You can't flash any custom zips in a 3e recovery. Does your device have its firmware released? If so, you can extract the recovery.img and use it to create a CWM recovery img at builder.clockworkmod.com. REply directly to my post so I get a notification please, because I have way too many subscriptions and I don't want even more. I'll try to help you out as much as I can.
Click to expand...
Click to collapse
@Codename13, It's the AKAI MID1048. There is neither a custom recovery nor the official firmware for it, available anywhere online. I need to do what it takes to access /system from 3e to revive this otherwise dead device.
Prasad007 said:
@Codename13, It's the AKAI MID1048. There is neither a custom recovery nor the official firmware for it, available anywhere online. I need to do what it takes to access /system from 3e to revive this otherwise dead device.
Click to expand...
Click to collapse
Can you get into a download mode of sorts? If so, I may be able to scrap together a basc custom recovery for you. However, in order to do so, I would need to know your screen size (example 480x800) and what your basic partitions are. For the partitions, download the app "Partition Table" and go to the Advanced Partition Data. Give me the paths to the partitions for /system, /data, /cache, and /sdcard and each of those partitions' filesystems. With all that, I should be able to build a custom recovery for your device. Say, what Android version is your device running? Have you tried any root exploits such as Oneclick, UnlockRoot, etc? Also, be wary that I'm not responsible for any damage that may be caused to your device.
Codename13 said:
Can you get into a download mode of sorts? If so, I may be able to scrap together a basc custom recovery for you. However, in order to do so, I would need to know your screen size (example 480x800) and what your basic partitions are. For the partitions, download the app "Partition Table" and go to the Advanced Partition Data. Give me the paths to the partitions for /system, /data, /cache, and /sdcard and each of those partitions' filesystems. With all that, I should be able to build a custom recovery for your device. Say, what Android version is your device running? Have you tried any root exploits such as Oneclick, UnlockRoot, etc? Also, be wary that I'm not responsible for any damage that may be caused to your device.
Click to expand...
Click to collapse
There's no download mode for this device that I know of. Fastboot never worked on it from the beginning (code 43 in windows/unseen in ubuntu).
Screen resolution: 280 x 800 px
Android version: 4.0.3
I can't run any app since I can't boot into android. The only thing I'm able to do is sign any flashable for it's 3e recovery, move it into the ext_sd and flash it. I tried flashing SuperSU but it returns Status 255. I'm also unable to see /system with the Aroma file manager.
Prasad007 said:
There's no download mode for this device that I know of. Fastboot never worked on it from the beginning (code 43 in windows/unseen in ubuntu).
Screen resolution: 280 x 800 px
Android version: 4.0.3
I can't run any app since I can't boot into android. The only thing I'm able to do is sign any flashable for it's 3e recovery, move it into the ext_sd and flash it. I tried flashing SuperSU but it returns Status 255. I'm also unable to see /system with the Aroma file manager.
Click to expand...
Click to collapse
Oh, so the problem is that you softbricked your device, and since there is no download mode/fastboot (and only 3e recovery), how can you fix your device so you can boot into Android? If so, then you're screwed. I think. I'm pretty sure there's some Android manufacturer rule stating that there must be some download mode of sorts, so there must be one somewhere. How exactly did you get stuck in 3e recovery? Can you try using a USB JIG? They usually can get the user into an emergency recovery mode. Anyways, if there is NO download mode, and NO way to bypass the signature authentication in 3e recovery (you would need to modify it then flash it to the device, which would not work if there is NO download mode), then I think you are most definitely screwed.
Codename13 said:
Oh, so the problem is that you softbricked your device, and since there is no download mode/fastboot (and only 3e recovery), how can you fix your device so you can boot into Android? If so, then you're screwed. I think. I'm pretty sure there's some Android manufacturer rule stating that there must be some download mode of sorts, so there must be one somewhere. How exactly did you get stuck in 3e recovery? Can you try using a USB JIG? They usually can get the user into an emergency recovery mode. Anyways, if there is NO download mode, and NO way to bypass the signature authentication in 3e recovery (you would need to modify it then flash it to the device, which would not work if there is NO download mode), then I think you are most definitely screwed.
Click to expand...
Click to collapse
I AM able to sign packages for the signature verification. I figured out how to get it signed for this device's 3e recovery. Traditional SignApk or testsign didn't work, but I've made it work. That's the progress thus far. So I can pretty much flash anything. I have no USB JIG. I don't think this manufacturer has followed any norms to the most part (including no Play Store / Google Play Services, etc.) which is what began this charade for me, as I tried to force install gapps. Flashing it didn't change anything so I used root explorer to move everything from the zip's /system to the device's /system. I didn't fix permissions and I assume that's what's preventing my device from booting. Factory resetting from 3e only wipes /data and /cache.
Prasad007 said:
I AM able to sign packages for the signature verification. I figured out how to get it signed for this device's 3e recovery. Traditional SignApk or testsign didn't work, but I've made it work. That's the progress thus far. So I can pretty much flash anything. I have no USB JIG. I don't think this manufacturer has followed any norms to the most part (including no Play Store / Google Play Services, etc.) which is what began this charade for me, as I tried to force install gapps. Flashing it didn't change anything so I used root explorer to move everything from the zip's /system to the device's /system. I didn't fix permissions and I assume that's what's preventing my device from booting. Factory resetting from 3e only wipes /data and /cache.
Click to expand...
Click to collapse
Oh, so it's some faulty GAPPS that are causing the issue? Do any of your signed packages install without errors? If AROMA filemanager doesn't work when signed, I can make a package to uninstall whatever the GAPPS did install as long as you provide me with the updater-script from that GAPPS package. Also, what method are you using for signing packages to be compatible with 3e recovery. I'm curious to know. And if you get your device back up and booting, you can still redeem my offer for making a somewhat functional CWM. It would actually be a pleasure to do so.
Codename13 said:
Oh, so it's some faulty GAPPS that are causing the issue? Do any of your signed packages install without errors? If AROMA filemanager doesn't work when signed, I can make a package to uninstall whatever the GAPPS did install as long as you provide me with the updater-script from that GAPPS package. Also, what method are you using for signing packages to be compatible with 3e recovery. I'm curious to know. And if you get your device back up and booting, you can still redeem my offer for making a somewhat functional CWM. It would actually be a pleasure to do so.
Click to expand...
Click to collapse
I simply used the latest gapps for CM9 from the CyanogenMod wiki. All packages I've tried so far show to have installed fine without errors, with the exception of SuperSU. The output after flashing is as to be expected (as would be seen also in CWM). I'm wondering if updater-script even takes effect in 3e though? Does it use amend by any chance? In any case, I've attached the relevant updater-script and the shell file it uses. I'd love to see CWM on this device too, but let's focus on getting it to boot first.
This is how I sign for 3e recovery:
Code:
java -Xmx512m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update.zip update_signed.zip
Prasad007 said:
I simply used the latest gapps for CM9 from the CyanogenMod wiki. All packages I've tried so far show to have installed fine without errors, with the exception of SuperSU. The output after flashing is as to be expected (as would be seen also in CWM). I'm wondering if updater-script even takes effect in 3e though? Does it use amend by any chance? In any case, I've attached the relevant updater-script and the shell file it uses. I'd love to see CWM on this device too, but let's focus on getting it to boot first.
Click to expand...
Click to collapse
I've compiled a script to delete everything that the GAPPS package installed. Your device may not be working because the GAPPS had overwritten a necessary file, so I cannot guarantee that the script can fix your device. Just paste the whole script into an updater-script of a package and do your signing thing so it can be installed. Hope it works.
ui_print("UNINSTALL Google Apps for Android 4.0 - 20120429");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
delete("/system/app/ChromeBookmarksSyncAdapter.apk");
delete("/system/app/GalleryGoogle.apk");
delete("/system/app/Gallery2.apk");
delete("/system/app/GenieWidget.apk");
delete("/system/app/GoogleBackupTransport.apk");
delete("/system/app/GoogleCalendarSyncAdapter.apk");
delete("/system/app/GoogleContactsSyncAdapter.apk");
delete("/system/app/GoogleFeedback.apk");
delete("/system/app/GoogleLoginService.apk");
delete("/system/app/GooglePartnerSetup.apk");
delete("/system/app/GoogleQuickSearchBox.apk");
delete("/system/app/QuickSearchBox.apk");
delete("/system/app/GoogleServicesFramework.apk");
delete("/system/app/GoogleTTS.apk");
delete("/system/app/MarketUpdater.apk");
delete("/system/app/MediaUploader.apk");
delete("/system/app/NetworkLocation.apk");
delete("/system/app/OneTimeInitializer.apk");
delete("/system/app/Phonesky.apk");
delete("/system/app/SetupWizard.apk");
delete("/system/app/Provision.apk");
delete("/system/app/Talk.apk");
delete("/system/app/VoiceSearch.apk");
delete("/system/etc/permissions/com.google.android.maps.xml");
delete("/system/etc/permissions/com.google.android.media.effects.xml");
delete("/system/etc/permissions/com.google.widevine.software.drm.xml");
delete("/system/etc/permissions/features.xml");
delete("/system/etc/g.prop");
delete("/system/framework/com.google.android.maps.jar");
delete("/system/framework/com.google.android.media.effects.jar");
delete("/system/framework/com.google.widevine.software.drm.jar");
delete("/system/lib/libfilterpack_facedetect.so");
delete("/system/lib/libflint_engine_jni_api.so");
delete("/system/lib/libfrsdk.so");
delete("/system/lib/libgcomm_jni.so");
delete("/system/lib/libpicowrapper.so");
delete("/system/lib/libspeexwrapper.so");
delete("/system/lib/libvideochat_jni.so");
delete("/system/lib/libvideochat_stabilize.so");
delete("/system/lib/libvoicesearch.so");
delete("/system/tts/lang_pico/de-DE_gl0_sg.bin");
delete("/system/tts/lang_pico/de-DE_ta.bin");
delete("/system/tts/lang_pico/es-ES_ta.bin");
delete("/system/tts/lang_pico/es-ES_zl0_sg.bin");
delete("/system/tts/lang_pico/fr-FR_nk0_sg.bin");
delete("/system/tts/lang_pico/fr-FR_ta.bin");
delete("/system/tts/lang_pico/it-IT_cm0_sg.bin");
delete("/system/tts/lang_pico/it-IT_ta.bin");
show_progress(1, 15);
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation complete!");
Click to expand...
Click to collapse
Codename13 said:
I've compiled a script to delete everything that the GAPPS package installed. Your device may not be working because the GAPPS had overwritten a necessary file, so I cannot guarantee that the script can fix your device. Just paste the whole script into an updater-script of a package and do your signing thing so it can be installed. Hope it works.
Click to expand...
Click to collapse
^This requires busybox, that this device doesn't have I suppose. Thus, it won't install. Also, don't I need update-binary? I'm searching now for a way to get busybox installed from recovery.
Hello,
I am trying to update my H60-L12 from 6.1.1 to 6.1.16 (and then beyond) using OTA.
I have my phone rooted and with custom recovery. I know I have to unroot and restore stock recovery to get the OTA updates. Yesterday I learnt also that to get 6.1.16 I have to use TAPVPN to connect to the internet via Singapore (thanks to @bcostea for the hint).
Now I find that my phone downloads the update and when it tries to install there is an error in the process at the 6%.
I learnt that the update process logs its progress in the file /splash2/recovery_log
There I find this:
Code:
UI percent:5%.
file "/system/framework/com.google.widevine.software.drm.jar" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/framework/com.google.widevine.software.drm.jar", "6189c99c76c84310f35b967e768440088e140f78", "7b4afc644b4d388fe159120f434f769a635a8c5e")
str1:/system/framework/com.google.widevine.software.drm.jar, str2:6189c99c76c84310f35b967e768440088e140f78
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=231: err_no = 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=233: push binary errno 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=238: assert info: assert_filename:/system/framework/com.google.widevine.software.drm.jar
E:assert failed: apply_patch_check(E:
It seems that my com.google.widevine.software.drm.jar is not the one expected by the process.
That makes some sense, as after I installed the full stock rom, I was not able to apply the pa_gapps (some error related to not being possible to install them in a system that did not had a previous version installed to avoid conflicts) (more details on this are available if anybody has a hint or is willing to trobuleshoot it).
Thing is that I applied open_gapps, which are working just fine, but seem to have a different com.google.widevine.software.drm.jar version.
Till 6.1.1, I was able to replace the com.google.widevine.software.drm.jar file in my phone with one from the system.img of the Stock ROM, and then the update was working.
With 6.1.1 I have not been able to find the right file (one with a SHA-1 hash of 7b4afc644b4d388fe159120f434f769a635a8c5e, seems to be necessary).
I have 3 files with hashes:
6189c99c76c84310f35b967e768440088e140f78
654d36de1c8e9e84979a67e897f36dc17a6f7565
bb6bfd30b3d6d03ecf9531e37bcdb0b5a8123e11
They come from stock, from pa_gapps and from open_gapps, but none of them work.
I put them in the \system\framework folder, but the update still fails with the same error.
Can anyone give me a hint? I am going to try by deleting the file, as I have seen that in the log there is one that is not found and the process does not complain that much.
Maybe someone has the right file in this phone and can send it to me. That would be great!!
Thanks in advance!
Well, it seems I managed to make it work.
Instructions below are without warranty. You know that. It's your phone, if you break it, it's your fault. Not mine. You acknowledge that.
Here is how I did it (if you don't know how to execute any of the steps, just google. Instructions have been provided a million times on how to boot in recovery, how to flash an image or how to do a full backup from custom recovery...):
1. I downloaded the full image of the release I had in my phone (I.e. 6.1.1)
2. Using Huawey Upgrade Extractor I extracted system.img and recovery.img
3. I restarted into custom recovery (TWRP) and took a full backup of my phone to the SD. I then removed the SD.
4. I restarted in fastboot mode and using fastboot.exe I flashed recovery.img and system.img (in my case that did not remove anything from my phone, but as I said before, I took a backup beforehand, just in case).
5. I rebooted the phone. Everything was working just fine.
6. I used TAPVPN app to connect through Singapore, so I could get the update to 6.1.16.
7. The update downloaded and installed as expected.
8. Then I used again TAPVPN to get 6.2.1.
9. Same result: download and installation as expected.
10. Then I rooted again and installed custom recovery by using Honor Multi-Tool.
I hope this helps.
Hi all,
First off, I am not familiar with alot of the technical wording in these forums so I hope that I am able to communicate properly with my issue.
I was not happy with how slow the stock version of this tablet was so I decided to install a custom rom, however, I managed to get to the point of unlocking it but that's about as far as I got out of being overwhelmed with what came next! Here is where I am at:
I am currently on Android version 4.2.1 and my laptop is running Windows 10.
I have downloaded latest TWRP image file and renamed that twrp.img and it is stored in the main root folder of my tablet (SD Card aka Internal Storage). USB debugging has been enabled after I activated the Developer Options.
The custom rom I am looking at is CyanogenMod version 11 which I have downloaded, however it should be noted that on the download page it says that there is no recovery available for this build?? whatever this means? I also downloaded Minimal ADB and Fastboot but when I connect the tablet to the laptop (the tablet connects fine) I type in the command prompt "fastboot devices" but nothing happens.
I am at a point now where do I try to continue with the custom rom? or go back to stock?
Can anyone help with basic instructions please?
Thanks in advance.
Head to the General section and read the Beginners Guide. It's the first sticky, so it's easy to find.
It's your decision which rom you run, but you should give Katkiss LP or Katshmallow a good look.
The latter is the only rom for this tablet that is still under active development.
Sent from my Nexus 5X using Tapatalk
Can I ask questions in this thread with reference to the beginner guide?
Sure. Ask away
Sent from my Nexus 5X using Tapatalk
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
binx77 said:
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2688891
As many times as it takes to understand it. :laugh:
In the meantime I will update post #2 a little.
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
binx77 said:
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
Click to expand...
Click to collapse
It's all in my Beginner's Guide - you just have to read it:
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery
Click to expand...
Click to collapse
And I gave you the remaining steps in my last post....
Now it's up to you to read and read again. And google terms you do understand. Then read again
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tran...p-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
Click to expand...
Click to collapse
This is where I am up to now as per the beginners guide
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
the error I get says "cannot open twrp" (I renamed the TWRP file that I downloaded) even though this image file has been moved into the fastboot directory on my PC (I downloaded and installed the ADB, Fastboot and Drivers tool)
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
berndblb said:
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I renamed the file just in windows explorer and I can confirm that the file name is twrp.img
That's with file extensions enabled? Do you see the extensions for all the files in that folder or just for TWRP?
BTW, which TWRP version do you try to flash? Downloaded from where?
Sent from my Nexus 5X using Tapatalk
Ok I got past this point, I hadn't added .img to the command prompt.
Now I am in TWRP and attempted to install KatKiss but it came up with "Zip Signature Verification Failed!" Error installing zip file '/sdcard/download/katkiss-6.0_TF700T_026.zip".
It did say that it could not find MD5 file?
I now have 2 options
1 - Wipe Cache/Dalvik
2- Reboot System
Just hit the Home button in TWRP, go back to Install and this time uncheck the box that says "verify zip signature" then flash the rom. It always checks if you have a md5 checksum file, but it doesn't matter if you don't. The flash goes through anyway
Sent from my TF700T using Tapatalk
Excellent, I successfully installed KatKiss 6.0.1!
Thanks for your help mate!
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
binx77 said:
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
Click to expand...
Click to collapse
You got it resolved?
Katkiss Marshmallow - Can't run Goggle Services/Play
I converted my TF7000T from 4.2.1 to KatKiss Marshmallow, using TWRP Manager on the installation end. Steps included boot access, rooting, wiping/formatting and flashing. Marshmallow functions fine. My problem is that I can't get Google Play or Google Services to run. I tried one installation that was a 'moderate' Gapps installation. It was completely unstable despite some of the apps actually updating. I then repeated the wipe and reinstall of KatKiss-026 and Android 6.0.1 with a minimal Gapps installation - just Google Play Store and Google Play Services. Google Play Services flashes constantly that it is not working. I am also not able to log into my Google Play Store account. I'm afraid I have an outdated version of Google Play. However, I cannot figure out a way to update Play Store or Play Services. Does anyone have a solution to this problem? If I could download a minimal Gapps zip that contained either the current, or update-able version of these two apps, I would also be in business. Help!!
You are running the wrong gapps package I think. You need to install the pico gapps and only the pico gapps package that is linked in the KatKiss OP.
And you have to flash rom, gapps and Supersu(if you want root) in the same recovery session together in that order. Every time. You cannot just flash a gapps package on MM rom anymore.
ROM, pico gapps, supersu - reboot
Oh - and to start out with I'd highly recommend you wipe, better format data before flashing. Wiping of cache and Dalvik goes without saying right?
Sent from my TF700T using Tapatalk
Yes I did thanks, I haven't played around too much with it though - I did experience it to be very slow when trying to install Facebook app though. I do plan to start using it more often so time will tell.
"This package is for A0001, this device is bacon." Wiped internal storage, cant flash
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
KuranKaname said:
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
Click to expand...
Click to collapse
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
Instead of using adb push metod try to flash stock rom (https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/) and then flash the rom you want.
Good luck!
Note: You will loose twrp, so you have to flash it via fasboot [fastboot flash recovery (recovery name).img]
I'd suggest you to start over with a clean flash of COS13 fastboot factory image. Sounds like you are on a very old base.
Try to reboot TWRP and flash again. Or remove that check string from the updater-script.
download CM11 factory recover tool from my google drive @ https://drive.google.com/open?id=0ByfGPjP5zNYSTDZZcXZpLU44Q00 and install drivers and go to fastboot and plug in the phone and run recovery tool to push default factory image then install whatever CM version you want directly
No updater-script file that I can see
Can't find that file!
Anghirrim said:
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
Click to expand...
Click to collapse
use usb otg, success each time!
setup on ubuntu
Instructions for install on linux (test on ubuntu)
1- install adb :
Code:
$ sudo apt-get install android-tools-adb
2- install fastboot :
Code:
$ sudo apt-get install android-tools-fastboot
3- Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
4- test if the phone is detected with the cmd :
Code:
$ fastboot devices
5- unlock bootloader (/!\ it wipe the phone) :
Code:
$ sudo fastboot oem unlock
6- install TWRP :
- go to the path where is the img
Code:
$ cd path/to/twrp/folder/
- rename the image to twrp.img
Code:
$ mv old_name.img twrp.img
- flash the recovery
Code:
$ sudo fastboot flash recovery twrp.img
/!\ Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually turn it off by pressing and holding power button until it switches off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step. /!\
7- install custom/official ROM with TWRP :
- Wipe > Swipe to Factory Reset
- Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
- Install GApps using same process as ROM, then reboot. (optionnal: the official OnePlus ROM come with GApps pre-installed)
Possible errors with official ROM :
"This package is for device: A0001; this device is bacon" or "This package is for device: OnePlus; this device is A0001" or other similar
==> go into the ROM zip file, in "/META-INF/com/google/android/" there is an "updater-script" file. Open it, locate the expression ' getprop("ro.build.product") == "A0001" ' and replace the "A0001" by the device name you have. Replace the file in the archive. Note : after that, you can't verify the official MD5 !
- example : "This package is for device: A0001; this device is bacon", the ' getprop("ro.build.product") == "A0001" ' become getprop("ro.build.product") == "bacon" '
Sources :
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
https://forum.xda-developers.com/oneplus-one/help/package-a0001-device-bacon-wiped-t3457766
Oneplus one Oxygen Installation error using TWRP
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
check this post
wirelessindeed.blogspot.com/2017/07/oxygen-installation-error-on-oneplus.html
Update TWRP Recovery
I know this is an old post, so this is here in case anyone finds it in the future and requires help...
My mate asked me to upgrade his OnePlus (original, codename Bacon) and I received this error when upgrading from LineageOS 14.1 to 15.1.
To resolve, its extremely easy - simply upgrade the TWRP recovery. My mate originally had TWRP 3.1.1.0 installed, but the latest weekly LineageOS 15.1 required v3.2.3.0 installed which resolved the error message "This package is for device: bacon, a1001. this device is ."
Either Vol+ and Power to enter bootloader, or from command line:
adb reboot bootloader (with Android USB debugging turned on. You can test for connection using command "adb devices" and if successful it should show your phone's serial number). You will need to trust the computer's connection on your phone. To get to Android USB Debugging, you need to go Settings -> Developer menu options, and if you can't see that: Settings -> About Phone and tap "Build" 7 times for developer mode to appear.
Once phone goes into bootloader mode, type:
fastboot flash recovery "path:\twrp-x.x.x.x-bacon.img" (obviously path is the directory that the recovery is stored in, and x.x.x.x will be replaced with the version you've just downloaded. At time of writing, v3.2.3.0 is the latest. You can always use "fastboot devices" if you used Vol+ and Power to enter bootloader to ensure you have a valid connection, in USB debugging mode on your phone and correct Android adb drivers installed in Windows.
Wait until it's succeeded, and turn off phone. Now go into recovery and try again - and this time you should be good to go!!!
All the above implies your bootloader is unlocked. If you need to unlock your bootloader, there are plenty of instructions telling you how to do this - but HAVE A BACKUP as unlocking your bootloader will do a factory reset on your phone.
Hope this helps someone
......mmmmmm BACON!!!