[RECOVERY] TWRP 3.1.1-0 for Z5C [suzuran] - Xperia Z5 Compact Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download : Google Drive
How to flash?
1. Shutdown your Z5C
2. Connect to PC in Fastboot mode
3. Flash with this command
Code:
fastboot.exe flash recovery twrp_recovery.img
Do NOT forget to hit Thanks button :fingers-crossed:
Credits : bbs.gfan.com
Contributor : @grayleshy

Seriously, someone took my recovery and changed the theme and all?

grayleshy said:
Seriously, someone took my recovery and changed the theme and all?
Click to expand...
Click to collapse
I don't know it is yours or not? How can you be sure?
Did you left any #comment# for this? If you did I will add you as a contributor.

delete

grayleshy said:
ro.build.host=grayleshy-virtualbox
Click to expand...
Click to collapse
I see, thanks. I edit the post.

grayleshy said:
delete
Click to expand...
Click to collapse
sorry I did not go through your consent then modify the TWRP, sorry again.
your work are very nice!
thanks again.

@sceryavuz What sources did you use to compile? I tried Dirty Unicorn's and Omnirom's but I had lot of errors with both.

DJHasis said:
@sceryavuz What sources did you use to compile? I tried Dirty Unicorn's and Omnirom's but I had lot of errors with both.
Click to expand...
Click to collapse
Here : https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050

this work on 7.1.1?

sceryavuz said:
GreyLeshy said:
Seriously, someone took my recovery and changed the theme and all?
Click to expand...
Click to collapse
I don't know it is yours or not? How can you be sure?
Did you left any #comment# for this? If you did I will add you as a contributor.
Click to expand...
Click to collapse
isn't there a rule about not doing this?

it's flashing well but it doesn't work on 7.1.1.
I'm new to the Z5C and currently not sure about choosing the best approach for installing TWRP.

Ilko said:
it's flashing well but it doesn't work on 7.1.1.
I'm new to the Z5C and currently not sure about choosing the best approach for installing TWRP.
Click to expand...
Click to collapse
What do you mean "it doesn't work"? How did you install TWRP?

I meant what I said, after flashing, rebooting into recovery has no effect, it boots normally. I know that I'm doing it wrong for now but looking for the right method.
BTW, just found that for being as up-to-date as possible the only way seems to flash a .33 firmware first. I already miss my ZR, everything was easier...

When I give twrp permission to modified system partition my phone fail to boot to system is there any fix for that?
I am using Xperia z5 compact E5803
Android version: 7.1.1
Build number: 32.4.A.0.160
Kernel: 3.10.48-perf-g5e25a09 (stock)

Mostafa8296 said:
When I give twrp permission to modified system partition my phone fail to boot to system is there any fix for that?
I am using Xperia z5 compact E5803
Android version: 7.1.1
Build number: 32.4.A.0.160
Kernel: 3.10.48-perf-g5e25a09 (stock)
Click to expand...
Click to collapse
I don't know what's the problem but when I flashed Greenkernel every thing works fine.It maybe the stock Kernel was the problem

Lost TWRP
I lost twrp tried to flash in fastboot mode but having errors..
I connect pc via fastboot
opening command screen
fastboot flash recovery recovery.img and getting this error
-target reported max download size of 536870912
sending recovery (19800 KB )
OKAY ( 0,757s )
writing recovery ...
failed ( remote: image is not a boot image, nor ELF )
finished. total time : 0,777s
It s first time i am having this problem.. I can flash a kernel bot cant flash a recovery.
Also not working this command too fastboot boot recovery recovery.img
I dont think i have a driver problem ( i checked many times )

Ilko said:
I meant what I said, after flashing, rebooting into recovery has no effect, it boots normally. I know that I'm doing it wrong for now but looking for the right method.
BTW, just found that for being as up-to-date as possible the only way seems to flash a .33 firmware first. I already miss my ZR, everything was easier...
Click to expand...
Click to collapse
I have the same problem you had. The device simpy wont boot into recovery. Did you manage to get it working with a .33 firmware? did you use Stock kernel?

