[RECOVERY][3.1.0-0] TWRP Recovery for BLU Pure XL - Blu Pure XL

{
"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"
}
TeamWin's TWRP Touch Recovery for BLU Pure XL (and clones)​https://twrp.me/​
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.​
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom ROM like OmniROM.​
Source to build TWRP you can find here.​
SCREENSHOTS: HERE
Bugs:
If you find any bug I haven't noticed, please go here and send me bug report. It would help me solving most problems in further builds.
Flashing instructions:
Use Flashify, TWRP Manager or follow this thread.
WARNING!
Code:
This is custom recovery image.
Wait for progress but don't ask for ETA - I have my own life too.
You are flashing it at your own risk - don't do it if you don't know what it's used for!
I'm not responsible for earthquake, thermonuclear war or any damage on your phone. If you point finger at me for messing up your phone I'll laugh at you.
Changelog:
Code:
[B]3.1.0[/B] 2017-03-18[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html"][link][/URL]
[*]Fixed partitioning problems.
[*]Added support for more partitions (/logo, /nvram etc.)
[*]Fixed restoring backups.
[*]Fixed CPU temp indicator.[/LIST]
[B]3.0.2-0 Official [/B] 2016-04-05
[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html"][link][/URL]
[/LIST]
[B]3.0.1-0 Official[/B] 2016-04-01
[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2016/04/01/twrp-3.0.1-0-released.html"][link][/URL]
[/LIST]
[B]3.0.0-1 Official[/B] 2016-02-26 (on AndroidFileHost)
[LIST]
[*][B]Recovery is now STABLE in usage![/B]
[*]Restoring backups is now [B]FIXED![/B]
[*]Mounting to PC should be now [B]FIXED![/B]
[*]Some improvments to code
[/LIST]
[B]3.0.0-0 Official[/B] 2016-02-20
[LIST]
[*]Added official support for this device
[*]Nothing changed since last build
[/LIST]
[B]3.0.0-beta3[/B] 2016-02-07
[LIST]
[*][STRIKE]Fixed backup restoring issue[/STRIKE] Seems not to be fixed, will be working on it
[*]Some iprovements
[/LIST]
[B]3.0.0-beta2[/B] 2016-02-07
[LIST]
[*]Fixed partitions problem - TWRP sees & mounts them now
[*]Fixed battery percentage indicator
[/LIST]
[B]3.0.0-beta1[/B] 2016-02-06
[LIST]
[*]Initial release
[*]TWRP can't mount partitions, doesn't read storage
[*]Any other bugs are related to problem mentioned above
[*]TWRP boots and reboots correctly
[/LIST]
Donwload: here (SourceForge)
Device tree: device_x2xtreme
Credits: Ethan Yonker aka Dees_Troy & whole TWRP Dev Team
XDA:DevDB Information
TWRP 3.1.0, Tool/Utility for the Blu Pure XL
Contributors
bemolx
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: v3.1.0-0
Stable Release Date: 2017-03-18
Created 2016-02-06
Last Updated 2017-04-03

Bugs & changelogs
What does work:
Everything.
What doesn't work:
Look at changelog. Thank you

No disrespect, bit did you compile this? I ask cause I am trying to compile the new TWRP for my device wich is a LG G Stylo and my touch input does not work. So I was wondering if you had this issue and if so how did you fix it?

T-Macgnolia said:
No disrespect, bit did you compile this? I ask cause I am trying to compile the new TWRP for my device wich is a LG G Stylo and my touch input does not work. So I was wondering if you had this issue and if so how did you fix it?
Click to expand...
Click to collapse
Yes, Ive compiled it without any errors at first time. I don't know how to help you at this moment. Ask TeamWin Devs
Cheers
Wysłane z mojego X2_Soul_Xtreme

bemolx said:
Yes, Ive compiled it without any errors at first time. I don't know how to help you at this moment. Ask TeamWin Devs
Cheers
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
bemolx said:
What doesn't work: CPU temperature indicator, mounting to PC
3.0.0-beta2
Fixed partitions problem - TWRP see & mount them now
Fixed battery percentage indicator
3.0.0-beta1
Initial release
TWRP can't mount partitions, doesn't read storage
Any other bugs are related to problem mentioned above
TWRP boots and reboot correctly
Click to expand...
Click to collapse
Olá, estou com problema em montar "cache" não consigo restaurar a rom stock... Backup feito com o novo twrp 3.0 beta 2... Alguma dicas.....

eualex said:
Olá, estou com problema em montar "cache" não consigo restaurar a rom stock... Backup feito com o novo twrp 3.0 beta 2... Alguma dicas.....
Click to expand...
Click to collapse
Can you provide me logcat or at least error shown while restoring your backup? It would help much.
PS. Next time write in English because it's better for me and other users in this forum to understand what's your problem.
Update: Yeah... I've bricked my device too. Now I know the problem and I am working on it. Wait for beta3
Wysłane z mojego X2_Soul_Xtreme

bemolx said:
Can you provide me logcat or at least error shown while restoring your backup? It would help much.
PS. Next time write in English because it's better for me and other users in this forum to understand what's your problem.
Update: Yeah... I've bricked my device too. Now I know the problem and I am working on it. Wait for beta3
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
The error was with TWRP 3.0 beta 3. Could not mount the cache for that reason did not finish the restoration, I reinstalled TWRP 2.8 per adb and got a mont in the cache. Now all ok with TWRP 2.8. Thank you for your attention, I am waiting for the first custom for blu pure xl. Summary error was to assemble cache error does not happen with TWRP 2.8.

eualex said:
The error was with TWRP 3.0 beta 1. Could not mount the cache for that reason did not finish the restoration, I reinstalled TWRP 2.8 per adb and got a mont in the cache. Now all ok with TWRP 2.8. Thank you for your attention, I am waiting for the first custom for blu pure xl.
Click to expand...
Click to collapse
Okay, I see In beta3 everything has beed updated - in beta1 you couldn't mount any partition because of bad recovery.fstab which is already fixed
Cheers
Sent from Nexus 5

bemolx said:
Okay, I see In beta3 everything has beed updated - in beta1 you couldn't mount any partition because of bad recovery.fstab which is already fixed
Cheers
Sent from Nexus 5
Click to expand...
Click to collapse
Edit, was using the TWRP 3.0 beta 3 ...... So I could settle with TWRP 2.8. Thank you

beta restore fail
Same issue at me. When I tried to restore the backup in twrp 3.0.0 beta 3 it stopped. And briked my phone.
I was needed to install twrp 2.8.6.0 back and restore the backup to boot again the phone.

AlexDC2013 said:
Same issue at me. When I tried to restore the backup in twrp 3.0.0 beta 3 it stopped. And briked my phone.
I was needed to install twrp 2.8.6.0 back and restore the backup to boot again the phone.
Click to expand...
Click to collapse
eualex said:
Edit, was using the TWRP 3.0 beta 3 ...... So I could settle with TWRP 2.8. Thank you
Click to expand...
Click to collapse
Restoring backup problems have been solved in v3.0.0-1. Please wait for upload at the official download page. Thank you
Wysłane z mojego X2_Soul_Xtreme

Help!! My BLU Pure XL will not go into Recovery
I try to go into recovery mode and the phone just reboots. I hold the
power and Vol up key like I did when I originally rooted it but now it will not go into recovery any longer. I'm trying to revert back to stock and upgrade to the latest release. Can someone please assist?
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
I can not get my phone into ecovery mode. I did the buttons as I have in the past but the phone just reboots. It's like my recovery mode was deleted and the phone just resets. Help!!!!

KingKe said:
I try to go into recovery mode and the phone just reboots. I hold the
power and Vol up key like I did when I originally rooted it but now it will not go into recovery any longer. I'm trying to revert back to stock and upgrade to the latest release. Can someone please assist?
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
I can not get my phone into ecovery mode. I did the buttons as I have in the past but the phone just reboots. It's like my recovery mode was deleted and the phone just resets. Help!!!!
Click to expand...
Click to collapse
Try to reflash the recovery img using fastboot method.
Wysłane z mojego X2_Soul_Xtreme

bemolx said:
Try to reflash the recovery img using fastboot method.
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
I would by I do not have root access.

KingKe said:
I would by I do not have root access.
Click to expand...
Click to collapse
You don't have to. Follow this thread.
Wysłane z mojego X2_Soul_Xtreme

bemolx said:
You don't have to. Follow this thread.
Wysłane z mojego X2_Soul_Xtreme
Click to expand...
Click to collapse
I started with this link.
Let me restate my issue and shed light on my environment.
Power Button + Vol up does not go to Recovery mode - My phone just goes to a black screen and reboots. So, if any procedure requires that I can not execute right now. I need recovery mode back.
I am running Windows 10 Professional 64Bit variant. My BlU Pure XL connects via MPT so I can not assign a drive letter to it so that I can navigate to it via CMD prompt.
Fastboot command comes and stating 'waiting for device' because I can not get my device into recovery mode. So, can someone walk me through this issue and get my recovery mode reinstalled/repaired (Also I am not rooted)?

KingKe said:
I started with this link.
Let me restate my issue and shed light on my environment.
Power Button + Vol up does not go to Recovery mode - My phone just goes to a black screen and reboots. So, if any procedure requires that I can not execute right now. I need recovery mode back.
I am running Windows 10 Professional 64Bit variant. My BlU Pure XL connects via MPT so I can not assign a drive letter to it so that I can navigate to it via CMD prompt.
Fastboot command comes and stating 'waiting for device' because I can not get my device into recovery mode. So, can someone walk me through this issue and get my recovery mode reinstalled/repaired (Also I am not rooted)?
Click to expand...
Click to collapse
1. If you have adb working (for some reason in my case, my Pure XL doesn't want to be detected by it), then launch cmd in the same directory as adb and fastboot (SHIFT+Right Click) and use the command adb reboot bootloader to put it into the bootloader (don't worry about the tiny text on the bootloader screen saying stuff about security).
2. Then, after you put the TWRP recovery.img in the same folder, use the command fastboot flash recovery recovery.img to flash TWRP back onto your device (not sure how you managed to corrupt/remove it in the first place).
3. If you don't have adb working (like me), download and use WinDroid Toolkit (which can be found on another post under "Pure XL Android Development"), connect your phone to your computer, select Pure XL under BLU in WinDroid Toolkit, go to the Commands tab, and click Bootloader under the Reboot section, then follow step number two listed above.

Short Circuit said:
1. If you have adb working (for some reason in my case, my Pure XL doesn't want to be detected by it), then launch cmd in the same directory as adb and fastboot (SHIFT+Right Click) and use the command adb reboot bootloader to put it into the bootloader (don't worry about the tiny text on the bootloader screen saying stuff about security).
2. Then, after you put the TWRP recovery.img in the same folder, use the command fastboot flash recovery recovery.img to flash TWRP back onto your device (not sure how you managed to corrupt/remove it in the first place).
3. If you don't have adb working (like me), download and use WinDroid Toolkit (which can be found on another post under "Pure XL Android Development"), connect your phone to your computer, select Pure XL under BLU in WinDroid Toolkit, go to the Commands tab, and click Bootloader under the Reboot section, then follow step number two listed above.
Click to expand...
Click to collapse
Fro no ADB, make sure you have debugging enabled in the dev options under settings (hidden menu you have to tap either kernel version or software version multiple times to unlock; i forget which, but its all over the forums and google...
Also if you have root (its unclear because you are saying you cannot get into recovery, and I honestly didnt read but the last post...) you can load terminal from play store and type "su"<enter> then "reboot recovery" <enter> and it will reboot into recovery
but Id look into the issue of the buttons not working, do they work fine else ware?

Short Circuit said:
1. If you have adb working (for some reason in my case, my Pure XL doesn't want to be detected by it), then launch cmd in the same directory as adb and fastboot (SHIFT+Right Click) and use the command adb reboot bootloader to put it into the bootloader (don't worry about the tiny text on the bootloader screen saying stuff about security).
2. Then, after you put the TWRP recovery.img in the same folder, use the command fastboot flash recovery recovery.img to flash TWRP back onto your device (not sure how you managed to corrupt/remove it in the first place).
3. If you don't have adb working (like me), download and use WinDroid Toolkit (which can be found on another post under "Pure XL Android Development"), connect your phone to your computer, select Pure XL under BLU in WinDroid Toolkit, go to the Commands tab, and click Bootloader under the Reboot section, then follow step number two listed above.
Click to expand...
Click to collapse
Thanks I am up and running and all is well. I can't get the update because I originally rooted the phone before all hell broke loose. But thanks for the help.

I get an error that it cannot mount '/cache' (invalid argument) after i do a factory reset

Related

I'm really stuck getting recovery installed - please help?

Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch - don't get the 'amber LED' which various guides tell me to press Vol Down at.
I'm using
Code:
fastboot boot recovery.img
to boot the phone into recovery and
Code:
fastboot flash recovery recovery.img
to flash it, which hasn't worked at all. All of theTWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
[snip]
TimTams said:
Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch. I'm using
Code:
fastboot flash boot boot.img
to write the boot images and
Code:
fastboot boot recovery.img
to boot the phone into recovery. All of the other TWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
Click to expand...
Click to collapse
I don't think your bootloader is unlocked because:
1: your device won't boot after flashing an image.
2: your rooting status says: bootloader unlock allowed.
(if unlocked, it says rooting status: bootloader unlocked)
Yes means it can be unlocked.
Unless you unlocked already and use drm fix because then it still shows yes but Im pretty sure your bootloader isn't unlocked.
BTW this thread belongs in Q&A section.
You can request a movement by hitting the small "!" triangle button underneath your post when viewing this page in a browser.
Sent from my E6653 using XDA-Developers mobile app
Thanks heaps - that sounds like it might be the issue, I'll have a play and post back here. It would explain why I've had so much trouble with what seems like a simple task
langeveld024 said:
I don't think your bootloader is unlocked
...
Click to expand...
Click to collapse
EDIT:
It looks like this was done correctly.
{
"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"
}
I'm not sure I want to go and have another crack at flashing a recovery... I couldn't seem to get any of them to work.
I've just followed this guide to installing recovery and it hasn't worked... I still just get stuck at the sony logo. Any ideas why? How do I know the recovery image linked is correct for my phone?
http://www.digitbin.com/unlock-bootloader-flash-twrp-root-sony-xperia-z5/
OK, I got recovery installed! Thanks to this guy: http://forum.xda-developers.com/xperia-z5/help/boot-flashmode-fastboot-t3457818
mentions what no other guide mentions...
I need to have a custom kernel before I can flash recovery (first mention of this I've seen)
The kernel I flash needs to match the firmware I have installed
With that, I had instant success.
EDIT:
And now I have managed to get a custom ROM installed at last My procedure was, for anyone that be stuck in a similar way:
If your phone already won't boot:
Download Flashtool and install it. I have mirrored it here as all the sources I found were very slow: http://noobs.wtf/uploads/flashtool-0.9.22.3-windows.exe
Go to the 'drivers' folder inside your Flashtool install directory (default C:\Flashtool\drivers) and follow the instructions to install the "flashmode" driver
Select XperiFirm within Flashtool and download the correct firmware for your phone - mine was "Xperia Z5 > Sumire > E6653 > Australia > Telstra AU > 32.2.A.0.253 / R5C"
Turn off your phone and boot it in flashmode - Insert USB while holding vol down until the LED is green
Once Flashtool has finished downloading your firmware, go back to the main screen and click the 'lightning' button to flash your phone with the new firmware that should show up in the list - leave all the options unticked. Wait for it to say 'complete - un plug your phone'
Your phone should now boot successfully
To install a custom ROM:
I was not able to access my SD card in any version of TWRP - so copy your ROM to the internal storage of your phone. I used v1.5.0 of THIS ROM successfully.
Copy v36 (or newer) of THIS KERNEL .zip file to your internal storage as well. (v32 and higher are in the google docs link) NOTE this must match the firmware version - v36 was the one I used because, as above, I re-flashed my phone with 32.2.A.0.253 from Flashtool. The appropriate versions are listed on that link
[*]Also download TWP-3.0.2-2-E6653.img (or newer equivalent) from that same link.
[*]Follow the instructions HERE to unlock your bootloader (and make sure your fastboot drivers are installed correctly)
[*]Reboot your phone and re-enter fastboot mode (vol-up while plugging in USB) you can issue the command 'fastboot oem unlock' and it will return 'already rooted' if it has been done correctly
[*]Now with your phone in fastboot mode, issue the commands "fastboot flash recovery TWP-3.0.2-2-E6653.img" then "fastboot boot TWP-3.0.2-2-E6653.img" to install and then boot into TWRP recovery
[*]Once in TWRP, go to "Install" and install first the Kernel, then install the ROM, making sure to do the wipes
For me, this completed the process of installing a custom ROM I was stuck on the lack of info around installing the kernal and whatnot.
TimTams said:
I was stuck on the lack of info around installing the kernal and whatnot.
Click to expand...
Click to collapse
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
TimTams said:
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
Click to expand...
Click to collapse
Hmm maybe u should suggest the OP of those threads to add this information then.
I personally never read those guides lol[emoji14](not anymore at least, at some point I was learning about this like you as well, we all had to learn)
Sent from my E6653 using XDA-Developers mobile app

[Guide-root][oreo][mate 10 lite] How to root mate 10 lite after update to oreo

{
"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"
}
HTML:
/*
* I Do not Become Responsible For The Bad Installation
* Now Your Warranty Is Mine, Before Flashing Investigate
* You Decide to Make All These Modifications to Your Device
* Under Your Own Risk, If You Spoil Your Device, I Will Laugh At You
*/
REQUIREMENTS:
-Bootloader Unlocked You can unlock bootloader from here
-Activate USB Debugging
-Activate Unknown Applications
-SdCard
-Activate OEM Unlock
-Android Nougat 8.0 EMUI 8.0 If you are not you can upgrade from here https://forum.xda-developers.com/ma...grade-to-android-oreo-huawei-mate-10-t3784637
ROOTING:
-First You have to download twrp from https://androidfilehost.com/?fid=746163614322267109 Thanks For @Azan Mughal For His Twrp
-now flash twrp unzip the rared file you will have twrp8.img reboot your device to fastboot (Completely Shutdown your device press Volume Down Key And Plug USB)
-flash by type
HTML:
fastboot flash recovery_ramdisk twrp8.img
-now unplug your device From USB turn off by hold Volume Down Key + power Key
-Download Magisk Flashable from this http://tiny.cc/latestmagisk
-Copy magisk file to sd card
-Enter to recovery mode by press volume Up Key + Power Key
-flash magisk file
-Congrats Now You are rooted
Don't Forget To press Thanks :fingers-crossed:
But is there a working Super SU (instead of Magisk) for Oreo for RNE devices ?
Works like a charm
Made an account just to say that i had previously messed up the recovery by installing an incompatible (outdated) TWRP recovery, however this works like a charm.
I need some help however regarding the fact that i tried installing xposed framework from magisk manager that caused my device to bootloop, i was able to get it running back by factory reset and dalvik cache cleaning, the problem however is that i have lost huawei services (health app says its incompatible) and apps such as whatsapp also say that theyre incompatible with my device. Any help would be appreciated. If i could go back to stock completely and start over i'll accept that too as i cant re-flash stock rom (perhaps cause im already on stock rom)
My Model is RNE-L21C130 (if you can provide a backup for me to restore from that would make my day)
usman400 said:
But is there a working Super SU (instead of Magisk) for Oreo for RNE devices ?
Click to expand...
Click to collapse
I Don't know i tried to root with super su but it's doesn't work
Muhammad Fuzail said:
Made an account just to say that i had previously messed up the recovery by installing an incompatible (outdated) TWRP recovery, however this works like a charm.
I need some help however regarding the fact that i tried installing xposed framework from magisk manager that caused my device to bootloop, i was able to get it running back by factory reset and dalvik cache cleaning, the problem however is that i have lost huawei services (health app says its incompatible) and apps such as whatsapp also say that theyre incompatible with my device. Any help would be appreciated. If i could go back to stock completely and start over i'll accept that too as i cant re-flash stock rom (perhaps cause im already on stock rom)
My Model is RNE-L21C130 (if you can provide a backup for me to restore from that would make my day)
Click to expand...
Click to collapse
Yes You can back to full stuck if your bootloader is unlocked you can back i have an method to downgrade to nougat if you want oreo you can re-update your device to oreo just you have to be on unlocked bootloader
faw_wal said:
Yes You can back to full stuck if your bootloader is unlocked you can back i have an method to downgrade to nougat if you want oreo you can re-update your device to oreo just you have to be on unlocked bootloader
Click to expand...
Click to collapse
I really need the details on how to roll back to Nougat as i am fairly new to this, my bootloader is unlocked and i have TWRP (recovery) the one you shared installed.
Muhammad Fuzail said:
I really need the details on how to roll back to Nougat as i am fairly new to this, my bootloader is unlocked and i have TWRP (recovery) the one you shared installed.
Click to expand...
Click to collapse
Ok Please Be Carefull i'm not responsible for any damage to your phone and i didn't try so you will do it at your own risk
First of all make Backup of every thing with twrp
So First make sure you are unlock frp from developer option and bootloader First You Have to rebrand your device to meafnaf L21C185
You Can Do it from here https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385
or if you want my explain you have to download this https://mega.nz/#!BCRzEQST!L7GnMoI28VSz3Iiw3Mf1ePqHWYUiwqkBQ8fZm4Nf0wU
Make Backup of these file
oeminfo address:
HTML:
dev/block/platform/hi_mci.0/by-name/oeminfo
and this
custom.bin address:
HTML:
data/custom.bin
then flash it with TWRP No Your Bootloader it will be Locked So You Have to reboot to bootloader and re-unlock it
Please Make Sure to do it this Very important because if you didn't unlock it and have frp locked and bootloader locked and you stuck at fastboot so you have to pay 15 euro to dc phoneix to unbrick your phone So Please Make Sure To unlock it after flash Oeminfo now if you want to stay on oreo but back it to full stuck so this is your rom
https://drive.google.com/file/d/16soc6NiVwoV0nwlxwlSHBn6zP1-iAGbp/view
Download it and copy it to your sd card and restore it with twrp
If you need to back to nougat download this rom
https://androidfilehost.com/?fid=890129502657589833
Extract it then you will have update.app
use This https://www.youtube.com/watch?v=OKRTbv-6Kzc tutorial to know how to flash it with fastboot
if you want any help i'm ready to help you but remember you will do this at your own Risk
phone keeps booting into recovery
faw_wal said:
HTML:
/*
* I Do not Become Responsible For The Bad Installation
* Now Your Warranty Is Mine, Before Flashing Investigate
* You Decide to Make All These Modifications to Your Device
* Under Your Own Risk, If You Spoil Your Device, I Will Laugh At You
*/
REQUIREMENTS:
-Bootloader Unlocked You can unlock bootloader from here
-Activate USB Debugging
-Activate Unknown Applications
-SdCard
-Activate OEM Unlock
-Android Nougat 8.0 EMUI 8.0 If you are not you can upgrade from here https://forum.xda-developers.com/ma...grade-to-android-oreo-huawei-mate-10-t3784637
ROOTING:
-First You have to download twrp from https://androidfilehost.com/?fid=746163614322267109 Thanks For @Azan Mughal For His Twrp
-now flash twrp unzip the rared file you will have twrp8.img reboot your device to fastboot (Completely Shutdown your device press Volume Down Key And Plug USB)
-flash by type
HTML:
fastboot flash recovery_ramdisk twrp8.img
-now unplug your device From USB turn off by hold Volume Down Key + power Key
-Download Magisk Flashable from this http://tiny.cc/latestmagisk
-Copy magisk file to sd card
-Enter to recovery mode by press volume Up Key + Power Key
-flash magisk file
-Congrats Now You are rooted
Don't Forget To press Thanks :fingers-crossed:
Click to expand...
Click to collapse
hey this twrp from azan due to this my phone doesnt boot up and always goes into recovey the twrp from king of meizi doesnt do this, why?
bk2010 said:
hey this twrp from azan due to this my phone doesnt boot up and always goes into recovey the twrp from king of meizi doesnt do this, why?
Click to expand...
Click to collapse
If you're using Stock Firmware you can search on xda the unofficial TWRP for P10 Lite by @Pretoriano80 I use this on Mate 10 Lite, it has encryption/decryption support and is working perfectly for everything.
It just doesn't work if you use AOSP based Roms. But for Stock Firmware and Root it works like a charm.
Tecalote said:
If you're using Stock Firmware you can search on xda the unofficial TWRP for P10 Lite by @Pretoriano80 I use this on Mate 10 Lite, it has encryption/decryption support and is working perfectly for everything.
It just doesn't work if you use AOSP based Roms. But for Stock Firmware and Root it works like a charm.
Click to expand...
Click to collapse
For mate 10 oreo right? RNE-L21 8.0.0. 310 its rooted aswell
bk2010 said:
For mate 10 oreo right? RNE-L21 8.0.0. 310 its rooted aswell
Click to expand...
Click to collapse
Yes, I use it on RNE-L21 8.0.0.311. Flash new TWRP in Fastboot Mode.
It will work, if your internal storage is original encrypted by the Firmware (it is, if you haven't formatted data)
Tecalote said:
Yes, I use it on RNE-L21 8.0.0.311. Flash new TWRP in Fastboot Mode.
It will work, if your internal storage is original encrypted by the Firmware (it is, if you haven't formatted data)
Click to expand...
Click to collapse
https://www.google.com.pk/amp/s/for...velopment/recovery-twrp-3-2-1-0-t3783447/amp/
Is this it?
bk2010 said:
https://www.google.com.pk/amp/s/for...velopment/recovery-twrp-3-2-1-0-t3783447/amp/
Is this it?
Click to expand...
Click to collapse
Yes, that's the right one.
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Tecalote said:
Yes, that's the right one.
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
So i flashed this image and its working but i still cant pass the safteynet check in magisk i could pass it only in the twrp provided by azan mughal for mate 10 lite oreo but that caused my device to reboot into recovery and never into system.
Also why does this twrp ask for my decryption password can i turn it off? And i cant seem to insall updates. I have a security update when i press update it reboots into twrp (same with the previous versions i had) i locate the update.zip but it gives me error 9
Tecalote said:
Yes, that's the right one.
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Hello
Great,
so, twrp p10 lite 0.4.img starts on mate 10 lite.
and it can do data backup only in rom stock, if I understood well ??
Chisetdel31260 said:
Hello
Great,
so, twrp p10 lite 0.4.img starts on mate 10 lite.
and it can do data backup only in rom stock, if I understood well ??
Click to expand...
Click to collapse
Where's 0.4? I only found 0.3 and yes its working but i haven't tried a backup yet
bk2010 said:
Where's 0.4? I only found 0.3 and yes its working but i haven't tried a backup yet
Click to expand...
Click to collapse
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Chisetdel31260 said:
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Thanks
I tried the backup and it's working
But one thing I'm curious about is that when i reboot to recovery it asks me for password and starts decryption but there's a line "failed to unmount system device or resource busy"
bk2010 said:
So i flashed this image and its working but i still cant pass the safteynet check in magisk i could pass it only in the twrp provided by azan mughal for mate 10 lite oreo but that caused my device to reboot into recovery and never into system.
Also why does this twrp ask for my decryption password can i turn it off? And i cant seem to insall updates. I have a security update when i press update it reboots into twrp (same with the previous versions i had) i locate the update.zip but it gives me error 9
Click to expand...
Click to collapse
1) Safetynet has nothing to do with TWRP
2) This TWRP ask you for your PIN, if you use a PIN for screen unlock. It's for security. If you don't use PIN for screen unlock, TWRP don't ask you
3) You are "Newbie" Everyone which owns a Huawei Phone should know in the meantime that's not possible to make official OTA updates with TWRP and/or Root.
bk2010 said:
Thanks
I tried the backup and it's working
But one thing I'm curious about is that when i reboot to recovery it asks me for password and starts decryption but there's a line "failed to unmount system device or resource busy"
Click to expand...
Click to collapse
for the moment I have not tested yet.
I do it now.

Installing TWRP makes me crazy

Hello !
Just acquired an HTC U12+ in replacement for my brave Oneplus One, that i kept updated to Android Pie. Compare to my old One, HTC didn't make it easy to make mod...
As I hate all these stupid UI, i want AOSP without the google app as much as i can, so i wanted to try the Android Pie GSI "FLOSS", hoping it works great.
Anyway since yesterday i spend a lot of time trying to install TWRP on my U12, and fastboot and adb make me crazy. First i unlock the bootloader with the describe procedure, it works fine, i use fastboot from offical repo of ubuntu 18.10. I red all the thread and understand that i must boot first twrp and then flash it with the installer. The problem is fastboot and adb are not working after unlocking the bootloader. I am using the USB type C to type A cable from HTC.
My phone was with firmware 1.25 with june patch when i bought it. So i download the right version of TWRP. Fastboot is not working anymore and i get an error of "protocol". Then i see in the FAQ that you need to use the last version from google. This fastboot didn't worked much more, "too many links" error or similar. I tried different usb port of my pc, it seems the usb 3.0 and 3.1 do this, with usb 2.0 error is different, it said "downloading boot.img" and nothing happens. Then i tried to update to 1.30, but fastboot is not working more. I tried in windows, i install the htc driver and use the latest fastboot, same errors. Also tried another pc running ubuntu 18.04 without success.
Right now "fastboot devices" find the U12 properly but all command show error, and "adb devices" shows nothing in download mode.
I guess the problem come from the usb cable ? I live in a small town in the middle of nowhere and have no type c cable, so i ordered two new cable among other accessories, i hope they works but i won't have them before two week probably more (revolution in coming in France ).
But what i don't understand, if it's a problem with the cable, why fastboot was working when i do the "fastboot flash unlocktoken Unlock_code.bin" to unlock the bootloader, and then it refuse to work ?
Regards !
When you do fastboot devices and U12 shows up then you should be alright.
To boot TWRP you must be in boot loader, NOT download mode.
fastboot boot twp.img
It has worked for me just fine on windows, macOS, and Ubuntu
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Use
fastboot --version
To see what fastboot version you have. Latest should be 28.0.1
Hello,
Thank you for your answer. I know the difference between the fastboot and download mode, i try everything but the problem is always the same. My fastboot is the latest from the xda topic :
./fastboot --version
fastboot version 28.0.1-4986621
For example i just try again, it's connected to the usb 2.0 port of my pc, i'm in fastboot (recovery) and not download mode :
./fastboot devices
FA8731F01429 fastboot
./fastboot boot twrp-3.2.3-2-ime.img
Downloading 'boot.img' ... and nothing happens
If it's connected to usb 3.0 or 3.1, get the "too many links" error.
Edit : another exemple, if i use the fastboot from kubuntu 18.10 repo :
[email protected]:~$ fastboot devices
FA8731F01429 fastboot
[email protected]:~$ fastboot boot twrp-3.2.3-2-ime.img
< waiting for any device >
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
That is a strange issue.
Several users on the Pixel 2 forum had the same issue and a different cable worked. I don't know how a cable only works with certain commands.
Looks like you're doing it right however. Unfortunately it might simply be a cable.
Maybe try flashing a boot.img that already has twrp in it so you can just use the bootloader recovery option?
---------- Post added at 08:35 AM ---------- Previous post was at 08:27 AM ----------
k_l_o said:
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
Click to expand...
Click to collapse
You should be on this screen.
BOOTLOADER
{
"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"
}
Yes i am to this screen when i use fastboot. Not have the same info in the screen though. I cannot make a photo now so i will just write what i see :
press volume key etc...
Fastboot Mode (in red)
PRODUCT_NAME - HTC_Phone
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - FA8731F01429
SECURE BOOT - PRODUCTION
SECURE STATE - S-ON
DEVICE STATE - UNLOCKED (U) (in red)
KEY STATE - NONE
*** Software status: Modified *** (in red)
Guess i will try again when i'll get the other cable, but it's very strange indeed.
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
k_l_o said:
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
Click to expand...
Click to collapse
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
ghstmm said:
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
Click to expand...
Click to collapse
I brought up the HTC Sync Manager only for the purpose of installing the drivers. I uninstall the Sync Manager portion of the package afterwards. Anyway, try this link for the latest HTC Driver:
http://www.mediafire.com/file/g4r62oz2v9b1x0q/HTC-Mobile-Driver-v4.17.0.001.zip
I was already in v4.17.0.001. Guess i have to wait now for the new cable, hope it solve the problem...
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Alan-B said:
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Click to expand...
Click to collapse
I don't have any problem with adb, it works always without issues. Yeah sometimes it's difficult to boot into bootloader, but I use adb for that also
Sent from my HTC U12+ using XDA Labs
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
master66 said:
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
Click to expand...
Click to collapse
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
ghstmm said:
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
Click to expand...
Click to collapse
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
DeeZZ_NuuZZ said:
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
ghstmm said:
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
Click to expand...
Click to collapse
No not bricked, but you can't sideload an img. Just get it back to sdcard and flash it from there, also for GSI it is better to wipe from stock recovery
Sent from my HTC U12+ using XDA Labs
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
ghstmm said:
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
Click to expand...
Click to collapse
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
mauiblue said:
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Ok i get it Short timing indeed.
Edit : I finally install the latest android 9 pie gsi. It's working great and i love the floss version, but their is a few bugs : no brightness adjustment, localisation not working and few screen bugs (icon mostly).
Anyway thanks you all for your help

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.1 | Crystal |

{
"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"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-CTL_sprout.img & twrp-installer-3.4.0-0-CTL_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-CTL_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 10 Twrp-3.4.0-0 From Here
​For More Information About Status Official Click Here​
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.1
Contributors
Raghu varma
Source Code: https://github.com/TeamWin/android_device_nokia_CTL_sprout
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2019-01-26
Created 2019-01-26
Last Updated 2020-06-25
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
usernamedoesnotexist said:
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
Click to expand...
Click to collapse
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Raghu varma said:
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Click to expand...
Click to collapse
Thanks for the info! Unfortunately, I couldn't pull my stock recovery from adb and had to use the terminal inside TWRP to pull my recovery. After successfully getting stock recovery, I patched the stock recovery (after copying) to my external SD with magisk and flashed that via adb. Magisk is now installed and I am satisfied.
Note: this is relatively the first time I am leaving stock recovery on my device vs custom recovery to keep the OTA updates. This is because there isn't much of a dev community here at the moment and not much to do on the device.
New Build Is Up
Based On R40
Android version - pie
twrp- based on June 2019
################ The final Main installation procedure #################
Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
1 . Download twrp-3.3.1-0-CTL.img & twrp-installer-3.3.1-0-CTL.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.3.1-0-CTL.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? just power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
congratulations now you are successfully booted in to twrp
@Raghu varma
Any telegram group for development? If that exist, please add me t.me/theHari08.
Note - Twrp Support is back for Nokia 7.1
Changelog
13-12-2019
* Initial android 10 twrp builds are up
* Twrp based on 3.3.1-0
* Supports on Android 10 stock roms and custom roms
* supports on Android 9 stock roms and custom roms
* Follow instructions as i mentioned above in the xda thread for installation
* Omni sources based on latest r47
* Decryption works
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
giant_karlik said:
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
Click to expand...
Click to collapse
Before you can modify anything on a phone you always have to unlock the bootloader. Since Nokia does not allow official bootloader unlocks, we have to go through a paid method (see other threads about unlocking the bootloader here).
this guy will do it for a small fee well worth it ...
Added official support
Android 10 TWRP doesn't work on 7.1 december update
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Reysen said:
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Click to expand...
Click to collapse
*make sure your phone bootloader is unlocked.
* make sure you downloaded twrp files from xda thread download links
* make sure you follow steps as i mentioned above
according to your info i tested again on my Nokia 6.1 Plus android 10 stock rom based on december security patch.
Nokia 7 Plus , Nokia 7.1 , Nokia 6.1 & Nokia 6.1 Plus all sources are same
so it should work on 7.1 too make sure you re flashed stock rom and test again because trying several times on same partition may corrupt and failed to boot.
Hey, thanks for your fast answer.
*make sure your phone bootloader is unlocked.
Click to expand...
Click to collapse
The bootloader is indeed unlocked
* make sure you downloaded twrp files from xda thread download links
Click to expand...
Click to collapse
I tried multiple versions from the sourceforge link.
* make sure you follow steps as i mentioned above
Click to expand...
Click to collapse
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Reysen said:
Hey, thanks for your fast answer.
The bootloader is indeed unlocked
I tried multiple versions from the sourceforge link.
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Click to expand...
Click to collapse
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Raghu varma said:
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Click to expand...
Click to collapse
Hi,
I flashed my nokia 7.1 like instructed and everything went well (though I noticed it wasn't the latest version, but that's a detail).
Went into the bootloader and tried running TWRP but still had the same issue as before (stuck on the android one boot, it was a totally stock ROM, the one provided on your other post).
So I used the boot.img from the stock ROM you uploaded and patched it, then flashed it in the bootloader and it worked.
So even though TWRP still doesn't work in the end I did what I wanted to do, so thanks for your help.
And again, thanks for all the work you're doing, sorry to bother you.
Have a nice day.
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
husky69 said:
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
Click to expand...
Click to collapse
TWRP went official so technically you can go to the TWRP site and download the current there
In addition to it going official, there is no need to download both the img and zip installer with it.
https://dl.twrp.me/CTL_sprout/
You can now just flash (fastboot flash recovery twrp-3.3.1-0-CTL_sprout.img).
https://twrp.me/nokia/nokia7.1.html
Things to keep in mind: If you have a PIN or Passcode you should disable it on the ROM before booting up to TWRP because of encryption.
If you flash another ROM such as Lineage OS shortly after flashing TWRP, it will replace the TWRP with the Lineage OS recovery. So you will probably have to flash TWRP again.
I hope that this works?!
i have android 9 is there a twrp image for 9?
Alas, this does not help, the same problem, the phone hangs on the logo)
P.S
executed the commands like this:
fastboot flash recovery (error issued)
fastboot boot
and successfully loaded into TWRP

[RECOVERY][STOCK]TWRP 3.3.1-0 UNOFFICIAL

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June patch)
- Brightness is a little bit buggy
- Transfering files to the external SD card will cause the phone to reboot
- Installing is not working yet, only booting.
- Please report any other bugs
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it
Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button
If it keeps booting into TWRP and not System try
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Download
Changelogs:
3.3.1-0 25.06.2019
- Fixed brightness bug
3.3.1-0 20.06.2019
- Adding logcat support
- Adding support to install TWRP to ramdisk
- Trying to fix brightness bug (seems to be not working yet)
- MTP probably fixed (needs reports)
3.3.1-0 19.06.2019
- Initial release
Source code:
https://github.com/Schritti/device-sony-kirin
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
XDA:DevDB Information
TWRP, ROM for the Sony Xperia 10
Contributors
Schritti, MartinX3, Oshmoun, Marijn, SODP Team
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-06-19
Created 2019-06-19
Last Updated 2019-06-25
Reserved
Reserved
First!
Woohooooo!
Thanks @Schritti, he helps me root my device
on my device (i3123), it shows a black screen.
ToastedToast said:
on my device (i3123), it shows a black screen.
Click to expand...
Click to collapse
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
thanks!
bug report:
the file name in SDcard folder shows abnormal. please see attached pictures. (not only in windows explorer anf command line, but also in phone.)
wang4632 said:
thanks!
bug report:
the file name in SDcard folder shows abnormal. please see attached pictures. (not only in windows explorer anf command line, but also in phone.)
Click to expand...
Click to collapse
Thanks for the report.
That's due to the not working decryption of the internal storage, already on the bug list
It did not work on I4293
Thank you for customizing TWRP
But,I have a black screen with I4293 I have
Would you like to customize it
naoki2010 said:
Thank you for customizing TWRP
But,I have a black screen with I4293 I have
Would you like to customize it
Click to expand...
Click to collapse
Afaik I4293 is a Xperia 10 Plus. This TWRP is only for the normal Xperia 10.
I am already working on a TWRP for the 10 Plus.
under latest version I3123_Customized US_1317-7745_53.0.A.6.92_R8A, TWRP /sdcard decrypt doesn't work, however external storage is fine.
EDIT: realized that is already on the bug list
I wonder when it can work with costom rom???
Has the project been stopped?
I really need to flash third party rom..???
does it work on the i3113?
Hello, did the state of decryption change ?
If not, are you missing something ?
Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
How can I get out of the black screen I get from making this mistake?
Would someone plaese so kind and write down a step by step installation guide for a noob?
any twrp for xperia 5?
Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
Hi, thanks for all your work first of all!
I have rebooted into fastboot mode via ADB command line but after running "fastboot boot twrp.img" in command line, it says okay, and then I get the same problem, a black screen. My phone is a normal Xperia 10, not plus.
Could you please help me?
---------- Post added at 03:16 PM ---------- Previous post was at 03:01 PM ----------
Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
Hi, thanks for all your work first of all!
I have rebooted into fastboot mode via ADB command line but after running "fastboot boot twrp.img" in command line, it says okay, and then I get the same problem, a black screen. My phone is a normal Xperia 10, not plus.
Could you please help me?

Categories

Resources