{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official stock Android 6.0 Marshmallow 20i files for the T-Mobile LG G4 H811 variant only. Included below: TWRP-flashable stock rom, boot, modem and bootloader zips. Stock 20i KDZ and individual images are also included.
20i NOTES...
1. *AntiRollback / QFuse V2* Safe to downgrade to 10N only.
2. Marshmallow bootloader requires bootloader unlock via fastboot
Requirements:
You must have TWRP 2.8.7+ installed to use these zip files. Thanks to Dees_Troy as always for that. Or you need LGUP installed to flash the KDZ in download mode.
Install Directions:
You can install stock 20i M with zip files in TWRP or flashing a KDZ in LGUP or LG Bridge. Due to the new 20i bootloader fastboot oem unlock requirements there is almost no benefit in using one method over the other.. both KDZ or ZIP upgrade methods work. If coming from Lollipop there is no way to retain TWRP or root since the new bootloader has a new unlock method.
To flash via zip in TWRP:
1. Download LG-H81120i-Flashable.COMPLETE.zip place it on internal or external sdcard (external preferred).
2. (re)Boot into TWRP if not there already.
3.* Backup current partitions: boot, system, data, efs to external sdcard if possible (optional but suggested)
4.* Up to you if you want to wipe data (TWRP > Wipe > Swipe slider) but not needed if coming from a stock rom.
5. Install LG-H81120i-Flashable.COMPLETE.zip (Install > select zip > swipe to confirm/flash)
6. After zip finishes you can reboot into M! (if TWRP asks if you want to install SU, HIT NO!!!)
7. If you want root or TWRP follow the bootloader unlock directions in the next section below.
To flash via KDZ:
1. Easiest way to flash the KDZ is just using the official LG Bridge tool. You can grab it for Windows or Mac HERE
2. Alternative to LG Bridge is downloading the 20i KDZ yourself from the Codefire directory link further below then following the LGUP thread HERE for a how-to on KDZ flashing. .
3. If you want root or TWRP follow the bootloader unlock directions in the next section below.
Bootloader OEM Unlock + Root:
Starting with the Android 6.0 20i bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.
1. Flash stock 20i using zip or KDZ. Boot into Android after upgrade to 20i.
2. Download the twrp-2.8.7.1-h811.img file HERE. This file needs to be on your computer and external sdcard*.
3. Download the latest SuperSu zip (2.67+) from HERE [Thanks to Chainfire] and stick on external sdcard*.
4. Confirm "OEM Unlock" is set to enabled in the hidden Developer Settings.
5. Enable "USB Debugging" in Developer Settings, connect USB cable PC <-> Phone... and send the following 3 commands in command prompt/terminal:
Code:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
fastboot boot twrp-2.8.7.1-h811.img (phone boots TWRP)
6. For perm TWRP: In TWRP hit Install > Images... (bottom right corner) > select TWRP.img on ext sdcard > select "recovery" > swipe.
7. If you want root: Hit the Home button > Install > select SuperSU zip on external sdcard > swipe.
8. All done. Reboot into Android. (if TWRP asks if you want to install SU, HIT NO!!!)
*if you do not have an external sdcard to save SuperSU and the TWRP.img onto.. you will need to skip saving the files to sdcard until AFTER you fastboot OEM unlock and boot into TWRP. After fastboot booting TWRP you can use adb push to put SuperSU and TWRP.img onto the internal sdcard to install with TWRP. Or you can use the MTP mount option in TWRP and drag n' drop the files from the computer to the phone. You cannot store the files on the internal sdcard before the OEM unlock because OEM unlock wipes all you data.
Please do not mirror my files!
Downloads:
LG-H81120i-Flashable.COMPLETE.zip
100% stock untouched system, boot, modem and bootloader.
LG-H81120i-Flashable.Modem.zip
This is a flashable stock 20i modem.
LG-H81120i-Flashable.Boot.zip
This is a flashable stock 20i boot.img. Boot.img contains kernel + dtb + ramdisk.
LG-H81120i-Flashable.Bootloader.zip
This is a flashable stock 20i bootloader. It contains aboot, factory, hyp, laf, pmic, raw_resources, rpm, sbl1, sdi, sec and tz. If you have not already unlocked the bootloader through fastboot on 20i or higher... you will need to run stock LG M to unlock before using the M bootloader on CM or AOSP roms.
Also, KDZ + all stock images for 20i are available in the link below...
CODEFIRE DIRECTORY
MD5 Sums:
Click button below to view MD5 for each file...
MD5 (aboot.img) = 1d46ac119f89e48bb5c7d412a01eaf70
MD5 (boot.img) = 01ae6bd65523428567cbd5e012b1fef7
MD5 (factory.img) = 6e2d5a6f596befbb9b4a6852712b0c6c
MD5 (H81120i_00_0201.kdz) = 21b011e8b0410b64336c40bf6817f32a
MD5 (hyp.img) = 2c633be343054a300e4c161158762db3
MD5 (laf.img) = c7b4b2e478ce4749089d07de3a0be823
MD5 (LG-H81120i-Flashable.Boot.zip) = bfa2f1b8cbb9a55af23be7ac080c1ea4
MD5 (LG-H81120i-Flashable.Bootloader.zip) = 527bb58d7f9fcbaa383c6b4500d91424
MD5 (LG-H81120i-Flashable.COMPLETE.zip) = bf9d74bb603063e3e45549e1cfef9c4d
MD5 (LG-H81120i-Flashable.Modem.zip) = 3509dda24c85cb60c07d5818823e9524
MD5 (modem.img) = 7e67c715f70b5b6d797a2c6c71247279
MD5 (persist.img) = 451427e31a42ff055adeb7364b9b927d
MD5 (pmic.img) = 27949a20917c61f9fbb296178565b4b1
MD5 (raw_resources.img) = 43d74c6229d6e4ac851844ce8933c0c7
MD5 (rct.img) = 03e489583925004bab373b4fd71ab251
MD5 (recovery.img) = 41c1d13acd617d882e8f8ac678ce3b94
MD5 (rpm.img) = 3f1c59968b8c798fbb664cd279076deb
MD5 (sbl1.img) = a7ee1a6e3370917b6b57e927b337a83e
MD5 (sdi.img) = df16bace89164b4a8ad224fb0ca4f4c8
MD5 (sec.img) = e1d32ec012c59dd9020687ea71241d1a
MD5 (system.img) = d1f18956219cfe75d0732d1ce7be31ea
MD5 (tz.img) = 0088536b7dbf8013fb49055db5410a7f
Downgrade:
To downgrade you can use TWRP to restore your backups... and then just flash the matching bootloader zip and modem zip from my previous threads... or just check the CODEFIRE DIRECTORY link for previous stock files.
OR
Use LGUP HERE to flash a previous KDZ version. KDZ will remove TWRP but easy enough to reinstall that.
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Like getting M ASAP? Enjoy flashable zips? Hit the Thanks button!
Feeling extra generous? Hit the Donate button under my name in post #2 or click my name at the top of this post.
Seems XDA removed the visible Donate button in OP. Thanks XDA...
Thank you to the following people for their donation:
@MickyFoley
@mark-e-mark
#TEAMCODEFIRE
I'll be using this space to respond to some questions rather than posting throughout the thread where others may not see it. Everything should be pretty standard at this point though. These are 100% stock files.. not debloated or deodexed or anything.
Feb 16 2016
I have edited the OP to suggest the 2.8.7.1 TWRP over the 3.0.0-0 version for now. I have had a few users in IRC tell me that after flashing 20i, unlocking bootloader, installing twrp then flashing CM13 causes some issues with data not mounting and some mention of "cannot find crypto footer". Will talk to dees_troy tomorrow hopefully and see what's what.... not sure if it's a TWRP issue.. or an LG issue or wat. But just in case.. using a known good working TWRP is the best bet for now.
Q & A:
Q:
DrakenFX said:
I know the answer but, updating via LG Bridge will loose Root/TWRP right?
If that the case which i know it is, is there a way to root in Marshmallow? Or is just safe to flash the files but stock recovery?
Click to expand...
Click to collapse
A:
due to the new bootloader unlock on 20i it is possible to flash stock unrooted 20i and then bootloader unlock and install TWRP/root. Directions for bootloader unlock are in the OP!
Wooooohooooooo
Sent from my LG-H811 using Tapatalk
This was fast!! Thank you!
i love you autoprime ! <3
Holy crap outta nowhere. Thank you auto!
Thanks. Will try tonight.
Pat
@autoprime
I'm so wanna give you a hug , been waiting for this for a while
Question..
I know the answer but, updating via LG Bridge will loose Root/TWRP right?
If that the case which i know it is, is there a way to root in Marshmallow? Or is just safe to flash the files but stock recovery?
Yes!
Thank you!
Just installed all this along with the latest xposed.
Now I have secure booting error 1003.
Wtf. I followed everything to a T how do I get back into TWRP from here?
I had OEM unlock checked before I flashed.
Raptor5150 said:
Just installed all this along with the latest xposed.
Now I have secure booting error 1003.
Wtf. I followed everything to a T how do I get back into TWRP from here?
I had OEM unlock checked before I flashed.
Click to expand...
Click to collapse
Check out this post. Stated you need OEM Unlocked in Developer Options first:
http://forum.xda-developers.com/showpost.php?p=62104913&postcount=3
Also to get to TWRP: completely shut down the phone. Remove the battery if you need to. Then when it's off, hold down Power and Vol Down buttons together. Then when the LG logo appears let go of Power Button for a second (still holding down Vol Down) , then hold the Power Button and Vol Down again. The factory reset screen comes back, click yes and yes. It will reboot into TWRP. (this is if you know for a fact TWRP is still there)
aoaleman said:
Check out this post. Stated you need OEM Unlocked in Developer Options first:
http://forum.xda-developers.com/showpost.php?p=62104913&postcount=3
Click to expand...
Click to collapse
I could have sworn I had it checked. I always have it checked.
Especially on a phone that will let me.
Now what do I do? Its just bootlooping the LG screen.
Raptor5150 said:
I could have sworn I had it checked. I always have it checked.
Especially on a phone that will let me.
Now what do I do? Its just bootlooping the LG screen.
Click to expand...
Click to collapse
You wouldn't have it checked if you flashed the complete zip above. I'm guessing you would need to wipe all (except internal and/or sd card), then reflash the complete zip, boot into system. Check OEM unlocked in Dev Options. Then reboot back to recovery, flash SuperSU.
I'm thinking this would make it work, not sure though.
aoaleman said:
You wouldn't have it checked if you flashed the complete zip above. I'm guessing you would need to wipe all (except internal and/or sd card), then reflash the complete zip, boot into system. Check OEM unlocked in Dev Options. Then reboot back to recovery, flash SuperSU.
I'm thinking this would make it work, not sure though.
Click to expand...
Click to collapse
Its bootlooping though how do I get past this?
edit: Read your edit
Coming from stock 10n, Wiped, Flashed 20i zip, flashed SuperSU -
Now i get "Secure booting error - Error Code:1003" then continues to bootloop showing that error everytime
Can't even boot into recovery, damn i'm screwed all day at work only Macs here D':
Raptor5150 said:
I could have sworn I had it checked. I always have it checked.
Especially on a phone that will let me.
Now what do I do? Its just bootlooping the LG screen.
Click to expand...
Click to collapse
You can Re-check just go to DEVELOPER OPTION and check OEM ENABLE gain
Doing the factory reset still didnt work. GOD DAMN IT.
Sigh... Phone is just a brick now I guess.
Raptor5150 said:
Doing the factory reset still didnt work. GOD DAMN IT.
Sigh... Phone is just a brick now I guess.
Click to expand...
Click to collapse
Factory Reset screens don't take you to TWRP? What happens?
aoaleman said:
Factory Reset screens don't take you to TWRP? What happens?
Click to expand...
Click to collapse
Just shows the secure boot error again doesnt load into anything. Which I have no idea how that is possible. Ill keep trying. But I hit yes and yes and then nothing. Phone reboots and keeps secure booting error.
Related
..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OTA Help-Desk
*5.1.1 LMY48B Available*
*5.1 LMY47I Available*
*5.1 LMY47D Available*
This thread is only for OTA help and nothing else!
Flash stock recovery before proceeding
.
NOTE: If You are a rooted non-stock user I suggest you look at @rootSU's thread before proceeding as his method for rooted users is far less prone to cause issues.
http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876
First, let's talk about what an OTA is:
An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have it up and running, with the latest software.
We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.
Now that you have read the important info above, Let's update your Nexus 5!
In order for the OTA to apply successfully without intervention; you must be completely stock
From 4.4.4 KTU84P
Current Bootloader: HHZ11k
Current Radio M8974A-2.0.50.1.16
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
From 4.4.3 KTU84M
Current Bootloader: HHZ11k
Current Radio:M8974A-2.0.50.1.13
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
Note: Literally any modification will break the OTA. Xposed, DPI, build.prop, volume mod, etc. ANYTHING!
Seriously, I'm not joking guys.
If you meet the above criteria, the OTA will complete successfully.
If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.
Current OTA's
5.1.1 LMY48B from LMY47D: https://dl.dropboxusercontent.com/u/33560221/OTA_update_from_lmy47d_to_lmy48b.zip
5.1 LMY47I from 5.0.1 LRX22C: http://android.clients.google.com/packages/ota/google_hammerhead/90bd789f499ea5ad33510c568ec920aae7214d34.signed-hammerhead-ota-LMY47I-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0.1 LRX22C: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0 LRX21O: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
Legacy OTA's
5.0.1 LRX22C from 5.0 LRX210: http://goo.gl/eoV0GE
5.0.1 LRX22C-from-KTU84: http://android.clients.google.com/packages/ota/google_hammerhead/6dadaf477bab65f42f5681b03bd535f431594b95.signed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
5.0 LRX21O-from-4.4.4 r2 KTU84Q: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
Thanks @pppp6071
5.0 LRX21O-from-4.4.4 KTU84P: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
Thanks @saberdragon18
4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Thanks @sucro
http://forum.xda-developers.com/showpost.php?p=46289250&postcount=1 Thanks @oldblue910
These are the most common scenarios. If you aren't sure where you fit, feel free to ask.
NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions.
Scenario #1
You are completely stock. Unlocked/locked bootloader. No root permissions.
Continue to Section A
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Scenario #3
You are stock, with Xposed Framework installed.
Continue to Section C
Scenario #4
You are stock, with a custom kernel and/or old radio and no other modifications.
Continue to Section D,1
Scenario #5
You are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.
Continue to Section D,2 or See 2nd Post (Special Scenario #1) **Special Scenario #1 is not updated yet**
Scenario #6
You are running a Custom ROM
Continue to Section D,3
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. It's attached at the bottom of this. Also Starting with Android 5.0 you must sideload the OTA through a stock recovery. Custom recoveries for now will error out.
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press and hold POWER, and then press volume up and release. The menu will appear. Select “apply update from adb
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Section C: Uninstalling Xposed Framework
Use the Xposed Framework Installer to remove the framework before applying the OTA.
Go into Xposed Framework, Framework-> Uninstall (it will restore the original file "app_process") then reboot.
NOTE: If you just uninstall Xposed Framework (the app itself), even after a reboot the "app_process" file (in /system/bin) is still the modified one by Xposed Framework, the original file is not restored.
Xposed Installer and info can be found here.
Once Xposed is uninstalled; jump back up to Section A on stock recovery (5.0 and above) and Section B on custom recovery (4.4.4 and below).
Thanks @Hammer_Of_The_Gods & @C3C076
Section D: Let’s get back to stock
1) Flash the stock boot.img and/or radio.img (whatever is applicable) from the factory image using fastboot. Also flash recovery.img if updating to 5.0
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img
fastboot flash recovery recovery.img
NOTE: Some custom kernels will modify files in /system/ If this is the case you will see a status 7 error and the file modified. The easiest way to fix this is to flash the system.img
2) Replace the stock kernel or .apk(s) you removed or modified.
If you don't have a backup of removed or modified apk(s) flash the system.img
Note: These must be the exact versions that shipped with the rom.
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
3) Flash the KOT49H stock image. Follow abaaaabbbb63's guide if you need help.
--------------------------------------------------------------------------------------------------------------------
After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:
Section A if you are running stock recovery.
Section B if you are running a custom recovery (for 4.4.4 OTAs and below only).
Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.
FAQ
Q: When in Recovery/Bootloader the phone isn't listed in Windows Device Manager.
A: Uninstall all current N5 drivers and install the Universal Naked driver. Turn on USB Debugging in Developer Settings and boot to recovery
Q: I'm seeing a status 7 error when trying to install the OTA
A: Look at the error closely. It will describe on the file it is failing at. Post the file path so we can help resolve the issue.
Q: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?
A: Flash the custom recovery of your choice in fastboot and use it to regain root permissions
Q: I've tried everything, but I'm still getting status 7 errors.
A: Unfortunately you may have to start from scratch. Follow Section C1.
Q: I flashed a .zip file that modified (insert mod here.) Will I the OTA install successfully?
A: No, any modification at all will cause the OTA to fail.
Q: Why do I get a "cannot read update.zip" error when trying to sideload?
A: If you named the file update.zip, the actual name would be update.zip.zip. Windows auto names extensions by default. That could be your problem. If not try another usb cable or a different usb port. If that still doesn't work, make sure you type exactly what you renamed the file. You may have made a typo. It is also case-sensitive.
UPDATED: 6/19/14 - Updated for KTU84P
..
Special Scenario #1
If you are running the stock ROM, rooted, with a custom kernel, and you want to retain root after the OTA; follow this great detailed walkthrough by @Lettuce!
If it helps you, make sure you thank him on the original post, located here:
http://forum.xda-developers.com/showpost.php?p=48212456&postcount=2681) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) download Latest SuperSU from http://download.chainfire.eu/supersu
5) put SuperSU.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install latest SuperSu.zip
18) clear dalvik and cache
19) reboot phoneUPDATED: 1/25/15
Good job :thumbup:Nice to see you here
Sent from my NEXUS 5
Scenario #2: Will I receive a message ?
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).
If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.
david31262 said:
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).
Click to expand...
Click to collapse
I believe the new versions of recovery will ask to keep the custom recovery and/or root. We'll see how the custom recoveries handle the OTA on the N5 and I'll update the post accordingly.
BirchBarlow said:
If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.
Click to expand...
Click to collapse
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel.
Sent from my Nexus 5 using Tapatalk
What about cf auto root? From the description it looks like that only adds the root apps and nothing else.
El Daddy said:
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel. Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.
Evo_Shift said:
What about cf auto root? From the description it looks like that only adds the root apps and nothing else.
Click to expand...
Click to collapse
BirchBarlow said:
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.
Click to expand...
Click to collapse
Cf-auto root and super su should be fine as they don't modify the kernel.
Sent from my Nexus 5 using Tapatalk
Nice!!
Every time someone mentions me, I regret choosing this username.
abaaaabbbb63 said:
Nice!!
Every time someone mentions me, I regret choosing this username.
Click to expand...
Click to collapse
Yeah, I regretted mentioning you.
Thank you copy & paste.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.
maxal said:
Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.
Click to expand...
Click to collapse
As long as everything is stock an unlocked bootloader does not effect an OTA.
Sent from my Nexus 5 using XDA Premium 4 mobile app
El Daddy said:
Nexus 5 OTA Help-Desk
Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C
Scenario #4
You are running a Custom ROM
Continue to Section C
Section C: Let’s get back to stock
You have two options to do this:
Option #1 Flash the KRT16M stock image. Follow @abaaaabbbb63 guide if you need help.
If you want to keep data intact flash only the boot.img, system.img, and recovery.img (optional)
OR
Option #2 Replace the stock images or .apk(s) you removed or modified.
Note: These must be the exact versions that shipped with the rom.
Click to expand...
Click to collapse
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.
Synyster06Gates said:
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.
Click to expand...
Click to collapse
That is correct.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
That is correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did it... everything booted correctly, my apps and settings were still there, but for what ever reason - my APN settings will not stay. I save it, and it takes me back to an empty menu. Any ideas?
Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Tried that. Says it's done, nothing comes up.
I tried searching for network as well but that didn't work either. The wifi works, but no network.
I restored a backup I made last night and it still isn't working. Any ideas?
Tried to do a system wipe then restore again
E: Unable to mount '/cache'
Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed it. I went ahead and flashed the stock cache.img as well and all is working. Some how I guess the cache corrupted or deleted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRODUCTION
I'm providing a set of files that allow you to unlock your bootloader or recover from the closest thing you can get to a hard brick.
MiFlash is capable of flashing anything to your phone while it is in Emergency Download mode.
Yes, this is voodoo magic and it works! Recover from any and all bricks! Some might call it necromancy.
However, it can be also be used even if the device is perfectly alright to simplify upgrading procedures and make ROM flashing fairly painless.
This is for A2017U (North America) and A2017 (China) models only! Do not attempt this on A2017G.
INSTRUCTIONS
If you are flashing TWRP on a locked bootloader, you must first enable OEM unlocking on your device.
You can do this by navigating to Settings -> About phone -> Tap "Build number" 7 times.
Now navigate to Settings -> Advanced settings -> Developer options -> Enable "OEM unlocking".
Follow the steps below with the FASTBOOT_UNLOCK package first, then go into fastboot mode and use the
"fastboot oem unlock" command to unlock (and wipe) your device. Download adb and fastboot below.
Install the Qualcomm QUSB_BULK drivers from below.
You should be able to simply extract them, then right click qcser.inf and press Install.
If you don't have this option, then use devmgmt.msc (Device Manager) to update the driver after entering EDL mode by
selecting manual install and browsing to the qcser.inf file there.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Now install MiFlash (download below).
Open MiFlash and use the [select] button to select the A2017U_*_EDL folder package that you wish to flash.
Boot into EDL mode. (hold Volume Up + Volume Down + Power until you're stuck on a black screen)
Now just hit [flash] - watch the progress bars move and wait for the device row to turn green with flash complete!
If you are flashing TWRP, use the [Power] + [Volume Up] key combo to exit EDL mode and enter recovery. Release the keys when you see the ZTE logo.
You must have an unlocked bootloader to enter TWRP!
If the flash fails or is unable to communicate with the device, use the [Power] + [Volume Up] + [Volume Down] key combo to restart EDL mode.
Release the keys after 5 seconds then wait another 5 seconds before using the [refresh] or [flash] buttons on MiFlash.
EDL PACKAGES
FASTBOOT_UNLOCK
This will unlock all fastboot operations, including OEM unlock and fastboot boot/flash.
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Click here to download! (ZIP, 195.8 KiB)
B29_TWRP (Marshmallow 6.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B29 boot stack.
Click here to download! (ZIP, 59.4 MiB)
B15-NEW_TWRP (Nougat 7.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B15-NEW boot stack.
Click here to download! (ZIP, 60.6 MiB)
B15-NEW_FULL (Nougat 7.0)
This will install the entirety of the B15-NEW firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
B19-NOUGAT_TWRP (Nougat 7.1.1)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B19-NOUGAT boot stack.
Click here to download! (ZIP, 61.0 MiB)
B19-NOUGAT_FULL (Nougat 7.1.1)
This will install the entirety of the B19-NOUGAT firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
TOOLS
Xiaomi MiFlash Installer
Version: 2016.08.30.0
Click here to download! (MSI, 31.0 MiB)
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click here to download! (ZIP, 2.7 MiB)
ADB & Fastboot
Visit the SDK Platform Tools download page
Using this, you should safely be able to recover from any brick!
Once in TWRP, you can flash a full OTA or restore your backups and be on your way.
It is tested and working on Windows 10 64-bit.
All zips are signed with Android SignApk and can be verified with TWRP. (they won't install, just say it's not a valid zip after verifying)
A2017 (China) can use this to convert their phone to A2017U if they want. DO NOT flash on A2017G.
POSSIBLE ISSUES & SOLUTIONS
OTA update zips may fail in stock recovery even after flashing FULL EDL packages. This is because MiFlash does not erase blocks before writing the system image. You can run this command from TWRP terminal or adb shell to erase system partition before flashing the EDL package:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/system bs=272144
Once this is done, OTA zips should succeed in stock recovery after flashing a FULL EDL package.
CREDITS
This was based on the A2017 B07 EDL zip provided by @tenfar at this XDA thread.
HISTORY
2017-04-10 - Added B19-NOUGAT FULL and TWRP package
2017-02-11 - Added B15-NEW FULL signed OTA capable package
2017-02-11 - Added fastboot operation unlock package
2017-02-11 - Separated MiFlash, Qualcomm QUSB_BULK Driver, and EDL packages, removed 7z archives
2017-02-09 - Added B15-NEW TWRP package
2017-02-09 - Added B29 TWRP package
Any idea if this will work with Nougat or not?
neo4uo said:
Any idea if this will work with Nougat or not?
Click to expand...
Click to collapse
It will work on Nougat, however, you will end up on B29 bootloader. You'll need to flash B29 full and upgrade again.
I am having some weird issues with Nougat boot stack flashing + TWRP so I'll hold off on posting a B15-NEW version of this for now.
Update: You can now flash the B15-NEW TWRP package instead.
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Situation: A2017U full stock in Nougat no unlocked bootloader, no root
Want to: Install LOS because i HATE this bullsh... called MIFAidonotknowWTF
Can i use this procedure to do that?
Thanks a LOT
So basically, MiFlash just lets you firehose in any file to a QualComm device from EDL mode? That's pretty handy.
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Snaptraks said:
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Click to expand...
Click to collapse
It is softbrickable by adb commands... I have one device in boot loop.
trying to wrap my head around this whole bootstack/fastboot issue we have with the a7.
So in theory one could use this tool and then unlock (or just have working fastboot) directly from b15?
Then download the bootstack from los thread and be good to go? Or would that bork fastboot again...
I think I am currently running b20 bootstack on b15 by flashing draken's unlock zip without issue (that I know of) but am considering flashing the N version from los thread.
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
KwesiJnr said:
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
Click to expand...
Click to collapse
Have fun! Nougat images are now up!
jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Altomugriento said:
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Click to expand...
Click to collapse
step 2.5) reboot to bootloader from recovery
step 4) wipe system in twrp
step 6) use the [Format Data] button on wipe page of twrp (lineageOS may not be compatible with your current encryption, this will wipe all your settings and internal storage)
and yes that's everything, I believe.
Sticky. Nuff said.
Dev is finally taking off on this phone, thanks to literally 4 or 5 key people. I was afraid I'd made a mistake purchasing instead of O+3, but has worked out well.
Thanks for all your help in your free time.
DrakenFX said:
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Click to expand...
Click to collapse
Thanks buddy, that keymaster -> xblbak appears to have been my issue! So illogical.
I compiled applypatch and used that to apply the B29_TO_B15-NEW .p files to my B29 binaries so they should be nice and exact. (sha1 matches from updater-script)
I can provide a full B15-NEW verity/OTA update friendly package if somebody wants. Just let me know.
Flash Done.
But i can't join to TWRP, it just turn it self off.
Eroticus said:
Flash Done.
But i can't join to TWRP, it just turn it self off.
Click to expand...
Click to collapse
If you are not unlocked you now need to go to fastboot mode and unlock before you can enter TWRP.
If you just mean the screen is still black, you have to hold volume + power up after flashing until it starts up, then let go when you see the ZTE logo.
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock, rooted and fastboot working N B15 build?
Thanks
khangozzy said:
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock and rooted N B15 build?
Thanks
Click to expand...
Click to collapse
Look up a couple posts.
jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Because it had been reported that this was impossible, or at least very difficult, I wanted to clarify whether this means people with locked bootloader running N can now unlock and install TWRP?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some china OP5 user got it from OnePlus staff, and uploaded it to china cloud drive.
[Driver]
Mega:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=889764386195921378
[Oxygen Version Download]
After you use this tool, your OP5 will be restore into stock Oxygen OS.
Mega 1:
https://mega.nz/#!MPBXkJjK!O2uDD7Xx04KPT_cx9coMHnGtaeSK06t9gwNpUR4KDXE
Mega 2:
https://mega.nz/#!gjRFmB4C!-HN00YSS2tUy5ZQTbJbzwEmZ8VU_iv5lLaTlbXin7Ec
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=745425885120760474
[Hydrogen Version Download]
After you use this tool, your OP5 will be restore into stock Hydrogen OS.
Source :
http://www.oneplusbbs.com/thread-3587805-1-1.html
Baidu pan:
http://pan.baidu.com/s/1qYz7hZu
pwd: 0fb4
Mega (corrupted):
https://mega.nz/#!kyJ1XJ7D!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Mega 2:
https://mega.nz/#!RmQnQKTB!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Google Drive:
https://drive.google.com/file/d/0B9vxnq7dlG4pYVJGaGZOYWNuZzA/view?usp=sharing
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?w=files&flid=204903
[Tutorial]
The steps is the same as 1+3T.
Ref:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Great ! I always prefer a fastboot / edl flash.
Sent from my ONEPLUS A5000 using Tapatalk
Isn't it Oxygen OS?
gonsa said:
Isn't it Oxygen OS?
Click to expand...
Click to collapse
Yes,it isn't.
However you can easily install Oxygen OS by yourself.:laugh:
Ref:
https://forum.xda-developers.com/oneplus-5/how-to/guide-installing-oxygenos-chinese-t3647409
Someone should be able to tweak this to fetch OOS files instead of H2OS. Both the firmwares are the same except userdata
Sent from my ONEPLUS A5000 using Tapatalk
Someone should upload this to androidfilehost so there are other places to download incase the original is taken down.
file in mega is corrupted.
please upload in any uploading site
@snowwolf725 ,since I already "came back" from fastboot-ed github/OOS/MSM8998 build, I like to clarify few tips:
-Unbrick via Qualcomm QFIL tools were well documented here and there (Oneplus 1/2/3/3T) ; but Qualcomm never granted free distribution of QualcommQDLoader9008 DRV or QFIL, AND your WindowsPC has to be disabled with integrity checks or antivirus. So it should be considered as the last extreme ultimate rescue.
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.
@oF2pks if I get your process correctly, for a clean flash, Flash all needs to be done 3 times with the stock recovery followed by OEM lock and post that the last step is to fastboot erase boot/system/user data/cache followed by adb sideload of the stock firmware?
Sent from my ONEPLUS A5000 using Tapatalk
On this subject, we need a return to stock guide for the OP5 :good: Fine writeup oF2pks! :highfive:
oF2pks said:
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.
Click to expand...
Click to collapse
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!
TwinAdk said:
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!
Click to expand...
Click to collapse
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
File in mega is corrupt please re upload
hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu
Sir link is not visible
Link is not visible
hsareminia said:
file in mega is corrupted.
please upload in any uploading site
Click to expand...
Click to collapse
sanjeevattre said:
File in mega is corrupt please re upload
Click to expand...
Click to collapse
hsareminia said:
hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu
Click to expand...
Click to collapse
I add new mirror links and dirver download link.
Driver:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ
jasonwsc said:
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
I am aware that the process above is HIGHLY complicated - and is often not necessary.
At the time of my post, my phone was in a state where I had been doing crazy things with it (decrypted data, multiple custom ROMs and TWRP versions, including multiboot variants and the chinese one. On top of that I had flashed the am-verity and force decryption patch zip). This is as such not unusual, but my attempts to return to stock had failed (stock ROM zip failed to flash, stock recovery were wierd as well).
Therefore, when the quick layout for COMPLETE STOCK were outlined above, I grabbed them and did the process, while documenting it for future reference for others. Also, I choose to include the oem unlock and lock part - though I am fully and completely aware that it's unnecessary to 99% of the readers, after all this is One Plus phones
I had not been able to find any other sources of the steps outlined, though they may be simple, so I took all the steps how ever overkill they might be, because then there would be a documented process
The steps above would recover a One Plus 5 from a state where only adb works, pretty serious condition indeed....
I'm staying on OOS based custom ROMs as long as the blobs for the camera is undisclosed by One Plus. I haven't had time to reply to this sooner, have a great weekend, and @asonwsc, I agree with you :highfive:
Kind Regards
TwinAdk
jasonwsc said:
...If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.... flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )
oF2pks said:
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )
Click to expand...
Click to collapse
But if the device is considered certified on the play store, then it passed SafetyNet without an issue.
Correct me if I'm wrong, but shouldn't SafetyNet pass under the following conditions?
1. Locked bootloader with no root (stock)
2. Unlocked bootloader with Magisk root.
Is it actually possible for a locked bootloader and unrooted phone to fail SafetyNet? You can't root without the unlocking the bootloader, so how would that trigger SafetyNet?
Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome ?
Any chance on doing a full backup before installing TWRP, as I don't have a default recovery of 1.18.400.20 dugl dual sim and still hope for OTA?
I hoped for "fastboot boot recovery" but I think only with nougat firmware was reimplemented.
Thanks
I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?
FireStorm919 said:
I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?
Click to expand...
Click to collapse
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...
process failed
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.
david_montes said:
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.
Click to expand...
Click to collapse
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck
Fain11 said:
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck
Click to expand...
Click to collapse
I did try to uninstall magisk but it gets stuck in the boot process (only htc logo), the same thing happens with the backup I made with twrp (only htc logo), the best result so far is applying magisk to the boot, then the system starts but keeps asking me to decrypt the storage, the exact message is "The password you have entered is correct, but unfortunately your data is corrupt" I did factory reset but does not solve the problem, it keeps asking for the password.
Also RUU for my OS-2.13.709.20 is not available so I'm currently stuck.
These things get harder and harder every day
Desire 10 Pro recovered
Finally the last option was to fully stock flash with RUU 2.13.709.20, but now I am back to step one.
At least it works
---------- Post added at 04:20 PM ---------- Previous post was at 04:08 PM ----------
Been human means to keep trying, so I tried again, now I did full factory wipe before applying supersu 2.82 (not working) or magisk 15 (works but keeps asking for a password to decrypt storage).
So I can confirm this procedure does not work with OS-2.1.3.709.20.
If any of you is able to root this version I will be glad to try again in the future but by now I'm done with htc 10 pro.
Happy new year everyone!
thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help
thekingomar said:
thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help
Click to expand...
Click to collapse
It has been confirmed to be working on 1.18.400.20
Please make a backup before u try because this doesnt seem to work on newer ones like 2.13.709.20
Please leave a reply here if u get it working.
?
Fain11 said:
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...
Click to expand...
Click to collapse
Sorry for the delay,
I couldn't find that link either so I extracted it from a RUU for variant a56dj_pro_dugl
Here you go
https://drive.google.com/file/d/1FxKDDOXISNTf5uQJT90nlw6tuClJaX9o/view?usp=drivesdk
Hope this helps
???
thanks for the guide again,
after pulling my courage together I decided to do it on my a56dj_pro_dugl software number 1.18.401.20
everything worked fine from the top to step 14 but there is one problem, flashing the SuperSU zip file is failed,
I tried to re-download it and not renaming it but still the same, here is the log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any suggestions ?
never mind
just rooted it using Magisk , apparently SuperSU is not applicable on my device
I used the same method as SuperSU zip
downloaded the latest version of Magisk (v 15.3) zip file and install it using TWRP
and everything is fine ever since
thanks folks for being awsome developers :laugh:
Required Video
Hi Member,
Can you please upload step by step video for root the HTC Desire 10 pro.
waiting
warnning !!! htc desire 10 pro os 2.13.709.23 taiwan
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!
Mykyzo007 said:
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!
Click to expand...
Click to collapse
Did you manage to unbrick?
yes
dearbasheer said:
Did you manage to unbrick?
Click to expand...
Click to collapse
yes i manage to unbrick, i'am waiting to see the rom .
But i need help
Unable to flash recovery
When unlocking bootloader I selected any other supported since desire 10 pro isn't listed. Process went through but when flashing twrp I'm getting error. Commad not allowed whereas it shows unlocked
FireStorm919 said:
Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome
Click to expand...
Click to collapse
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot
Sangam IME
seyyed.april said:
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I havent checked my inbox for quite some time.
I searched around for this Sangam IME everywhere in,
/system/app
/system/priv-app
/data/app
/data/app-private
But I couldnt find it. I even tried using 3rd party apps like you suggested but it simply doesnt seem to exist.
Even a quick Google search didnt give me any leads.
So are you sure the name is correct ?
Or maybe any more ideas on where to look for the apk ?
Sorry I couldnt be of more help
Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
158 views, 20 downloads and not one reply.
Smashing guys. :good:
4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?
Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!
notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.
It will not work on SM-A750FNXXU1ARIC?
Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse
sorry
ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542
ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop
A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes
A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?