maxi*king said:
I have the same problem you had. The device simpy wont boot into recovery. Did you manage to get it working with a .33 firmware? did you use Stock kernel?
Click to expand...
Click to collapse
Yes, in fact, it was a problem that I wasn't expecting. I was trying to boot into recovery via reboot menu or app, but it's not actually working. Simply try VolDown+power while the device is off. You can release when it vibrates.
Sent from my Funky Z5C

Ilko said:
Yes, in fact, it was a problem that I wasn't expecting. I was trying to boot into recovery via reboot menu or app, but it's not actually working. Simply try VolDown+power while the device is off. You can release when it vibrates.
Click to expand...
Click to collapse
Thank you so much! :good:
Now it works
I can't believe that I flashed my phone multiple times because I didn't manage to start into recovery :cyclops:

Can´t get twrp to work on z5c
Hi guys!
I just bought a new Z5C and already saved TA, unlocked bootloader and flashed twrp (twice - 3.0.2 with rootkernel, this 3.1.1 with fastboot). All on Android 5.1.1 (32.0.A.6.200) stock rom. Now the phone is working and rooted with SuperSU.
Problem:
I can only start the old 3.0.2 twrp inside the kernel with pressing volume up when led is yellow but I can´t start 3.1.1 with power + volume down. I don´t get a purple led and most of times it just starts Android. Sometimes it gets stuck on Sony bootscreen (guess this happens when I did correct button combination but twrp fails to start?).
Any idea where the problem is?
fastboot flash recovery twrp_recovery.img results in:
sending 'recovery' (19800 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.636s
Click to expand...
Click to collapse
So everything should be ok, right?
Kernel can not be the problem as I understand as kernel has nothing to do with recovery, right?

Related

CWM Recovery and Root (Stock Kernel Sony 4.2.2)(pollux_windy)

Stock Kernel Packed with CWM
Requirements:
Sony tablet Z Wifi version aka pollux_windy
Unlocked Bootloader
Sony Firmware 4.2.2
a computer with working fastboot
Install Procedure:
connect device to pc
Open CMD/Terminal and cd to the folder you have placed the boot image
type this in CMD/Terminal:
Code:
adb reboot bootloader
Now Flash using:
Code:
fastboot flash boot boot.img
Now Reboot your tablet by:
Code:
fastboot reboot
How to Enter recovery:
The key combination to enter recovery is broken and will be fixed later on. Currently you can reboot to recovery using:
an app like Rom Manager
adb reboot recovery
using terminal emulator (su followed by reboot recovery)
Download Link: (POLLUX_WINDY ONLY)
boot.img
Credits:
Koush- for clockwork mod
DooMLoRD- for his recovery ramdisk
@dinitro - for actually taking the time to compile the cwm with stock kernel, this guy deserves all the credit
Since this is pure stock kernel with a custom recovery i assume i dont have to post the kernel sources, If there is a issue mods are welcomed to notify me via PM.
Rooting Instructions:
Download the latest zip from Here and move to device
Reboot to recovery
Flash
Reboot
​
XDA:DevDB Information
CWM Recovery and Root (Stock Kernel Sony 4.2.2), a Kernel for the Sony Xperia Tablet Z
Contributors
bluefa1con
Kernel Special Features:
Version Information
Status: Testing
Created 2013-09-05
Last Updated 2013-09-06
Woot! Thanks. Gonna try it out tonight.
drazyw said:
Woot! Thanks. Gonna try it out tonight.
Click to expand...
Click to collapse
releasing the kernel first so people can be ready when i release my dual boot for tablet z
more details on my pac thread
Damn, I spent ages getting the root on 4.2.2 sorted out this morning ! Thanks !
Thanx for your work !
I assume it will never work on with locked bootloader ?
ibis69 said:
Thanx for your work !
I assume it will never work on with locked bootloader ?
Click to expand...
Click to collapse
locked bootloader= cant flash a kernel other than stock sony kernel
there is a way to have recovery on locked bootloader but it still needs root
i am too busy these days, if only i had time i would look at xperia z root exploit and implement it on tab z
meanwhile here is what u can do
backup your TA parition
unlock bootloader and root via this method
flash back to stock sony kernel
restore your TA and your device would behave like it was never unlocked
Unlocked my bootloader a few moments ago .. Trying your kernel now.
...
It can access to the internal storage but i don't have any files to flash.
And error appears when trying to mount or install zip from the external storage.
Thank you So much we appreciate your hard work. =)
Half Alive said:
Unlocked my bootloader a few moments ago .. Trying your kernel now.
...
It can access to the internal storage but i don't have any files to flash.
And error appears when trying to mount or install zip from the external storage.
Thank you So much we appreciate your hard work. =)
Click to expand...
Click to collapse
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGP311 using Tapatalk 4
bluefa1con said:
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
Sent from my SGP311 using Tapatalk 4
Click to expand...
Click to collapse
Just tried now flashing from the internal storage ,.. And it's Working.
Hope you can fix the external_sd problem ,.
And that Big surprise is coming soon like today ?
Can't wait to test it. :good::good:
bluefa1con said:
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
Sent from my SGP311 using Tapatalk 4
Click to expand...
Click to collapse
with that great surprise you say,since sony roms can only be primary,what if we have already installed an aosp rom?will we be able to move it to secondary rom partition or we will have to reinstall it from scratch?finally the second rom will be stored at /cache or at /sdcard?sorry if i reveal some of your surprise with these questions
pangiotis24 said:
with that great surprise you say,since sony roms can only be primary,what if we have already installed an aosp rom?will we be able to move it to secondary rom partition or we will have to reinstall it from scratch?finally the second rom will be stored at /cache or at /sdcard?sorry if i reveal some of your surprise with these questions
Click to expand...
Click to collapse
currently the project is in its infancy, we got basic dual boot done and we got more plans
copy your data partition to some other place (sdcard etc) and copy it back when u install pac on second rom
we got big plans for this and we are talking to recovery devs to customize the recovery for RomSwitch dual boot implementation
Dual Boot released HERE
Is this kernel from 311 or 312 version of Tablet Z?
Rootk1t said:
Is this kernel from 311 or 312 version of Tablet Z?
Click to expand...
Click to collapse
Should work on both, I have tested on 311 because that's the device I have but both are identical besides more storage capacity
Sent from my SGP311 using Tapatalk 4
bluefa1con said:
releasing the kernel first so people can be ready when i release my dual boot for tablet z
more details on my pac thread
Click to expand...
Click to collapse
Well it seems to work perfect. Followed all the steps and it worked flawlessly. After a few days of struggling to maintain root when updating to 4.2.2 with Sony's OTA, this took 5 min. Thanks for all the work. Can't wait to try out some dual boot stuff now.
I tried this procedure on my SGP321 LTE Tablet. After flashing the boot.img, my tablet refuses to boot up. There is just a Red LED. No Sony logo or nothing. I somehow managed to get it into Fastboot mode (Blue LED) but apart from that I cannot do anything. On trying Vol - and plugging the USB at the same time, the FlashTool recognizes the Flash Mode (but there is no Green LED) I even tried flashing the FTF through the FlashTool but it gets stuck on flashing data. I really am struggling since 5 hours. Is my Tablet dead? I really cannot figure out what to do next Please help me!!
aashayjardosh said:
I tried this procedure on my SGP321 LTE Tablet. After flashing the boot.img, my tablet refuses to boot up. There is just a Red LED. No Sony logo or nothing. I somehow managed to get it into Fastboot mode (Blue LED) but apart from that I cannot do anything. On trying Vol - and plugging the USB at the same time, the FlashTool recognizes the Flash Mode (but there is no Green LED) I even tried flashing the FTF through the FlashTool but it gets stuck on flashing data. I really am struggling since 5 hours. Is my Tablet dead? I really cannot figure out what to do next Please help me!!
Click to expand...
Click to collapse
Do not worry, you just flashed the wrong kernel for your device, happens to everyone. Just simply try to flash your FTF, or you could install Cyanogenmod.
mamenyaka said:
Do not worry, you just flashed the wrong kernel for your device, happens to everyone. Just simply try to flash your FTF, or you could install Cyanogenmod.
Click to expand...
Click to collapse
I tried flashing the 4.2.2 FTF but it gets stuck on loading data. I tried flashing the boot.img from CM10.2 but that too gets stuck on 'Flashing Selected Kernel'..
aashayjardosh said:
I tried flashing the 4.2.2 FTF but it gets stuck on loading data. I tried flashing the boot.img from CM10.2 but that too gets stuck on 'Flashing Selected Kernel'..
Click to expand...
Click to collapse
You need to flash the boot.img with fastboot.
mamenyaka said:
You need to flash the boot.img with fastboot.
Click to expand...
Click to collapse
Forgive my noobness...but where do I get the original 4.2.2 boot.img from? I extracted the 4.2.2 FTF but there is no boot.img in it. On the other hand I extracted the boot.img of CM10.2 but that gets stuck on Flashing selected kernel.

