Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Marcusprit said:
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Click to expand...
Click to collapse
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
es0tericcha0s said:
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
Click to expand...
Click to collapse
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Marcusprit said:
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Click to expand...
Click to collapse
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
es0tericcha0s said:
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
Click to expand...
Click to collapse
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Marcusprit said:
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Click to expand...
Click to collapse
Your device boots and is already rooted, right? If so, try to flash the updated img files with : https://play.google.com/store/apps/details?id=com.cgollner.flashify
recovery
Thank you I now have recovery
Marcusprit said:
Thank you I now have recovery
Click to expand...
Click to collapse
Related
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer
I installed SultanXDA's CM13 ROM and I am using TWRP (not the 3 version). I haven't installed SuperSU, so it means that I am not rooted, too... But...
I wanted to flash this camera: http://forum.xda-developers.com/one...t-oxygenos-3-0-1-beta-camera-cm-aosp-t3386799
The problem is that when I get to recovery mode in order to install the zip file, I see all kinds of folders, but not my "normal" ones... I am using my SD card as internal space...
I read somewhere that I have to update to new TWRP 3 in order to overcome this...
So, does it have to do with the version of twrp and if so, how can I update it without being root and without being able for the current TWRP to read the zip files that I will "feed" it?
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
dimxr said:
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
Click to expand...
Click to collapse
If your Bootloader is unlocked try Fastboot.
Reboot OPX into Fastboot Mode. (Power + Volume Up i think or trough TWRP or CM)
Connect it to your PC
On PC: Download the latest TWRP img File
Start CMD in same Folder as the downloaded File is.
Type: 'Fastboot devices' to make sure your OPX connected properly
Typ: 'Fastboot Flash Recovery *DownloadedTWRP*.img'
Flashing new TWRP only overwrites current TWRP and doesn't erease anything else
OverBit said:
On PC: Download the latest TWRP img File
Click to expand...
Click to collapse
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
dimxr said:
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
Click to expand...
Click to collapse
Without any problem.
Maybe you be able to download it when i attach it.
Was to big to upload it as img, so I renamed it to .apk,
So don't forget to rename it to .img
Great! So, the procedure begins!
EDIT: I encountered numerous problems in installing CM13 on Z5C, but a solution is already written here, and it's better than what I could write (because me no good english
Also the problem as explained below is determined only by a wrong environment, in which I blindly flashed uncompatible SW.
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
C:\adb>fastboot flash recovery TWRP-3.0.0.0-suzuran-v2.img
sending 'recovery' (21760 KB)...
OKAY [ 0.756s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.943s
Click to expand...
Click to collapse
Despite the lack of errors the phone is completely unaffected, there's no way I can enter recovery but flashing with "fastboot flash boot", which is improper and so OS loading is broken (it boots only the recovery).
EDIT: I then discovered that's normal behaviour, and that I wasn't able to boot in recovery normally because I flashed Marshmallow SW on Lollipop
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
davidbevi said:
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
Click to expand...
Click to collapse
There's nothing wrong here? Looks successful to me.
civicsr2cool said:
There's nothing wrong here? Looks successful to me.
Click to expand...
Click to collapse
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
You might want to re-download the TWRP and flash it again. You might be that one in a million person who have a corrupted downloaded file.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
Download twrp 3.0.2, you're using the wrong one. Also if you use flash tool you can hotboot the recovery to get into it if you don't have a custom kernel that will allow you to get into recovery.
firdyRAY said:
[...] corrupted downloaded file.
Click to expand...
Click to collapse
I doubt because I tried 3 different packages, and every single one works, just I have to flash it unproperly. I would follow your advice anyway if it wasn't for:
civicsr2cool said:
Download twrp 3.0.2 [...]
Click to expand...
Click to collapse
This is the only thing I found googling, can you please give me a link or more info?
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
davidbevi said:
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
Click to expand...
Click to collapse
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
civicsr2cool said:
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
Click to expand...
Click to collapse
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
davidbevi said:
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
Click to expand...
Click to collapse
its in the thread somewhere towards the middle because i tested lollipop to cm13 and got nowhere fast as well.
edit:it says in op that required firmware is 6.0 fwiw
I try to install .img file in recovery, but after install this, my phone shutdown in software brick....
AyalaE96 said:
I try to install .img file in recovery, but after install this, my phone shutdown in software brick....
Click to expand...
Click to collapse
Don't use install img option on twrp it may not work always
Instead of that you can flash recovery using fastboot with "fastboot flash recovery (the name of recovery).img) command
raminta said:
Don't use install img option on twrp it may not work always
Instead of that you can flash recovery using fastboot with "fastboot flash recovery (the name of recovery).img) command
Click to expand...
Click to collapse
I tried, and it didnt work...
AyalaE96 said:
I tried, and it didnt work...
Click to expand...
Click to collapse
Do you have unlocked bootloader???
raminta said:
Do you have unlocked bootloader???
Click to expand...
Click to collapse
yep
raminta said:
Do you have unlocked bootloader???
Click to expand...
Click to collapse
I solved it, I first must install Repack boot with "fastboot flash boot ...img"
After install recovery with "Fastboot flash recovery ...img"
My error Because I should read this first...
Dees_Troy said:
Note that the Z2, like most other Sony devices does not have a proper bootable recovery. As such you have to install a kernel that includes a recovery with it. For a time I will try to continue to supply updated stock kernels repacked with TWRP in them. If you are running one of my kernels or have a custom ROM like OmniROM installed, you can install TWRP in the FOTAKernel partition to stay on the latest version of TWRP.
Device page on our website
Mirror 1
Mirror 2
To install a stock kernel, boot the device into fastboot mode and then from your computer: fastboot flash boot path/to/filename.img
Click to expand...
Click to collapse
However is it true? With latest updates there was bootloader update which brings (or at least should as Sony said) /recovery partition (or more gives access to it, coz partitions was probably always there).
However how it exactly works? I always thought that onee flashed update with newest bootloader will leave new bootloader and this partition forever. But I got Z2 with .291, downgraded it to 4.4.2 for Root and TA backup and than tried to flash recovery to recovery partition, but got error: FAILED (data transfer failure (Unknown error)).
Does it mean that only on latest update(s) there is possibility to use this partition?
Never tried it on my ZU before. I just started form latest 5.1.1.
EDIT: OK, so what i assumed was right - on 6.0.1 I was able to flash the recovery to it's partition.
Now the problem is with booting into it. How? With Power + Vol- it still stright to boots to OS...
EDIT2: adb reboot recovery boots to different bootloader screen (Power+Vol- gives SONY screen and adb gives SONY + XPERIA screen.
However it still boots strght to Android...
Any idea what I'm doing wrong? I have 23.5.A.1.291 + unlocked bootloader + TWRP 3.0.2-0 (official) flashed with fastboot flash recovery img.
I'm 100% sure that SONY screen (w/o XPERIA) is the right one as I have identical one on my ZU when booting into bootloader-recovery mode. But why here it don't boot TWRP, but OS?
HELPPPP
Pleaseeeee tell me how did you flash twrp 3.0? I have tried almost everything it now seems impossible for me... Pleaseee helpp me T_T ... Thankk youuu