Database Develop

Questions about unlocked bootloader and CWM

Hey all,
I have a little complicated story here:
Yesterday I got my Xperia Z, a branded T-Mobile one which was unlockable. First I rooted with the exploit and after that I made a backup of my TA partition for later uses. I had to install TWRP to set the bootloader to unlockable with this file. So by then the bootloader was unlockable again like in the very beginning.
Later I watched this video and did all the steps until the bootloader was unlocked. Then I went back to the root thread with the expliot and rooted it the same way like I did before.
My goal is to successfully flash CyanogenMod 10.1 on my Xperia Z, so I watched this video from the same guy. When he said that I needed CWM I went back to the bootloader unlocking video and did everything after unlocking the bootloader, which was flashing root, insecure fw and the kernel. I accidently used a newer one which didn't work like you can see in this picture:
{
"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"
}
The Xperia Z still works like before and I have CWM 6.0.2.8 installed, but I'm unsure if I could brick it because I accidently used another kernel beforehand. Also, I can't reboot to CWM with an adb command, but it works by pressing vol up when booting. Does that make a difference?
If so, what can I do to get CyanogenMod 10.1 on my device?
Actually I'd be really happy just to know if my bootloader is really unlocked, since I have no real proof.
CWM is also asking if I want to "Disable recovery flash" which would prevent my rom from flashing the stock recovery on boot.
Okay, that's everything for now I think. Would be really nice if someone could help me with this.
Thanks in advance!
FingerMove

FingerMove said:
Hey all,
I have a little complicated story here:
Yesterday I got my Xperia Z, a branded T-Mobile one which was unlockable. First I rooted with the exploit and after that I made a backup of my TA partition for later uses. I had to install TWRP to set the bootloader to unlockable with this file. So by then the bootloader was unlockable again like in the very beginning.
Later I watched this video and did all the steps until the bootloader was unlocked. Then I went back to the root thread with the expliot and rooted it the same way like I did before.
My goal is to successfully flash CyanogenMod 10.1 on my Xperia Z, so I watched this video from the same guy. When he said that I needed CWM I went back to the bootloader unlocking video and did everything after unlocking the bootloader, which was flashing root, insecure fw and the kernel. I accidently used a newer one which didn't work like you can see in this picture:
The Xperia Z still works like before and I have CWM 6.0.2.8 installed, but I'm unsure if I could brick it because I accidently used another kernel beforehand. Also, I can't reboot to CWM with an adb command, but it works by pressing vol up when booting. Does that make a difference?
If so, what can I do to get CyanogenMod 10.1 on my device?
Actually I'd be really happy just to know if my bootloader is really unlocked, since I have no real proof.
CWM is also asking if I want to "Disable recovery flash" which would prevent my rom from flashing the stock recovery on boot.
Okay, that's everything for now I think. Would be really nice if someone could help me with this.
Thanks in advance!
FingerMove
Click to expand...
Click to collapse
Yes your bootloader is unlocked becuase you successfully flashed unsigned kernel, now you need to download CM10.1 and inside it will give you a kernel to flash and rom to install

Maddhouse said:
Yes your bootloader is unlocked becuase you successfully flashed unsigned kernel, now you need to download CM10.1 and inside it will give you a kernel to flash and rom to install
Click to expand...
Click to collapse
Do I just have to flash via CWM or do I have to extract the boot.img out of the .zip, flash it via fastboot and then with CWM again?
(That's how it's presented in the video about flashing custom roms).

QUOTE=FingerMove;41047686]Do I just have to flash via CWM or do I have to extract the boot.img out of the .zip, flash it via fastboot and then with CWM again?
(That's how it's presented in the video about flashing custom roms).[/QUOTE]
you will have to unzip the folder and it should give you two files boot.img and a zip, zip is rom so copy that over to you phone, you can only flash kernel via adb or flashtool so what you need to do is open up cwm and install after install complete then flash CM kernel.
I am still on locked for the XZ but this is what i had to do on X Arc which i am 99.9% sure it is the same way

Maddhouse said:
you will have to unzip the folder and it should give you two files boot.img and a zip, zip is rom so copy that over to you phone, you can only flash kernel via adb or flashtool so what you need to do is open up cwm and install after install complete then flash CM kernel.
I am still on locked for the XZ but this is what i had to do on X Arc which i am 99.9% sure it is the same way
Click to expand...
Click to collapse
This is what's inside a CM10.1 nightly:
In the video about custom roms the order is like this:
1. Extract boot.img out of the .zip
2. Put cm10.1.zip and gapps.zip on sdcard
3. Flash boot.img via adb
4. Restart into cwm
5. Factory reset/wipe cache
6. Install cm10.1.zip and gapps.zip
7. Reboot and it should start CyanogenMod 10.1
Should that also work?
Sorry for so many questions and step-by-step asking, I just don't want to brick it or get bootloops, since that would completely throw me off.
Thanks in advance!
FingerMove

