Related
This is FINAL working method.
First off you must unlock bootloader, and install twrp.
instructions for unlock bootloader are in this thread
http://forum.xda-developers.com/r1-...mazon-root-t3490882/post69387472#post69387472
I made many cycles between 6.6 and 6.1 and found that this set of files was minimum needed to maintain stable device. I started with only the preloader, and that left the phone able to connect to spft but the preloader was o longer in the "trusted zone" so it would not load the second step of power on (lk). replaceing the lk with spft after that allowed to boot to the boot menu, but would not trust the next step(boot.img). But with the preloader and lk I was able to fastboot, so was able to oem unlock.. this was the first method I was going to suggest. After more trials I decided it better to foll back all the bin files that the update replaced and also the secret bin so no more need to oem unlock after the roll back.
I got so comfortable moving between preloaders and version I got careless. My carelessness allowed me to mix up secure preloader and bin files with custom non secure recovery files and without realizing it I rebooted like that. I was left in a secure environment that was panicking because the recovery was not properly signed. (a terminal soft-brick)
My point is once you roll back DO NOT go back to locked and DO NOT blame me if you forget and restore some backup that does that to you down the road.
I do recomend that you roll back though. Because with the roll back, you are almost certain not able to brick because you can always use spft to to fix things.
THIS WILL ROLL BACK BOOT LOADER AND ALLOWS SPFT .
THIS HAS ONLY BEEN RUN WITH TWRP.
But the fastboot mode can also flash preloader if prefered. Just remember you may also need to oem unlock again after. This has not and will not be tested by me.
ONCE YOU HAVE UNLOCKED BOOTLOADER AND INSTALLED TWRP, return here and download "after_bootloader_roll_back_5.tar" unpack the tar and run the .bat file. It will adb push the recovery image to you phone and then install it.
It will rewrite :
1. preloader
2. lk (little kernel)
3. boot img
4. seccfg.bin
5. frp (to make sure bootloader remains unlockable)
6. trustzone (goes into both TEE1 and TEE2
7. secro.bin
All done.
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
jhonjahegu said:
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
Click to expand...
Click to collapse
Sounds like you need to do oem unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot oem unlock"
6. If need to do oem unlock you will also need to "fastboot format userdata"
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
digihaven said:
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
Click to expand...
Click to collapse
If it is looping into twrp then you must do step 6 from above.
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
clownkitty said:
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
Click to expand...
Click to collapse
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
mrmazak said:
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
Click to expand...
Click to collapse
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
clownkitty said:
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
Click to expand...
Click to collapse
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
mrmazak said:
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
Click to expand...
Click to collapse
I didn't realize you had to load straight into recovery mode after flashing it, I got it to work now, thank you so much!
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
tuespazio said:
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
Click to expand...
Click to collapse
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
mrmazak said:
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
Click to expand...
Click to collapse
Hi, dont worry now is fixed i return to 6.1 and then flash full 6.5 firmware.
Data is now working fine .
Thanks for your Support
sorry, wrong thread
ncy1 said:
Hi guys, sorry to bother you with this
I was on 6.0 rooted and without ads, i just tried to update my phone using the v17 and settings on this thread, when i went to cellphone info on settings it said i was still on 6.0. Did i miss something or this a normal thing? Anyway, i went back to recovery mode, did a wipe and tried to flash the 7.4.2 rom but it sent me an error, now the phone won't boot and gets stuck on the blu loadscreen.
Click to expand...
Click to collapse
Don't get me wrong, I feel bad for you that your phone is in this situation, but that has nothing to do with the thread you are posting in.
This thread is for rolling back the preloader.
And all the oem and Amazon Roms are 6.0
To get help you should post in the thread you got the ROM from.
And include the error you got.
mrmazak said:
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Click to expand...
Click to collapse
I think I just want to try this method, since I want to convert it to OEM and still keep OTA updates anyway. I'm blanking though as to how I need to go about this.
I have adb installed, and I have access. I assume this requires a fastboot command, but I don't know which.
Jessooca said:
Mrmazak... does this work on a new out of the box blu r1 that came with the 6.6 August update already installed?
I'm trying to help a friend, I surprisingly can't get the bootloader unlocked, dirtycow continually failed.
He doesn't care about updates etc... just wanted to flash the no ads firmware onto a prime version blu r1 hd
Click to expand...
Click to collapse
To the best of my knowledge it was.
Last time someone told me they were having trouble, they ran the codes manually one by one instead of using the script, and it worked. Apparently they had trouble pushing the files from the batch file. I had similar trouble when I wrote the script, that is why there are 3 second pauses ,that seemed to fix it for me. I will change them to 10 seconds and see if it helps.
I will update here when I change it then you candownload again and try, or you can make the changes yourself and let the me know
OK i updated the one-click.bat . you can download it again to see if that help. Also you said dirty-cow keeps failing, please let me know the fail message and also the comments displayed during the first part of the script. the part that is pushing files.
Also I have not been able to get feedback on the one-click.sh for linux. I don't normally use linux and did not test the shell. If you are using that one maybe the fail is my poorly written .sh
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
danbcooper said:
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
Click to expand...
Click to collapse
"oem" is not supposed to be capitalized
i went back and edited that original post too.
mrmazak said:
"oem" is not supposed to be capitalized
i went back and edited that original post too.
Click to expand...
Click to collapse
Now I ran "fastboot oem unlock" and it says FAILED (remote: unknown command). Do you know why?
Never mind.. Tried again and worked! Thanks for everything!
The instructions are updated as of 11-20-17. Win7 only cause Win10 sucks and uses powershell and the fastboot commands don't work in powershell.
These are the proper files and procedures for installing Root, the latest Kernel, the best Superuser version and TWRP.
This is for NOUGAT 7.1.1. (and possibly beyond) There is a special procedeur to make flashtool work with the latest firmwares for Nougat ..
Before you Root and install TWRP you need to go back to my link and unlock bootloader..
You also need to download and install Android Studio Software and install it. Back to this portion of the install later.
You also need a special kernel to allow things on the phone to keep working.
This will work only for Nougat firmware.
You will need to download Boot img, TWRP img, SuperSu
Save TWRP and boot img files to the Android Platform folder in your PC here C:\Users\enter the current pc users log in name here\AppData\Local\Android\sdk\platform-tools . Save the Kernel zip and SUperSU zip file to an SD card and put the card inside your phone to access it through TWRP later in the process. Keep in mind that the Kernel may be updated. Check for updates herel here. Do a "date last modified" list of the files on that page by clicking on the grid view box on the upper right portion of the screen just under the "sign in" button. This helps you see what files have been updated in most recent order.
You will need to download the special Flashtool file here Install it.
Download the .jar patch file that makes the software version updated to the latest 9.23.2 and place it in this location C:\flashtools.
Now, download the special .fsc file and paste it in C:\Users"current user that is logged in"\.flashTool\devices\F81XX. Without this file you will not beable to update the device to nougat.
Goto C:\Flashtool\drivers and click on this file which was installed during the Flashtool installation.
Check off these boxes to install the drivers for the device you will be rooting. "Flash Boot Drivers, Flash Mode Drivers"
Now download and install these special ADB drivers to allow it to perform the Firmware update. Without it you wont beable to install the FTF file.
Open Sony Flash tool. Click on XI button. A window open. Click on Xperia Performance and then a small menu open under that. Choose F8132 ( i choose dual for my device)
If you can not get the newest firmware to show up for your device.( mine is 41.2.A.7.8 aka Nougat 7.1.1) then you can download it here Close Sony Flashtool.
Copy this FTF file and place it in folder C:\Users"The user you are currently logged into your pc with"\.flashTool\firmwares. Open Sony flash tool. Click on lightning bolt. Choose Flash mode in the small popup box. Window opens and shows your formware in the "firmwares" box. Click on plus symbol to the left of that firmware and it opens to the bottom to show the device model ( mine is F8132)/ Click on that plus symbol to the left of the model number to show the location of your firmware origination. Click on plus symbol and it then shows the firmware number 41.2.A.7.8. Click on the firmware and the entire window will populate a bunch of new options. If you want to wipe everythign on your phone then you need to check off the boxes "SSD and UserData" in the "wipe" box. Leave everythign else unchecked. Click the flash button at the bottom and it will start to prepare the files for installation onto yout device.
A window pops up that tells you to turn off your phone.
Turn your phone off. After its turned off, hold the volume down button while plugging the phone into your pc to get into fastboot mode. Your computer should be looking for the correct drivers to allow the device to work in this Flashboot mode. Once the flashing is done just close the flashtool. Turn your phone on. Go into settings and scroll down to "about phone then click on "build number" about 7 times. You will get a new optioon back in settings menu called "developer option". Click on that tabturn on "usb debugging" and turn off "verify apps over usb". Turn off phone.
Hold volum button UP this time while plugging phone back into pc.
Now go back to the folder C:\Users" name of user that is logged into the pc"\AppData\Local\Android\Sdk\platform-tools. You will open a cmd prompt in this folder by holding down your right mouse button and click on the shift key then release the mouse button. This will open a pop up window where you can choose to " open command window here" when the cmd window opens, copy and paste this "fastboot devices" press enter button, your computer should respond with this ......CB512A697c fastboot.......This lets you know that your phone is in the correct mode and ready to be programmed.
Now you will install the boot img by copy and pasting this in cmd line "fastboot flash boot boot.img" The PC should tell you OKAY with some other irrelevant info.
Now you will install the twrp img by copy and pasting this in cmd line "fastboot flash recovery TWRP-3.0.3-0-dora.img" The PC should tell you OKAY with some other irrelevant info.
Now you will install Kernel, and SuperSU. Turn on phone while pushing power button holding volume down button for about 5 secnds then release the bottom volum button then after 5 seconds release the power button to initiate TWRP.
Swipe to allow modifications then choose "Install" to install the zip files. Navigate to the SD card that has the kernel and SU zip files. Click on them to install. Reboot. TWRP might ask if you want to install the TWRP app before the phone starts to reboot. Just say no. After that, a few seconds later, the device reboots and then the Phone might go throw optimization process which takes some time. You will notice the counting of optimized files. Be patient.
When phone is booted and running, you might have to reinstall SuperSU via the Operating system as a APK like you would a normal app just to get root going. No big deal.
A caution...
When doing a backup with Twrp you should only backup System and Data
When doing a full restore, wipe only System, Data and the cache files. Do not ever delete your SDcard with the backups on it.
THIS IS THE VERY LAST UPDATE FOR ROOTING THE X Performance. IT IS NOUGAT 7.1.1
FORGET ABOUT ROOTING OREO>> ITS NOT GOING TO HAPPEN. PLUS IT IS NOT A DECENT UPDATE TO BE HONEST> IT JUST CHANGES A BUNCH OF MENUS AROUND AND LOCKS DOWN YOUR PHONE MORE>
Please do not upload my kernel to other hostings!
Official website for my kernel is
https://kernel.andro.plus/tone.html
So, if I was to relock my bootloader after installing TWRP and rooting, what would happen? Would TWRP go away? I'd like to let the phone OTA update to nougat, and you can't do that with an unlocked bootloader....
jakebriggs said:
So, if I was to relock my bootloader after installing TWRP and rooting, what would happen? Would TWRP go away? I'd like to let the phone OTA update to nougat, and you can't do that with an unlocked bootloader....
Click to expand...
Click to collapse
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Arturiuz! said:
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Click to expand...
Click to collapse
Thanks heaps! Now, to find a couple hours spare
Arturiuz! said:
your phone will soft brick..or rather bootloop..if you're still on MM,do a nandroid backup..& here's what you do:
-relock phone using Flashtool.
-repair device using Xperia Companion(it will update automatically to Nougat).
-unlock phone again using Flashtool.
-install AndroPlus Kernel through command prompt(or you can also use Flashtool to do it.however you prefer).
-install TWRP recovery..you're all set!
P.S.
on steps i said(this is optional),you may not turn on your device along the process..that's what i do & i find it easier that way..goodluck!
Click to expand...
Click to collapse
Following this left me with a phone that boots to a screen "To start Android, enter your password". I don't have a password to enter :/
jakebriggs said:
Following this left me with a phone that boots to a screen "To start Android, enter your password". I don't have a password to enter :/
Click to expand...
Click to collapse
that occured to me too!my apologies but i forgot mention about that..but you could try again that after you fixed/updated your phone using Xperia Companion to turn your phone first & set up everything.then unlock using Flashtool.install kernel & recovery.. :good:
Arturiuz! said:
that occured to me too!my apologies but i forgot mention about that..but you could try again that after you fixed/updated your phone using Xperia Companion to turn your phone first & set up everything.then unlock using Flashtool.install kernel & recovery.. :good:
Click to expand...
Click to collapse
I did try that - although, I set it up with a pin rather than a password. It didn't accept my pin when asking for the password.
Now I have a phone with a locked bootloader, running nougat, and I set it up with a password. I wonder if that password you use on the lock screen is the same password that Android is asking for when I unlock my bootloader?
I also could not seem to get the phone to boot into recovery after rebooting when I got the password screen. So weird....
jakebriggs said:
I did try that - although, I set it up with a pin rather than a password. It didn't accept my pin when asking for the password.
Now I have a phone with a locked bootloader, running nougat, and I set it up with a password. I wonder if that password you use on the lock screen is the same password that Android is asking for when I unlock my bootloader?
I also could not seem to get the phone to boot into recovery after rebooting when I got the password screen. So weird....
Click to expand...
Click to collapse
you can't use recovery or root your phone when bootloader is locked..could you try now unlock your phone using Flashtool?then install kernel & recovery?mind that data will be wiped..
Arturiuz! said:
you can't use recovery or root your phone when bootloader is locked..could you try now unlock your phone using Flashtool?then install kernel & recovery?mind that data will be wiped..
Click to expand...
Click to collapse
So if unlocking the boot loader wipes data, how can android ask for my password when I reboot? I am a little mystified at how this is supposed to work Rooting Marshmellow was easier than Nougat....
jakebriggs said:
So if unlocking the boot loader wipes data, how can android ask for my password when I reboot? I am a little mystified at how this is supposed to work Rooting Marshmellow was easier than Nougat....
Click to expand...
Click to collapse
true!MM was easier but Nougat is a bit complicated..however,you could still make changes on Nougat when phone is rooted.anyway,try again from the very beginning then this time after fixing phone using Xperia Companion,do the steps i mentioned..i myself couldn't figure out how it's asking for any password at first.AndroPlus also mentioned it before but didn't explain further.but it's alright coz i got it working now.
Arturiuz! said:
true!MM was easier but Nougat is a bit complicated..however,you could still make changes on Nougat when phone is rooted.anyway,try again from the very beginning then this time after fixing phone using Xperia Companion,do the steps i mentioned..i myself couldn't figure out how it's asking for any password at first.AndroPlus also mentioned it before but didn't explain further.but it's alright coz i got it working now.
Click to expand...
Click to collapse
I think my issue with the unknowable password after unlocking the bootloader on Nougat could have been fixed by wiping data+dalvik cache. I was having issues with the camera under nougat so I flagged trying to get it going and flashed MarshMellow. Once that was done, I got the bloody password prompt again, so I wiped data + cache and it booted correctly.
Anyway, gonna ignore Nougat until fastboot supports nougat
Issues with passwords kept / unknown and blocked are due to the fact the security portion is stored
next to the data partition area, in what we call the footer, and that area was wrong for you.
By wiping data completely (most reliably, a factory reset which will format the data partition),
the footer is also erased instead of simply deleting the files like a Wipe would do.
lost system?
I got as far as getting boot.img and twrp.img in my phone, and then appeared to lose my system since it stuck on the Sony logo and wouldn't boot into the system despite several tries. Idiot that I am, I panicked and come onto the forum to post a plead for help. I've managed to get my system back on now and feel very foolish, so just editing the post to remove the request for help. Thank you so much for the guide, very greatly appreciated! Looking forward to upgrading to Nougat.
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
mongastein said:
I got as far as getting boot.img and twrp.img in my phone, and then appeared to lose my system since it stuck on the Sony logo and wouldn't boot into the system despite several tries. Idiot that I am, I panicked and come onto the forum to post a plead for help. I've managed to get my system back on now and feel very foolish, so just editing the post to remove the request for help. Thank you so much for the guide, very greatly appreciated! Looking forward to upgrading to Nougat.
Click to expand...
Click to collapse
Don't feel like a fool. I'm panicing right now.
Can flash boot.img and twrp.img and even enter twrp to flash su and kernel. But thats it. When done i reboot and i can pass SONY logo and enter bootanimation but it stucks here forever. Been trying with everything exept flashing official MM.
You did get the system back. So I'm the fool
---------- Post added at 07:45 AM ---------- Previous post was at 07:40 AM ----------
chiobesek said:
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
Click to expand...
Click to collapse
Didn't for me. Have a softbricked phone in front of me since yesterday. Going to try to flash MM soon but my internet is terrible slow. Won't give up.
chiobesek said:
Will this guide work with Nougat? I have a F8132 with 39.2.A.0.327
Click to expand...
Click to collapse
It works if you get updated files. I struggled a bit before I finally extracted the boot.img from the AndroPlusKernel for my version which I flashed in fastboot and flashed the kernel and supersu in twrp. I think that's what did it. I was so eager to root that I missed that I was using MM-files at first. :silly:
Edit: oh I answered a pretty old post. Anyway, this is another way https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
Wimz3n said:
Don't feel like a fool. I'm panicing right now.
Can flash boot.img and twrp.img and even enter twrp to flash su and kernel. But thats it. When done i reboot and i can pass SONY logo and enter bootanimation but it stucks here forever. Been trying with everything exept flashing official MM.
You did get the system back. So I'm the fool
---------- Post added at 07:45 AM ---------- Previous post was at 07:40 AM ----------
Didn't for me. Have a softbricked phone in front of me since yesterday. Going to try to flash MM soon but my internet is terrible slow. Won't give up.
Click to expand...
Click to collapse
I ended up finding a way to downgrade to marshmallow following some instructions from from @sdugoten
The instructions are updated.. With proper files for the latest and greatest kernel and SuperSU and TWRP. NOUGAT Only .. Will not work for any other OS versions
AS flashtool does not work for 7.1.1 how to proceed to install nougat 7.1.1 and enable root and install twrp?
Using the following method I was able to successfully ROOT my H830 running stock 20A NOUGAT. With this root method you will get TWRP Recovery and SuperSU. This method WILL wipe your internal storage, so please BACKUP!
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, or lost photographs.
Please do some research if you have any concerns about root!
I used jcadduono's method which he describes on the V20 forum [Easy Recowvery ALL CREDITS TO THE AUTHOR. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!] https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
1. Bootloader Unlock
For this method to work you must have an unlocked bootloader. Despite the fact that I already had an unlocked bootloader, after the upgrade to stock N, jcadduono's script failed to work initially and gave me an error message saying my bootloader was locked. To fix this I had to manually relock and unlock my bootloader one more time. Unlocking/Locking your bootloader will wipe the internal storage of the devices so backup before this step. If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script. If you do skip these steps, don't forget to download the LG Drivers from below.
1. Download and install the latest LG Drivers from HERE
2. Download the minimal adb and fastboot tool from HERE. I recommend the portable version, which you can extract to your desktop.
3. On your phone, go to Developer Options and turn on Enable OEM Unlock.
4. Enter fastboot mode: Turn off your device, press and hold the volume down button, while holding the volume down button connect your phone to your computer by USB, continue holding the volume down button until your device enters into fastboot mode.
5. On your computer go to the folder which you extracted in step 2. Open a command window by holding down SHIFT, right clicking with you mouse inside the folder, and selecting "Open command window here"
6. In the command window type "fastboot oem unlock" to unlock your bootloader, this will erase all of your data.
7. Type "fastboot reboot" to reboot to system.
2. Installing TWRP using Recowvery
Prior to this step I HIGHLY recommend factory resetting your device, if you just unlocked your bootloader, your device was automatically factory reset so you are good to go. Once your phone turns on after a factory reset, I suggest signing into your google account and setting up your phone as if you are going to use it, we will not be factory resetting after this step. However do not download any apps or mess with the settings yet, you can do that later, once your device is successfully rooted.
1. On your computer, download Recowvery from HERE and extract the folder to your desktop.
2. Now on your phone enable USB Debugging in Developer Options.
3. Connect your phone to the computer and make sure File Transfer is chosen in the "Use USB connection for" pop-up.
4. On your computer, download the latest version of TWRP: H830 or H850
5. Rename the downloaded file to "recovery.img" and place it on your phone's internal storage [/storage/emulated/0]
6. On your computer, open the Recowvery folder you extracted in step 1, and click on EasyRecowvery.
7. Once there, type option "5" and "ENTER", in the "Extras and Advanced Tools Menu" disable integrity verification by typing option "7" and "ENTER". Return to the main Menu of Recowvery by typing option "0" and "ENTER"
6. After disabling integrity verification, run the exploit by choosing option "1"
7. Follow the prompts in Recowvery, your phone should reboot about two times in the process.
8. DO NOT Wipe Cache while in TWRP.
8. Once finished, your device should reboot to system and will have TWRP recovery, instead of the stock recovery. The only thing left now is to install SuperSU.
3. Installing SuperSU through TWRP
Although Recowvery does give you an option to install SuperSU through its interface, doing so caused problems in my case. Therefore I recommend manually booting into TWRP and installing SuperSU from there.
1. Download the latest version of SuperSU from HERE and place the .ZIP file on your phone's internal storage.
2. To boot into TWRP, go into the adb and fastboot folder, which I described in the very first steps of this tutorial. There, once again open a command window and type "adb reboot recovery".
3. You should now be in TWRP, there select Install, find the .ZIP file of SuperSU in the file explorer, and install it. DO NOT Wipe Cache after the installation.
4. Reboot to sytem, you should now have a rooted LG G5 with TWRP and SuperSU installed!
Credits:
jcadduono - Recowvery
RealPariah - Compiled Recowvery zip for LG G5
shimp208 - Minimal ADB
TWRP
SuperSU
[Reserved]
I'll try this later tonight, I spent the whole night yesterday trying that. Thanks in advance. ???
Didn't work for me. Thanks for this though. The script actually made it's way through this time (multiple times at this point), but whenever I try to adb reboot recovery I get the "No Command" screen (which I believe is still the stock recovery?). Success all the way through. Don't know what I could be missing.
Also tried manually pushing the recovery image via adb thinking there might be an "Internal Storage" (as seen by pc) vs "/storage/emulated/0" on the phone. No dice either way.
Dumboguy03 said:
Didn't work for me. Thanks for this though. The script actually made it's way through this time (multiple times at this point), but whenever I try to adb reboot recovery I get the "No Command" screen (which I believe is still the stock recovery?). Success all the way through. Don't know what I could be missing.
Also tried manually pushing the recovery image via adb thinking there might be an "Internal Storage" (as seen by pc) vs "/storage/emulated/0" on the phone. No dice either way.
Click to expand...
Click to collapse
To me it seems like your recovery is not flashing, make sure to download the latest version of TWRP, rename it "recovery.img", and place on the internal storage of the device. If still doesn't work, try a complete clean start. Relock and unlock your bootloader again.
To be safe, I would remove "others try at your own risk" as it will not work and could possibly brick any model other than the H830 and H850. All other models are bootloader locked and I have tested myself; it won't work on anything else.
It worked! Thank you so much.
It worked! Thank you!!!ðŸ‘ðŸ‘ðŸ‘
Sent from my LG-H830 using XDA-Developers mobile app
If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script.
What do you mean with thiz sentence? We cant unlock our bootloader its not supported, can we still try this method?
Will this trigger some flag or fuse? Or with the flash of the firmware though lgup and locking the bootloader will create a Perfect stock device?
Can someone confirm it works on H850
yken said:
If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script.
What do you mean with thiz sentence? We cant unlock our bootloader its not supported, can we still try this method?
Click to expand...
Click to collapse
No, you have to have an unlocked bootloader. I meant if you already unlocked your bootloader, you can skip this step. Possibly it will work once we get bootloader unlocks for other variants of the G5.
Do I have driver issues? Adb recognizes phone when turned on. When in fastboot only waits for device to connect.
Sent from my LG-H830 using Tapatalk
Tinbender418 said:
Do I have driver issues? Adb recognizes phone when turned on. When in fastboot only waits for device to connect.
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
The drivers in the post should work for both fastboot and adb. What do you mean, "when in fastboot only waits for device to connect"? You can run the "fastboot devices" command there to see if the device is recognized.
Will not let me run any commands. Just says waiting for device. Crazy, I know.
Sent from my LG-H830 using Tapatalk
Looks like hd on pc is going.
Sent from my LG-H830 using Tapatalk
adb and fastboost not recognizing my phone even after installing drivers
Finally got root back. My problem was getting adb to work but I had no problems with minimal adb and fastboot. Thanks for the tutorial.
Will we be able to flash the current roms that our out?
Sent from my LGE LG-H830 using XDA Labs
Running in normal exploit mode
Press any key to continue . . .
- - - Making sure we're good to go - - -
Checking permissions in the EasyRecowvery directory...Checking that the exploit files exist...SUCCESS!
Locating adb.exe... SUCCESS!
Looking for ADB device...
This device doesn't look like a T-mobile V20. Proceed anyway? (DANGEROUS!)
(Y/N) y
Checking unlock status... error: device '*' not found
FAILED!
Your device does not appear to be unlocked.
Please boot into fastboot mode and run:
fastboot oem unlock
From your computer, then try again.
http://i.imgur.com/2BhNatP.png
Press any key to continue . . .
so this is what i am running into. I know with 100% certainty that the device is oem unlocked. I get the whole, "your device software can not be checked for corruption" screen and everything.
i started the process completely stock, with oem locked. I unlocked it as per your instructions and followed everything closely as far as I can tell. i have tried to re-lock oem . reboot and then unlock it again twice, as well as rebooting pc and G5 multiple times. usb debugging is turned on, and usb options are set to file transfer. still same result.
Any ideas?
EDIT: i will leave the whole post up in case some one makes the same mistakes i did and this helps them out. What i needed to do to fix this was simply set "use usb connection for " to photo transfer instead of file transfer.
Now i am stuck on :\Users\test\Desktop\LgG5 RooT\minimal_adb_fastboot_1.4.1_portable>adb reboot recovery
error: no devices/emulators found like another person before me. hopefully this will be figured out soon
EDIT#2: used adb reboot recovery command with phone turned on and on main screen of launcher, not fast boot, like i was trying at first. and twrp loaded up fine.
dont have a sd card to put superuser.zip on and it seems like i can't reach the internal storage download folder through twrp, or atleast i could not find it, so i ended up sideloading it by going to sideload in twrp and typing "adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip"
into it.
i hope that documenting all my mistakes and solutions for everyone to see will help someone running into the same problems i was.
Disclaimer: I have done these steps multiple times and haven't come across any issues, but before you continue please read this fully, and follow the steps completely. Any issues or damage to your phone that occurs while doing this I am not responsible.
That being said below will be everything you need to make sure this all goes smoothly:
Windows or Linux Laptop/PC
Atleast 50% battery on OP3T
Usb Cable for OP3T
Internet Access
Patience
Now to Begin the process to return to stock:
Step 1: Go to http://downloads.oneplus.net/devices/oneplus-3t/ , and download the 4.0.2 version. Again these are the steps I do so that I can make sure the process is done correctly and also that I can get rid of the annoying dm-verity warning. Don't worry at the end of this you will have the latest version for you're device.
Step 2: Go to your phone and reboot to twrp, once in twrp go to wipe>Advance Wipe> Tick everything but usb otg (I do this to make sure my phone starts out in a completely clean state>then swipe to wipe. Once it's finished press back twice to get back to the main screen for twrp.
Step 3: Please reboot device back to twrp. (I found the best way to do this without issues is on the main screen for twrp go to reboot>power off>when the unlocked bootloader warning comes on click the volume up button quickly>use the volume down button when another menu comes on and go to recovery. Again I did it this way because the with twrp version 3.0.4-1 gave me issues when trying to reboot twrp within twrp. Also you will get an No OS installed this is normal as you wiped the system completely. Don't worry just reboot back to twrp.)
Step 4: Once back to twrp you will get the screen where is says to allow modification. Please swipe to allow. Next please connect phone to pc/laptop, and transfer the 4.0.2 you downloaded to your phone. One completed go back to phone and click install and click on the file you just transferred and swipe to install. Once completed reboot device. (Warning: at this time you will get the Dm-verity warning, but dont be alarmed we will take care of that in the up-coming steps.
Step 5: Once the phone reboots and comes to the setup screen don't go through and add your accounts because we will be doing another reset. Quickly get to the home screen of your phone and go to settings>about phone>tap build number 7-10 times>back once>developer options>make sure oem unlocking is ticked, advance reboot is ticked, and usb debugging is ticked(If none of them are please tick them). Since your phone is connected to the pc/laptop after you turn on usb debugging a allow authorization box will show on your phone. Please allow that for this to work.
Step 6: Next go to this link: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.0.3/ , and go all the way to the bottom where it says download Oxygen Recovery (optional), and download that file, and place it on desktop.
Step 7: Now this is assuming you have adb/fastboot setup on you're pc/laptop. Please open up a Command prompt window with phone connected and type these commands in:
1) adb devices ( this will show your device ID Number). If it shows it please continue, if not there is an issue with adb/fastboot set up on your computer, or you typed that command in wrong. Once u get the issue resolved try the command again.
2) adb reboot bootloader (this will reboot your device to bootloader mode)
3) fastboot devices ( again this will show your device ID number as from before)
4) fastboot flash recovery [click and drag the recovery file you downloaded from oneplus website and saved to the desktop here, press enter, and once completed go to your phone and use either the volume up or down button till u see the word Start in green and then press the power button. This will reboot your device, and again you will still have the dm-verity warning on. We are almost done.
Step 8: Once your device is rebooted we need to get rid of all traces of twrp so go to your computer>file explorer>this PC tab>your device should be listed there since its still connected to pc> internal storage>locate twrp folder and delete. Now after you are done with this and you want to lock bootloader go to step 9, but if u don't want to relock the bootloader please just factory reset device, setup your device and then go back to oneplus.net and download the 4.03 version and adb sideload it, and dm verity is gone.
Step 9 Relocking bootloader is easy, and will reset your device. While on your phone go to settings>about phone>tap build number 7-10 times>back once>developer options> make sure that OEM unlocking is ticked, advance reboot is ticked, and usb debugging is ticked (again u may get the allow authorization pop up on your phone please allow). Go to command prompt for adb/fastboot and type in these commands:
1) adb devices ( this will show your device ID Number). If it shows it please continue, if not there is an issue with adb/fastboot set up on you're computer, or you typed that command in wrong. Once u get the issue resolved try the command again.
2) adb reboot bootloader (this will reboot your device to bootloader mode)
3) fastboot devices ( again this will show you're device ID number as from before)
4) fastboot oem lock; once you click enter go to your phone, and use your volume up or down buttons to click on lock bootloader. Let finish. This will reset your device again. Once this is all completed and reboot you have gotten rid of all the warning screens, and your device is like it was when you first got it. Set up device with your accounts and you will get a notification of a update. Download and install.
Congrats your phone is back to stock. If anyone has questions please pm me.
Again these steps are longer than what most of you may do. A few others including myself have done this multiple times to confirm. None of us had issues. It works
**Special Thanks**
The guys that tested this with me to confirm my steps are accurate
Google for well google
Oneplus for yet another awesome device and software.
***UPDATE***
Thanks to @ashokmor007 he made the video below on the steps.
https://www.youtube.com/shared?ci=xDFI-287K-Q
If there is anything else that someone may want a guide on how to do and there isn't one currently on xda. let me know and i can get a guide out. We are currently figuring out if this will work on the oneplus 3.
Very helpful tutorial
if anyone here has tried this please comment, and if u need help please pm me.
the_rooter said:
Thanks to @ashokmor007 he made the video below on the steps.
https://www.youtube.com/shared?ci=xDFI-287K-Q
Click to expand...
Click to collapse
If possible add to the main thread
ashokmor007 said:
If possible add to the main thread
Click to expand...
Click to collapse
done and finished thanks again for the video
TWRP - Mount Decrypt Data?
Good afternoon, the_rooter... Thanks for posting this. I'm trying to get back to stock and found this. I'll explain from the beginning...
My 3T will not boot now. Stuck on “Powered by Android” Screen. Here’s the sequence of events that led to this:
1. Flashed TWRP 3.1.0-1
2. Did a backup of phone (Orig OS… Just got phone a few days ago)
2. Flashed Sultan’s ROM
3. Installed Xposed.
At this point… Everything was working just fine… This morning I decided to install the Xprivacy Module and then I rebooted phone. When I did that, the phone just hung at the “blue android” start screen. I then did the following:
1. Held power button until shutdown
1. It took a while, but I was finally able to boot into TWRP.
2. Did a Wipe – The regular one
3. Restored my backup and rebooted. (Would not boot into the OS)
This is where I think I screwed it up even further… … Here’s what I did… I grabbed a shotgun and… LOL… No… but I was thinkin’ it… LOL… I did this:
1. Booted into TWRP
2. Did the Advanced Wipe and just wiped Everything(Internal Storage as well) except USB OTG
Also getting "Mount Decrypt Data" message when I boot to TWRP... Not sure why that's happening...
Now I can’t copy any files to the phone… Tried with Linux(Ubuntu) and a Windows system... Before all of this I could copy to the phone just fine. I tried disabling MTP in TWRP but that didn't work either. So I'm stuck on copying things to the phone at this point...
Can you set me straight?
Edit: Crisis over... Was able to load ADB drivers on a Windows Box and copy ROM back to phone... I'm back and smiling again.
Just use these tutorial for return 100% stock,it worked very good but the last dm verity message only dissappeard for me after step 9 updating to last 7.1.1 using adb sideload.
Thank You very much!!!!!
Is there a reason why you have to swipe to allow modifications? Can't you just keep TWRP read only and then the stock recovery will automatically be flashed so you don't have to do it manually? Also there will be no dm-verity warning.
Thanks for this guide, it worked great.
When you flash the downloaded 4.0.3, the ota of 4.1.0 will fail because somehow a partial ota is for some reason not possible. Anyway this is no problem because the phone will perform an automatic retry and downloads the full ota which worked for me and let the dm-verity warning disappear. I imagine future partial otas will work.
Therefore I think it is important to start with a version that is not the newest version (but e.g. with newest version - 1) or otherwise use some other way to get rid of the dm-verity warning.
Took the 4.0.3 update OTA but other than that followed exactly. Worked beautifully!
I didn't relock bootloader.
I also removed the default encryption.
I've followed all the steps, but dm-verity warning is still showing. I'm still on OOS 4.0.2 though. Someone with simmilar experience? How to get rid of that dm-verity warning?
Edit:
Manually upgraded to OOS 4.0.3 and dm-verity warning gone! Not sure why I was not receiving OTA update though.
What about returning to stock for 4.1.1??
I was coming from the beta channel, and after the initial wipe I was unable to boot into either recovery or the software. I had to reflash TWRP, and then I was able to install 4.02.
After unlocking, I was still getting the dm verity warning. The software attempted an OTA, but it failed. After this it downloaded the complete 4.1.3 via OTA, which worked and got rid of the dm verity warning.
Thanks for the guide!
Followed Tutorial 100% :/, Didn't get any error doing Flashing, Worked perfectly but still the DM-Verity warning.
That official TWRP 3.x is prone to cause dm-verify error and due to that I even has many files in /data lost! Better use TWRP 3.1 bluspark version. Though it's Unofficial its work best.. I also upgraded from 3.0 to 3.1 TWRP without getting the dm-verify error back..
arvindgr said:
That official TWRP 3.x is prone to cause dm-verify error and due to that I even has many files in /data lost! Better use TWRP 3.1 bluspark version. Though it's Unofficial its work best.. I also upgraded from 3.0 to 3.1 TWRP without getting the dm-verify error back..
Click to expand...
Click to collapse
How can I upgrade to the 3.1 version?
To return it to stock I just
1.flash the oneplus's Oxygen Recovery
2. full wipe in Oxygen Recovery
3. ADB sideload 4.0.3
4. lock oem in fastboot
and all the warning would disappear and every return to stock
diego97yey said:
How can I upgrade to the 3.1 version?
Click to expand...
Click to collapse
Just flash latest TWRP from recovery by clicking Install Image file or flash from fastboot...
x10000 said:
To return it to stock I just
1.flash the oneplus's Oxygen Recovery
2. full wipe in Oxygen Recovery
3. ADB sideload 4.0.3
4. lock oem in fastboot
and all the warning would disappear and every return to stock
Click to expand...
Click to collapse
Thanks bro ,, working Fine :good::good:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.