Related
I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THIS GUIDE.
This is primarily for D802 users. However, people with other variants have had some issues and asked for help, so I have added some files here to help them as well.
PREREQUESITES
1) You must be rooted.
2) Then download one of the following files:
2.6.3.3
IMG
Download the D802 img file here.
Download the AT&T img file here.
Download the VZW img file here.
AUTO
Download the automated D802 file here.
Download the automated AT&T file here.
Download the automated VZW file here.
ZIP
Download the ZIP if flashing from a different TWRP version, or CWM: D802, AT&T, VZW
NOTE: If USB-OTG does not seem to be working on TWRP 2.6.3.3, please revert to 2.6.3.2. if this feature is needed.
Themes - Samurai Champloo
Download the theme itself here.
Download the Flashable ZIP of the theme here.
Download the Flashable D802 TWRP 2.6.3.3 and theme here.
2.6.3.2
Download the D802 img file here, or the latest official software F320K img file here.
Download the automated D802 file here, or the latest automated official software F320K file here.
Download the ZIP if flashing from a different TWRP version, or CWM: D802, F320K, TMO, VZW
INSTALLATION
Auto-Method
1) Extract the contents of the RAR file.
2) Double-click "Install.bat".
3) Prompt will open, click any button to proceed.
4) RSA Fingerprint message will appear on the phone (accept).
5) After installation procedure, type "y" and press enter to reboot into recovery!
1st Manual Method: Initiate ADB and use the following code.
Code:
[COLOR="DarkOrange"]REPLACE "XXX" WITH THE ACTUAL IMG NAME! DO NOT TYPE THE ORANGE WRITING![/COLOR]
adb push XXX.img /data/local/tmp/XXX.img
adb shell
[COLOR="DarkOrange"]IF YOU DONT SEE A # prompt, type su to get it.[/COLOR]
cd /data/local/tmp
dd if=/data/local/tmp/XXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[COLOR="DarkOrange"]Be sure to replace "data/local/tmp" with the actual place your img is stored.[/COLOR]
exit
adb reboot recovery
2nd Manual Method: Place the img on your phone, then use a terminal emulator app with the following code.
Code:
[COLOR="DarkOrange"]REPLACE "XXX" WITH THE ACTUAL IMG NAME! DO NOT TYPE THE ORANGE WRITING![/COLOR]
su
dd if=/data/local/tmp/XXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[COLOR="DarkOrange"](Be sure to replace "data/local/tmp" with the actual place your img is stored.)[/COLOR]
Optional Method: If you want to run some safety checks first, use loki [method here as first option].
INSTALL THEME MANUALLY
1) Connect your phone to your PC.
2) Go into your "internal storage" (internal SD card).
3) Find and open the TWRP folder.
4) Add a folder called "theme".
5) Place the ui.zip into the "theme" folder.
ENTER RECOVERY
Method 1: Hold the power button + volume down button until the LG image appears. Once it does let go of the buttons then immediately push and hold them again until recovery boots.
NOTE: The method above will arrive at the "hard reset" area, but when choosing hard reset, it will take you to TWRP (without actually resetting).
Method 2: Download the free app "Rebooter" from Google Play. If you have root, you will be able to select to reboot into recovery (among other options).
SLOW WIPE CACHE FIX
1) Once in TWRP, go into Settings.
2) Check off the box, "Use rm -rf instead of formatting."
3) Go back and now go into Wipe.
4) Wipe Cache (or another option with wiping cache).
Credit: Credit goes to Dees_Troy and wolfgart, djrbliss who made all recoveries for this phone possible, WACOMalt for his steps, and thecubed for his auto-install code.
USB-OTG
To access USB-OTG devices, go into the desired area (Install, Backup, or Restore). Select "Internal Storage" at the top. Press your USB-OTG device. It may take a second to show as selected on the screen. Once selected, press OK.
If your device does not show up, you can first try going to Mount and check off the USB-OTG box. If it doesn't allow you to check the box, then it doesn't support that device.
NOTE: It may not work with OTG cables and USB devices...
MISC.
Folder Name - There is an "issue" with the date and time [1970]. This issue is reflected in the backup folder names. There are two options to change a backup folder name:
Go into recovery and select Restore. Select the folder you wish to rename. There should now be an option to change the backup folder name.
Go into your TWRP folder by connecting to a PC or using a file explorer and change the backup folder name.
Time Zone - The time zone may be wrong but can be changed in Settings.
SUPPORT
Please check previous posts to see if your question has been answered prior to posting (there is a good chance it has).
Please always include with whether you are rooted or not.
Please always include the variant you are using.
Please always include the method you used.
Please always explain what happened in as much detail as possible.
Anything else that may be relevant.
Otherwise, you might have to wait for others to help you...
now for the mods and custom roms (hopefully kernels too)!!!! Thanks bros!
Thank you for all built hardwork. Was waiting for this.
-LG G2
Thank
Sent from my LG-D802 using Tapatalk 2
Thank you ! Flash successfull on my D802.
But when I want to wipe cache + dalvik cache, it stay on "wipe cache", it's normal issue ?
When I used Wipe Cache it took a long time to finish.
Ok thank you
Like 10 minutes or more ?
Envoyé depuis mon LG-D802 avec Tapatalk 4
I don't recall the exact time, but I would say at least 10 minutes.
Heatshiver said:
I don't recall the exact time, but I would say at least 10 minutes.
Click to expand...
Click to collapse
I have the same. But its not 10min. It is one min. Maximum two.
Sent from my LG-D802 using xda app-developers app
cosmique said:
I have the same. But its not 10min. It is one min. Maximum two.
Click to expand...
Click to collapse
I've noticed the time changing for certain things. One restore I did took nearly 30 minutes! I did restore after that took less than 10. As long as it works, that's all that matters! :good:
I'm on a Recovery Loop. Selected Reboot > System and it keeps rebooting to TWRP.
Used Flashify btw.
m0ngstr0us said:
I'm on a Recovery Loop. Selected Reboot > System and it keeps rebooting to TWRP.
Used Flashify btw.
Click to expand...
Click to collapse
Did you have a recovery before this installed? If so, what recovery? Did you have a good WiFi connection when you downloaded the file (i.e @home, @restaurant, etc.)? Did you try any other methods before flashify?
This should be fixable in either case. If you have a backup from before, I suggest restoring. If not, then you may have to follow this guide to unbrick your phone.
Oddly enough, I'll be in Singapore tomorrow, but I won't be able to reply until late night.
Works perfectly. Thanks!
Sent from my LG-D802 using xda app-developers app
Heatshiver said:
Did you have a recovery before this installed? If so, what recovery? Did you have a good WiFi connection when you downloaded the file (i.e @home, @restaurant, etc.)? Did you try any other methods before flashify?
This should be fixable in either case. If you have a backup from before, I suggest restoring. If not, then you may have to follow this guide to unbrick your phone.
Oddly enough, I'll be in Singapore tomorrow, but I won't be able to reply until late night.
Click to expand...
Click to collapse
Heya! Restoring as we speak. Home networks pretty stable.
Currently downloading the firmware. I can see that the system was not mounted on TWRP. Hence the Recovery bootloop.
Jumped from the Samsung era, gosh I didnt know LG doesnt have much support.
Once back up, bahhh imma just remain stock till more Devs pops up.
Cheers man.
m0ngstr0us said:
Heya! Restoring as we speak. Home networks pretty stable.
Currently downloading the firmware. I can see that the system was not mounted on TWRP. Hence the Recovery bootloop.
Jumped from the Samsung era, gosh I didnt know LG doesnt have much support.
Once back up, bahhh imma just remain stock till more Devs pops up.
Cheers man.
Click to expand...
Click to collapse
Feel free to try CWM, it's much easier to install, and also has a touch-interface.
Heatshiver said:
Feel free to try CWM, it's much easier to install, and also has a touch-interface.
Click to expand...
Click to collapse
I need sleeppppp ~ T.T Lol! Its 1:14am here man. Getting up at 6am later. Prolly another round (with CWM) over the weekends!
I travel to the airport in 4 hours, no rest for the wicked!
Heatshiver said:
I travel to the airport in 4 hours, no rest for the wicked!
Click to expand...
Click to collapse
Just want to check the link is still up, as i'm getting a dead page on the file.
Edit: Ignore the above, i couldnt get online at all. Rebooted and now all ok. Used Flashify to backup original and then flash TWRP.
Thanks
Sent from my LG-D802 using Tapatalk 4
can i use this method to upgrade from twrp 2.6.3 to 2.6.3.2 ?
j_h3000 said:
can i use this method to upgrade from twrp 2.6.3 to 2.6.3.2 ?
Click to expand...
Click to collapse
Yes. I have done so.
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse
Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG G5.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available guides below:
Guides:
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_1
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_2
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Re-install_STEP_3 <------ If you want to re-install stock MM 6.0.1 with root
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Upgrade_only_STEP_3 <------ If you want to root current stock MM 6.0.1
Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 <------ If you want to have stock MM 6.0.1 only (no root, use this if you want to return the phone or sell it)
They will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on File Transfer mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
You read the Useful tips & information for the T-mobile LG G5 post
You read the Changelog + News & Additions post
***Un-root***
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Disclaimer***
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
If possible use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people for making all of this possible:
tungkick
wolfu11
arjuna_
Your work and dedication does not go unnoticed, thank you. I would also like to thank anyone else not mentioned here that allowed the rest of us to get root on our beloved LG G5 phones. The android community is awesome!!!
Sections:
Post#1: Main introduction & Files
Post#2: Useful tips & information for the T-mobile LG G5
Post#3: Changelog + New & Additions
Please leave a thank you if you find any of this helpful
**Useful tips & information for the T-mobile LG G5**
How to install xposed: (Keep in mind that versions will change over time)
Download the latest xposed framework currently (xposed-v85-sdk23-arm64.zip):
- Go to the following web address: http://dl-xda.xposed.info/framework/
- Click on the sdk23 link
- Click on the arm64 link
- Download the latest xposed zip file currently xposed-v85-sdk23-arm64.zip
Download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk):
- Go to the following web address (xda thread): http://forum.xda-developers.com/showthread.php?t=3034811
- Scroll down to the "Attached Files" section and download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk)
Copy both files to the SD-CARD of your phone
Restart your phone into TWRP
Click on the INSTALL button
Flash the xposed framework file (xposed-v85-sdk23-arm64.zip)
Restart your phone and let it start normally
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and make sure there is a check mark next to Unknown Sources option
Open a file manager
Go to the location of the xposed apk
Install the xposed installer .apk file (xposed Installer 3.0 Alpha 4 apk)
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and remove the check mark next to Unknown Sources option
Start the xposed app
How to enter download mode
Power off the phone
Press and hold the VOLUME UP key
Connect the phone while holding the VOLUME UP key to your PC (use a USB-C cable)
Keep holding the VOLUME UP key until you boot into download mode
How to fix the Fastboot device driver issue (no devices detected)
Visit the following website and follow the instructions: Manually installing Android ADB USB Driver
**Changelog + News & Additions**
Changelog (for the guides only):
7.16.16 - All guides have been updated to reflect the new 10d .kdz and .tot files. All links to tools, .kdz, and .tot files have been updated as well.
News & Additions:
7.16.16 - Multiple updates
A modified H83010d rooted .tot file has been released (thanks to Tungkick & wolfu11)
Guides are safe to use again. All links in all the guides have been updated to reflect the new H83010d files
If TWRP is not showing the internal storage but only the external SD-card take a look at post 24
7.9.16 - There is a new firmware update (H83010d) for the LG G5 (T-mobile) which is not compatible with firmware (H83010a) the .TOT files used in this thread have
If you upgrade to this new firmware, you will lose root.
There is no current way to get root on the new H83010d firmware unless the modified .TOT / KDZ files are released with TWRP included
There is an anti-rollback feature in the LG G5 (t-mobile) phone that prevents you from flashing back the H83010a firmware after you upgrade to the H83010d firmware. Attempting to do this WILL BRICK your phone!
Do not attempt to use the guides which are using H8301a .tot / kdz files if you have updated to H8301d. I will be updating the guides as soon as the H83010d modified .tot / kdz files come out.
5.29.16 - LG G5 & LG V10 possible driver issue: First reported on Post#6
If you own an LG V10 and have used your PC to root it, you most likely installed drivers, tools, and or files specific for the V10. What this means is that you may have to uninstall those drivers, tools, and or files prior to installing anything to be used for rooting the G5. This does not include the ADB program which can work for both.
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
mallman said:
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
Click to expand...
Click to collapse
Thank you.
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
Two questions:
1) Does this automatically encrypt the phone? After flashing both the no verity and the SU it boots in to "encrypting" with no other option. I have not had this happen with any other device. Did I mess something up?
2) The password at the beginning of TWRP is requested every time, even after flashing the no verity zip. What did I do wrong?
Click to expand...
Click to collapse
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Thank you for your input skyfox99. Your solution to the issues you faced will help others avoid them. You made me think of something I did not anticipate which is what happens when you attempt to root your G5 using the same PC you used to root a V10. I am definitely adding a service announcement to the Changelog (post#3) to address this possible issue.
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
bigchuq said:
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
Click to expand...
Click to collapse
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Your internal storage gets wiped. That's why they weren't there.
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No I was not, I'll give it a shot. Thanks
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
mikeyinid said:
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No, I copied after wipe so they were there. Computer recognized them and so does file manager.
jun19inf said:
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
Click to expand...
Click to collapse
TWRP has trouble mounting.
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
There is a TWRP bootloop set of instructions in another thread, run those commands and see if it resolves it, maybe?
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
I had to reflash no verity a few times, before installing SU. There seems to be a problem with TWRP.
Sent from my LG-H830 using Tapatalk
I didn't have any of the issues you guys are reporting in this thread. TWRP sees both internal storage and SD card. And has since I originally rooted.
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
shaneg79 said:
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
jun19inf said:
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
Click to expand...
Click to collapse
It's ok I found out it doesn't affect it thanks for your answer.
Sent from my LG-H830 using XDA-Developers mobile app
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
rebelde80 said:
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
Click to expand...
Click to collapse
It's a very weird problem and unfortunately the only thing I can think off is that TWRP might not be compatible with the SD-Card you are using.
Hi All!
As plenty of people know by now that the latest modified twrp that we have does not work with encrypted storage when flashing official nougat oos. And there must be many people like me who due to reasons dont have time to copy n move everything back or don't want to decrypt their storage. So me and all of op3 community would appreciate if anyone can take some time out of their schedule and build an updated twrp version so that we can flash official nougat without screwing with storage or encryption. Because nougat is the future now and we'll start receiving nougat update from now onwards. And its a shame tha such an active dev device like op3 does not even have an updated twrp version. Thanks!
+1
A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.
AcmE85 said:
A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.
Click to expand...
Click to collapse
Totally agree to that. I was also assuming that an updated kernel sources are required to build a compatible twrp recovery for nougat. Waiting eagerly for the same. And considering the feedback of people on official OOS, i don't feel it's really a must have update as of now.
I also agree to the point about users. People need to stop taking developers for granted, and give them their space to release updates, and they should understand the dev is doing this in his/her free time not as a full time job. I hope we'll see an updated TWRP soon. Until then, MM is serving me well. No hurry
He is only asking, stop crying dude
To many ladies with balls here
fanbogo said:
He is only asking, stop crying dude
To many ladies with balls here
Click to expand...
Click to collapse
Sorry for the confusion what is it intended for me?
TWRP password, please help.
As first i wasn't able to flash any twrp files at all as after flashing it shows some black screen so not even from the official TWRP site the files were helpful, then after ages of serching I found some thread in XDA where a guy posted the link to this twrp https://forum.xda-developers.com/on...nity-build-t3461648/post68691560#post68691560, then I was able to successfully install it and boot into TWRP recovery.
So here I am now stuck with the ****** password to decrypt data and I simply want to root my OP 3 but due to this situation I am unable to so any solutions on this will be much helpful and any way to remove the dumb password for the TWRP.
Thanks.
Dude even if twrp shows encrypted you can still flash supersu. Just mount the /system partition in Mount options and flash supersu via otg.
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
Connect your phone to your pc, boot TWRP via fastboot from the PC and flash SuperSu via adb under advanced in TWRP.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.
samyj22 said:
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.
Click to expand...
Click to collapse
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.
AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?
AcmE85 said:
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.
Click to expand...
Click to collapse
Just a little confusion, as the internal storage is the same as root directory or the one level back to the SD card is the root directory?
abhibnl said:
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?
Click to expand...
Click to collapse
Yes you can directly sideload.
Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful...... ?
samyj22 said:
Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful......
Click to expand...
Click to collapse
Mount system in recovery,
adb sideload sample.zip
adb push <source-path> <target-path>
If file is in the adb folder already, then
adb push sample.zip /system or whatever path you want to send it to.
Edit: While pushing, make sure you mount system as RW first. But i guess when you mount system in TWRP, it's automatically in RW mode. But please do check with someone who has done it or an expert. I have limited knowledge, so sharing as far as i know
abhibnl said:
Mount system in recovery,
Click to expand...
Click to collapse
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.
acetone802000 said:
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.
Click to expand...
Click to collapse
Do you have all those 3 options in the mount menu? I don't think that should be there. I'm sorry, your statement is a bit unclear actually.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!