[OFFICIAL] Marshmallow (B317) + ROOT instructions

Huawei released, probably final, update for P8 with android 6 Marshmallow
Download here
You can upgrade directly from B200, but i highly recommend to you factory reset after upgrade, otherwise phone can be slow, laggy and battery can drain fast.
ROOT link was deleted due pirated content, if i will see legal way i will update
Updated from b200 and everythings seems fine. Had an error during install but phone seems ok with B317. Battery seems to go a bit fast but need tot test for a couple of days
[email protected] said:
Updated from b200 and everythings seems fine. Had an error during install but phone seems ok with B317. Battery seems to go a bit fast but need tot test for a couple of days
Click to expand...
Click to collapse
i suggest to full wipe data and cache after update, there could be some probles if you wont and battery drain in B317 should be noticable better than b200
00471 said:
i suggest to full wipe data and cache after update, there could be some probles if you wont and battery drain in B317 should be noticable better than b200
Click to expand...
Click to collapse
It's done automaticly during install, it's not a real upgrade the wipe is default
Hi, last weekend i tried the Beta and wasnt satisfied and rolled back to B200.
System was always on and whatsapp en mail notifications didnt pushed true, eventough i had all the settings right.
I want to try this version but does anyone knows if there is a rollback to B200 if i dont like it?
djg269 said:
Hi, last weekend i tried the Beta and wasnt satisfied and rolled back to B200.
System was always on and whatsapp en mail notifications didnt pushed true, eventough i had all the settings right.
I want to try this version but does anyone knows if there is a rollback to B200 if i dont like it?
Click to expand...
Click to collapse
of course, there is way to rollback, im testing it, i will let to know for all later
[email protected] said:
Updated from b200 and everythings seems fine. Had an error during install but phone seems ok with B317. Battery seems to go a bit fast but need tot test for a couple of days
Click to expand...
Click to collapse
Yeah battery goes faster at yellow zone mobile signal, but when red or green it seems not bad.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
link dosent work !!
the file you are trying to download is no longer available
im sorry, i forgot to edit OP, link was deleted because of pirated PRO copy of SuperSU and i can not reupload it
It worked only partially.
I was on B200, rooted and with TWRP installed. In order to use this update I've flashed back stock recovery.
Update went well half way and then crashed with some errors. Phone rebooted and surprise, was updated to Marshmallow 6.0 B317.
Biggest problem is, I've lost stock recovery and can't flash TWRP or stock recovery anymore. Fastboot says it is flashed:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2871.img
target reported max download size of 471859200 bytes
sending 'recovery' (25880 KB)...
OKAY [ 0.550s]
writing 'recovery'...
OKAY [ 0.339s]
but phone does not go to recovery just bootloops few times and then booting the system normally.
I'm also unable to relock bootloader. No factory reset or wiping cache works anymore.
I'm in a mess now.
i have the same problem. nothing seems to work. no stock recovery and no twrp.
Download the file used to root b313. It contains twrp_new.img that will work. No other recoveries will work. If you want to root, download the latest superSU 2.67. That will automatically patch your boot image and root. To install busybox, download BuzyBox Free and install using that. Remember to install into system/xbin for compatibility with apps like Viper.
The easiest way to boot into recovery or bootloader is via adb.
tomtro74 said:
I was on B200, rooted and with TWRP installed. In order to use this update I've flashed back stock recovery.
Update went well half way and then crashed with some errors. Phone rebooted and surprise, was updated to Marshmallow 6.0 B317.
Biggest problem is, I've lost stock recovery and can't flash TWRP or stock recovery anymore. Fastboot says it is flashed:
Click to expand...
Click to collapse
You have to re-flash b317 using three buttons (power, vol+, vol-)
mai55 said:
You have to re-flash b317 using three buttons (power, vol+, vol-)
Click to expand...
Click to collapse
No luck there as it forces the update through recovery, same like update with the service menu from the stock phone app.
Problem is, there is NO stock or custom recovery in the device and I don't know the way to flash it other than through fastboot and this method does not work.
I need to get the stock recovery working first, before I can flash anything else.
rodlane said:
Download the file used to root b313. It contains twrp_new.img that will work. No other recoveries will work. If you want to root, download the latest superSU 2.67. That will automatically patch your boot image and root. To install busybox, download BuzyBox Free and install using that. Remember to install into system/xbin for compatibility with apps like Viper.
The easiest way to boot into recovery or bootloader is via adb.
Click to expand...
Click to collapse
Thanks but I can't find a link to this file
i will upload it for you in about 5 hours, still got that root package
i can't find a link this recovery
irgendeinname said:
i can't find a link this recovery
Click to expand...
Click to collapse
im gonna upload twrp recovery for marshmallow today, dont worry, be patient
http://forum.xda-developers.com/showthread.php?p=65499548
thank you