FingerMove said:
This is what's inside a CM10.1 nightly:
In the video about custom roms the order is like this:
1. Extract boot.img out of the .zip
2. Put cm10.1.zip and gapps.zip on sdcard
3. Flash boot.img via adb
4. Restart into cwm
5. Factory reset/wipe cache
6. Install cm10.1.zip and gapps.zip
7. Reboot and it should start CyanogenMod 10.1
Should that also work?
Sorry for so many questions and step-by-step asking, I just don't want to brick it or get bootloops, since that would completely throw me off.
Thanks in advance!
FingerMove
Click to expand...
Click to collapse
1 Download the prebuilt release of CyanogenMod you wish to install. (Or if you've built CM yourself, look in the $OUT directory for the .zip.)
Optional: Download any supplemental 3rd-party applications packages for the device you wish to use. (You have to install a 3rd-party app to get the Google apps, like Gmail, Play Store, and Youtube.)
2 Place the CyanogenMod rom .zip file on the root of the SD card.
Optional: Place any supplemental packages' .zip file on the root of the SD card.
3 Extract the boot.img from the zip, you will need this file for fastboot.
4 Put the phone into fastboot mode:
5 Open a terminal on the PC and enter the following:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
While the device reboots, press the Volume rockers a few times to load recovery.
6 Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the Xperia Z.
7 Select the option to wipe data/factory reset.
8 Select Install zip from sdcard.
9 Select Choose zip from sdcard.
10 Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
11 Once the installation has finished, return back to the main menu, and select the reboot system now option. The Xperia Z should now boot into CyanogenMod.
http://wiki.cyanogenmod.org/w/Install_CM_for_yuga

Thanks for all your help, I just did it
Working really good here, had no bootloops or other problems

[Q] How to upgrade bootloader to 10.26.1.18 ?

Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"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"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !

Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]

berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?

Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:

usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?

Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go

berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!

Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.

berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!

Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.

Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.

Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app

How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?

US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card

Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse

I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87

Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.

MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/

[RECOVERY] TWRP 3.1.1-0 for Z5C [suzuran]

{
"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?

help rooting device with oreo 8.1

Hello,
I have this phone (infinix note 4 x572) running oreo 8.1 , build number :X572-H5312CE-O-180531V117
I wish to root it but after a while of searching i'm overly confused and frustrated..
can you please guide me through rooting it?
thanks alot

btw, does local update help in any way ?
{
"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"
}

All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.

Didgeridoohan said:
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Click to expand...
Click to collapse
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?

and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?

yazansayed said:
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
Click to expand...
Click to collapse
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
yazansayed said:
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
Click to expand...
Click to collapse
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...

Didgeridoohan said:
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
thanks alot for the quick responses, i will try it and reply as fast as possible

okay, i downloaded the twrp recovery image for Note 4, flashed it using Fastboot method successfully,
the problem is when i try to boot into the twrp recovery mode, i tried holding the power menu+ vol.down buttons, it sends me into a black screen with "factory mode" upwards in yellow, no button is working.
i then tried
Code:
adb reboot recovery
the phone reboots and says "No command" under a red triangle.
i then tried to flash the twrp img using sp flash tools, and flashed it successfully but the same errors occur, i can't seem to be able to boot into recovery mode.

i looked up for a solution for the "no command" problem, here's one:
I faced the same problem with nexus 6p. It works when you root immediately after flashing the TWRP. Keep the superSU file in the storage. Get into bootloader. Flash TWRP via fastboot. Without restarting anything, just press volume up/down buttons while in the bootloader to select recovery. TWRP will open. Flash the SuperSU.zip. Then restart the system. Next time, if you open recovery, you won't get the "no command". If you don't flash SuperSU and you try to open recovery later, you will get the "No command".
Click to expand...
Click to collapse
what i understood is that i shouldn't reboot my device using "fastboot reboot" , he says i should get into recovery mode directly without restarting, idk how to do that since there are no option for it on the screen, i just have
Code:
=> FASTBOOT mode...
on the screen !

Didgeridoohan said:
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
unfortunately i never used the sp flash tool before, so i tried flashing a stock rom but the device is now dead with "dram failed" error, i'll try fixing this first

It's tricky trying to help with a device you don't have...
Did you manage to boot to recovery? Usually you use the volume buttons to select the options and then the power button to confirm. You could also just use the fastboot boot option command I wrote earlier. It'll boot straight into TWRP.
There are a few threads for your device around, so if you need help specific to your device, that's the place to go...

everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot

the twrp from the post you provided is for an older firmware, this is why i couldn't get into recovery after i flashed the provided twrp img,, there is no available twrp for the oreo version of the firmware, but i requested one from twrp builder project,, thanks alot, i've learnt alot in the last 24 hours

yazansayed said:
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
Click to expand...
Click to collapse
could you upload the boot.img pls (the stock and the patched if possible )

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