This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devicesadb reboot fastboot "
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.
Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devicesadb reboot fastboot "
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.
Related
Hello everyone!!
After doing a lot of extensive research I finally decided to flash Cyanogenmod 11 on my device (btw it's Moto G XT1033). I followed all the instructions of an xda member. Unfortunately my phone fails after flashing the recovery image. It shows on the cmd prompt that the flashing was successful but everytime I go to recovery mode I am no longer able to access the recovery.img
All I get is a blank screen with occasional blanks, freezes and various types of patterns on the screen. I followed each and every instruction to the letter still I do not know why this is happening. cannot even access the default bootloader now!
Here are the steps I used:
1. Unlock the bootloader
2. Installed adb and fastboot and copied the img file to the adb directory
3. Restarted my phone to the boot menu
4. used the command "fastboot flash recovery recovery.img"
5. got a message that the operation was successful.
However after these steps, I am unable to access the cwm bootmenu. Even the default one is no longer accessible.
Please help!!!:crying::crying:
After flashing recovery, do not reboot the phone. Use the phone's volume buttons to enter fastboot from the phone's fastboot menu.
I would install trwp instead.
I agree on Kannz2's suggestion for TWRP.
AFAIK, the recovery you're trying to flash is closed sourced and is no longer being updated.
Here's a link to TWRP:
http://techerrata.com/browse/twrp2/xt1032
Link to ADB and Fastboot that I use:
http://forum.xda-developers.com/showthread.php?t=2588979
I have a Koodo LG P500H. I am having a very hard time installing TWRP.
Firstly Play store doesn't work. It has this old thing called "Market" that has some apps, but not all. Market eventually gets updated to Playstore, but I can't even find TWRP manager. There was another app in the Playstore that I tried called ROM Manager. It said it installed TWRP for me. I restarted the phone, and nothing happened.
Restarting and Holding power/volume down/home will show a picture that seems to be some sort of recovery mode. But it only run for 1-2 seconds before the phone restarts itself. Nothing happens.
I tried to use ADB. But after rebooting the device it just restarted without ever going into recovery mode. So the flash command just get stuck at "Waiting for Device." Does this phone even have a recovery mode?
This phone doesn't support Odin.
I am used to using TWRP. Without it I cannot flash the phone into new OS.
And every single time I fail, the whole phone seems to have reformatted. So I have to enter in my wifi password and gmail again. All of that typing on a very small keyboard takes a lot of time. I had spent hours on this phone without getting TWRP working.
Please help.
going to twrp web site here
downloading the recovery
reboot to fastboot ( bootloader ) than using terminal whit adb driver :
fastboot flash recover '' recovery.img ''
Gw4nM4n said:
going to twrp web site here
downloading the recovery
reboot to fastboot ( bootloader ) than using terminal whit adb driver :
fastboot flash recover '' recovery.img ''
Click to expand...
Click to collapse
The problem is when I reboot into fastboot (adb reboot bootloader), the phone will go into "phone off battery charging mode". It never actually goes into the bootloader.
Ok I did the following and it seems fastboot and TWRP works now. Be sure to enable USB Debugging on your P500.
1) Fastboot tutorial (I did everything here. I hit "ok" on the LGMDP 1.5 tool as needed. Do not wait till the countdown timer goes to zero.)
http://forum.xda-developers.com/showpost.php?p=15122833&postcount=100)?
FastBoot Tutorial
1. Please download this (or from here) file and unzip it in to any folder.
2. Start LGMDP 1.5 tool with the phone connected (you need to have USB drivers installed) and click on Select Port
3. A separate window should appear like the one below
Just click connect
4. Another window will take shape (LGE Mobile security) with lots of options (links)
Click on the first upper right Browse and select the folder in with you have unzipped the files. You will get some errors that some image, table or headers are missing. Just click OK and in the end everything that should remain selected is Partition Table, APPSBL Image Header and APPSBL Image.
Now just close the window (click on x)
5. Now you are back on the main window and here you'll have to click on Download
6. You are almost done and from now on everything should go on automatically.
NV Backup
Autorestart in Emergency\Download mode and upgrade the files (you selected on step 4)
NV Restore (the last step) Do not disconnect the USB cable until the restore is done
Wait for the phone to restart in normal mode (your current rom).
That should be everything you need to do to get fastboot enabled.
Click to expand...
Click to collapse
2) Install PdaNet+ (This was the only thing I did in this tutorial. It fixed the usb driver and the fastboot can then communicate with my PC.)
http://forum.xda-developers.com/showthread.php?t=1350733
http://pdanet.co/a/
(Note: On top of Partition Table, APPSBL Image Header and APPSBL Image in step 4, I also selected the TWRP image file as my RECOVERY image. Not sure if this make a difference. )
(Note 2: I think you can also get the LG drivers here.)
3) Restart, hold down power + home to boot to the fastboot. Or in ADB type adb reboot bootloader.
4) Open ADB (while phone is still in fastboot mode) and type fastboot flash recovery twrp.img (after downloading the TWRP image, renaming it and moving it to my ADB root folder. I am using TWRP 2.8.0.1 here.)
5) Type fastboot reboot
6) After the phone restarts, type adb reboot recovery. TWRP runs for me. Power+Home+Volume Down (3 button combo) also works now. (Previously this would reset the phone.)
Hey Man, im glad it worked. I could use your help.
I bricked my phone and need the restore file, Do you think you could make a backup from TWRP and upload it?
I would be super grateful.
Thank you.
Here is a zip with CM11, twrp 3.0.2.0 and Gapps for CM11.
Its the best rom I found.
https://www.dropbox.com/s/qt7z1cxq92nhpz5/LgP500CM11V4.4.4.zip?dl=0
Hi. What is your "brick" like? Does your TWRP still run? If yes you can just copy a custom OS into your Microsd card and install it from your Microsd.
You can also use ADB push to move files from your PC to the phone.
http://www.androidauthority.com/android-customization-transfer-files-adb-push-adb-pull-601015/
Sent from my MT2L03 using XDA-Developers mobile app
If you TWRP doesn't run, you need to install that first. Do steps 3 and 4 in the above post to boot into bootloader and install TWRP.
3) Restart, hold down power + home to boot to the fastboot. Or in ADB type adb reboot bootloader.
4) Open ADB (while phone is still in fastboot mode) and type fastboot flash recovery twrp.img (after downloading the TWRP image, renaming it and moving it to my ADB root folder. I am using TWRP 2.8.0.1 here.)
Hi,'
I think I disabled google app on my nexus 5 (stock android) and since then my phone is stuck in boot loop. (My phone does not go past logo of marshmallow rolls or message saying starting apps 10 of 10). I have very important data that is not yet backed up and I need them to be recovered.
From various threads, I did following in recovery mode
1. Wipe cache option under recovery menu - as it was mentioned, that it would not delete any user data on my sdcard. (No help, still stuck with boot loop)
2. In recovery mode - there was an option to mount phone memory and I did that. My phone shows a message at the bottom of the screen that it is successfully mounted. But I am not familiar how to proceed further or to recover data from my phone.
My phone is running stock android and I think I have not disabled USB debugging. I am not familiar about ADB, but can follow your guidelines and execute them. When I connect my phone to windows laptop, I see my laptop trying to install the MTP device driver, but fails saying unable to find the driver.
I need to recover my data and Any help is greatly appreciated.
Is your bootloader unlocked? I'm guessing not.
Sent from my Nexus 5X using XDA Free mobile app
If the bootloader is unlocked, you could flash twrp and then mount the data partition from twrp. If the bootloader is not unlocked, you could try pulling the data from the phone using adb commands. Was debugging enabled in the rom?
I have not unlocked my boot loader. Is there a guide to use adb with stock android?
Only if you enabled debugging in developer options.
Today, I installed 15sec ADB installer and booted my device in to recovery mode by pressing power and volume keys.
Then under recovery menu there was an option called - Mount / System. I selected it by pressing power key and from ADB ran adb devices.
No devices was listed, when I ran ADB devices.
But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the pacakge you want to apply to the device with adb sideload filename".
Now, when I execute ADB devices in my PC cmd prompt, I see my device with its serial number.
then I tried to use ADB Pull /sdcard/ to recover files from PC command prompt. But I got a message - saying error closed.
Am I doing the right things? Can you guys guide me to recover files from this point.
My bootloader version is HHZ20h. Product - Hammerhead.
I noticed from below link a user has had luck with sideloading a launcher. Has anyone here tried it ? will it affect my data on phone?
https://code.google.com/p/android/issues/detail?id=64773#c22
Any guide to sideload google search app in recovery mode?
Have you considered side loading the OTA from Google? https://developers.google.com/android/nexus/ota Directions are on the site.
When you get to this point
(But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the package you want to apply to the device with adb sideload filename".), you send the ota zip. (Adb sideload <name of zip> ). You have to make sure the zip file is in the folder with adb files.
Sent from my Nexus 9 using Tapatalk
I tried to install OTA update and did the reboot. But it did not help.
Can anyone provide me a launcher that I can sideload in recovery mode? Reading from various threads, I think my phone is in this state because I disabled the google app, which is also the launcher.
Thank you
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
santi1993 said:
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
Click to expand...
Click to collapse
How to perform this flash without wiping my user data? Any guide for it?
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
audit13 said:
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
Click to expand...
Click to collapse
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
smartey said:
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
Click to expand...
Click to collapse
Boot ur phone in fastboot mode (From power off to vol down + power), then connect it to the pc and install latest_google_drivers for nexus devices, ull need to manually install them, after that ur fastboot will recognize ur device.
From that type fastboot devices, if u see ur device connected u simply need to get into the commands that the other user gave to you, i u are lucky ur device will boot.
if u had unlocked bootloader the thing was easy as installing twrp 3.0.2.0 and backup all ur data via MTP
Introduction
This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.
Known Bugs
- Screen may flash on the password-input UI. Anything else is fine though.
This TWRP has been tested with official ROM and my LineageOS 17 port (https://forum.xda-developers.com/android/development/unofficial-lineageos-17-0-umidigi-f1-t3997827) and it works fine.
This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.
Why Bother
Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.
Instructions
1. Unlock bootloader
2. Enable ADB debugging in system
3. Execute "adb reboot bootloader" while having your phone connected to PC
4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"
5. Reboot phone while holding Volume Up + Power buttons
Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.
Downlaods & Sources
20191103: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191103-twrp
- Fixed issues with Magisk and OpenGAPPS
20191102: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191102-twrp
Device Tree: https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0
Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery
Updated to 20191103
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
mrmazak said:
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
Click to expand...
Click to collapse
Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
mrmazak said:
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
Click to expand...
Click to collapse
Cause i test it without changes , it reboot to system
I think because they have different kernels
I am unable to install twrp.
When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...
Am I doing something wrong?
no fastboot response
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
tarvoke said:
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
Click to expand...
Click to collapse
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Try installing:
- https://androidmtk.com/download-15-seconds-adb-installer
- https://androidmtk.com/download-mtk-usb-all-drivers
- https://www.androidweblog.com/download-mediatek-usb-vcom-drivers/
Start the process from device on using adb commands to always allow access to the pc. I mean:
Code:
adb devices
and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then
Code:
adb reboot bootloader
while on fastboot follow with
Code:
fastboot devices
SubwayChamp said:
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Click to expand...
Click to collapse
thanks!
adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.
this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.
(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)
like I said, pilot error lol. but thank you again for the reply!
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
opticyclic said:
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
Click to expand...
Click to collapse
While in fastboot the first you should do is see if device is detected by pc with
Code:
fastboot devices
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
If your device is detected then you can flash the recovery as you were trying to do it with
Code:
fastboot flash recovery recovery.img
and then you can reboot directly to it without need to reboot to system previously and this will prevent TWRP from being overwritten, with
Code:
fastboot boot recovery.img
hmm, so when I checked the udev rules, it already had one for MTK/mediatek - and the USB vendor is '08ed' in fastboot as well as in regular adb, so it wasn't a problem with udev/plugdev.
which I guess may mean the lunix generic android drivers for fastboot might be... "lacking" - I'll have to scrounge up a win7 laptop and try the recommended windows drivers.
SubwayChamp said:
...
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
...
Click to expand...
Click to collapse
I don't think it was anything to do with the path as it output the file transfer size.
I think it was a combination of the following:
I wasn't pressing the right combinations of buttons after flashing.
i.e. holding VOL UP and pressing POWER on the screen saying "Your device has been unlocked and can't be trusted".
Rebooting might (?) have been reverting the recovery.
I was originally trying this on the firmware that was shipped 2019012414 but after flashing 2019090418 with SPFlashTool I had more success.
I also able to reboot to recovery directly after flashing with fastboot with the following:
Code:
fastboot oem reboot-recovery
Whichever was the key I can now reboot to recovery from adb too.
:good:
Your twrp eliminates fingerprint authentication.
I discovered something interesting, your twrp only works on my device, no other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
LyrielAlk said:
No other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
Click to expand...
Click to collapse
Try to clean flash last vendor build with spflash tool. First boot need stock recovery.
You don't need custom recovery to achieve root.
Maybe give a try to SNwriter (I never needed it though and can't help here).
Both of those twrp are not sticking. I have flashed with spoken flash tool v5 1944 win and I fastboot cmd with the same results.
Thanks
Gracias for this master ?
good
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
good idea
Hi all! Now we can root our Sunny 2 phones!
I'd make a TWRP port for this device (adb enabled) so we can just sideload the Magisk installer.
History:
After some time having a Wiko Sunny 2 phone, I'd search a lot and didn't find any method for rooting this little thing.
Then I had the idea to mod the stock recovery to allow test keys and then flash anything, tried to do that and didn't work.
Another idea came to my mind: port TWRP from another phone with same chipset. Started my search for a SPD7731c device with working TWRP and after some time found some guy who made a TWRP port for his "Selecline S6S4IN3G" device and as it had the same chipset it worked. Just gathered the recovery.img from the stock rom (thanks Wiko for giving it on they web page) and unpacked it with carliv image kitchen, replaced the stock ramdisk with TWRP's one and just modded some things inside it (default.prop and the init.rc files). As the vold.fstab is the same, didn't need to modify it.
After some testing, the only problem remaining is that the touch doesn't work well (it receives touch input all the time, even if not touched) but it's enough to get our Sunny2's rooted via ADB and magisk's zip.
REQUIREMENTS:
A PC (or another phone with OTG support, if you use a phone then you'll also need an adb binary compiled for ARM)
ADB, Fastboot and drivers: https://drive.google.com/open?id=1N38jqQqX87dEKsBIgDb_9MC-k43YUi85
TWRP image: https://drive.google.com/open?id=1DZhL6RckvzQyxGCq2Yy64Cqnpnnm1Ofp
Stock recovery image (in case something goes wrong you can revert to this): https://drive.google.com/open?id=1spaFc1sqqjFdwzt9cYDfSO_KVh1aYuh5
Magisk ZIP (can be latest or this zip): https://drive.google.com/open?id=1-OPU1JycSr8nVyAGfdkhdajn8Uap_0dl
ROOT PROCESS:
1. While on Android, go to Settings>About this device and toch 7 times Build number (this will enable Developer Options)
2. Now go back to Settings and then Developer options>Enable OEM unlock and USB debugging.
3. Connect the device to the PC and install the correct driver (for doing this just open Device Manager and force the install of Android Composite ADB Interface on your unrecognized device (should be called SUNNY2)).
4. Open a CMD/Terminal and type this:
Code:
adb reboot-bootloader
5. Now type
Code:
fastboot flash recovery path/to/twrp-suny2.img
and after that just
Code:
fastboot reboot
.
6. Now the phone will start, just type in CMD/Terminal
Code:
adb reboot recovery
and you will boot into TWRP.
7. Okay, this TWRP has a buggy touch so just use ADB to install the magisk zip:
Code:
adb shell twrp sideload
, then
Code:
adb sideload path/to/magisk.zip
and finally
Code:
adb reboot
.
8. Nice, now Magisk should be installed. Now with root access, happy modding!
Some things to note:
1) In this guide I did everything via ADB, never booted to recovery or fastboot using button combinations. Why? Simple, on my device I didn't find the correct combinations.
2) You can use TWRP also for factory resetting or installing anything, but via ADB only (as the touch doesn't work properly).
3) If you need any help with this device just PM me!
I hope this guide will be useful for anyone.
CREDITS:
This guy for his work on porting TWRP to his device
Magisk team for his work on making root as simple as flashing a ZIP!
AndroidMTK website for hosting the ADB installer which
I just mirrored!
Stuck in boot loop
Hi ! Thanks for the HowTo !
But...
I followed the exact same procedure (except I had to fastboot oem unlock before flashing the twrp image, in addition to unlocking it in dev mode).
After flashing, the device was stuck in a boot loop : "orange state your device has been unlocked and can't be trusted / your device will boot in 5 seconds". Tried all manners of key combos to reboot in recovery (Vol Up + power is supposed to be the right combo) but to no avail.
Fortunately Wiko provides an "upgrade" tool that allows you to factory reset the device (support dot wikomobile dot com /maj/Sunny2Plus_V24.zip, window$ only) but no luck installing twrp.
Any idea why ? Thanks in advance
tofleplof said:
Hi ! Thanks for the HowTo !
But...
I followed the exact same procedure (except I had to fastboot oem unlock before flashing the twrp image, in addition to unlocking it in dev mode).
After flashing, the device was stuck in a boot loop : "orange state your device has been unlocked and can't be trusted / your device will boot in 5 seconds". Tried all manners of key combos to reboot in recovery (Vol Up + power is supposed to be the right combo) but to no avail.
Fortunately Wiko provides an "upgrade" tool that allows you to factory reset the device (support dot wikomobile dot com /maj/Sunny2Plus_V24.zip, window$ only) but no luck installing twrp.
Any idea why ? Thanks in advance
Click to expand...
Click to collapse
Hmm this device is pretty strange, his key combinations never worked for me (because of that I'd need to reboot into system a few times, instead of booting to fastboot with keys).
You can try this:
After flashing stock rom and allowing oem unlock on settings, reboot directly to fastboot. Then use "fastboot boot recovery.img" and tell me what it says. If it says something about bad boot image, it's normal (that happens in my device even if try to load stock boot.img).
Also there's a tool called SPD Research Download Tool, which let's you flash the phone partitions one by one (manually selectable) from the path you want, while phone is in download mode (volume down and connect USB to PC). However, I don't know if that tool's license allows it's free redistribution, so I recommend research for it before downloading anything.
You can get the stock files by running the wiko upgrade tool, going to the folder it extracted his files and then looking for a file called rom.pac (then unpack it, there are guides here on XDA for doing so). You can even edit the boot splash image lol
Sorry for wasting your time
I'm so stupid ! It turns out my device is a different model, the Sunny 2 Plus.
Sorry, and thanks again
Does anyone know if a custom rom exists for the Wiko Sunny 2?
Klab98 said:
Does anyone know if a custom rom exists for the Wiko Sunny 2?
Click to expand...
Click to collapse
Nope, sold the device some days after writing this post so didn't even bother to port anything.
BTW it's a 4-core phone with 512MB RAM, so what would you expect to run there? I thing nothing higher than MM (KK would be nice if it was not so outdated nowadays)
Hi, i have got a problem with my wiko sunny 2 plus.
i flashed twrp via fastboot, it succeed. but after reboot the phone didnt start,
only shows orange state, didn´t connect to pc anymore with same cable. i mean i can hear the win7 sound of connecting device and right after connect sound appear then disconnect sound follows right after. so i cant detect the device with adb anymore. what to do, any idea? P.S. sp flashtool also cant detect device. greets
merci beaucoup j espere sa marche