I'm having an issue while trying to install CM10.2 (new 4.3 build)
I went into TWRP 2.6.0.0 with the ROMs on an external SD, and wiped everything. (I wanted a really clean install, didn't know I'd make it this hard on me)
I tried to install 10.2, but it would just give me the same error "Error executing updater binary in zip cm-10.2-20130730-UNOFFICIAL-tf700t.zip"
I went back and did a factory reset, then installed 10.1 nightly ROM and 4.2.2 Gapps. The Tablet started up fine and got to the setup screen.
Without starting into the setup, I powered down and started up in recovery mode again.
This time I installed 10.2 ROM and the 4.3 Gapps.
This time, it gets to the setup screen, but I get the "Unfortunately, Settings has stopped" and can't get past the Welcome screen.
I went back again, and installed 10.1 and gapps, then went through setup, updated google apps, restarted, the reboot into recovery.
I installed 10.2 and new gapps again. Everything starts up
EXCEPT:
I can't access Settings or DSP Manager. They both crash on startup and can't be accessed after that.
Went back and wiped everything, started over with Stable 10.1.2. It installed fine.
Set up and installed SuperSU and set binaries, then installed goomanager
loaded up 10.2 and gapps in goo and flashed. Flash would fail with same error as above.
What I tried
wipe everything in TWRP:
Install SuperSU
Factory Reset in Wipe Data
Flash ROM and Gapps
Wipe Cache and Dalvik
Reboot
Set Up Profile
Uncheck to recover from your google account (this will save you from having everything installed)
Update the google apps in play store
Install SuperSU
Grant SuperSU SU privaleges
Run SuperSU and update binaries through TWRP/CWM
(Reboots)
Install GooManager and Grant SU privaleges
From here, I should be able to flash 10.2 and associated new Gapps, but when it restarts into TWRP to install, it fails because of the same error. When I go to reboot from TWRP, it tells me that it appears I do not have root access and asks if I want to install SuperSU.
I install CWM to install a new recovery script instead of TWRP.
I get the exact same scenario.
Then I go and reinstall 10.1.2 and 4.2.2 gapps and everything seems to be fine.
I also cannot install any of the nightly ROMs dirty.
Did I lose root access in recovery?
If I'm in the OS, and go to CWM ROM manager and select "Boot Into Recovery" it essentially just restarts. It never goes to recovery.
I downloaded the Touch Recovery file and when it was done, selected it to install from top left, and it says "Unfortunately, the process android.process.media has stopped"
wtf is going on?
Do this:
– Reboot Recovery (TWRP 2.6)
– If TWRP promt the SuperSU installation, install it.
– Boot into Android.
– Reboot Recovery
– Flash CM 10.1 and Gapps
– Boot into Android
– Don't install SuperSU, superuser it's already merged in CM.
– Reboot Recovery
– Flash CM10.2 like an update (In TWRP /install/select the zip files, ROM and Gapps/wipe cache and dalvik/reboot system
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4 Beta
Hi again mate, if i were you i would try to install a full Asus rom and Wipe everything and i mean a complete Wipe, including data/media (you will use all your data stored on the internal memory).
1) Dowload the latest Asus firmware from Asus site
2) Unpack the zip file, the result will be another ZIP file (this is the file you need to flash)
3) Push the file on a MicroSD
4) Boot in recovery and install the firmware from the MicroSD
5) Reboot your device (at this point you will see a blu bar filling slowly)
6) Wait untill the blu bar is full and when the tablet will reboot press Volume Down so you will go into the bootloader menu
7) Select the WIPE icon (this will erase all your data so be sure you made a backup)
8) After the wipe process is done your device should boot in Android just fine
Now you can install TWRP via fastboot mode, make a nandroid backup of your clean Asus rom and then proceed with the CM 10.2 and GAPPS install , it should work at 99%.
Edit: And btw you don't have to install SU, Rom Manager, Goo Manager or stuff like that, CM builds are already rooted and ready to go.
soyusado said:
Do this:
– Reboot Recovery (TWRP 2.6)
– If TWRP promt the SuperSU installation, install it.
– Boot into Android.
– Reboot Recovery
– Flash CM 10.1 and Gapps
– Boot into Android
– Don't install SuperSU, superuser it's already merged in CM.
– Reboot Recovery
– Flash CM10.2 like an update (In TWRP /install/select the zip files, ROM and Gapps/wipe cache and dalvik/reboot system
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Followed it exactly, and when I get to the point of installing 10.2, it gives me the same error as when we talked in the other thread using TWRP (this is now using CWM):
set_perm: some changes failed
E:Error in /sdcard/cm10.2-20130730-UNOFFICIAL-tf700t.zip
(Status 7)
Installation aborted.
It doesn't make sense to me that I can install the stable builds, but not the 10.2 or nightly builds.
I'm going to try Pretoriano80's method now. I think it's deeper than just the ROM or Recovery script.
Pretoriano80 said:
Hi again mate, if i were you i would try to install a full Asus rom and Wipe everything and i mean a complete Wipe, including data/media (you will use all your data stored on the internal memory).
1) Dowload the latest Asus firmware from Asus site
2) Unpack the zip file, the result will be another ZIP file (this is the file you need to flash)
3) Push the file on a MicroSD
4) Boot in recovery and install the firmware from the MicroSD
5) Reboot your device (at this point you will see a blu bar filling slowly)
6) Wait untill the blu bar is full and when the tablet will reboot press Volume Down so you will go into the bootloader menu
7) Select the WIPE icon (this will erase all your data so be sure you made a backup)
8) After the wipe process is done your device should boot in Android just fine
Now you can install TWRP via fastboot mode, make a nandroid backup of your clean Asus rom and then proceed with the CM 10.2 and GAPPS install , it should work at 99%.
Edit: And btw you don't have to install SU, Rom Manager, Goo Manager or stuff like that, CM builds are already rooted and ready to go.
Click to expand...
Click to collapse
While trying to flash the file, I get this error:
assert failed: package_extract_file("blob", "/tmp/blob")
E:Error in /sdcard/US_epad-user-10.6.1.14.8.zip
(Status 7)
Installation aborted.
sigh
No problems while wiping everything and installing 10.1 stable and gapps, but I can't install 10.2, nightlies, and the asus firmware
As a test, I installed Stable 10.1.0 and gapps, then set up google and it immediately notified me of updates, and I downloaded 10.1.2 and then selected upgrade. It reboot into recovery fine, and installed the file just fine.
I just can't move to 10.2.
A note: When I first unlocked and rooted the tablet, I went straight to 10.1. Ever since then, I've been installing nightly builds as dirty flashes. This is the first time I've done a clean wipe of everything.
I'm wondering if I've lost some root access.
I've tried to connect it to adb. I have the drivers, the PC recognizes it as a TF700 and I can transfer files fine. If I try to connect to the device, it just stays hanging at the "adb wait-for-device" step.
JoJoDaClown said:
While trying to flash the file, I get this error:
assert failed: package_extract_file("blob", "/tmp/blob")
E:Error in /sdcard/US_epad-user-10.6.1.14.8.zip
(Status 7)
Installation aborted.
sigh
Click to expand...
Click to collapse
you are trying to flash from the internal storage or MicroSd?
Edit: Btw, which recovery you are using?
Edit 2: It makes no sense being able to install just CM 10.1 stable and no other rom, something is wrong there. Asus full rom use the staging partition to install but the recovery is failing for some reason.
Maybe you could flash the TWRP 2.5.0.0 via fastboot and try again a full wipe.
---------- Post added at 07:03 PM ---------- Previous post was at 06:43 PM ----------
Are you able to get fastboot up and running? Maybe adb doesn't work because you didn't enabled ADB debugging in Setting/Developer options
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I could also provide you the Stock Recovery for the latest Asus firmware, i'm sure that using the stock recovery you will be able to fix the issues you have. But you will have to flash it via Fastboot.
Pretoriano80 said:
you are trying to flash from the internal storage or MicroSd?
Edit: Btw, which recovery you are using?
Edit 2: It makes no sense being able to install just CM 10.1 stable and no other rom, something is wrong there. Asus full rom use the staging partition to install but the recovery is failing for some reason.
Maybe you could flash the TWRP 2.5.0.0 via fastboot and try again a full wipe.
---------- Post added at 07:03 PM ---------- Previous post was at 06:43 PM ----------
Are you able to get fastboot up and running? Maybe adb doesn't work because you didn't enabled ADB debugging in Setting/Developer options
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I could also provide you the Stock Recovery for the latest Asus firmware, i'm sure that using the stock recovery you will be able to fix the issues you have. But you will have to flash it via Fastboot.
Click to expand...
Click to collapse
I'm currently installing from microSD, although I've tried internal "sdcard" as well.
I'm now using CWM 6.x (whatever the latest is), but had been using TWRP 2.6.0.0
Your Edit2: The point of my confusion and headache.
I haven't been able to get adb up and running, it doesn't find my device. My PC interacts with the device. I've enabled developer options and enable "Android Debugging" as CM calls it.
JoJoDaClown said:
I'm currently installing from microSD, although I've tried internal "sdcard" as well.
I'm now using CWM 6.x (whatever the latest is), but had been using TWRP 2.6.0.0
Your Edit2: The point of my confusion and headache.
I haven't been able to get adb up and running, it doesn't find my device. My PC interacts with the device. I've enabled developer options and enable "Android Debugging" as CM calls it.
Click to expand...
Click to collapse
So from the MicroSD the install proccess of the full Asus firmware is working?Anyway just in case it doesn't work i've prepared a Stock Recovery blob (see attachement) for you,but it must be flashed via Fastboot.
Steps to flash:
1) Download the attachement and unzip the file ,the extracted file will be " recovery.blob "
2) Move the recovery.blob in the same folder where fastboot.exe is located ( this is valid for a Windows OS)
3) Boot your tablet in Fastboot mode (Press Volume Down + Power until you get to the Menu with the 3 icon.Don't select any icons because once you get there the device will enable the fastboot mode by default)r
4) Now open a Command Prompt from the folder where fastboot.exe is located and type the following command
Code:
fastboot flash recovery recovery.blob
5) If everything went good you will see a blu bar ,this means your Stock recovery was installed so you can reboot with this command
Code:
fastboot reboot
If nothing else works try the above and let me know.
Pretoriano80 said:
So from the MicroSD the install proccess of the full Asus firmware is working?Anyway just in case it doesn't work i've prepared a Stock Recovery blob (see attachement) for you,but it must be flashed via Fastboot.
Steps to flash:
1) Download the attachement and unzip the file ,the extracted file will be " recovery.blob "
2) Move the recovery.blob in the same folder where fastboot.exe is located ( this is valid for a Windows OS)
3) Boot your tablet in Fastboot mode (Press Volume Down + Power until you get to the Menu with the 3 icon.Don't select any icons because once you get there the device will enable the fastboot mode by default)r
4) Now open a Command Prompt from the folder where fastboot.exe is located and type the following command
Code:
fastboot flash recovery recovery.blob
5) If everything went good you will see a blu bar ,this means your Stock recovery was installed so you can reboot with this command
Code:
fastboot reboot
If nothing else works try the above and let me know.
Click to expand...
Click to collapse
I'll see if I can get to that this week. I have to fly out for work, so I'll have to load adb on the laptop.
Funny, the 20130808 CM10.2 update installed just fine.
JoJoDaClown said:
Funny, the 20130808 CM10.2 update installed just fine.
Click to expand...
Click to collapse
Well,i don't know why this build works and the previous one don't,but i'm glad you made it this time.
Hello,
As I also have the message assert failed : package_extract_file ("blob, "/tmp/blob") I used the recovery blob provided by Pretoriano80. I got the blue bar, I reboot with the command and since, my TF201 displays on loop the Asus logo and the message up above on the left "The device is Unlocked". It's blocked. Any help please?
When I try to reinstall, I got this :
C:\nvflash1>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d0787be201812
[-] Incorrect BLOB selected. nverror: 0x4.
Yet, it's my blob.bin
J'ai trouvé un autre blob.bin sur mon PC issu de ma sauvegarde. Je ne sais pas trop quel blob.bin j'utilisais avant...En l'utilisant, j'ai eu une autre erreur :
[-] Error 3 receiving response from command
J'ai suivi la recommandation de jim.g87 qui indique de télécharger un autre nvflash
https://forum.xda-developers.com/showth ... ?t=2457624
et effectivement, ça a débloqué la situation.
J'ai enfin pu lancer la commande et suivre la procédure de vanquische
https://forum.xda-developers.com/showth ... 507&page=2
Ma tablette refonctionne, avec la ROM d'origine.
You were able to get into the tablet once, it got you to the tablet's setup screen correct? - NP
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 made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?
Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.
Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.
solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S
Hi,
I'm about to install CM11 (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip) on my Nexus 5, but wanted to be sure I'm not about do something obviously stupid. I tried using the CM Installer, but it said 'firmware not supported'.
I have
- Minimal experience.
- LG Nexus 5, hammerhead
- unlocked and rooted. (it did a factory reset on unlocking)
- Fresh Android 5.1.1 with bootloader version HHZ12h.
- TWRP 2.8.7.1 (took a backup and copied the whole TWRP folder to my laptop), flashed manually using fastboot flash recovery twrp.img.
- Latest TWRP manager installed from Play Store.
- standalone adb and fastboot installed on my Windows 7 laptop. No SDK. 'adb devices' lists the phone when connected.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip is also present in same folder as adb.exe and fastboot.exe.
Questions are:
- Hope this build of CM is compatible with my Nexus 5 & the bootloader version and whatever else there might be compatibility issues.
- How should I do this: According to "official CM installation on Nexus 5 guide" on wiki.cyanogenmod.org it seems like I'm supposed to push the zip file to /sdcard/0, but /sdcard seems to be a link to /sdcard/emulated/legacy, which contains no folder named '0'. Should I create it and put it there?
If you're coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/
Click to expand...
Click to collapse
OR
Given that "cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/", can I just: boot to recovery, click on Install, select the zip file and swipe to flash?
Finally a general query: Is there any reason I have to connect the phone to my laptop and run any adb, fastboot commands except to transfer the zip file from laptop to phone and to boot into bootloader or recovery with fastboot command? I already have TWRP running.
Thanks
Kashyap
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
I don't use cm, but that sounds like the right file. It doesn't matter which location the zip file is on your sdcard as far as I know, I think they've just said /sdcard/0 to make it easy to find from within twrp. Sounds to me like you've covered all your bases, nice to see someone manually flashing a nexus as a start. I'd go ahead and flash the zip, don't forget to factory reset if you're coming from stock. Also, you may want to find a gapps package if you haven't already. Since you seem to have taught yourself the right way, and your PC is setup for fastboot already, it should be easy to flash back to stock/restore under twrp. You don't even need adb to push files to your phone, you can just download them straight to the device. I generally only use my PC for fastboot flashing to stock,or transferring large amounts of data. Good luck, enjoy your nexus - first boot will generally take just long enough that you'll start wondering if its broken.
Thanks for the quick response.
scissors_cut_paper said:
don't forget to factory reset if you're coming from stock.
Click to expand...
Click to collapse
Just curious why?
If i do a factory reset, will it not delete /sdcard/cm-11-20141008-SNAPSHOT-M11-hammerhead.zip? Do I just copy it from laptop to phone after reset and proceed to flashing? Or there is some way to not wipe 'sdcard' during factory reset?
scissors_cut_paper said:
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
Click to expand...
Click to collapse
I did do a TWRP backup, but selected what to backup in the TWRP manager app, there is no option called EFS. Anyway, I'm creating a new using the recovery UI, where there is a check box called EFS. Thanks!
scissors_cut_paper said:
nice to see someone manually flashing a nexus as a start.
Click to expand...
Click to collapse
Didn't know there was any other more automated option/way. , is there? Only thing I knew was the CM Installer, which said the firmware isn't supported. .
scissors_cut_paper said:
Also, you may want to find a gapps package if you haven't already.
Click to expand...
Click to collapse
Yes, I was planning to, but taking it step at a time. .
I was planning to get gapps-kk-20140606-signed.zip from cyanogenmod.org, but lets see. I'll probably post another question here asking which is the compatible one.
Factory reset just wipes data/cache/dalvik, it should leave your sdcard storage intact. Just out of interest,why cm11? KitKat is pretty long in the tooth, and I've always found aosp based ROMs to perform better than cm on nexus 5. The problem with having no gapps will be no access to play store/google account services, so you'll have to get apps from less trustworthy sources.
Worked
Thanks.
It worked fine. Though it was totally useless without either the play store or basic CM apps. Couple of notes:
- After wipe/factory-reset (from TWRP Recovery UI) /sdcard was untouched.
- Installed the ROM using TWRP Recovery UI -> Install -> Select the zip file from /sdcard and swipe.
- CM Installer on Windows 7 laptop worked fine once the CM was installed. But it downgraded the build from Nov to Aug-2014.
- Also CM Installer removed my TWRP and replaced it with CWM. Not happy.
So actually all that's needed is:
- Unlock the bootloader and root.
- Install TWRP Manager
- Try to use the TWRP Manager's "Install TWRP" to install the TWRP Custom Recovery. If that doesn't work then do it manually. Download twrp.img
- Install ADB and fastboot, you don't need the whole 1GB Android SDK. Just search for "ADB Fastboot without SDK".- Enable USB debug, connect the phone and ensure that 'adb.exe devices' prints a device.- fastboot flash recovery twrp.img- Download the ROM zip file you wanna install on the phone itself, no need to involve the laptop.
- Boot into recovery (e.g. using TWRP Manager -> Reboot options) and do what I did above.
Once you've installed Cyanogenmod, DO NOT use CM Installer. This is written in July'2015. May be things would improve in future.
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.
My new Xiaomi Poco X3 Pro is showing an error screen after some time, like in this post:
https://forum.xda-developers.com/t/cant-load-android-system-lineageos.4314035/
It reads "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
After the first error screen
- I tapped Try again,
- When the error occurred again, I tapped "Factory data reset," but the error still occurred. The phone is new, no user data is on the phone.
- I booted into recovery and reset all the data I could. When I tap "Format system partition" it throws an error "E: Failed to open /dev/block/dm-0: No such file or directory. System wipe failed."
- Then I repeated the adb sideload. The error occurs again.
- I removed the SIM card, as someone in the forum suggested this could be a problem source. The error still occurs.
What can I do now?
----
Update [2021-12-05 Sun 20:09]
It seems to be a Problem with the GApps Version.
What I did Try so far is:
- Install 03-12-LOS and latest GApps via LOS recovery (didn't work)
- Install 03-12-LOS and latest GApps via TWRP recovery (didn't work)
- install LOS Build from 26-11-2021 without GApps (works)
- Install LOS Build from 26-11-2021 with latest GApps (didn't work)
- Install LOS Build form 26-11-2021 with GApps from 25-11-2021 (works)
Just use TWRP, flash ROM and AFTER flashing ROM Format Data where you have to type "yes". (Format, not Wipe)
Xiaomi Poco X3 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Thanks for the Idea. At the moment it has not solved the problem.
This is what I did:
- Flash TWRP
Code:
fastboot flash recovery TWRP-3.5.2-vayu-Nebrassy-2.img
- copy lineage-18.1-20211203-nightly-vayu-signed.zip and "open_gapps-arm64-11.0-nano-20211204.zip" to the Poco device
- install via "install" option, wipe cache at the end of installation
- Format files (via "Wipe" -> "Format Data" -> type "yes")
- Reboot
After some time of the animated Lineage OS logo, the phone reboots into TWRP.
To me this seems very similar to the Lineage recovery before.
Any ideas what could be wrong?
You probably wiped System or Vendor partition or something, you are not supposed to do that.
Most likely you have to reflash MIUI now first. Make sure it's atleast version 12.5.X.X.
Flashing instructions are really simple, this apply to all ROM's.
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
FLASHING UPDATES?:
Download via OTA Updater and let it automatically install; OR
Download an update, transfer to internal/external storage (always check file sha256)
Flash ROM zip and reboot.
Do not wipe anything else or add any additional steps. (maybe except Gapps if ROM doesn't have them included)
ps.
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
Click to expand...
Click to collapse
k3lcior said:
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
Click to expand...
Click to collapse
I followed the LOS Install Guide: https://wiki.lineageos.org/devices/vayu/install But this procedure does not seem to bee the cause (see below).
Download the LineageOS installation package that you would like to install or build the package yourself.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. When Xiaomi/POCO/Redmi splash appears, release Power and keep pressed Volume Up until recovery appears.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Click to expand...
Click to collapse
Okay so this is what I did (the part that works):
- I downloaded the latest possible stock ROM from https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/#vayu The fastboot ROM is more than 5GB.
- Extract the file "vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea_05cc38de43.tgz"
- then connect the phone via USB cable in fastboot mode and:
Bash:
cd ~/Downloads/vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea
/bin/bash ./flash_all.sh
- The default MIUI starts flawless, as it dit the first time I turned on the phone. So far so good.
What didn't work:
1. I installed the LOS Recovery again and flashed the OS and Gapps. Only after that I did step 3 - formating. The result ist the same bootloop as in the beginning.
2. I flashed the stock MIUI ROM again (which woks fine). Then I flashed TWRP, transfered the OS and GApps file and installed. I did not wipe anything, just used "format data" like above.
In both cases the OS does not start. After a while displaying the LOS-logo the phone reboots to recovery.
What did work:
I downloaded lineage-18.1-20211126-nightly-vayu-signed.zip, one version before the latest verion and the corresponding recovery lineage-18.1-20211126-recovery-vayu.img
I flashed only the OS, and no GApps -- and it launched successfully. Installing with the latest GApps failed again.
Install older gapp, not all gapp is compatible