Hello
I try to install a custom recovery on my tf701 (android 4.3, USB debug ON)
here are the previous steps i did :
1/ i have unlock the bootloader using ASUS tools : OK
2/ i have root the TF701 : OK
for this, I installed Minimal ADB and Fastboot
I copy the files found here
and I lauch the command : adb reboot bootloader
then : fastboot boot zImage_dtb ramfs.img.gz
the root is ok
-------------------------------------------------------------------
3/ i try to install recovery
i download the file here : droidbasement.com/asus/tf701t/recovery/
i put the file in the folder of Minimal ADB and Fastboot
and i launch the commande : adb reboot bootloader
then, when the fasboot usb mode is ready on the device : fastboot flash recovery recovery.img
first time :
target reported max download size of 64382
sending 'recovery' (6652 KB)...
FAILED (data write failure (Unknown error)
finished. total time: 5.050s
second time :
target didn't report max-download-size
sending 'recovery' (6652 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.010s
Can you help me please ? I add that, when the device is ON in a normal mode (not fastboot) and connected to the PC with USB, the adb driver interface are ok :
"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
E1OKCY174091 device
"
i have tried to plug on other usb port ... it's the same ...
i have tried to reboot my computer : ... it's the same ...
i have tried to download another version of adp/fasboot (platform-tools_r28.0.2-windows.zip) : it's the same
without this installation, I can't install a custom rom ..
Many thanks in advance !
There are only two working recoveries for the TF701, one CWM without touch interface which I don't quite trust and a pretty good TWRP with touch here https://www.google.com/amp/s/forum....-kang-twrp-tf700t-2-8-x-xarea51-t3121989/amp/
The one you have there is probably the stock recovery...
The Kang TWRP is a little buggy though. You may come to a point where TWRP tells you it cannot mount /system or any other partition for that matter. All you have to do is convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.
Good luck!
Sent from my Pixel 2 using Tapatalk
Hello berndblb
Many thanks for your help
The recovery I try to install is Recovery v6.0.4.6 CWM 11.
Which one is the easier to install for a beginner ?
Because what you said previously seems difficult for me ("convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.")
Can you explain me how to do ?
Recovery v6.0.4.6 CWM 11 or Kang TWRP : can i install then the Rom "
ROM][N 7.1.2] [ KatKiss - Nougatella #037 ] for asus tf701
?
Many thanks in advance
They are equally easy to install since you just flash both of them in fastboot
But if you are asking which is easier to use, then it is the Kang TWRP. CWM does not have the drivers for the touch interface and you have to navigate everything with the vol buttons. More importantly I do not trust the "format data" function in CWM and that is crucial to install a custom rom. The issue with the corrupt file system in the Kang TWRP is a minor nuisance and you fix it right in TWRP. If you get the "cannot mount....." error, you just go to Wipe > Advanced > Change or repair file system, check the System partition and convert it to ext3 (or ext2 - does not matter). Swipe the button and when it is done (less than a minute) you repeat the step and change it back to ext4. After that everything should be good. If you want to read more about this issue search the Katkiss thread for "cannot mount"
Actually, there is another custom recovery out there which I have not tried and cannot vouch for. But maybe you go for that one, it does not seem to have the same issue and is based on a later version of TWRP: https://forum.xda-developers.com/tr...lopment/recovery-twrp-3-2-1-x-tf701t-t3720912
Read the thread, it seems to work fine. The Kang TWRP is 2.8, that one is based on 3.2.1 - both are fine to flash a Katkiss rom.
You do know that you have to fully format /data before you can flash a custom rom, right? You do that in your custom recovery (in TWRP: Wipe>Format Data, swipe the button). TWRP does a secure erase which wipes and trims every block. That's why this formatting takes around 60 minutes. Do not interrupt it!! CWM does not have this functionality, another reason I prefer TWRP..
hello berndblb and all helpers !
i have installed the Kang TWRP: it's ok
then I copy the custom rom KatKit for TF701 on /sdcard
i do a full wipe : error : "cannot mount..." : so I convert to ext2 and then I convert to ext4 the partition System and data
then i do a full wipe
my problem ... i'm sure you find it : i have erased all my data on /sdcard. No kitkat.zip yet !! :crying::crying::crying:
how to copy the rom on my tablet ?
for your information, when I am in TWRP, i can do "adb devices" on my computer :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
15C4110C61C00000009FB01C0 recovery
But push commande is failed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push KatKiss.zip /sdcard/
adb: error: failed to copy 'KatKiss.zip' to '/sdcard/KatKiss.zip': no response:
Connection reset by peer
i put kitkat.zip on a USB Key and I plug it on my docks : it seems not be recognized ...
i 'm really lost
please help !!
Put the Rom on a microSD, mate. You can navigate in TWRP to the card and flash from there
Sent from my Pixel 2 using Tapatalk
Hello !!
I have nevers seen the microsd port ! I discover it 2 days ago !
Just before your answer, a 'adb push' was successfull ! I don't know why, and the next 'adb push' for gapps ans supersu were unsuccessful...it's strange !
But all IS ok now !
I have just a last 2 questions :
1/ next Time, where Can i copy the rom (.Zip) , somewhere it will not be deleted ?
2/my tablet is not rooted now ... Is the way to root depends on the Rom ?
If I follow the steps i did when my tf701 has the rom stock, IS still good ? (https://forum.xda-developers.com/showthread.php?t=2516215)
Thanks for your help !
1) the safest place is a microSD. You can flash the Rom straight from there. But as long as you do not format your data partition - and you only need to to that if you install a different rom - you can keep it on internal storage. In most cases you only need to wipe /data, not format, and that leaves /data /media where your files live, untouched.
2) First the question is: Do you need root? You should only root your rom for a good reason. If you are not sure if you need root - you don't.
Cyber threats are multiplying. You're safer if the tablet is not rooted.
That said: you can root by just flashing the zip in recovery.
BTW, if you did not flash gapps yet, you always should flash it together with the rom, not separate. To install gapps now flash the rom, then gapps, then root (if needed), reboot
Sent from my Pixel 2 using Tapatalk
Related
just a quick tool i put together that unlocks bootloader, flashes a recovery image, installs root, s-off and writes superCID!
simply install the exe file and run it off your desktop(sorry windows only)
FULL FEATURES:
Free Me (Unlock Bootloader, Flashes Recovery, Roots Device, S-OFF, Writes SuperCID)
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
S-Off
Enable root permissions
Force Update
Flash any .zip file
Flash a rom
Create a logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Flash custom radio
Fix sdcard errors
Fix low batter error
Reboot options
Advanced wipe Options
Pulls Files From Server
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
Click to expand...
Click to collapse
Download Here
REMEMBER! IF YOU LIKE MY TOOL HIT THE THANKS BUTTON OR EVEN BUY ME A KANGAROO!
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
anders3408 said:
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
Click to expand...
Click to collapse
i have flashed .zip files on other phones like nexus and desire hd, it was successful, but i have not tried it on sxl as do not have the device anymore but seeing as developers gave so much to me from this forum, i thought id give a little back before i move on to learning ios development, try manual adb and executing adb root then flashing your kernel or zip
i havent tested roms yet though
as of the flashing kernel.zip, i do not know why it did not flash, maybe also try the adb root command before flashing?
and on some devices your phone will not charge it bootloader or recovery and when you want to revert back to stock os, no root, no custom recovery etc. some peoples devices fail to restore after the phone wipes system, data and cache partitions while there battery is below i think 18 percent, and fastboot wont allow you to boot into recovery until battery is above that amount.
why dont they turn their phone off abd let it charge? because when they connect the charger the phone boot into bootloader
i found a guide on google the other week as a request of adding the feature and those commands worked
this is a beta, thanks for the bug reports, will update it and fix the bugs later tonight
our bootloader does not support flashing zip files, that part is locked even if s-off
anders3408 said:
our bootloader does not support flashing zip files, that part is locked even if s-off
Click to expand...
Click to collapse
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
ricky310711 said:
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
Click to expand...
Click to collapse
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
anders3408 said:
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
Click to expand...
Click to collapse
i will look into that, as im sure you know i have only just started development, im still learning from people like, but am gonna give back as much as i have took
So this tool basicly roots the sxl for ya am I right going to give it a try today if it does
Sent from my GT-N7105 using xda premium
Hi !
I tried to install Milaq Rom CM11 from CM10.1.
My partitions layout is ok :
- system 600 Mb
- cache 200 Mb
- media 6Go
- data ~20 Go
But, after flashing with CWM 6.0.4.6, the screen stayed blank.
So, i decided to format partitions, but i formated all partitions (i was tired :crying Now, i don't have access to my .zip on CWM.
How could i retrieve them to flash again ?? maybe with WebOS ?
Thanks for you help !
Bristow69 said:
Hi !
I tried to install Milaq Rom CM11 from CM10.1.
My partitions layout is ok :
- system 600 Mb
- cache 200 Mb
- media 6Go
- data ~20 Go
But, after flashing with CWM 6.0.4.6, the screen stayed blank.
So, i decided to format partitions, but i formated all partitions (i was tired :crying Now, i don't have access to my .zip on CWM.
How could i retrieve them to flash again ?? maybe with WebOS ?
Thanks for you help !
Click to expand...
Click to collapse
try sideloading your installation zips
Choose install from ADB Sideload in CWM. On your Computer type in a terminal: adb sideload image.zip, where image.zip is the file you like to flash.
Good luck on the sideload.
And you now have 10 posts and can post in the CM11 thread!
Flash with ADB sideload on Ubuntu
Thanks !
I tried with success adb sideload on Ubuntu.
It's pretty easy :
Code:
sudo apt-get install adb-tools
Go in to the recovery and activate sideload (install zip from / activate sideload...)
Code:
adb devices
in order to see if device is recognize
Code:
adb sideload rom.zip
That's all !
I like it :victory:
Hi guys,
I have xperia sp, where I had a newest firmware installed. I decided to mod it to newest cyanogenmod (android 7.1).
Using night build, install boot.img and using adb install rest of system. Forgot to install gapps, but system ran smoothly.
So i decided to install cyanogen once again, following these steps:
1. fastboot - flash boot.img
2. system clean - wipe /system, /data, /cache (wipe all available from recovery menu)
3. Trying to upload system using adb, by selecting on recovery menu "sideload". ADB failed - mot recognise device
4. Upload system (cyanogenmod) to sd card and trying to update from recovery menu
5. SD card is fully visible, but when trying to update got an error: "E: unable to find /misc partition" (!!!)
6. 3,4,5 I tried many time, unsuccessful
7. Decided to downgrade to original firmware using flashtool.
8. All files *.sin uploaded successfully, except system.sin (size above 1GB)
9. Trying to upload system.sin manually using fastboot, but got the error "(file too large)
Now I have original boot, but phone is locked on "SONY" screen
I need any advice, how to upgrade phone to any system.
btw, I tried all available stock firmwares (254, 205, etc)
best regards
M.
Dunno and not sure but it doesn't cost nothing to try:
with fastboot flash kernel from 7.1 zip package and also flash twrp 3
then try to enter twrp recovery (VOL+ when lights up)
Don't use the latest version of flashtool and use version 0.9.18.6 instead to flash stock firmware
http://www.flashtool.net/downloads.php
Sent from my Xperia SP using Tapatalk
Thanks.,
it helps Previous version of flashtool did it correctly.
Now I have new question related to CM:
after sucessful installation of CM, I back to recovery
1. Copy OpenGAPPS to sdcard
2. Initiate aplly update from sdcard
3. Installation started but
4. Got an error "E: failed to map file"
tried different versions of OpenGAPPS (pino, nano, micro) with the same result.
Should I use recovery image from cyanogenmod?
And next, when I tried to execute:
fastboot flash recovery twrp.img
got an error:
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
I need to install open gapps.
best regards
M.M.
Ok, I fixed it
Installed TWRM recovery and install gapps finally.
Thanks for help
Dear friends I need help!
I've tried to flash my tablet but I've got an error message while flashing Katkiss 6.0
What I did:
downloaded Rom.(md5sum is OK)
my bootloader is ww_epad-11.4.1.17-20140711
recovery CWM v6.0.5.0
previous rom zoombi pop
/format data
wipe data factory reset
install zip from sd card. (from internal storage or micro sd card)
And I have got the following error (in attachement)
Please help, my tablet boot only recovery now.
Thanks in advance for the help
trying to boot in fastboot mode when children let me try that...
Edit: fastboot ok.
I placed the the files
KatKiss-6.0_TF701T_033.zip
open_gapps-arm-6.0-pico-20170120.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
In
C:\Program Files (x86)\Minimal ADB and Fastboot
ok I don't know how to proceed now.
Seems I cannot change the recovery from CMW to TWRP,
My bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30
So how can I do?
I there a way to upgrade the bootloader to be able to install TWRP?
Or should I Flash the custom rom from fastboot?
My TF701 in not booting anymore.... only bootloader and recovery CMW
the positive thing is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
15C3E10090400000011FA8580 fastboot
Please help
I have been able to flash CROMI X (unfortunately with strong battery drain) so CMW is able to flash but for some reasons not Katkiss 6.0.
I have been told that my problem is not ROM related... So it is recovery related?
What is the better option to get katkiss on my tablet? Flash the recovery to get TWRP even if my bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30????
There is a technical reason about this warning?
Edit: I found this on an old post:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
Click to expand...
Click to collapse
Would this method work to get the latest stock rom from Asus?
Got your PM and will try to find some time at work today. Hang in there and don't do anything to make it worse
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
berndblb said:
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
Click to expand...
Click to collapse
Thanks a lot to take time to help me.
Will try that tonight and I'll let you know the result.
Thanks a lot!
It was just like you said.
I had to format to ext3 and ext4 because I had errors.
Battery seems to be very good. Just the screen display is very white, needs color saturation and contrast I guess...
Thanks again you save my tablet.
Now that's what I like to read! :cyclops:
Hello dear fellows,
since 2 days i try to fix a problem with my unlocked and rooted Sony Xperia Z C6603. Still not finding any solution via internet, i take my last chance and post it here.
I unlocked and rooted my C6603 2 days ago and installed via fastboot the actual Lineage Custom ROM lineage-14.1-20171027-nightly-yuga-signed.zip.
Everything worked fine.
Bootloader -> fastboot flash boot boot.img (from lineage-14.1-20171027-nightly-yuga-signed.zip) :good:
Restart into Android Recovery :good:
Install via ADB sideload lineage-14.1-20171027-nightly-yuga-signed.zip :good:
Install via ADB sideload LineageOS 14.1 ARM32 SU (for full root access) :good:
Boot into Lineage, activate dev options and enabled Android-Debugging + Root-Access -> Apps and ADB :good:
Now my problem:
The so called "Android Recovery" is rly bad, so i try to override this recovery with TWRP 3.0.2.0 (yuga) but everytime i get the following error:
Code:
fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10656 KB)...
OKAY [ 0.351s]
writing 'recovery'...
[B]FAILED (remote: Command not allowed)[/B]
finished. total time: 0.370s
Where is my fffffff problem^^ Yes my phone is unlocked and yes, it is rooted (checked it also via root app).
I cant install gapps (dont work with ADB sideload) and and i want a proper recovery for backups and stuff...
So, what is wrong with me? Maybe someone of you have a good idea and can help me, i would rly appreciate it!
Sry for my not so proper english, hope u understand my problem anyway
Phone information:
Sony Xperia Z C6603
Android 7.1.2
LineageOS 14.1-20171020-NIGHTLY-yuga
LineageOS API-Level Guava (7)
Kernel-Version 3.4.113-yuga-gd710842
Build-Number lineage-yuga-userbug 7.2.1 NJH47F f281cb28f4
Thanx for all the help^^
I figured it out what to do:
1. fastboot flash boot twrp(actualversion).zip NOT fastboot flash recovery twrp(actualversion).zip
2. reboot into TWRP recovery mode
3. check if u can mount your data folder
3.1 if not, go to wipe -> advanced wipe -> change file system to ext4
4. install via ADB the actual LineageOS (or put the actual LineageOS file on your Sony/SD)
4. install LineageOS 14.1 SU via ADB (or put the actual LineageOS 14.1 SU file on your Sony/SD) -> https://www.lineageosroms.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/
6. install Open gapps -> http://opengapps.org/
7. reboot and configure LineageOS
7.1 check your developer options -> Debugging + root access for ADB and apps
8. download TWRP apk via PlayStore
8.1 give TWRP apk root access and download the actual TWRP file for yuga
9. flash this TWRP recovery via app
10. DONE
Everything works fine (for now )
Topic can be closed!
Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.
nurps said:
Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.
Click to expand...
Click to collapse
Did you manage to solve the issue? I have the exact problem. The TWRP says it flashed but recovery is still stock android.
I have C6602. Someone on reddit gave me the solution; (do note that I had to run
Code:
adb root
for
Code:
su
to work.
You have a Xperia device which deals with recovery kind of weird. Recovery is stored with the kernel, not in a standalone recovery partition. Because of this you need to flash it to a FOTAKernel partition and use a kernel that supports FOTAKernel (the LineageOS one does).
To flash TWRP, first move the recovery image to your device with the adb command
Code:
adb push twrp-3.0.2-0-yuga.img /sdcard
. Then run
Code:
adb shell
to get access to the shell. Then run
Code:
su
and accept any prompts to gain root access. Then to actually flash, run
Code:
dd if=/sdcard/twrp-3.0.2-0-yuga.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse