Database Info

[RECOVERY] TWRP 3.0.2-0 [06/06/2016]

PREAMBLE
Team Win Recovery Project, or twrp 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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 image
* [B]before[/B] flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I'll keep this thread short and simple. Want a changelog or a list of features? See teamw.in.
DOWNLOAD
recovery.img
INSTRUCTIONs
Code:
fastboot flash recovery < recovery image >
or, if you only want to use it temporarily:
Code:
fastboot boot < recovery image >
XDA:DevDB Information
TWRP for Sony Xperia Z3+, Tool/Utility for the Sony Xperia Z4
Contributors
Olivier
Source Code: https://github.com/omnirom/android_kernel_sony_msm
Version Information
Status: Stable
Created 2016-03-28
Last Updated 2016-09-13

Have tested this build - works perfectly, fully stable.

Thanks! but this twrp not work for my dualsim version Reboot after few seconds of booting recovery.
I'll check whats wrong soon. But probably need use dsds defconfig.

Quarx said:
Thanks! but this twrp not work for my dualsim version Reboot after few seconds of booting recovery.
I'll check whats wrong soon. But probably need use dsds defconfig.
Click to expand...
Click to collapse
In this case check out my recovery in Dev sector - works on both single and dual.
MotexT

Quarx said:
But probably need use dsds defconfig.
Click to expand...
Click to collapse
The ivy defconfig is now unified and can hence be used for both variants as per commit ec71e11 upstream. Can you please test if it works now? twrp-ivy-20160401.img

@MotexT, yep, your version works.
@Olivier, works now

Can you flash this in twrp? Or has it got to be done through fastboot?

@Olivier, there another problem. USB not work at all in twrp. PC not detect any usb device...

USB (0) AND SD CARD (0)
Hi,
Have also detected in TWRP 3.0.1 both the USB and SD Card Storage show 0. Thus only the Internal Storage contents are visible whereas SD Card contents are not. To flash items, I have to copy them from the SD Card onto the Internal storage before booting into recovery. Worth looking into this.
Thanks!

new version from 08.04.2016 not work for extern sd....

Doesn't work for me with 185 build. Just blinks red three times when trying to start, then rebooting.

Quarx said:
@Olivier, there another problem. USB not work at all in twrp. PC not detect any usb device...
Click to expand...
Click to collapse
I don't know what causes this (yet), but this issue seems to be pretty random: Sometimes MTP/ADB work for me, sometimes they don't.
yawo76 said:
USB (0) AND SD CARD (0)
Hi,
Have also detected in TWRP 3.0.1 both the USB and SD Card Storage show 0. Thus only the Internal Storage contents are visible whereas SD Card contents are not. To flash items, I have to copy them from the SD Card onto the Internal storage before booting into recovery. Worth looking into this.
Thanks!
Click to expand...
Click to collapse
BustedFly said:
new version from 08.04.2016 not work for extern sd....
Click to expand...
Click to collapse
External SD cards should be working now; twrp-ivy-20160408.img - USB OTG is still broken though.
diemadedrei said:
Doesn't work for me with 185 build. Just blinks red three times when trying to start, then rebooting.
Click to expand...
Click to collapse
Works for me, have you tried using "fastboot boot"?

Olivier said:
Works for me, have you tried using "fastboot boot"?
Click to expand...
Click to collapse
Tried around a bit now. None of your builds work, neither through boot nor through flash recovery. When using boot the sony screen appears and the LED stays blue and then nothing. I then tried @MotexT's build, which works both when booting and flashing for me.

diemadedrei said:
Tried around a bit now. None of your builds work, neither through boot nor through flash recovery. When using boot the sony screen appears and the LED stays blue and then nothing. I then tried @MotexT's build, which works both when booting and flashing for me.
Click to expand...
Click to collapse
Try this build. It uses the kernel from .185, not the AOSP one like my other builds.

Olivier said:
Try this build. It uses the kernel from .185, not the AOSP one like my other builds.
Click to expand...
Click to collapse
I got soft brick after flashing this recovery , E6533 . 185 firmware

alphaprosper12 said:
I got soft brick after flashing this recovery , E6533 . 185 firmware
Click to expand...
Click to collapse
Use the builds from the OP, that one was just a test build for the single SIM variant.

MOD EDIT
There is never a need to quote the whole OP
Can you please tell me how to boot to recovery? I installed the recovery but don't know how to boot into it. I've tried the power+volume up, power+volume down and the power on and then volume up and down. Nothing worked I'm on 6.0

