LG L Fino MegathreadAll LG L Fino informationROM's, Root, Recoveries, etc.
General information:LG L Fino is a 2014 LG Smartphone with G-series characteristics such as the Volume and Power buttons on the back and general design. It caries a powerful 1.4Ghz quad core Qualcomm SnapDragon 200 [MSM8610]
8MP back camera with flash and a VGA front facing camera.
The device comes in two flavors:
[*]D290 - Single sim.
D295 - Dual sim.
Click to expand...
Click to collapse
Rooting:
Root access can be achieved on the LG L Fino using PurpleDrake.
Initially created for LG G Series devices, it seems to work quite well on devices running a fork of the same firmware such as our Fino or the LG L Bello. It's easy and only requires you to hit next.
Be sure to install SuperSU or Superuser from Google Play afterwards.
Click to expand...
Click to collapse
Unlocking the bootloader:
Unlocking the Bootloader of an android device is required in order to install custom firmware such as recoveries or ROMs. Fortunately unlocking the bootloader on the L Fino is easy as pie. All you have to do is download a file and type a bunch of commands in the terminal. Be careful not to make a typo or else you might HARD BRICK your device.
Instructions:
Root your device.
Download the required file for your device:
D290X
D295X
Place the aboot.bin file right in your SD card. Not in any folder
Using terminal emulator or ADB SHELL execute these commands in order:
Code:
su
dd if=/storage/external_SD/aboot.bin of=/dev/block/mmcblk0p6
Reboot your device.
Your bootloader is now unlocked!
Click to expand...
Click to collapse
Recoveries:
Currently there is only one STABLE recovery with no bugs what so ever. TWRP 3.0.0.0 ported by me and @proudlytm. Here is a link to it's thread containing downloads and installation instructions.
Click to expand...
Click to collapse
ROMS
Currently there is only ONE NON STOCK BASED custom ROM and numerous stock modifications.
CyanogenMod 12.1 by @christpp, me and @proudlytm - HERE
A bunch of stock based roms - HERE
More ROMS will most likely appear after CM 12.1 gets up and running propperly. For now we all have to wait. Stock based ROMS do not use custom kernels and as such do not have features like Overclocking.
Click to expand...
Click to collapse
Help I bricked my device!
A reflashing/unbrck guide is available - HERE. Please note that this only works if the device is a soft brick or if you want to return to stock. This will not unbrick your HARD BRICKED device.
Click to expand...
Click to collapse
Thanks to:
@proudlytm - Helping me develop for the device and risking his own device for testing
@christpp - Creating and developing the CM 12.1 port for L Fino.
Me - Squashing bugs, helping out wherever I can and porting TWRP 3.0.0.0.
If you feel that I have missed something or something needs to be added to the thread feel free to tell me and I'll do it.
Reserved
Hello, I'm looking for a way to get my d290g's original firmware back, but I can't flash it from the d295 firmware. It has the d290 bootloader and it's recognized as a d290g, but the firmware it's from the d295 version. can I get it by using a d290's TWRP backup?
Appreciate any help.
elpipeta said:
Hello, I'm looking for a way to get my d290g's original firmware back, but I can't flash it from the d295 firmware. It has the d290 bootloader and it's recognized as a d290g, but the firmware it's from the d295 version. can I get it by using a d290's TWRP backup?
Appreciate any help.
Click to expand...
Click to collapse
Just reflash it using flash tool. If the bootloader is stock it will work.
meganukebmp said:
Just reflash it using flash tool. If the bootloader is stock it will work.
Click to expand...
Click to collapse
Thanks for the reply, it's not the stock one, it's the unlocked bootloader d290x. If I extract the aboot from the kdz, can I flash it into the phone like the others? or I need edit it?
elpipeta said:
Thanks for the reply, it's not the stock one, it's the unlocked bootloader d290x. If I extract the aboot from the kdz, can I flash it into the phone like the others? or I need edit it?
Click to expand...
Click to collapse
What?!. Just reflash the whole rom. Nothing bad will happen.
meganukebmp said:
What?!. Just reflash the whole rom. Nothing bad will happen.
Click to expand...
Click to collapse
The problem is that it stops flashing at 2%, I'm pretty sure because the program is checking the aboot or maybe the build.prop or any other file that is saying that my d290g is a d295 instead
LG placed a new update for D290N, V10G (last one was V10E). I've flashed this KDZ through the LG Flash Tool 2014 with success. After messing with it, I haven't actually found out what's been "updated", probably some bugs and stuff.
So I wanted to root it and flash TWRP, but then I've found out that I somehow cannot root it. Attempted to root it with PurpleDrake method, failed, then tried the KingoRoot method, failed also. Seems like they messed around with that.
I'll try flashing the V10E sometime when the CM 12.1 gets less buggy and try to root it then (was successful the last time).
RenegadeX44 said:
LG placed a new update for D290N, V10G (last one was V10E). I've flashed this KDZ through the LG Flash Tool 2014 with success. After messing with it, I haven't actually found out what's been "updated", probably some bugs and stuff.
So I wanted to root it and flash TWRP, but then I've found out that I somehow cannot root it. Attempted to root it with PurpleDrake method, failed, then tried the KingoRoot method, failed also. Seems like they messed around with that.
I'll try flashing the V10E sometime when the CM 12.1 gets less buggy and try to root it then (was successful the last time).
Click to expand...
Click to collapse
Rooting DOES NOT work on XXG firmware.
Thanks
Yes it does, just use Kingo Root and replace the su app with Super Su. The only prob I saw is that Xposed doesnt work on the new update, but Stagefrigth and other exploits are fixed, prob some optimizations for the system aswell.
Hey guys, I have two questions. Is there a way to extend memory by creating partition with external memory card? And is there maybe jellybean rom for our device?
Thanks.
cyber808 said:
Hey guys, I have two questions. Is there a way to extend memory by creating partition with external memory card? And is there maybe jellybean rom for our device?
Thanks.
Click to expand...
Click to collapse
There will never be a Jellybean ROM for the device. Jellybean is outdated, slow and insecure.
Check tutorials online. There are many tutorials on how to expand the data partition.
cyber808 said:
Hey guys, I have two questions. Is there a way to extend memory by creating partition with external memory card? And is there maybe jellybean rom for our device?
Thanks.
Click to expand...
Click to collapse
Hi. Search the magic partition wizard. I have same problem and i've solved with magic partition wizard. But i can't explain how i do, cuz my english not good. Now i'm using 8GB ext sd card as internal application memory
This phone have overclock to 1.4 GHz ? ?
Sent from my Moto E using XDA-Developers mobile app
After many fails to root v10c with Purple Drake and many others, i have rooted it with LG Root Script v1.2
[URL="http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/[/URL]
I've done the root with PurpleDrake but with some tricks because PurpleDrake wasn't able to permaroot my LFino, just succeed with temproot.
If you can't permaroot your phone you can't run with su permissions in terminal emulator or using adb in normal phone session.
The second problem is that I can't mount the sdcard, tried many different options that were in forums but none results..
Here it's what I did:
1- Run the specific purpledrake script for your OS
2- When the script told you that has temproot your device just close the script without trying permaroot, but do not turn phone off
3- Open a terminal and go to the path where you have the 2 files (TWRP recovery.img and aboot.bin)
4- Push the files
adb push aboot.bin /temp
adb push recovery.img /temp
5- Run this commands
adb shell (a $ will appears after run the following comand)
/temp/fakesu (a # will appears it means you're running with SU rights)
dd if=/temp/recovery.img of=/dev/block/mmcblk0p17
dd if=/temp/hidden/aboot.bin of=/dev/block/mmcblk0p6
adb reboot recovery
now you've installed the TWRP Recovery and you can put roms on device, keep in mind if you boot the phone in normal mode after doing this there's a possibility of your TWRP recovery get's swapped by the OEM recovery (OTA updates??)).
if you pay attention to all the passes you'll notice that I wrote on the second dd command /temp/hidden/aboot.bin instead /temp/aboot.bin, that happens because when I list the files on my phone after push them I saw that the aboot.bin gets pushed to a folder called hidden inside /temp, check if in yours happens the same.
keep in mind I'm not responsible for this, this is just an help for those who can't get permaroot with script, a simple letter or space in the last commands can brick your phone.
In terminal emulator firstly I wrote "su
dd if=/storage/external_SD/aboot.bin", and then the entire text again. The phone is still working, restarting it will HARD BRICK it ?
Reloaded92 said:
After many fails to root v10c with Purple Drake and many others, i have rooted it with LG Root Script v1.2
[URL="http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/[/URL]
Click to expand...
Click to collapse
This worked for me on d290g with v10d-SCA-XXX firmware, thanks!
So,I've rooted my lg l fino with Purple Drake before few days,installed supersu; because I wanted to find alternative way to move all apps on sd card (I found out that rooting your phone will allow you to do this and because my android is kitkat,I have no control over moving all apps to sd).So,I've installed lucky patcher (app that needs root),tried to move some app to SD that I downloaded and guess what-it says: "Moving to SD card finished with an error (try again): pkg: /data/app/
#name of the app
failure
[INSTALL_FAILED_INSUFFICIENT_STORAGE]''
My storage is not a problem,on SD card I have almost 5 GB of free space. The app I tried to move had only 5 MB.This was just pure test,nothing more.After lucky patcher I downloaded some app called Link2SD,something like that.That app didn't work either,so I stopped downloading apps that maybe could help me. If I am missing something,I would be very happy if someone puts me in the right direction.On other forums people just say ''buy some expensive phone if you want so much internal memory". Instead of helping,they are judging people for not having money for expensive phone.Just to be straight,I don't need my phone for very large apps like games,I use Bluestacks for that. If someone has some tips,anything,I would be gratefull.Lg l fino is a solid phone,I have no need nor money to buy expensive phone.
Thanks to:
@proudlytm - Helping me develop for the device and risking his own device for testing
@christpp - Creating and developing the CM 12.1 port for L Fino.
Me - Squashing bugs, helping out wherever I can and porting TWRP 3.0.0.0.
If you feel that I have missed something or something needs to be added to the thread feel free to tell me and I'll do it. [/QUOTE]
Related
I know a couple people asked for a guide and I didn't see anything concise had been posted (Mods feel free to remove if it's a duplicate.). Things are still a bit fresh, but this should be a short list of steps to perform the upgrade of your Nexus 7 (2012) WiFi to Lollipop.
As with other guides, I make no expressed or implied warranties - you break it, it's on you.
This is how I was able to get Lollipop working on my own Nexus 7 (2012). I was coming from a rooted factory image of 4.4.4.4 which was the previous most-recent factory image released by Google for this device. I like my device as bone stock as possible and wanted to upgrade and keep it that way.
I assume the following:
You know how to use both adb and fastboot and have already configured your system to use these utilities.
You have already performed an oem unlock on your device.
That out of the way, on to the guide...
It goes without saying, but I'll call it out anyway... Take a backup of your current device setup. Most likely this is within your custom recovery or TiBu. If your not familiar with how to do so, consult the help pages for those apps.
Download & unpack the requisite files
LRX21P factory image from Google.
CF-Auto-Root from Chainfire.
OPTIONAL Only if you're upgrading from a version of Android prior to the JWR66Y Android 4.3 factory image, download the KRT16S factory image from Google.
Start by rebooting your device to the bootloader.
Code:
$ adb reboot bootloader
OPTIONAL If you have ignored my assumption and haven't already done so, now would be the time to oem unlock the bootloader
Code:
$ fastboot oem unlock
Run the following commands to prep your device to install Android L. NOTE:This will erase your device
Code:
$ fastboot erase cache
$ fastboot erase recovery
$ fastboot erase system
$ fastboot erase userdata
OPTIONAL If you are upgrading from a version of Android prior to the 4.23 bootloader release which was originally released along with the Android 4.3 JWR66Y factory image, then you will need to upgrade the bootloader also. The bootloader included in the Android L factory image is not correct and will fail to install. Your best bet is to download the KRT16S factory image from Google and use the bootloader-grouper-4.23.img file from that factory image. Be sure whatever version of the bootloader-grouper-4.23.img file you use has the correct md5sum.
Code:
$ md5sum nakasi-krt16s/bootloader-grouper-4.23.img
df53028033c9eccf4fe5ba7bc198ce24 nakasi-krt16s/bootloader-grouper-4.23.img
$ fastboot erase boot
$ fastboot flash bootloader nakasi-krt16s/bootloader-grouper-4.23.img
Now, install the actual Android L system
Code:
$ fastboot -w update image-nakasi-lrx21p.zip
Your device will automatically reboot at this point and when it does, you will be running Android L (5.0) 100% stock and WITHOUT ROOT. This boot usually takes a very long time (~5-10 minutes) as it's performing the initial setup of the OS. When the device is back up fully, you will have to go through the setup steps as if it were a new device. Once that's done, proceed to the next step.
Now that Android L is freshly-installed, not only have you lost root, but you've also lost the Developer Options menu and the USB Debugging option contained therein. So, before we proceed, we need to enable Developer options & USB Debugging in the settings menu so that adb & fastboot will work recognize the device. Again, if you have any experience with running adb & fastboot, you will know how to do this. The process is exactly the same as with previous versions, so there should not be any surprises here.
Go to the Settings menu and scroll down to and tap on "About Tablet"
On the next screen tap on the "Build Number" field seven (7) times and you'll be presented with a message of "You're now a Developer!"
Hit the back "triangle" and go into the Developer Options menu and turn on USB Debugging.
Just be sure to accept the key on your device when you connect it to your computer.
Now, we can use adb to reboot the device so we can apply the CF-Auto-Root patches and SuperSU from the bootloader
Code:
$ adb reboot bootloader
Once in the bootloader you will need to apply the cf-auto-root. Use the following command.
Code:
$ fastboot boot image/CF-Auto-Root-grouper-nakasi-nexus7.img
NOTE: Windows users have reported that the file is in the same directory so just double-check the path to the file.
This will boot the device onto a custom kernel, install the kernel fix to allow root and also install the latest beta version of SuperSU (2.20) for Android L.
You will now end up with a device running Android L with root. I did not mention at any point about installing a custom recovery. These steps will remove a custom recovery, so if you want to install that, you will need to consult the instructions for your custom recovery of choice. I usually use the CM instructions for installing CWM as they're easy to find. This is not strictly necessary for root. Similarly, my main purpose for rooting was to use Titanium Backup. The current production version of TiBu doesn't support Android L, but the TiBu team has released a test version for L via their twitter feed. Here's a direct link or you can go to their twitter feed for more info...
Questions? Comments? Did I miss something? Let me know.
EDIT: Seems that the performance has really gone down over the past few days. Not really sure what the cause of the performance degradation is but it's quite severe. I noticed last night after having left it plugged in all night that the device wouldn't even turn on or took an inordinately long amount of time (many minutes) to wake from sleep. As it stands I attempted to play a game that's slightly intensive and after a short period of time the device got really hot and started really having performance issues to the point where it rebooted on it's own. Further, I noticed a number of things aren't working that probably should... Bluetooth & "Battery Saver" mode are the first two that come to mind.
Anyone else experiencing similar issues?
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
petenatas said:
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
Click to expand...
Click to collapse
Would you mind pointing me to it?
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
jasoraso said:
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
Click to expand...
Click to collapse
added
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
Click to expand...
Click to collapse
Not sure about on Windows, but on Linux when I unzipped the root zip file, there was a directory layout as such...
Code:
cf-auto-root/
cf-auto-root/image/
cf-auto-root/image/CF-Auto-Root-grouper-nakasi-nexus7.img
cf-auto-root/root-linux.sh
cf-auto-root/root-mac.sh
cf-auto-root/root-windows.bat
cf-auto-root/tools/
cf-auto-root/tools/AdbWinApi.dll
cf-auto-root/tools/AdbWinUsbApi.dll
cf-auto-root/tools/fastboot-linux
cf-auto-root/tools/fastboot-mac
cf-auto-root/tools/fastboot-windows.exe
In any case, you were able to find it. Should be pretty obvious which file I'm referring to...
apocope said:
Would you mind pointing me to it?
Click to expand...
Click to collapse
Added a link in the paragraph at the end.
Yes!
I needed my root. (The stock kernel underclocks like crazy, making the tablet nearly unusable.)
Thanks for the guide brother. You are awesome
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
A very very very very usefull guide!!!!
All working fine!!!!
Thanks!!!!!!!
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
OMG corrupted bootloader AGAIN.
GOOGLE what's wrong with you???
Thanks for the guide! Works fantastically on my aging N7.
Short rundown video by me on YouTube here:
Does it wipe internal storage?
abobobilly said:
Thanks for the guide brother. You are awesome
Click to expand...
Click to collapse
:good:
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
Click to expand...
Click to collapse
:good::good:
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
Click to expand...
Click to collapse
I made a mistake on the version number that I listed in my instructions. When I did my N7, I had originally just tried flashing SuperSU via the standard zip file method. The most recent version of SuperSU available in the SuperSU XDA thread is/was 2.19, so I just assumed that it was the same version being used in the CF-Auto-Root. But as you correctly point out, the process installs 2.20 not 2.19. I updated the version number in the guide. Thanks.
ToucherCD said:
Does it wipe internal storage?
Click to expand...
Click to collapse
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
Added a link to the KRT16S factory image which contains a proper bootloader-grouper-4.23.img file that you could use.
jetsaredim said:
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
Click to expand...
Click to collapse
Hi. Good job on the guide. Very detailed. That's good.
Thanks for the tip with booting CFautoroot img. I was wandering why superSU 2.16 was not working and was looking for modified karnel all morning.
BTW. I know it's not recommended, even my Tapatalk signature says it
but I didn't wipe user data while upgrading. See my post here with details.
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Can I just ask about the bootloader?
I'm seeing alot of users reporting there's an issue within the bootloader that is included on the LRX21P image for Grouper, I performed a clean flash yesterday and flashed the leaked image for grouper, I haven't had any single issue flashing all of the images, even bootloader that came from the lollipop image doesn't seem to cause an issue.
Btw, everyone's suggesting to flash the bootloader from JB & KK on this lollipop build, is there any impact on the performance of why's that recommended to flash the old bootloader?
And I didn't really expect this but lollipop made it worst to run on this device! Even if it's a 2012 device, why's that it can't handle lollipop smoothly? I can't even drop the status bar down at a rate of 60fps as promised by Google, can't even swipe the screen smoothly and it's freezing as hell! It feels like something's wrong with this build.
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
JovieBrett said:
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
Click to expand...
Click to collapse
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Natakranta said:
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Click to expand...
Click to collapse
Yup, I all agree of what have you said. I tried ext4, f2fs etc etc, none of them improves the N7's performance or at least the stock one has the best performance and stability for me.
Heard alot of users blaiming about the tegra chip for this, they said that tegra chips are getting worst every year and if all of these are true, I have doubts about Nexus 9's performance since even the one of the famous 'Android Police' senior editors have found that there are unusual freezes and glitches from the device itself, idk if that happened on the latest build for N9.
The 2011 device I'm currently comparing to is an Xperia Mini, snapdragon chip with 1Ghz single core, 512MB of RAM, I'll look away from tegra based devices...
Btw, do you have an N7 2013? I'm planning to buy one this December to replace my 2011 device. Can I trust this 2013 model with snapdragon processor? I always trust these snapdragon based devices.
This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Dude, quit being so amazing. It's getting ridiculous.
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Yes!!! Glad to see you!
@WugFresh
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.
I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.
bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.
Can confirm a working flash. Everything looks great! Thanks for all the hard work
no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Edit
Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.
dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks
Yes it seems Google decided to remove the backup confirmation dialog from TcSettings
So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2
Hi all ,
This problem is facing very one how install kingroot and made his/her device rooted with kingroot , the root is done will , but after Root we can receive ota updates but when we download and install the ota update a problem found :
Unexpected error : install-recovary.sh status 7
I have trying to make full un-root by kingroot , or superus and nothing fixed until now !!!
Some people told me that you must install stock-rom !?
But why stock-rom if there is better and easy solution ?
I need your help developers I guess this problem not hard one for you ^_^ .
So who is the hero that's will save the day
Thanks.
As I've told you, you need the stock install-recovery.sh for your device (LUZ17x or LUZ59x?)
Everything else it way too complicated! (You will need an unlocked Bootloader, modded stock-recovery or TWRP, patched updater-script, etc...)
But it seems, nobody here is willing to pull the file (or even better a stock system.img) from their device.
I forgot to pull a system.img before rooting, so I can't help.
Seems, that there is unfortunately no real active community in Thailand or Turkey (apart from the language barrier), when it comes to these devices.
At least until now.
update
theeteempire said:
Hi all ,
This problem is facing very one how install kingroot and made his/her device rooted with kingroot , the root is done will , but after Root we can receive ota updates but when we download and install the ota update a problem found :
Unexpected error : install-recovary.sh status 7
I have trying to make full un-root by kingroot , or superus and nothing fixed until now !!!
Some people told me that you must install stock-rom !?
But why stock-rom if there is better and easy solution ?
I need your help developers I guess this problem not hard one for you ^_^ .
So who is the hero that's will save the day
Thanks.
Click to expand...
Click to collapse
if you want update then why u rooted your device? this is the basic thing you have to keep in mind before root you device that you cant install OTA if your device is rooted or any thing is changed into the system(i.e. cant be done without root).
The people telling you about installing stock rom, is the best and last solution according to me... search the net you will surely find the stock rom and its procedure to install as well...
Best of luck with searching and flashing the stock rom:good:
sagar27691 said:
if you want update then why u rooted your device? this is the basic thing you have to keep in mind before root you device that you cant install OTA if your device is rooted or any thing is changed into the system(i.e. cant be done without root).
The people telling you about installing stock rom, is the best and last solution according to me... search the net you will surely find the stock rom and its procedure to install as well...
Best of luck with searching and flashing the stock rom:good:
Click to expand...
Click to collapse
I think that un-root will solve this problem with out need to make stock-rom
vel_tins said:
As I've told you, you need the stock install-recovery.sh for your device (LUZ17x or LUZ59x?)
Everything else it way too complicated! (You will need an unlocked Bootloader, modded stock-recovery or TWRP, patched updater-script, etc...)
But it seems, nobody here is willing to pull the file (or even better a stock system.img) from their device.
I forgot to pull a system.img before rooting, so I can't help.
Seems, that there is unfortunately no real active community in Thailand or Turkey (apart from the language barrier), when it comes to these devices.
At least until now.
Click to expand...
Click to collapse
I need stock " install-recovary.sh for LUZ17E ". But no one help me to do that , I think there is no real developers here in second generation
theeteempire said:
I think that un-root will solve this problem with out need to make stock-rom
Click to expand...
Click to collapse
If you don't have a backup of that file (either made by yourself or the rooting software you have used), then 'unrooting' cannot help. That file is gone.
I went through @Sadronis's LUZ17E rom dump, extracted install-recovery.sh and attached it for you. But next time, please remember to backup the original file before rooting since especially for non-Nexus devices, stock ROMs (and thus files inside them) are not easy to find.
pawitp said:
If you don't have a backup of that file (either made by yourself or the rooting software you have used), then 'unrooting' cannot help. That file is gone.
I went through @Sadronis's LUZ17E rom dump, extracted install-recovery.sh and attached it for you. But next time, please remember to backup the original file before rooting since especially for non-Nexus devices, stock ROMs (and thus files inside them) are not easy to find.
Click to expand...
Click to collapse
Thank you man.
I can't replace the file or. Overwrite it , I have the root for my device but I can do nothing do you know why ?
theeteempire said:
Thank you man.
I can do nothing do you know why ?
Click to expand...
Click to collapse
Yes, you have to mount /system as "rw", for example:
Code:
adb remount
vel_tins said:
Yes, you have to mount /system as "rw", for example:
Code:
adb remount
Click to expand...
Click to collapse
Thank youuuuuuuuuu you help me a lot man
It's all done good .
I wanna ask you the stok rom that shared in this forum , can it be updated normally or not ?
First of all king root did not support on mine tablet but after a week ,i install 4.6 version of kingroot and it work but after a day when i want to update mine tablet galaxy 4 10.1 with ota ,it seem that the operating system of your device has been ........try to connect pc and etc.please help me ,i try lots of things like wipe cage, re factory etc others but now please help me without using pc.
Hi there,
I think we should make a simple thread to sum up everything we know about root, since the main talking thread is long, here are the main informations:
Xperia Z5:
- No locked bootloader root yet
- AndroPlusKernel: http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
- TWRP here http://forum.xda-developers.com/xperia-z5/development/twrp-2-8-7-0-z5-rootable-kernel-t3240032
- CWM booting but not usable: http://forum.xda-developers.com/xperia-z5/development/recovery-clockworkmod-recovery-sony-t3249782
- Unlocked BL dirty rooting available and working as intended: http://forum.xda-developers.com/xperia-z5/development/dirty-root-solution-unlocked-bl-t3233274
- Dumped original firmware: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
- Xposed works but you need to let it bootloop a few times
Xperia Z5 Compact:
- No locked bootloader root yet
- Zombie Kernel testing release here: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
- Unlock bootloader root available (http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524)
- Prerooted firmware available for unlocked BL: http://forum.xda-developers.com/z5-...-rooted-32-0-5-32-firmware-one-click-t3231520
- Xposed doesn't work with prerooted firmware
Currently we need to:
- Compile Zombie Kernel for Z5
- Improve TWRP support
- Create prerooted-firmware
- Most obviously and most hardly, find exploit for Locked BL root
Ok I'm not an Xperia pro, just got my first one few days ago, but still a android and linux geek, so if there is mistakes in my post, or update I haven't seen, notify me
Knux14 said:
- Maybe dump the original firmware ?
Click to expand...
Click to collapse
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
Need root for Z5, thx for efforts.
Uclydde said:
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
Click to expand...
Click to collapse
Updated
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
You are the man, you saved me
my phone works now with root access
nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Huge thanks, But I can't get it working...
I open BL, I fastboot flashed the kernel, then I fastboot booted on the recovery (Which doesn't show a black screen as expected but a real non-fully-working twrp for me) and I tried to install Supersu but I write an error then...
EDIT: Kinda glitchy to do, but works.
If anyone has Xposed working, please make a tutorial
Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.
Most android devices have either already unlocked BL or you have to. For example, Nexus 5 needed to unlock the BL, as well as the OnePlus One, but those devices don't contain DRM so you don't loose anything when unlocking
nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did not had to :/
You guys work fast!
Unsure whether to root myself yet,
Kind of wouldn't mind being able to connect a ps3 pad instead of
Ps4 using the sixaxis app
I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.
Falenone said:
I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.
Click to expand...
Click to collapse
There is nothing clear enough for beginner yet. Sooner or later there will be a TWRP fully working and it will be easy.
Try the dirty method, but don't do things that you are not sure that will work. Ask us if needed
I don't want to lose features because of unlocked bootloader. I guess I'm going to survive without root til there's TWRP and pretty much flash n go root
You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...
Knux14 said:
You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...
Click to expand...
Click to collapse
Ages means..? I know that the Z1 is not so fresh anymore but we were able to root 4.2/4.4.4/5.1 without losing anything with locked BL. (I know nothing except following tutorials)
Sent from my E6653
Yes because there were security holes in android. For now we havent found anything yet in this version
harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did boot into TWRP (it was like tablet mode) mounted all partitions to be sure, flashed SuperSU from external sd. It is working. Thank you all
ChrissehB said:
Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.
Click to expand...
Click to collapse
Google "Verified Boot Android" .. there is almost 100% probability that locked bootloader root will never be achieved, because of this security feature. Verified Boot was introduced in KitKat, but almost nobody used it in so strict mode implementation... Until now, no single firmware using Verified Boot was ever rooted without either custom kernel (must unlock bootloader) or leaked engineering bootloader (try ask Sony engineers for it).
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite with the Chinese 6.0 Firmware
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Twrp needed?
slimbullet said:
Twrp needed?
Click to expand...
Click to collapse
Yes, it's needed, and thanks for pointing this out.
How are flash in Recovery Mode? He gives 3 options: Reboot - Download new Version and Recovery - Shutdown!?
You have to flash TWRP by fastboot adb before.
TWRP is needed for flashing the zip files
daviddosa said:
Yes, it's needed, and thanks for pointing this out.
Click to expand...
Click to collapse
I did all of those steps and now i have blackscreen and my phone wont turn on....
I have twrt,unlockedbloader,beta 6.0,debugging etc and it dont work...
and the second boot animation missing
Surdyn said:
I did all of those steps and now i have blackscreen and my phone wont turn on....
I have twrt,unlockedbloader,beta 6.0,debugging etc and it dont work...
and the second boot animation missing
Click to expand...
Click to collapse
the same problem here
daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.[/QUDo wee
Do wee need an sd card or it can be done witch the main storage?
Click to expand...
Click to collapse
not work stop Screen Takeoff and not star and restart
---------- Post added at 03:05 AM ---------- Previous post was at 02:52 AM ----------
blackscreen and my phone restart how fixed
daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Click to expand...
Click to collapse
Hi this method work only with the chinese version (B535) on european version (B524) i got a bootloop ...
This happen to me
xander33 said:
Hi this method work only with the chinese version (B535) on european version (B524) i got a bootloop ...
This happen to me
Click to expand...
Click to collapse
so how do we root B524 now?
omid.quist said:
so how do we root B524 now?
Click to expand...
Click to collapse
Follow the tutorial on generale section provided by sokkoban the thead it s called [TUTORIAL] ...
how to recover after the boot loop ?? i tried this on the EU marshmallow and now im stuck !!
daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite with the Chinese 6.0 Firmware
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Click to expand...
Click to collapse
Hi Daviddosa you have installed chinese beta android 6 fw? On that firmware is camera with special light effects.. Can you make backup of that camera, and get it here, or copy complete camera sw? Thanks a lot!
Here is HwCamera.apk on Chinese version of MM 6.0
sokkoban said:
Here is HwCamera.apk on Chinese version of MM 6.0
Click to expand...
Click to collapse
thx. just put it in system apps? and replace the old one? because update wont work
sokkoban said:
Here is HwCamera.apk on Chinese version of MM 6.0
Click to expand...
Click to collapse
Thanks.. sadly it is not working. Just wondering why on chinese ROMs there is working light painting, but on EU ROMS no.
danvo01 said:
Thanks.. sadly it is not working. Just wondering why on chinese ROMs there is working light painting, but on EU ROMS no.
Click to expand...
Click to collapse
I'm wonderin too. But this is not only difference in Chinese ROM. On B524 not feature like Touch Plus, Smart Care, Mobile data traffic counter, HiCloud and many others
So my opinion is Chinese firmware is much better that European. For that I change my ALE-L21 to ALE-UL00
sokkoban said:
I'm wonderin too. But this is not only difference in Chinese ROM. On B524 not feature like Touch Plus, Smart Care, Mobile data traffic counter, HiCloud and many others
So my opinion is Chinese firmware is much better that European. For that I change my ALE-L21 to ALE-UL00
Click to expand...
Click to collapse
so.. do you think it is better to flash back chinese beta v 311 (?) instead of 524? I looked for more stable bluetooth connection, and now i see differences...
I never use Bluetooth. But Chinese version of 6.0 is B535