I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Thanks for the thought but you don't need to credit me here
You should mention that running "fastboot format userdata" wipes the entire phone including pics/vids, texts, etc. Someone will run this command ignorantly.
Sent from my Nexus 5X using Tapatalk
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
chucky8 said:
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
Click to expand...
Click to collapse
First off. TWRP couldn't decrypt N right now, so to overcome this, we decrypt the device.
Forced encryption is implemented through the kernel. The modified boot image disables that. So now upon booting, your device shall not be encrypted.
As for the future, you will have to do the same and flash the corresponding modified boot.img, when it comes out.
How do i know if my nexus is decrypted or not ?
ariefabuzaky said:
How do i know if my nexus is decrypted or not ?
Click to expand...
Click to collapse
If you don't know, then you are Encrypted. Look under Settings/Security/Encryption. It will either read "Encrypted" which is obvious or "Encrypt Phone" which means you are decrypted.
Sent from my Nexus 5X using Tapatalk
You don't have to decrypt. You can just push things you wanna flash to /tmp instead of decrypting data
farshad525hou said:
You don't have to decrypt. You can just push things you wanna flash to /to instead of decrypting data
Click to expand...
Click to collapse
Exactly. But then again, it is all about personal preference. I personally don't like connecting any external device to flash anything. Too slow to first download the files, then push 'em up to the HDD or Pen drive and then connecting it to the device to flash. I believe there are more users here, just like me.
For those who would need to decrypt, this is aptly the right process to begin with. Appreciations to @hackarchive for making this thread. Over at the three N based threads, I see several people asking about the decryption process, and this thread would definitely help the newcomers to get their foot in the right direction.
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
lbcary said:
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
Click to expand...
Click to collapse
NM, read that as flash userdata ...
Sent from my Nexus 6P using Tapatalk
I just did this and it worked but now I rebooted to TWRP to flash suhide, all I did was to swipe right on the warning twrp gives at the start and flash suhide, now I'm stuck at the splash screen again
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Sent from my ONEPLUS A3003 using Tapatalk
shamps said:
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Click to expand...
Click to collapse
Doesn't work that way.
The Fix is not needed anymore, newest TWRP is able to decrypt your phones storage. Only use newest twrp.
hackarchive said:
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Click to expand...
Click to collapse
Dude you saved my ass. My phone would not show correct battery % reading and I decided to drain it completely. Then my phone got stuck in bootloop and recovery stuck on splash screen. I am really lucky I found out your post.
Tysm.
Related
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk
Stock kernels with the "forceencrypt" flag changed to "encryptable".
These are "IMG" files that need to be flashed with fastboot.
(Oct) N6F27M-noencrypt-boot.img - https://mega.nz/#!e4AmQJTa!-b9VEDCUHMa2YedScgHpSpStmKfhVWQMFWQf93L0OCU
(Oct) NGI77B-noencrypt-boot.img - https://mega.nz/#!XsBR0QBb!nkNQibCAT-IMpGH3pPVKLmHsGzE90JQfBcDzkWWwHEM
(Sept) NGI55D-noencrypt-boot.img - https://mega.nz/#!6sYSUbTb!dT-pBFhY4iJuHcqGWnRZiFvnUHLxVlNxrDDfgl0L_9w
(Aug) N6F27I-noencrypt-boot.img - https://mega.nz/#!atxQSZYK!y4H4uFt8pNW0szhUyWrp_QinytKIE3WhszAQMNJ4rO0
(Aug) N8I11B-noencrypt-boot.img - https://mega.nz/#!voxiWQqY!DtV5VWhRRLH3cvpxL37QJDFGMUjZU9uubBP8NuADG0k
Hi, and which one is to use? Are these carrier specific versions?
day242 said:
Hi, and which one is to use? Are these carrier specific versions?
Click to expand...
Click to collapse
Sounds like the N8I11B build has some Verizon specific code. After reviewing, it appears they devs used the same kernel in both builds, so it should not matter which is flashed.
Lose data?
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
TheTomahawk said:
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
Click to expand...
Click to collapse
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release and maintain the exisiting data)
Re: lose data
jbaumert said:
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release any maintain the exisiting data)
Click to expand...
Click to collapse
Cool. Em, could you provide instructions, please?
Tnx
TheTomahawk said:
Cool. Em, could you provide instructions, please?
Tnx
Click to expand...
Click to collapse
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Much obliged.
im assuming one of these brings back ota? probably N6F27I
guessing one is official ota from 7.0 to 7.1.1
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
dudikaz said:
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
Click to expand...
Click to collapse
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
jbaumert said:
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
Click to expand...
Click to collapse
if i flash it after los it gets stuck on google logo and doesn't boot at all :/
---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------
ok so now i've went back to stock N8I11B which is force encrypted. could you tell me exactly what steps should i take to make it not encrypted please? also what about the franco kernel does it get rid of encryption as well maybe?
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
jbaumert said:
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
Click to expand...
Click to collapse
it's really confusing as this is what it says in the official los thread here on xda - "Current lineage 14.1 shamu nightlies are based on the N8I11B August 2017 update from google. So you should be using the radio and bootloader img from that update. " also how do i erase this userdata properly? "fastboot format userdata"? i think last time i did it my device didn't boot at all afterwards. going to try it again now.
Added September 2017 "no encrypt" boot.img to OP
Added October 2017 "no encrypt" boot.img to OP
thumbs up !!!
i was looking all over for the latest img. really grateful for your work. thanks a lot
Thank you very much
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Jeffro64 said:
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also, can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Click to expand...
Click to collapse
You can leave the name of the file (unless you just want to type in a short command with fastboot). As for the backup of "userdata", if you are updating the phone from one stock version to another and following the instructions you quoted, there is no need to backup. Coming from another ROM you would want to wipe and then yes, a backup is a good idea (needed).
MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205