Related
I flashed a verizon rom on my atnt phone I can no longer go into recovery nor can I go into the rom I tried sideload didnt work I havent tried ruu because I cant find it for atnt please somebody tell me what I can do I know im a dumass for this but please tell me!!
Wont go into bootloader...you may have a brick on your hands.
Tak23 said:
I flashed a verizon rom on my atnt phone I can no longer go into recovery nor can I go into the rom I tried sideload didnt work I havent tried ruu because I cant find it for atnt please somebody tell me what I can do I know im a dumass for this but please tell me!!
Click to expand...
Click to collapse
Slow down and take a breath. Does the screen come on at all; and/or do you get the charging LED if you put the phone on the wall charger?
You also say you tried sideload; which if you are talking about sideloade flashing a ROM, that contradicts the statement that you can't get into recovery (need to be in TWRP and in sideload mode to do this).
---------- Post added at 10:25 AM ---------- Previous post was at 10:05 AM ----------
I see from your other threads (please don't "cross post" or create multiple posts for the same issue) that your screen comes on. Therefore you are likely not bricked.
Try to wipe cache and flash recovery via adb. RUU should also get you back up and running, but you need to either relock the bootloader or be s-off. And I honestly don't think you need to RUU (especially if it means you need to go through the hassle of relocking the bootloader, just to unlock it again later after the phone is running).
I see form your "other" posts you found the RUU link. But there is no way we would know that from this thread. A good example of one of the many reasons why cross posting is confusing and counter-productive.
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
part fixed
graminou said:
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
Click to expand...
Click to collapse
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
graminou said:
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
Click to expand...
Click to collapse
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
corkiejp said:
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA[/URL] again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
Click to expand...
Click to collapse
Hi corkyejp and thanks, i was aiming to go back to current supported not the beta N release, I officially unenrolled received the OTA image, installed, got stuck in bootloop, tried sideloading MOB30G which i beleive was the correct wifi not LTE version (I saw that version mentioned in my crashlogs too). the device was in developer mode, I think but am not sure, however the HBOOT screens always showed LOCKED. i tried the fastboot flashing unlock (and OEM unlock options) but neither unlocked me. anyway at least I have a device that boots now, will put up with crashes if they occur. thanks again
If you are not an H918, H830, or US996 (Unlocked, NOT US Cellular) user, kindly leave this thread, this will not do anything for your device, exchange it if you're so desperate. Thank you.
Note for US996: It's probably easier for you guys just to flash TWRP the normal way and pull your battery then do the factory reset dance to get in!
Team Win Recovery Project 3.0.2-1
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
This will allow you to install TWRP and flash SuperSU!
Step 1: Unlocking your bootloader
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
H918/H830 users only:
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You will probably need to complete the Android setup wizard at this point to get access to ADB again.
US996 users only:
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once you're finished with unlocking your bootloader, continue on to step 2.
Step 2: Running recowvery
You can find the recowvery binaries (you need to download all of these) at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow#running (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3: Flashing TWRP & Rooting
Notice: There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, you can also just use adb push. (mentioned here)
Download TWRP: (official builds, V20 is waiting for TWRP 3.1.0 for twrp.me download)
H918: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
US996: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
H830: https://twrp.me/devices/lgg5h830.html
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4: Have fun!
I know a few people have mentioned donating, there is a button right on this post under my username.
Sorry, I don't keep a list as I prefer to keep people's information confidential, but if you do send any money my way, you can request that I mention you at the bottom of this post with any details.
I ask that people please not attach files in this thread, everything required is mentioned in this post, and should be stable in its present state. Thank you.
Thanks for testing on my phone! =]
Does This wipe data on the phone?
justthefacts said:
Does This wipe data on the phone?
Click to expand...
Click to collapse
Unlocking the bootloader does.
jcadduono said:
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that I'm still working on getting TWRP to boot, there seems to be something about the stock kernel sources that doesn't want TWRP to be a part of it.
This will not get you SuperSU or app root access, this is only a root shell allowing you to flash TWRP when it's ready and do other things.
This does however open up some methods of installing SuperSU without TWRP. @Chainfire might have some ideas if he wishes to show up here and stir up some noise.
We do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for TWRP.
For the instructions on using recowvery, you should read the README.md on the GitHub page:
https://github.com/jcadduono/android_external_dirtycow
You can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, I'm really tired.
Click to expand...
Click to collapse
Thank you for taking the time to begin with the first step to develop on this device! (although i will have to do a replacement tomorrow for 2 defects that emerged on my phone) I always had in mind that this device had only a 50% of chances to get rooted, and that it might actually never get rooted . But now chances have increased even more thanks to your hard work. and also thanks to the others you previously mentioned. Let us see if Chainfire takes an interest on adding the final details :good:
I've got ADB working fine, but get nothing with fastboot. Just a blank line when I type 'fastboot devices'. Tried 3 different USB ports also. Windows 10 x64.
I did grab the ADB/fastboot files linked in the first post, but the older files I had don't work either, and they have no issues with my Nexus 7 2013 and HTC 10.
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
So Idk what to do or how to get the file to flash it.. Any help?
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
My advice? Never, ever take an update until the developers say that they are sure they can exploit it. From what I can see, this process uses the "dirty cow" exploit which will assuredly be fixed on the next security update.
---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------
bambam126 said:
So Idk what to do or how to get the file to flash it.. Any help?
Click to expand...
Click to collapse
Why not wait until they can get full root and TWRP? As I see it, this process is to help other developers and people that know what they're doing refine and advance the move to full root. I don't think it's quite ready for prime time yet. It does nothing but get the foot in the door for rooting.
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
And, we're off to the races. Let the "I bricked my phone" threads begin!
douger1957 said:
[/COLOR]And, we're off to the races. Let the "I bricked my phone" threads begin!
Click to expand...
Click to collapse
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Oh. Great to know. I hope they manage to do something with the verizon variants, in fact, with all the variants . Maybe after that they will have more interest on the device
jcadduono said:
alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over teamviewer thanks to @slayerh4x and @darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that i'm still working on getting twrp to boot, there seems to be something about the stock kernel sources that doesn't want twrp to be a part of it.
this will not get you supersu or app root access, this is only a root shell allowing you to flash twrp when it's ready and do other things.
this does however open up some methods of installing supersu without twrp. @chainfire might have some ideas if he wishes to show up here and stir up some noise.
we do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for twrp.
For the instructions on using recowvery, you should read the readme.md on the github page:
https://github.com/jcadduono/android_external_dirtycow
you can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
you will need to unlock your bootloader first. For this you'll probably need lg's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00120120425
mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00320110909
you will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
start by turning on developer options in settings -> about device -> software info -> build number. (tap 7 times until it's enabled)
now navigate to settings -> developer options -> oem unlock. (turn it on)
don't ever turn oem unlock or developer options off when using a custom rom or recovery. This could lose to loss of all your data.
For your computer to see adb, you will need to put the phone in ptp mode (for transferring images). I don't know why this is, a misconfiguration in lg's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your pc.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other usb ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
warning: This step will wipe all your data and factory reset your phone!
you can check the status of your bootloader lock with the fastboot getvar all command.
Ex. (bootloader) unlocked:yes
you should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
there's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, i'm really tired.
Click to expand...
Click to collapse
you are the man !!!!!!!!!!!!!!!!!!!!!!!
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
douger1957 said:
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
Click to expand...
Click to collapse
yup! i couldn't have written it better hahaha. But it is bound to happen for some people that will not pay careful attention. I mena, im not an expert, im maybe a little more than a noob now since i have been dealing with this for quite some time, and that is why i just started my C++ class in order to reach at least a good-to-go level of understanding.
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a H918 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Locked or unlock
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Oh, ye of little faith. Where there's a will, there's a way.
Chainfire just tweeted:
Just installed SuperSU on a V20, based on @jcadduono 's initial work. Good times.
Can this method be used on other devices?
Sent from my R1HD(ZenUI) via Tapatalk
Hello everyone this is my fist guide so be kind with the formatting, i will get better as I post more. I am writing this guide, because like you, the reader, I had installed lineageOS 14.1 and set up the phone and realized there was encryption on it, and with that tried to wipe it in twrp just to find out that it only wiped the encryption key, but not the encryption itself. Don't panic, it isn't all your fault, XD. Stay calm, the last thing you need is to be freaking out, flashing random zips in hopes of fixing it. I will give credit to all of the developers whose tools i am linking at the bottom.
Now that the introductions are out of the way, time for the complimentary dose of warning.
WARNING: Doing this won't guarantee that this will fix it, as every situation can vary. I am not responsible for any bricked devices, thermal reactors coming from your phone after this, or modding before it was cool.
Assuming you can still get into fastboot first you need to gather these files if you don't have them yet.
- Minimal adb and fastboot on windows after installing just drag to desktop to add files to it
- Qualcomm fastboot drivers for axon7tool.exe and for fastboot and adb
- TWRP 3.0.4-1 official for Axon 7
- B29 rollback modded zip on the second tab
- Nougat modem and bootstack
- Tenfar's axon7root.exe (just in case you can't use fastboot. that's what i used because i don't know how to use axon7tool.exe)
- Fastboot image to get fastboot working again flash it in twrp after getting twrp installed again through axon7root.exe
- Some time because this will likely take an hour of your time, assuming you have the drivers and files already downloaded, longer if not and slow internet.
- LineageOS 14.1
- GAPPS 7.1.1 ARM 64
- almost forgot, you also need a microsd card to store the files because we will be wiping your entire internal with this, so back up your lovely dank memes or forever hold the loss.
Step 0.5. if you don't have fastboot working flash the bootloader unlock file by drakenfx to get it working again. if you don't have twrp for whatever reason go to the guide for axon7root.exe linked above and reboot to edl mode by holding all buttons down and have your phone connected to computer to know you are there. there won't be a vibration to let you know, just your computer telling you it has a connected device. now flash twrp, by first renaming the recovery to recovery.img and putting it in the adb folder along with the the root exe and do 'axon7root.exe -p (insert your com number listed in device manager) -r' (without the ' obviously) and it should send the recovery. if it doesn't see your device. make sure you have the drivers installed and make sure you have put down your com number where i left the () at
Step 1. assuming your device boots to this beautiful screen. you need to go back to twrp and drag the B29 zip from your computer to your external sd card from mtp and go to mount and mount system read-only this is very important.
Step 2. flash the B29 modded and let it go through. this will take a few minutes. if the progress bar automatically jumps to the end, you didn't go read only.
Step 3. after it finishes reboot into system and let it set up your system, you can skip through because we will be resetting again anyhow.
Step 4. reboot back to recovery. you can do this by using that pesky bl unlocked message by pressing up on volume as soon as it shows and selecting recovery. there you can see you have stock recovery, don't panic this is what we need. select wipe data factory reset and let it do it
Step 5. go back and skip set up again and reboot to bootloader where you can now 'fastboot flash recovery recovery.img' to get back twrp.
Step 6. flash the nougat bootstack and modem i had you download. after flashing that, go to wipe: Advanced wipe. Select Dalvik, system, data, cache and swipe to wipe. this will format it as ext4 which is what is required to get to lineageOS
Step 7. flash lineageos 14.1 and your gapps category and wait to let it finish. Note, you don't have to flash the modem more than once after flashing lineageos, even for updating. just after leaving B29
Step 8. reboot to make sure your encryption problem is not there
Step 9. set up phone and profit.
If you have done everything right, you shouldn't have bricked and should be back to lineageos 14.1 with no further problems. If you skipped around and got yourself bricked, congratulations because i am not the best at fixing problems, and i can try to help, but you will be at the mercy of the Best devs this community has to offer.
Now to the part where I thank all the Devs who, without their tireless time and effort, would not have made this guide possible and development into this phone in the first place. @Unjustified Dev for the lineageOS build i use as my daily driver for now; you rock dude. ^^
@DrakenFX oh god where do i begin. for the bl unlock zip, B29 modded ota, inspiration to the rest of the community, etc.
@tenfar for the axon7root.exe tool used
@sixohtew for his constant help and advice with not only this guide, but with teaching me to build android. if you are interest in learning how to compile android for any device, he can probably help. he has a very fair deal and is amazing at what he does.
Thank you all for your copious hours of time spent in the building of each great tool and to the community as a whole. Everyone, these guys are amazing, even if i have only talked to one of them. Be sure to stop by and donate.
If i have left anyone's name out, please hit me up and i will add you to the credits, and to that i apologize.
Happy flashing!
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
gpz1100 said:
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
Click to expand...
Click to collapse
Sorry for delayed response, it gets removed when you do the factory reset in stock recovery. For some reason TWRP can't remove it from /data in nougat but stock recovery can in B29.
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
QuantumFluxx said:
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
Click to expand...
Click to collapse
I did try it. It doesn't wipe it because there is a bug with TWRP for our phone. I would wipe and even format data and it wouldn't work. If you go to the official TWRP thread it even warns you that if you have encryption to not wipe. We had a dev who wiped and it got rid of the encryption key and not the encryption, like what happened to me. I tried to wipe so many times and had to revert. Long process but I got my phone to work again
Rip me
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
navsterama said:
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
Click to expand...
Click to collapse
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
twilighttony said:
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
Click to expand...
Click to collapse
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
try this.
twilighttony said:
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
Click to expand...
Click to collapse
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
twilighttony said:
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
Click to expand...
Click to collapse
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
twilighttony said:
try this.
Click to expand...
Click to collapse
This is posted in the dev section. No need for external linkage.
navsterama said:
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
Click to expand...
Click to collapse
glad that worked. perhaps i will edit the guide to where fastboot is added at the end as an extra. seems that if we at least have twrp we can go from there. do you still have an unlocked bl?
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
will remember for future reference. thanks
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
gpz1100 said:
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
Click to expand...
Click to collapse
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
twilighttony said:
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
Click to expand...
Click to collapse
Right, I understand that, but the person reading your blog won't, and thus the confusion.
This guide really needs to be stickied or higher up. Restarted my phone yesterday and it randomly got encrypted upon booting. Was locked out of everything and no keyboard was popping up to be able to put in a PIN or Password. This guide saved me. Thank you.
Hi,
For some weeks i have the Echo Issue on my Z5C. I read that modify the mixer_path could help, and just install TWRP will be enough do modify it.
So this morning I Unlock my bootloader and I Install TWRP by using this thread :
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
I Used the 23.02.2018 version with this command :
"fastboot flash recovery recovery-name.img"
Until that no problems, I can restart with the TWRP interface. But, when i just want to restart by using "REBOOT" from TWRP, the phoe stays stuck on the Sony picture.
I can reboot on TWRP but thats all...and i'm stuck here...
I don't know verry much about developement...
my build is 32.4.A.1.54 and i'm on android 7.1.1
Thanks a lot for helping me.
I did that too last nite
I see you got that pesky sony s1 boot driver disable driver signing in windows 10 just to get the phone recognized. that sucks.
I just got this phone after some deliberation. I read good things here on it. I did what you did. Bricked it. Stuck on sony picture and both LED colors light at same time looking funky. I was able to recover the phone. I joined this forum just to tell you. Hope you fix it.
I used flashtool-0.9.25.0-windows software, installed it. Then pulled the US firmware from sony named E5823_32.4.A.1.54_1299-2920_R1E.ftf Flashed that and bam factory image.
I am still afraid to mess with twrp until I am sure. If you found it let me know. Thanks. I am on a newer firmware and perhaps that was the problem with TWRP?
---------- Post added at 08:59 AM ---------- Previous post was at 08:52 AM ----------
so many threads on this phone twrp
I am not wure
https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050
---------- Post added at 09:06 AM ---------- Previous post was at 08:59 AM ----------
check this thread over at saw it on reddit comments about :silly: lineage
just google
which twrp build_to_choose_for_xperia_z5_compact
Z5C bricked after TWRP 220218.img- FIXED
I did this again. installed TWRP and was stuck in SONY screen.
Used recovery_suzuran_220218.img
Then just booted into TWRP
Installed lineage-14.1-20181207-nightly-suzuran-signed.zip
Had to drop it on internal storage. TWRP didn't read the SD card right.
After installing that it boots to lineage OS and then just installed
open_gapps-arm64-7.1-full-20190106.zip
Phone is up and running. Hope someone finds this helpful