Quarx said:
Thanks! but this twrp not work for my dualsim version Reboot after few seconds of booting recovery.
I'll check whats wrong soon. But probably need use dsds defconfig.
Click to expand...
Click to collapse
Can you tell me how to boot into recovery?

How to add it to Z3+?(newly BL unlocked)

Not work after flashing 32.2.A.0.224
White screen with SONY logo and Unknown USB Device (Configuration Descriptor Request Failed) detected.

[Recovery][H850] Team Win Recovery Project for the LG G5

Team Win Recovery Project 3.0.3-0
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
A message to those with other variants of the G5:
The H850 International variant is the only one with an official bootloader unlock from LG.
Should there be a time where your flashing mechanisms get cracked, simply mention my name on this thread or via private message and I would be happy to create a thread with TWRP for your device.
I have device trees ready for ALL variants of the G5, pending their unlock!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://twrp.me/devices/lgg5h850.html
FULL STEPS FOR OBTAINING ROOT
Follow LG's bootloader unlocking instructions here before you begin!
{
"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 the latest TWRP .img for your device from this thread or twrp.me.
Use the same fastboot tool you downloaded in the LG unlock instructions to flash TWRP using the command:
Code:
fastboot flash recovery twrp-x.x.x-x-h850.img
* Replace x.x.x-x with the actual version you are flashing!
Now you can either power off your phone and boot into recovery using the button combo [Volume Down] + [Power], or you can run this command in fastboot:
Code:
fastboot boot twrp-x.x.x-x-h850.img
At this point, you will see the TWRP splash and reach a screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 8 you will be unable to boot!
If you are going to root your device or follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
Please consider backing up your stock boot partition in TWRP before proceeding to the next steps!
If you want to be rooted with SuperSU:
Download the latest SuperSU stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
-or-
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
[v]v3.0.3-0[/b] - TWRP app added - See .
[*]v3.0.2-0 - See [url=https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html]here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
LG encryption is not supported yet in TWRP 3. Your device will hang for a while when trying to enter a password. Skip it.
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
Device tree: https://github.com/TeamWin/android_device_lge_h850 (International)
Device tree: https://github.com/TeamWin/android_device_lge_h830 (T-Mobile)
Kernel sources: https://github.com/jcadduono/android_kernel_lge_msm8996/tree/twrp-6.0
TWRP: https://github.com/omnirom/android_bootable_recovery
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - LG G5, Tool/Utility for the LG G5
Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android_device_lge_h850
Version Information
Status: Stable
Current Stable Version: 3.0.3-0
Stable Release Date: 2017-01-03
Created 2016-04-21
Last Updated 2017-01-08

This is great news!! Thanks for all the great work!
I have a Sprint version of the G5. Does this work on Sprint variant?

rajbsn said:
This is great news!! Thanks for all the great work!
I have a Sprint version of the G5. Does this work on Sprint variant?
Click to expand...
Click to collapse
Is the Sprint variant H850? I don't think so. You need to have an unlocked bootloader which has currently only become available this morning for the H850 European variant.
Thanks for this! Time to go buy my G5 now (Australia's a bit behind the times, only became available yesterday lol)

Here we are!
Envoyé de mon SM-G925F en utilisant Tapatalk

getting stuck at the splash screen on the H850

LBensley said:
getting stuck at the splash screen on the H850
Click to expand...
Click to collapse
Same problem here.

Following instructions found here
For TWRP to "stick" you must first boot directly into TWRP and not back into Android, until after flashing the SuperSU zip.
After flashing TWRP unplug the USB cable and pull the battery. Plug battery back in then boot into recovery which should hopefully load TWRP.
To boot into recovery:
a. Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.
b. As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
c. Keep holding until you see the Factory Reset screen. Click thru the factory reset screens.. Yes.. Yes...
10. You will not be able to decrypt your internal data while in TWRP but you can manually mount your external SD card to view the SuperSu zip. Feel free to back up first.. but otherwise.. time to install SuperSu. Click the Install button and navigate to the external_sd, select the SuperSu zip then swipe to install. Now you're rooted and TWRP'd! Reboot into system...
Stuck on TWRP splash screen.

queloo said:
Following instructions found here
For TWRP to "stick" you must first boot directly into TWRP and not back into Android, until after flashing the SuperSU zip.
After flashing TWRP unplug the USB cable and pull the battery. Plug battery back in then boot into recovery which should hopefully load TWRP.
To boot into recovery:
a. Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.
b. As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
c. Keep holding until you see the Factory Reset screen. Click thru the factory reset screens.. Yes.. Yes...
10. You will not be able to decrypt your internal data while in TWRP but you can manually mount your external SD card to view the SuperSu zip. Feel free to back up first.. but otherwise.. time to install SuperSu. Click the Install button and navigate to the external_sd, select the SuperSu zip then swipe to install. Now you're rooted and TWRP'd! Reboot into system...
Stuck on TWRP splash screen.
Click to expand...
Click to collapse
I followed those instructions aswell but everything worked fine for me. Was able to get into twrp and flash supersu. Wonder why it's only working for some.

duckysempai said:
I followed those instructions aswell but everything worked fine for me. Was able to get into twrp and flash supersu. Wonder why it's only working for some.
Click to expand...
Click to collapse
I wonder what is which has stopped everyone else's from working?
what was your process in flashing it and everything?

LBensley said:
I wonder what is which has stopped everyone else's from working?
what was your process in flashing it and everything?
Click to expand...
Click to collapse
Just followed the instructions here to the letter. Didn't do anything different. Only thing I can think of is that I let the phone boot fully after unlocking and then installed twrp after that. Not even sure if that can affect anthing

Recovery hangs at TWRP splash screen.
My PC sees Recovery ADB device connected (in Device Manager), but ADB program doesn't see any device, so I can't get logs.

I think you are the first user with working twrp. 99.9% of all other user dit not work.

duckysempai said:
Just followed the instructions here to the letter. Didn't do anything different. Only thing I can think of is that I let the phone boot fully after unlocking and then installed twrp after that. Not even sure if that can affect anthing
Click to expand...
Click to collapse
If that was the reason behind it working, i cant imagine there is away to do that once the device is unlocked and how long did it take to get into TWRP

Works perfectly for me. Flashed TWRP, flashed SuperSU, then finally flashed V4A and it's all working perfectly.

xbenjii said:
Works perfectly for me. Flashed TWRP, flashed SuperSU, then finally flashed V4A and it's all working perfectly.
Click to expand...
Click to collapse
did you do anything different to the instructions

LBensley said:
did you do anything different to the instructions
Click to expand...
Click to collapse
Nope, followed them exactly.

xbenjii said:
Nope, followed them exactly.
Click to expand...
Click to collapse
why on earth is not working for some then i wonder!

Im stuck too at the splash screen. Followed all from other thread....

https://drive.google.com/open?id=0B4Y8DXE5iZ-iWnBJQ2FzZWJxMzA
recovery log if anyone can see whats wrong

@users with working twrp, which G5 device have you? I have H850 and this not work.

Warning: Current Pixi 4 (4) 4034N will softbrick if you unlock the flash

Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter

Good news!
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!

I think I'm seeing the same problem with a 4034X (UK variant, as sold by Tesco Mobile). Unfortunately, the mobile update software isn't working for me as it's detecting that I've already got the latest version of the ROM installed already and won't let me install it again. AIUI, the CM13 system has a few issues, so I'd rather not go that root, so would still like a stock ROM if at all possible. Anyone have any pointers?

Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.

One question worth asking: does this mean that *all* operations that cause a factory reset on an affected 4034 cause a boot loop? Or is it only unlocking the boot loader?

I managed to soft brick my 4034X simply by allowing my email program to encrypt the device. The encryption apparently failed and now it's stuck on boot animation. As @jh3141 said, the Acatel upgrade tool doesn't work. I guess I need to find a stock ROM, but my Googling hasn't found one yet. Can anyone help?

palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:

i need help
Tampopo said:
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
Click to expand...
Click to collapse
Can you brake this down for me? am kind of new to all this but i really need to root my device

jh3141 said:
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
Click to expand...
Click to collapse
Any luck with the UK version 4034X?
I'm stuck in the booting process just like you were.

me too - Pixi 4(4) chaos on unlocking.
Absolutely the same experience here.
I have nuked 2 of these trying to unlock. It is a brilliant phone, but this is a painful feature - as you describe.
My history is in one of the threads on this site. - I agree, I would love a stock ROM for it.
palbeda said:
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Click to expand...
Click to collapse

I also softbricked my 4034X after unlocking the bootloader and couldn't get the phone to boot into recovery or the bootloader. I eventually managed to flash a stock ROM with SP Flashtool as described here https://www.getdroidtips.com/install-official-stock-rom-on-alcatel-pixi-4-4/ - this restored the ability to boot into recovery or bootloader but the ROM wouldn't boot so I couldn't enable developer settings to allow OEM unlocking. I then tried flashing the ROM for the dual-SIM version of the 4034X (risky!) and this booted and I was able to unlock the bootloader and flash TWRP recovery. The next problem was when & flashed CM13 and got an error message saying that TWRP couldn't access /data. It then got stuck in a recovery bootloop. Next I used TWRP to format all the partitions but it still couldn't access /data and broke the ability of the Mobile Upgrade Tool to read the phone. My next step is to try flashing a different custom recovery but I'm rapidly losing the will to live and would be very interested in any suggestions.
UPDATE - got it sorted by re-flashing the dual-SIM 4034X ROM (even though I have the single SIM version!), flashing ctr-6.6-4034 recovery, doing a normal wipe then formatting the /data partition then flashed CM13. I guess the data partition must have got corrupted.

I have exactly the same problem with pixi 4 4043f. I unlocked bootloader and then flashed following your instructions on that link you shared. But I see is a white screen frozen no options shown just booting voice behind.... I have flashed it several times but same results I still cant entry fastboot or recovery... Volume down + power or volume up + power dn take me anywhere just that frozen white screen with booting ring tone in the back and thats it... Kindly guide me

i had a similar problem, but i always wanted to flash cm13, so i was fine.
There is an amazing thread here for our device.
For those of you with the 4034X, i have ported cm13 to it specifically, bu there are too many bugs, but if anyone wants it, just tell me!

also, can i just say, softbrick if you oem lock aswell :,(
i wanted to test something, but after fastboot oem lock, and then fastboot reboot, i get an android being repaired? key combo's not working, adb/fastboot not responding, can't remember how i fixed it when i oem unlocked ...
edit-
got into recovery with key combo, now it's just to fix it!

Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting

kirito9 said:
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
Click to expand...
Click to collapse
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Update: I've installed the stock ROM I linked to above, and it seems to be working pretty well. Only issue was that the scatter file that came with it was apparently broken. Fortunately, one that I had hanging around from attempts to fix this problem last time seemed to work with it. I've attached that to this message in case anyone else needs it.

jh3141 said:
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Click to expand...
Click to collapse
Thanks, I'll be sure to add a notice for 4034X users in the Magisk guide. I have yet to see a stable CM13 ROM for MT6580 with 3.18.19 kernel. There seems to be an issue with this device chip and ROMs.

Finally got root on the Pixi4-4034
Hi everyone,
yeah I finally managed to root the alcatel Pixi 4-4 (4034) (3G MODEL). It was really tricky and there are quite some issues you have to deal with.
Therefore please read carefully my instructions and remember I am not responsible for any inconvenience, do it at your own risk.
First of all you have to unlock the bootloader and here comes the first problem. On the Pixi4 this operation leads to a sotfbick because the unlocking process deletes completely the data-partition. The phone can't boot anymore and ends in a bootloop.
To resolve this problem you must reflash the phone with SP-Flash-Tool. After reflashing the bootloader remains unlocked so that you should be able to continue with the rooting process. The second problem is that I could find only one working ROM for flashing. It is for the 4034X, my phone was a 4034D (dual SIM), after flashing I had an 4034X what means that my Pixi became a single-SIM phone, I can live with that.
Here are the necessary steps to obtain root on the Pixi4
1. UNLOCKING BOOTLOADER
- Go to settings -> about phone -> hit many times on "build number" till developer message appears
- Enable "OEM unlocking" located in developer options.
- Switch also "USB debugging" on
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Confirm the debug authorization window on the phone, check "always allow from this computer" (afterwards phone should boot into fastboot, otherwise retype the command above)
- Unlock bootloader by typing "fastboot oem unlock"
WARNING: this deletes the data-partition leading in a softbrick and bootloop,
you have to reflash the phone afterwards to continue rooting!
- Confirm the unlocking with the volume-up key
2. REFLASHING THE PHONE
- I found only this working firmware for the 4034X on this page like described by jh3141:
https://forum.xda-developers.com/android/general/warning-current-pixi-4-4-4034n-t3463154/page2
- You have also to use the scatter file described by jh3141
- After loading the scatter-file in SP-Flash-Tool you have to link the missing img-files in the SP-Flash-Tool-Window
- If you flash the 4034X firmware over an 4034D you will end in a single-SIM phone instead of a dual-SIM.
- After flashing the phone will boot again so that you can continue with flashing the twrp-img.
3. ROOTING THE PHONE
- To root the phone you have to install the twrp-image, the one for the Pixi 4034 you find it here:
https://forum.xda-developers.com/showpost.php?p=68049551&postcount=97
- Download and untar the file at the bottom of the page: twrp-3.1.0-0-4034.tar
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Flash twrp by typing "fastboot flash recovery twrp-3.1.0-0-4034.img"
- Download Super-SU "SR1-SuperSU-v2.78-SR1-20160915123031.zip" from
https://download.chainfire.eu/1003/SuperSU/
and put the zip-file on the phone (external or internal storage)
- With the phone switched off boot into twrp by holding power and volume-up keys togehter
- In twrp go to "Advanced" -> "Terminal" -> Type the following code:
echo "SYSTEMLESS=true" > /data/.supersu
- Go back and choose "Install" -> flash the Super-Su-file (SR1-SuperSU-v2.78-SR1-20160915123031.zip)
- Reboot and you’re done, you have root and super-su on the PIXI4
- If you want to uninstall system-apps proceed to the next step.
4. UNINSTALLING BLOADWARE APPS
- You can’t uninstall system-apps directly from the Android-OS,
if you delete the apps with some uninstall-tools it’s strange but the phone will reinstall them after a reboot.
- To succeed you must uninstall the apps in twrp
- Be careful, uninstalling the wrong apps will end in a bootloop or bootfreeze and you will have to reflash the phone starting at step 2.
- Boot into twrp -> go to "Mount" -> check "System" -> go back and choose "Advanced" -> "File Manager"
- In file-manager navigate to the appropriate app-folders and delete the .apk-files
- IMPORTANT: before rebooting you have to wipe the dalvik-cache
- Go to "Wipe" -> "Advanced Wipe" -> CHECK ONLY "Dalvik / ART Cache"
- Confirm wipe and reboot
I personally like the Pixi4-4034, it’s a very small one that is very useful as second phone especially on holidays .
Have fun.

i bricked my alcatel
i have an alcatel pixi 4 (4) 4034x and when i unlocked the bootloader it softbricked my alcatel, the only solution i did was relflash it using spflashtools

same problem
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
I have exactly the same problem. But I haven't been able to find this Mobile_Upgrade_S_4.5.9. Any help will be greatly appreciated,
thnx,
Herman
update: i found the mobile upgrade tool. But it says the latest firmware is already installed. Earlier i tried spft, flashing seemed to go well but the phone stays in animation/bootloop.
Can anybody help?

【TWRP】Recovery 3.2.3.0 has come to the SM-C5010/C5018

TWRP Recovery 3.2.3.0 has come to the SM-C5010/C5018!​
In order to install this, follow these instructions:
Enable OEM Unlock in developer settings
Enter download mode (Press and hold home + volDown + Power when powered off)
Using Odin, click the 'AP' tab and select the twrp_recovery_3.2.3.0_c5pro.tar file you've downloaded.
Flash the TWRP image, then hold home + volUp + Power
Congratulations, you are now booted into TWRP!
Remember, on the stock ROM, dm-verity is enabled. What does this mean? If you swipe to allow system modifications, you must flash something that disables dm-verity (such as magisk or a dm-verity disabler.)
Also, on the stock ROM, you MUST format /data before performing any actions, due to the fact that it is force-encrypted by default.
BUGS
None, as far as I'm aware.
XDAevDB Information
TWRP for c5proltechn, Tool/Utility for the Samsung Galaxy C5pro(C5010/C5018)
Contributors
Cyborg2017
Source Code
https://github.com/TWRP-Recovery-Project-Unofficial/android_device_samsung_c5proltechn-twrp
Version Information
Status: Stable
Download
https://androidfilehost.com/?fid=5862345805528067341
Created 2018-08-01
Last Updated 2018-08-01

Great!

great job bro but I have a problem with it that it didnt detect my storages when I want flash a zip file
please help me

ROOT BLU R1 PLUS - R0051UU ROM 6.0 V13 - MT6737m

Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Thanks to @lopestom for all his help and porting TWRP to this device
Thanks to RootJunky for FRP Unlock.img
Thanks to Larry Miller for testing with his device
This has been done to Three 16 G devices and One 32 G device to date
WARNING:
Code:
[B][COLOR="red"]
DO NOT FLASH RECOVERY WITH SP FLASHTOOL AS IT
COULD BRICK DEVICE!![/COLOR][/B]
For use SPFT you need special file. So here's the best way is using ADB-fastboot to unlock bootloader, flash FRP Unlock.img and recovery!!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users:
Code:
[B][COLOR="Red"]MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC![/COLOR][/B]
This method uses adb and fastboot commands to achieve root
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contatcs or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play! Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone open setting
about phone, tap 7 times in build number
Enable Developer Options
Enable USB Debugging
2. On PC search the folder of adb and fastboot minimal ( included in zip to install }
Unzip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79-SR3-20170114223742.zip in adb and fastboot minimal folder
Open adb terminal
Code:
adb devices
to ensure connection
Code:
adb reboot bootloader
Code:
fastboot flash frp unlock.img
Code:
fastboot oem unlock
( Confirm with volume up select on phone )
Code:
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot TWRP Recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install in TWRP
Select Reboot System
Phone May reboot several time do not interrupt boot
Unlocked bootloader and TWRP
xposed arm v89 has been tested and works , Gravitybox 6.5.3 has been tested and works
Download link
TWRP_Root_R1_Plus.zip
mirror: TWRP Root R1 Plus.zip
William Smith
XDA:DevDB Information
[TUT] Unblocking & Unlocking - Installing TWRP - ROOT, Kernel for all devices (see above for details)
Contributors
lopestom, donnasbrt1
Source Code: https://forum.xda-developers.com/android/general/blu-blu-vivo-kernel-sources-t3767993
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-19
Last Updated 2018-09-24

More in info: Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Link of Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Click me post #13
.

lopestom said:
Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Click to expand...
Click to collapse
This is too late for me. I returned this phone long ago.

Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?

Donphillipe said:
Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
both of them have built in part of there install, a series of commands that remove other root, But is best to remove su before flash majisk. From the superSU app. in the menu is option to full remove superSU. Do that, then reboot make sure it is ok. Then try magisk. Note that it 'should' work, but it seems you will be first to try it.

Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.

The factory image I downloaded must be corrupt or something else is wrong. I tried flashing the factory image I downloaded "Blu_R0051UU_MT6737M_V13_REPAIR" and I received the error: ERROR: SBROM_DOWNLOAD_DA_FAIL (2004)
I still can boot to TWRP but I have no backup image in this format. If anyone has a factor or TWRP to share, please let me know.

Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.

Donphillipe said:
Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.
Click to expand...
Click to collapse
Larry Miller has also supplied a TWRP backup for this device ..thanks Larry
TWRP backup
Donphillipe said:
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
With Supersu installed you can install Magisk and after remove suspersu......
Donphillipe said:
Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: link
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.
Click to expand...
Click to collapse
After removed Supersu or Magisk the ROM can't start because have Custom recovery installed and made modified system option..... So in this case need install again supersu or magisk!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users: MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC!
Sent from my BLUBOO Xtouch using XDA Labs

Fixed, can't thank you enough!

Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
---------- Post added at 03:25 AM ---------- Previous post was at 03:10 AM ----------
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.

I no have the device in my hands. So you can install old version of magisk v15 or v16?
So if you need more information so you can enter here: BLU Development Team
Donphillipe said:
Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.
Click to expand...
Click to collapse

More in info on device R1 Plus
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this

donnasbrt1 said:
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this
Click to expand...
Click to collapse
Hello, which driver did you use? I can't get download mode work right

When loading bootloader ..power off device ...press volume up ..then power ( at the same time ) then plug device into pc ..device should load ..then device should flash .. do not flash preloader or imei issues may result

Any update on the progress lineage 14.1 on this phone? I use it for a day waa bit laggy

Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more

donnasbrt1 said:
Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more
Click to expand...
Click to collapse
Any update or ETA? I might put off a phone purchase if a build with a working camera comes along.... P.S. Another annoying bug I face is that videos don't play in some apps e.g. google photos, WhatsApp statuses and on Snapchat. Videos on Youtube and Facebook play fine. Fingers crossed for some good news! Wishing you a happy holiday season!

You can allways run stock rooted with xposed and gavitybox until bugs are worked out. Just a thought .Happy holidays to you also

+1 32G successful
Thanks for this! Waited for so long for a method.
Now: since I'm kinda newbie to root, I'm doubtful on how to detect custom kernels to flash based on this device model. Or is it possible to flash whatever?
I need something like 'ElementalX' or related.