Related
So I bought a Chinese OnePlus One, and it came pre-installed with CM 11 version 11.0-XNPH33r.
Connected to wifi, and got the system update for 11.0-XNPH38r Incremental, so I click download and install.
It reboots phone, then it loads ColorOS recovery looking screen with Chinese written on it and a green loading bar, then The CM splash icons comes back and loads. (alien looking guy with an arrow circling around his head)
After all that, I go to check the version and I'm still stuck at 11.0-XNPH33r!
I tried manually doing it from ColorOS recovery with 11.0-XNPH38r Incremental zip file, it installs about 3/4 of the way and then fails.
My Kernel Version is : 3.4.0-cyanogenmod-g0ad30e5
My ColorOS Recovery Version is : 1.2 (Rooted)
I've been looking around the forums, and I see people manually updating using TWRP which I don't have.
Can someone please help me, and if you have a solution can you please give me a step by step direction since I'm new to flashing/rooting and this phone.
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Thanks man, I'll try that out.
timmaaa said:
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Click to expand...
Click to collapse
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
TheOneinNeed said:
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
Click to expand...
Click to collapse
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
timmaaa said:
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks man. I actually tried the flashing of 44s on the guide you sent me and it worked. Sorry for my last reply. You've been a great help and my phone is up to date.
Two last question if you don't mind. When the new update comes, can I install through Settings> About Phones> System Updates
or do I have to do something similar to the flashing I just did
after flashing my custom recovery is gone (TWRP) and the Cyanogen Mod Recovery took its place. Should I leave it like that or get TWRP and if TWRP is the answer, do I use the same method I did installing the custom recovery?
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
timmaaa said:
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
Click to expand...
Click to collapse
Thank you for your time and effort to help.
I appreciate it a lot. Thanks again!
Hallo there,
at first sorry for the nearly 10th post about this topic, but as you can see I'm in a different position than the most of you. I'm on Arch Linux here and I don't rly want to root my phone with a windows box.
I got adb and fastboot installed, but I can't find a general guide how to flash recovery and root with them, because there are always these click-click-shiny-shiny gui .exes for windows, which take some tasks.
I did root my Droid 3, but this was years ago, and I did never get into this stuff so deep it would help me now. I am a lil exhausted from the day, and don't rly want to puzzle my way through the google search results, which as described above lead to a .exe with a gui at some point.
Anyone here, who knows the basics and is willing to give me a hand here?
As I said I'm a Linux aka a terminal user so you don't need to be soft on this, I just need it compact but complete.
Thanks in advance
p.s. What I think will be relevant at some point, based on the search results so far:
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/showpost.php?p=66546853&postcount=53
Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.
Mother_Teresa said:
Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.
Click to expand...
Click to collapse
aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
And there is another question. The part after
NOW LETS GET XPOSED AND LUCKY PATCHER WORKING
Click to expand...
Click to collapse
is not necessary if I use a different launcher than EMUI, or is it?
EDIT: A VM is not an option, would be the same for me than using a physical windows box.
quote: aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
sounds good to me, so now it is twrp and not cwm?
And there is another question. The part after "NOW LETS GET XPOSED AND LUCKY PATCHER WORKING" is not necessary if I use a different launcher than EMUI, or is it?
it allows customizing advanced settings and is implemented in boot. not necessary
EDIT: A VM is not an option, would be the same for me than using a physical windows box.
if you have recovery etc just flash supersu for root
Okay, good was just checking, if it's the way I puzzled it together. Don't want to wipe me phone.
Mother_Teresa said:
sounds good to me, so now it is twrp and not cwm?
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
What's the difference between twrp and cwm?
Mother_Teresa said:
it allows customizing advanced settings and is implemented in boot. not necessary
Click to expand...
Click to collapse
Okay, nice.
Mother_Teresa said:
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
Just like in the guide i guess. Thx.
This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?
pepper-jk said:
This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?
Click to expand...
Click to collapse
Yay well done and also on posting the solution. I reread what I typed and couldn't make sense to why I mentioned cwm and twrp (same stuff, diff developers or so) so maybe I mixed up bits of another topic
I had a Xperia L, its pretty old now but i wanted to do something with it like trying out Android Nougat feel on Xperia L
So i googled much (I don't have much knowledge in phones and flashing), I tried installing this https://forum.xda-developers.com/xperia-l/orig-development/rom-cyanogenmod-14-alpha-1-t3469162
Lineage OS on Xperia L(taoshan) by corphish
I read few of the blog posts about flashing a custom rom on Xperia L, and I got to know that the steps to install a custom rom are:
1. Root your phone
2. Unlock Bootloader
3. Install TWRP/CWM or some custom recovery
4. Flash the rom from SD Card or Internal Storage(Clear Cache, DALVIK CACHE obv)
I did root my phone with KingRoot APK
Did unlock bootloader with the official SONY Technique, but the thing happened was my phone went into a bootloop (boot animation didn't stop) although i fixed it by flashing the official stock ftf and when i turned my device on my Root and Bootloader was gone again
Could someone recommend me a solution to this issue
(Might be a way to directly flash the lineage rom from the PC/or some flasher app which takes all the load to flash a rom/
Or just a possible fix)
Thanks ! (In Advance)
~Haji
Hi Haji joon
Maybe you should try unlocking your bootloader with flashtool v0.9.18.4 , Then turn off your phone.
Then extract the "boot.img" file from the custom ROM's zip file and use adb&fastboot (you can get it from here: https://androiddatahost.com/bnjkh ) then copy boot.img file to the installation folder of adb&fastboot and connect your phone in fastboot mode (volume up + connect to pc) and type the command below, in fastboot app:
" fastboot flash boot boot.img "
Now you can turn on your phone and press volume up to enter recovery, and install any custom ROM you want
Kungfu73 said:
Hi Haji joon
Maybe you should try unlocking your bootloader with flashtool v0.9.18.4 , Then turn off your phone.
Then extract the "boot.img" file from the custom ROM's zip file and use adb&fastboot (you can get it from here: ) then copy boot.img file to the installation folder of adb&fastboot and connect your phone in fastboot mode (volume up + connect to pc) and type the command below, in fastboot app:
" fastboot flash boot boot.img "
Now you can turn on your phone and press volume up to enter recovery, and install any custom ROM you want
Click to expand...
Click to collapse
Thanks but have you tried this method ? (also the boot.img you were referring to do you mean the boot.img of the recovery?)
Yes!
LordHaji said:
Thanks but have you tried this method ? (also the boot.img you were referring to do you mean the boot.img of the recovery?)
Click to expand...
Click to collapse
In order to flash Nougat ROM, you must have latest TWRP recovery (v 3.0.2 for xperia L)
So, you should either flash TWRP image or the boot.img of any Nougat rom( because they have latest TWRP in them) and flashing boot.img is somehow safer in xperia L (but no difference in them)
And about boot.img, it is in the ROM file that you've downloaded. For example, in Lineage rom's zip installation file, there's a file named boot.img . You should extract and use it in the process I've said before.
And if anywhere you encounter with a problem, simply you can flash stock ROM and start again
And sorry for my long post!
Kungfu73 said:
In order to flash Nougat ROM, you must have latest TWRP recovery (v 3.0.2 for xperia L)
So, you should either flash TWRP image or the boot.img of any Nougat rom( because they have latest TWRP in them) and flashing boot.img is somehow safer in xperia L (but no difference in them)
And about boot.img, it is in the ROM file that you've downloaded. For example, in Lineage rom's zip installation file, there's a file named boot.img . You should extract and use it in the process I've said before.
And if anywhere you encounter with a problem, simply you can flash stock ROM and start again
And sorry for my long post!
Click to expand...
Click to collapse
Final Query are you sure that the ROM i linked in has TWRP & could you tell me bout the best Xperia L Kernel ?
LordHaji said:
Final Query are you sure that the ROM i linked in has TWRP & could you tell me bout the best Xperia L Kernel ?
Click to expand...
Click to collapse
Actually, I'm not sure about Lineage 14.1, because I've only tested it on RR Rom. But you can simply test it with no worries! Or just use the first method that I've told you before.
And about kernel, unfortunately there is no usable kernel developed for XL Nougat ROMs till now :crying: . You should use the ROM's default one.
..
Kungfu73 said:
Actually, I'm not sure about Lineage 14.1, because I've only tested it on RR Rom. But you can simply test it with no worries! Or just use the first method that I've told you before.
And about kernel, unfortunately there is no usable kernel developed for XL Nougat ROMs till now :crying: . You should use the ROM's default one.
Click to expand...
Click to collapse
Ok, can you give me the download URL for latest RR for XL ?
(I don't think its 7.1.1 yet) @Kungfu73
LordHaji said:
Ok, can you give me the download URL for latest RR for XL ?
(I don't think its 7.1.1 yet) @Kungfu73
Click to expand...
Click to collapse
Here you are:
https://www.androidfilehost.com/?fid=745425885120743168
Use this one. It's latest stable version of RR 7.1.2 ROM (2017/06/20). It has no bugs (but install some other file managers, default one can't access sdcard0)
There was a problem in last one (2017/07/06) but developer is working on it and maybe release an update soon ( I hope).
So I'll try it out today with the boot.img of the RR rom
Also for the ROM updates do i need it flash it again or is there some OTA updating feature ?
Ok, I again did unlock the bootloader and its in bootloop state again, will i start the flash mode (volume down + usb cable insert) and then load the boot.img of RR with
" fastboot flash boot boot.img " ?
Then i can power + volume up to start TWRP and install it right ?
LordHaji said:
So I'll try it out today with the boot.img of the RR rom
Also for the ROM updates do i need it flash it again or is there some OTA updating feature ?
Click to expand...
Click to collapse
Although there is an OTA update center, but it doesn't show latest updates! So you should check here in forum for updates!
---------- Post added at 06:24 AM ---------- Previous post was at 06:05 AM ----------
LordHaji said:
Ok, I again did unlock the bootloader and its in bootloop state again, will i start the flash mode (volume down + usb cable insert) and then load the boot.img of RR with
" fastboot flash boot boot.img " ?
Then i can power + volume up to start TWRP and install it right ?
Click to expand...
Click to collapse
No, you should press volume up and use fastboot mode to flash boot.img
Then type fastboot reboot and disconnect cable and press volume up when LED lights on.
Also, for recovery mode do i need to press the volume up button continuously or just long press it
LordHaji said:
Also, for recovery mode do i need to press the volume up button continuously or just long press it
Click to expand...
Click to collapse
Quickly pressing one time when phone vibrates is enough, but it's better to press 2-4 times continuously.
How to Install TWRP Recovery & Root Essential PH-1 (Windows/Mac/Linux)
This is an alternate method on how install TWRP. This one might give you a better understanding of slots.
Another method can be found at below link. Use whatever is easier for you.
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Warning 1: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 2: You might loose all your data. Make sure to backup your data.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pre-Requisites
Make sure you have unlocked the bootloader.
Download and Install drivers (Windows) :- https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Make sure to remove pin/password/pattern etc. Even though TWRP support decryption I personally suggest you remove it and can add it back later.
Make sure you are stock. If you are rooted, please install stock boot.img.
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Steps
1. Download all the files listed in downloads section and place them inside one folder say ph-1.
2. Unzip fastboot and adb zip file (platform-tools). Rename twrp image file to twrp-mata.img. move twrp img file to platform-tools folder.
3. Connect phone to computer and copy below files to internal memory.
* TWRP Installer Zip
* Magisk Zip
Reboot device into bootloader mode.
4. Using command prompt/terminal navigate to folder where fastboot is.
Command Prompt
Code:
fastboot devices
Mac/Linux/Powershell
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
5. Find current slot. Note this down some where.
Command Prompt
Code:
fastboot getvar current-slot
Mac/Linux/Powershell
Code:
./fastboot getvar current-slot
6. If you get current slot as
* A - we will flash twrp to slot B
* B - we will flash twrp to slot A
7. Flash TWRP to slot opposite of what we found out in Step 5.
Command Prompt
Code:
fastboot flash boot_slot twrp-mata.img
Mac/Linux/Powershell
Code:
./fastboot flash boot_slot twrp-mata.img
So, if your current slot was a, you will use boot_b above. If current slot was b, you will use boot_a above.
8. Set slot where we flashed TWRP as active.
Command Prompt
Code:
fastboot --set-active=slot
Mac/Linux/Powershell
Code:
./fastboot --set-active=slot
So, if your current slot was a, you will use --set-active=b above. If current slot was b, you will use --set-active=a above.
9. Use volume rockers till you see recovery option. Then press power button to select. You should now boot into TWRP.
If the touchscreen doesn't function, skip to instructions in post 2 below.
Now, flash TWRP installer zip file.
Once zip is flashed and has patched both slots. Go back to home screen.
Reboot.
On this screen select the slot which we had noted down in step 5.
Then reboot into system. You should now boot into Android.
10. To root. Boot back into bootloader mode. Go into TWRP recovery. Flash magisk zip. reboot.
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Video Guide
Downloads :
Latest ADB & Fastboot Zip File :- https://developer.android.com/studio/releases/platform-tools
TWRP for Essential Phone (need both .img and zip file) :- https://forum.xda-developers.com/es...official-twrp-3-2-3-0-essential-ph-1-t3840931
Magisk :- https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Going Back to Stock :- https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
If you flashed September Android 9.0 Pie Back to Stock (BTS) it flashes to both slots. In that case, if touch is not working please refer post 2.
Credits
@Dees_Troy for TWRP
@aer0zer0 for back to stock (BTS)
@topjohnwu for Magisk
@munchy_cool for this guide
reserved
Common Issues
Thanks to @starcms for helping with the instructions.
No touch in TWRP in Step 9.
Keep your phone connected to computer. Open command prompt/terminal/powershell.
Now we are going to install TWRP installer zip.
Command Pormpt
Code:
adb shell twrp install path/to/zip
So, let's say you have twrp installer zip (named
twrp-installer-mata-3.2.3-0.zip) in root of internal memory.
Code:
adb shell twrp install /sdcard/
twrp-installer-mata-3.2.3-0.zip
This should flash TWRP to both slots. Now, you can reboot using
Code:
adb reboot bootloader
and go back into TWRP. Check if touch is working and then set your slot to one noted in step 5.
If touch is not working use fastboot (step 8) to change the slot to that noted in Step 5..
Now boot back into TWRP using volume rockers and proceed to Step 10 (flashing Magisk zip)
Terminal/Powershell users please add ./ before the adb.
reserved 002
reserved 002
Nice write-up. I would also maybe add (to your discretion ofc) that if you flash the latest P BTS, it flashes to both slots, making touch unusable in twrp and will need to follow your addendum.
aer0zer0 said:
Nice write-up. I would also maybe add (to your discretion ofc) that if you flash the latest P BTS, it flashes to both slots, making touch unusable in twrp and will need to follow your addendum.
Click to expand...
Click to collapse
Done. Thanks for the advice :highfive:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"
Is my stockboot file is incorrect?
YunolexDDP said:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"
Is my stockboot file is incorrect?
Click to expand...
Click to collapse
recovery is part of boot image. if you flash stock boot, twrp is removed.
munchy_cool said:
recovery is part of boot image. if you flash stock boot, twrp is removed.
Click to expand...
Click to collapse
Yeah i know but now i wonder where goes wrong with my phone
Seem my English is not very good so....I dont know how to search the key word
So..I wonder if you have seem this situation before.
YunolexDDP said:
Yeah i know but now i wonder where goes wrong with my phone
Seem my English is not very good so....I dont know how to search the key word
So..I wonder if you have seem this situation before.
Click to expand...
Click to collapse
after installing twrp zip, if you instal stock boot or new kernel it will remove twrp.
you have to flash twrp zip after installing new kernel.
to root, boot into android once after instalinh twrp zip.
then boot back into twrp, and flash magisk zip.
munchy_cool said:
after installing twrp zip, if you instal stock boot or new kernel it will remove twrp.
you have to flash twrp zip after installing new kernel.
to root, boot into android once after instalinh twrp zip.
then boot back into twrp, and flash magisk zip.
Click to expand...
Click to collapse
I am pretty close it. Now i have my twrp install in one slot and the system can boot from another slot but uh..
do I need to flash stock boot before I flash magisk?
cus now I still cant boot the system from twrp..
the official website said "use the devices as normal" hmm..
I need to change the slot if i want to boot the system. Is that normal?
YunolexDDP said:
I am pretty close it. Now i have my twrp install in one slot and the system can boot from another slot but uh..
do I need to flash stock boot before I flash magisk?
cus now I still cant boot the system from twrp..
the official website said "use the devices as normal" hmm..
I need to change the slot if i want to boot the system. Is that normal?
Click to expand...
Click to collapse
NO you don't need to flash stock boot to instal Magisk.
yes, you need to change slot to boot system.
all of this is mentioned in first post.
i have a question, is there a way to just boot into TWRP to just flash magisk? without flashing TWRP itself? i want to recive OTAs still and all i want is just magisk installed, i tried the ,ethod of patching the boot.img but that was a huge fail please help!!!
DeimosPhobos said:
i have a question, is there a way to just boot into TWRP to just flash magisk? without flashing TWRP itself? i want to recive OTAs still and all i want is just magisk installed, i tried the ,ethod of patching the boot.img but that was a huge fail please help!!!
Click to expand...
Click to collapse
No.
We don't have fastboot boot
aer0zer0 said:
No.
We don't have fastboot boot
Click to expand...
Click to collapse
Ahhhh ok,
I figured out the patched boot image method, although when I tried to make my own patched boot IMG, it didn't work, I found a Reddit thread where someone had done it, I used theirs and it worked....although the command was supposed to be fastboot flash boot patched_boot.img and Everytime I did that it sent it to B, but failed on the write, they yelled at me saying that's the command and it should work lol, but I had to actually put fastboot flash boot_b patched_boot.img....the damn A/B partition stuff confuses me Alot lol
DeimosPhobos said:
Ahhhh ok,
I figured out the patched boot image method, although when I tried to make my own patched boot IMG, it didn't work, I found a Reddit thread where someone had done it, I used theirs and it worked....although the command was supposed to be fastboot flash boot patched_boot.img and Everytime I did that it sent it to B, but failed on the write, they yelled at me saying that's the command and it should work lol, but I had to actually put fastboot flash boot_b patched_boot.img....the damn A/B partition stuff confuses me Alot lol
Click to expand...
Click to collapse
sometimes older fastboot versions dont work well with Essential.
for ab slots, if you are want to flash magisk pre-rooted boot.img
just do
fastboot gervar current-slot (say you get a)
and then flash boot.img to current slot.
fastboot flash boot_a nameofboot.img
munchy_cool said:
sometimes older fastboot versions dont work well with Essential.
for ab slots, if you are want to flash magisk pre-rooted boot.img
just do
fastboot gervar current-slot (say you get a)
and then flash boot.img to current slot.
fastboot flash boot_a nameofboot.img
Click to expand...
Click to collapse
essential's driver package for windows doesnt require _a,_b unless you are being specific
fastboot flash boot whatever will work and flash to the current slot if your using essentials (which is an older version) if your using a newer version from google or minimal, it gives the __a or b error trying to append an extra underscore
aer0zer0 said:
essential's driver package for windows doesnt require _a,_b unless you are being specific
fastboot flash boot whatever will work and flash to the current slot if your using essentials (which is an older version) if your using a newer version from google or minimal, it gives the __a or b error trying to append an extra underscore
Click to expand...
Click to collapse
true, but not everyone is on Windows :highfive:
munchy_cool said:
true, but not everyone is on Windows :highfive:
Click to expand...
Click to collapse
Poor Linux folks ?
aer0zer0 said:
Poor Linux folks
Click to expand...
Click to collapse
lol.
Essential is the only phone to give me issues with fastboot though.
munchy_cool said:
lol.
Essential is the only phone to give me issues with fastboot though.
Click to expand...
Click to collapse
Tell me about it, lol.
---------- Post added at 12:00 PM ---------- Previous post was at 11:46 AM ----------
aer0zer0 said:
Tell me about it, lol.
Click to expand...
Click to collapse
Never seen a phone so finicky. I've also got the holy Grail cable that I don't let out of my sight. I've often wondered what makes it so finicky, and I come from a long line of HTC and motos
Hello everyone,
I found a working recovery for our phone
here
All credits go to
@yshalsager for developing and uploading
and
@yukimaru2215 for first linking
Bugs: Encryption not working - but stock rom boots up without encryption with a trick...
Attention: You will need to format data - all your data will be lost! Backup first!
How to install:
Tempearily root your device and modify fstab.qcom - this is needed to enable decryption
a) install fastboot and adb from hereb) load a prerooted kernel (patched bootimage) from here and copy it to your adb fastboot folderc) boot to bootloader -> reboot and keep holding vol+ until you see "FASTBOOT"d) Open command prompt, navigate to your adb fastboot folder and type in command prompt:
Code:
fastboot boot patched_boot.img
e) Go to apps, upgrade magisk manager, install any root explorer, grant root permissions and navigate to /vendor/etc/fstab.qcomf) open fstab.qcom with texteditor and change "forceencryption=footer" to "encryptable=footer" and save
[*]Install TWRP and wipe data backup everything first - this will wipe all your data
a) Download recovery form link aboveb) copy extracted TWRP-3.2.3-daisy-1808.img to adb fastboot folder and type in command prompt
Code:
fastboot flash boot TWRP-3.2.3-daisy-1808.img
c) Type in command prompt
Code:
fastboot reboot
before hitting enter keep holding vol+d) In TWRP you will get the message can´t read data -> skip decryption and go to "wipe" and "format data"e) if you want to root your device you need now need to boot to bootlaoder (reboot -> bootloader) - if not, you done here. Reboot to system and setup your device
[*]Root your device
a) You are in your bootloader... download patched_twrp from here and copy it to your adb fastboot folderb) Type in command prompt
Code:
fastboot boot patched_twrp.img
c) Boot up, upgrade Magisk manager and install magisk via manager -> choose "direct install"
If you flash back a stock boot.img, you will loose your wifi functionality!
Enjoy!
thanks man
You can make a video soon
Noob dude.... And with this method, how is the steps for can update via ota the next updates?
Thx for this hard word and sorry my bad english!
Enviado desde mi Mi A2 Lite mediante Tapatalk
Testing official TWRP tonight. Some issues with decryption but will be resolved soon hopefully. Stay tuned!
d1ngh said:
Testing official TWRP tonight. Some issues with decryption but will be resolved soon hopefully. Stay tuned!
Click to expand...
Click to collapse
When will it be available?
dannyzamora said:
Noob dude.... And with this method, how is the steps for can update via ota the next updates?
Thx for this hard word and sorry my bad english!
Enviado desde mi Mi A2 Lite mediante Tapatalk
Click to expand...
Click to collapse
If you using Havoc 2.0, linke me, it's everything,you need! This twrp lets you boot up all treble GSI Roms....
And otas should be installed normal.
1. Uninstall magisk
2. Install ota, not reboot
3. install magisk
4. Flash twrp and boot up with patched twrp via fastboot
You never boot up without root... So everything's fine with modules and otas doesn't touch vendor and encryption...
brunoliveh said:
When will it be available?
Click to expand...
Click to collapse
When it's ready :silly: just be a little more patient won't be long now.
brunoliveh said:
When will it be available?
Click to expand...
Click to collapse
Hopefully by end of week, maybe earlier
i did every step here but after all the phone stuck on bootloop.
any idea why?
Voodoojonny said:
Hello everyone,
I found a working recovery for our phone
here
All credits go to
@yshalsager for developing and uploading
and
@yukimaru2215 for first linking
Bugs: Encryption not working - but stock rom boots up without encryption with a trick...
Attention: You will need to format data - all your data will be lost! Backup first!
How to install:
Tempearily root your device and modify fstab.qcom - this is needed to enable decryption
a) install fastboot and adb from hereb) load a prerooted kernel (patched bootimage) from here and copy it to your adb fastboot folderc) boot to bootloader -> reboot and keep holding vol+ until you see "FASTBOOT"d) Open command prompt, navigate to your adb fastboot folder and type in command prompt:
Code:
fastboot boot patched_boot.img
e) Go to apps, upgrade magisk manager, install any root explorer, grant root permissions and navigate to /vendor/etc/fstab.qcomf) open fstab.qcom with texteditor and change "forceencryption=footer" to "encryptable=footer" and save
[*]Install TWRP and wipe data backup everything first - this will wipe all your data
a) Download recovery form link aboveb) copy extracted TWRP-3.2.3-daisy-1808.img to adb fastboot folder and type in command prompt
Code:
fastboot flash boot TWRP-3.2.3-daisy-1808.img
c) Type in command prompt
Code:
fastboot reboot
before hitting enter keep holding vol+d) In TWRP you will get the message can´t read data -> skip decryption and go to "wipe" and "format data"e) if you want to root your device you need now need to boot to bootlaoder (reboot -> bootloader) - if not, you done here. Reboot to system and setup your device
[*]Root your device
a) You are in your bootloader... download patched_twrp from here and copy it to your adb fastboot folderb) Type in command prompt
Code:
fastboot boot patched_twrp.img
c) Boot up, upgrade Magisk manager and install magisk via manager -> choose "direct install"
If you flash back a stock boot.img, you will loose your wifi functionality!
Enjoy!
Click to expand...
Click to collapse
hay bro i'm now unlock boot loader and flash boot twrp.img its boot to recovery
i flash DisableForceEncryption_Treble.zip via twrp then flash patched boot.img to root via magisk good till now
i reboot to system and root my device and every thing is good now
but when try to enter twrp its go to stock recovery ok.
what i can to do now to get twrp and keep phone rooted too?
and what is different between twrp.img and twrp patched.img
elkhshap said:
hay bro i'm now unlock boot loader and flash boot twrp.img its boot to recovery
i flash DisableForceEncryption_Treble.zip via twrp then flash patched boot.img to root via magisk good till now
i reboot to system and root my device and every thing is good now
but when try to enter twrp its go to stock recovery ok.
what i can to do now to get twrp and keep phone rooted too?
and what is different between twrp.img and twrp patched.img
Click to expand...
Click to collapse
Hey, it's written above! You need to root with patched twrp linked above... Else you will loose twrp or wifi
Voodoojonny said:
Hey, it's written above! You need to root with patched twrp linked above... Else you will loose twrp or wifi
Click to expand...
Click to collapse
sorry let me step by step going
now i;m rooted what do second ?
Official is here:
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Voodoojonny said:
If you using Havoc 2.0, linke me, it's everything,you need! This twrp lets you boot up all treble GSI Roms....
And otas should be installed normal.
1. Uninstall magisk
2. Install ota, not reboot
3. install magisk
4. Flash twrp and boot up with patched twrp via fastboot
You never boot up without root... So everything's fine with modules and otas doesn't touch vendor and encryption...
Click to expand...
Click to collapse
Please explain by video
maorhag said:
i did every step here but after all the phone stuck on bootloop.
any idea why?
Click to expand...
Click to collapse
Sorry for responding so late... I had a bit of full calendar...
I just did this with another phone (I use these phones for my employies)... Idk, why it´s not working for you sorry. But meanwhile there´s a official twrp - this should do the trick!
Sorry for inconvinience