[ROM] Oxygen OS 3.2.5 untouched system.img + boot.img (twrp + fastboot)

If someone wants to make mirrors or a flashable zip, feel free to contact me and I will update thread
I've got my new OP3 today and what I've noticed that it runs with Oxygen OS 3.2.5. So I have looked around and saw that nobody backed up their 3.2.5 und uploaded it so I decided to do it.
Here is the download link: https://mega.nz/#!PJhzRDyL!wX12zmq9ptiu8gNbtfQfypB2Q6wGdu3IfNFFwi9acQk
The only requirement is an unlocked bootloader as fastboot doesn't allow to flash on locked devices
How to install:
via twrp:
- boot into twrp recovery
- press "install"
- press "install image" on the bottom right
- select the image and confirm on which partition it should flash
(not recommended) via fastboot:
- boot into fastboot
- use these commands to flash it:
ignore the little warning message and pe patient because it can take a while till you get a response from cmd because fastboot splits the image into 6 parts
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Note: if your phone isn't booting, flash supersu and it should boot.
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot flashing is not working.
Can you comment on the LTE reception and performance? It was the only issue i had with 3.2.4
Anyone tried looks tempting
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
TWRP is working, fastboot not.
Im on 3.2.5 now so yes its working, but only with TWRP
*Extracted fine with newest winrar*
Error on my end, sorry, thank you!
Chronzy said:
@hellcat50 zip is corrupt, "unexpected end of archive" when I tried to extract the img's. Downloaded it twice. Don't recommend wiping and trying to install at this time.
Would love to have this though, would you mind repacking?
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
you were able to extract the imgs? I downloaded it twice and got corrupt zip both times.
Click to expand...
Click to collapse
It did extract without any issues on my end.
I downloaded and extracted the file on my PC with the latest winrar.
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
So, I will not lose my data, right?
No, but you should still do a backup in TWRP.
AcmE85 said:
No, but you should still do a backup in TWRP.
Click to expand...
Click to collapse
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Andrea224 said:
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Click to expand...
Click to collapse
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
AcmE85 said:
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
Click to expand...
Click to collapse
Mmh...ok, thanks anyway.
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Reconfigured said:
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Click to expand...
Click to collapse
SuperSU is not needed, why should it be? With this you overwrite the whole System partition, thus removing all mods including SuperSU and Xposed.
waiting for someone to confirm the LTE issue resolution.. if it's resolved, I'll flash this ASAP..
AcmE85 said:
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
Click to expand...
Click to collapse
Pick your brain for a moment if you don't mind...
Still having issues with both methods... in TWRP, at the install image screen i'm only getting boot and recovery partition options, supposed to have system too right?
Fastboot it hangs for a moment at an error of something about invalid sparsing but continues to flash, apparently successfully, but when i reboot system it just boots back to recovery.
Chronzy said:
Pick your brain for a moment if you don't mind...
Click to expand...
Click to collapse
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
Can we directly flash it over 3.2.4 in twrp ?
Any differences with the previous version guys?3.2.4....Tnx!!
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
I was on an older recovery, should have known... that did it, Thanks! :good:

Lenovo Z5s Update to ZUI 11.5 (Android 10)

Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot

Magisk v22.0 destroy my phone (bonker)

Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]

Categories

Resources