Related
GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES
THIS METHOD APPLYS TO:
ONLY FOR PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES
This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
chasama said:
This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10
Samsugn galaxy s2 GT-I9100 help!!
vincom said:
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10
Click to expand...
Click to collapse
i am running on RR Jelly bean rom 3.0.6, suddenly my comp stopped detecting my phone nd now its not detected by any comp!!
wen i connect it only charges but the phone is not recognised!! i want to install stock ics firmware plz help me!
Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.
zgibbyson said:
Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.
Click to expand...
Click to collapse
use internal if you have usb access to it
thanks
the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.
Re: [HOWTO] INSTALL STOCK ICS USING CWM/TWRP even w/a DEAD USB Port
PhoneTay11 said:
the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.
Click to expand...
Click to collapse
Don't put it in any folder, just copy to the SD card.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
PhoneTay11 said:
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
Click to expand...
Click to collapse
that screen is also odin/download mode
try flashing again
check odin troubleshooting section in the "install cwm/twrp" link in my sig
vincom said:
GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES
THIS METHOD APPLYS TO:
PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES
Click to expand...
Click to collapse
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.
ntd0626 said:
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.
Click to expand...
Click to collapse
no, why do u need gb, just flash the ics or jb roms, or if your usb is not dead go through the odin trouble shooting section in the restore to stock sticky to try to solve the connection issue, link to restore to stock is in my sig
Stock Rom Android M.
Hi, could you help me i have TWRP Custom recovery and cm12.1 android lollipop, i want to
Flash Stock Rom Android Marshmallow using TWRP is it possible using this method ,
my Device is Galaxy Tab S 8.4 wi-fi.
invalid zip
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
AFAIK all devhosts files are bad/fake, i cant even dl my own files.
if i find them all reup to androidfilehost
Stock Rom
champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
Just use "Flashfire" and do everything from your phone no need for a computer.
Using this to flash 1.7 gb file
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?
ParaSpl01t said:
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?
Click to expand...
Click to collapse
you mean this zip file when you unzip it show you 5 files that you can use with Odin?
I tried and says fail , why would tarp fail to flash a stock firm ?
I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?
Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.
Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.
solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
bzowk said:
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
Click to expand...
Click to collapse
First off, this isn't Development.
Secondly, I explained to you how to fix this in the very root thread you linked several times.
Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).
Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.
Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
bzowk said:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
Click to expand...
Click to collapse
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.
And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.
P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
bzowk said:
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
Click to expand...
Click to collapse
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Captain_Throwback said:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Click to expand...
Click to collapse
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
bzowk said:
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
Click to expand...
Click to collapse
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Captain_Throwback said:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Click to expand...
Click to collapse
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
4. Flash SuperSU 2.76 zip
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
9. Flash newly packed boot.img to phone using fastboot
10. Enjoy
I really appreciate your help and patience with me!
bzowk said:
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
Click to expand...
Click to collapse
Good so far . . .
bzowk said:
4. Flash SuperSU 2.76 zip
Click to expand...
Click to collapse
I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).
bzowk said:
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
Click to expand...
Click to collapse
Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).
bzowk said:
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
Click to expand...
Click to collapse
Looks good . . .
bzowk said:
9. Flash newly packed boot.img to phone using fastboot
Click to expand...
Click to collapse
TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.
bzowk said:
10. Enjoy
Click to expand...
Click to collapse
Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.
bzowk said:
I really appreciate your help and patience with me!
Click to expand...
Click to collapse
Guess we'll see if it all works out . . .
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
bzowk said:
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
Click to expand...
Click to collapse
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Captain_Throwback said:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Click to expand...
Click to collapse
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
bzowk said:
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
Click to expand...
Click to collapse
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go .
bad topic
I would like to install TWRP and after that Lineage OS on my Samsung S8+ (Exynos). So i tried flashing TWRP with Odin (Dream2lte version 3.3.1.0). But i ran into a FRP lock so i googled and try to solve this, but so far i am unable to.
I have the password to my Google account, so i removed the Google account from the phone and removed the phone from my Google account. After factory reset i am still getting an error FRP lock when flashing.
Shouldn't the FRP lock be gone after removing google account and doing a factory reset? I have tried a couple of YT Howto's but they don't seem to work.
How do i remove the FRP lock so that i am able to install TWRP and Lineage OS?
Like i said i know the password to my Google account and i 100% own the phone
(Bypass probably isn't the correct word, i am simply trying to turn it off )
Got exactly the same problem, hence like you, ended up here for help.
Well i fixed my problem (Disable USB debug and OEM unlock, couple of reboots and enabled them and it worked). But after that i broke my phone
I am stuck at the screen saying: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I know this is meant to scare me (is kinda working...), but i also know that Odin is still working. So as far as i know i have to flash the original firmware now to fix this. But i keep getting the error: Invalid magic string. When i try to also flash a BL file i get the error: ""Secure CHECK FAIL: (BOOTLOADER)" The option Re-Partition in Odin is switched OFF, as far as i know this is okee... right?
I have tried 3 different versions (Android 9/8/7):
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU1AQC9/128974/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU4DSBA/259612/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXS4CSA4/256485/
This zip files contain a BL/AP/CP/CSC file, i have tried them all at the same time in Odin as well as the AP and BL files seperate. (from one zip file, NOT different version files together of course)
I tried using Smart Switch 4.1 to do the emergency procedure using model nummer SM-G955F with my serial number but before it does anything it tells me this is not possible with an SM-G955F.
They all give me the same result.
Does anybody know how to fix this?
TheGeneral said:
Well i fixed my problem (Disable USB debug and OEM unlock, couple of reboots and enabled them and it worked). But after that i broke my phone
I am stuck at the screen saying: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I know this is meant to scare me (is kinda working...), but i also know that Odin is still working. So as far as i know i have to flash the original firmware now to fix this. But i keep getting the error: Invalid magic string. When i try to also flash a BL file i get the error: ""Secure CHECK FAIL: (BOOTLOADER)" The option Re-Partition in Odin is switched OFF, as far as i know this is okee... right?
I have tried 3 different versions (Android 9/8/7):
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU1AQC9/128974/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU4DSBA/259612/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXS4CSA4/256485/
This zip files contain a BL/AP/CP/CSC file, i have tried them all at the same time in Odin as well as the AP and BL files seperate. (from one zip file, NOT different version files together of course)
I tried using Smart Switch 4.1 to do the emergency procedure using model nummer SM-G955F with my serial number but before it does anything it tells me this is not possible with an SM-G955F.
They all give me the same result.
Does anybody know how to fix this?
Click to expand...
Click to collapse
Secure check fail on bootloader is your flashing a older firmware than on the device. Look at the builds 5th from last digit. You need to flash that equal or greater than.
The error screen you see for emergency recovery is ok. It's like a modified version of download mode. Kind of. You can still flash Odin files from said screen. Ii see you've flashed a bit 1. And two bit 4 firmwares. So you must be on a 5 or greater. I don't know the exy bit number but like snapdragon is at or near 7 or 8. I can explain better if you need. But not an exynos expert
TheMadScientist said:
Secure check fail on bootloader is your flashing a older firmware than on the device. Look at the builds 5th from last digit. You need to flash that equal or greater than.
The error screen you see for emergency recovery is ok. It's like a modified version of download mode. Kind of. You can still flash Odin files from said screen. Ii see you've flashed a bit 1. And two bit 4 firmwares. So you must be on a 5 or greater. I don't know the exy bit number but like snapdragon is at or near 7 or 8. I can explain better if you need. But not an exynos expert
Click to expand...
Click to collapse
Thanks for your reply! I am in the normal "Downloading...." screen is there anywhere i can check which number i am at?
But i have just tried this one: G950FXXS7DTA6_G950FOXM7DTA6_PHN and it is not working. But this is the newest one available on sammobile. Still the same bootloader error.
I have tried TWRP 3.3.1.0 and that worked, now i am in the TWRP menu but i don't have the LineageOS 17 + GoApps copied to the root. So i cannot install LineageOS now. What do i do now? My computer sees a SM-G955F but it is not showing any storage, if i can fix this i could copy the LineageOS files to the root...right?
TheGeneral said:
Thanks for your reply! I am in the normal "Downloading...." screen is there anywhere i can check which number i am at?
But i have just tried this one: G950FXXS7DTA6_G950FOXM7DTA6_PHN and it is not working. But this is the newest one available on sammobile. Still the same bootloader error.
I have tried TWRP 3.3.1.0 and that worked, now i am in the TWRP menu but i don't have the LineageOS 17 + GoApps copied to the root. So i cannot install LineageOS now. What do i do now? My computer sees a SM-G955F but it is not showing any storage, if i can fix this i could copy the LineageOS files to the root...right?
Click to expand...
Click to collapse
1. If you are on an S8+ flashing firmware for the S8 will cause you issues. Download firmware for the S8+ only. ie: 955f not 950f.
2. If you can't get into the system but can get into download mode there should be a line saying
AP SWREV: B:? K:? S:?
The B:? Is your bootloader version number. You will need to flash the same or higher.
3. How did you install TWRP?
If you don't have an SD card to store files on then after the Format Data stage you can then copy files from pc to phones internal storage.
spawnlives said:
1. If you are on an S8+ flashing firmware for the S8 will cause you issues. Download firmware for the S8+ only. ie: 955f not 950f.
2. If you can't get into the system but can get into download mode there should be a line saying
AP SWREV: B:? K:? S:?
The B:? Is your bootloader version number. You will need to flash the same or higher.
3. How did you install TWTP?
If you don't have an SD card to store files on then after the Format Data stage you can then copy files from pc to phones internal storage.
Click to expand...
Click to collapse
I am a bit embarrassed, it looks like i have been trying to flash the wrong ROMs last night 950 instead of 955, i am downloading the correct files now and wil try again. Sorry for this dumb mistake!
Just to be sure, i am trying to do this:
https://www.getdroidtips.com/lineage-os-17-samsung-galaxy-s8/
(I do know that this site says S8, but i picked the right files this time and thought the process would be the same)
But i first Flash TWRP with Odin, otherwise i cannot reach the TWRP recovery menu right?
But when i look bullet 5 (not number 5) it looks like i need to flash TWRP from within the TWRP menu. But that is not correct right?
I have placed these zip files on the phone:
lineage-17.1-20200211-UNOFFICIAL-dreamlte.zip
open_gapps-arm64-10.0-pico-20200303.zip
As a zip and unpacked, but when i am in the TWRP menu and i go to install, i cannot find the zip files. I placed them in the highest folder level possible. Why can't i find them now?
TheGeneral said:
I am a bit embarrassed, it looks like i have been trying to flash the wrong ROMs last night 950 instead of 955, i am downloading the correct files now and wil try again. Sorry for this dumb mistake!
Just to be sure, i am trying to do this:
https://www.getdroidtips.com/lineage-os-17-samsung-galaxy-s8/
(I do know that this site says S8, but i picked the right files this time and thought the process would be the same)
But i first Flash TWRP with Odin, otherwise i cannot reach the TWRP recovery menu right?
But when i look bullet 5 (not number 5) it looks like i need to flash TWRP from within the TWRP menu. But that is not correct right?
I have placed these zip files on the phone:
lineage-17.1-20200211-UNOFFICIAL-dreamlte.zip
open_gapps-arm64-10.0-pico-20200303.zip
As a zip and unpacked, but when i am in the TWRP menu and i go to install, i cannot find the zip files. I placed them in the highest folder level possible. Why can't i find them now?
Click to expand...
Click to collapse
I don't use custom roms yet.
Try searching for you device S8+ for installation instructions. Had a quick look the firmware is for S8 only not S8+. Need dream2lit for S8+
Try in separate stages instead of all at once.
I would sort out your stock firmware first get it up and running.
Then install TWRP. Install for S8+ from
http://twrp.me/Devices/Samsung/
They are many guides for this
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
If you need rmm bypass zip
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Get that up and running properly.
Then you can install custom roms,root etc.
In regards to transferring files to phone they need to be a zip file ( .zip ) or an image ( .img ) files to flash in TWRP.
Maybe select internal storage then from menu select sdcard folder check if file is there.
spawnlives said:
I don't use custom roms yet.
Try searching for you device S8+ for installation instructions. Had a quick look the firmware is for S8 only not S8+. Need dream2lit for S8+
Try in separate stages instead of all at once.
I would sort out your stock firmware first get it up and running.
Then install TWRP. Install for S8+ from
http://twrp.me/Devices/Samsung/
They are many guides for this
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
If you need rmm bypass zip
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Get that up and running properly.
Then you can install custom roms,root etc.
In regards to transferring files to phone they need to be a zip file ( .zip ) or an image ( .img ) files to flash in TWRP.
Maybe select internal storage then from menu select sdcard folder check if file is there.
Click to expand...
Click to collapse
I am using dream2lit.
I have the correct factory stock ROM (now), so i can always go back now. But i agree, my preparation wasn't good enough.
I will look at the links, but for now like i said my problem is that i cannot see my files in TWRP. But maybe that will be addressed in one of your links
With regards to your first link, i used the "Odin Method" so as far as i can tell i did this the right way(https://twrp.me/samsung/samsunggalaxys8plus.html):
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
TheGeneral said:
I am using dream2lit.
I have the correct factory stock ROM (now), so i can always go back now. But i agree, my preparation wasn't good enough.
I will look at the links, but for now like i said my problem is that i cannot see my files in TWRP. But maybe that will be addressed in one of your links
With regards to your first link, i used the "Odin Method" so as far as i can tell i did this the right way(https://twrp.me/samsung/samsunggalaxys8plus.html):
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Note: Samsung don't have fastboot commands. Have to use button configurations to enter recovery or download modes.
What stage are you at?
It will give me a better idea to be able to help more.
spawnlives said:
Note: Samsung don't have fastboot commands. Have to use button configurations to enter recovery or download modes.
What stage are you at?
It will give me a better idea to be able to help more.
Click to expand...
Click to collapse
Well i installed Lineage OS 17.1 and Open Apps (lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303) with an OTG plug and an USB stick. After installing i removed the USB Stick. But now i am having a new problem...
When the phone boots it asks: "To start Android, enter your password"
Which password is this? When i enter a password i often use it works but then:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt. (Which is no problem)
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.
(Button) Erase ALL DATA"
Of course i erase the data. Look at the attachment to see what happens then.
I will not give up, will get Lineage OS on this phone, and after that on my Tablet S2 and maybe even on my primairy phone (S10+)
What should i do now? Many thanks for all the help so far, and for help finishing this proces
TheGeneral said:
Well i installed Lineage OS 17.1 and Open Apps (lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303) with an OTG plug and an USB stick. After installing i removed the USB Stick. But now i am having a new problem...
When the phone boots it asks: "To start Android, enter your password"
Which password is this? When i enter a password i often use it works but then:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt. (Which is no problem)
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.
(Button) Erase ALL DATA"
Of course i erase the data. Look at the attachment to see what happens then.
I will not give up, will get Lineage OS on this phone, and after that on my Tablet S2 and maybe even on my primairy phone (S10+)
What should i do now? Many thanks for all the help so far, and for help finishing this proces
Click to expand...
Click to collapse
Mounting data errors in twrp generally ( but not always ) means your device is encrypted/re-encrypted when booting into system. Twrp has issues with encrypted devices.
What version twrp are you using?
Have you flashed the no-verity-opt-encypt zip in twrp. This zip file will prevent device from re-encrypting when booting phone back into the system ( after the Format Data stage / reboot back into twrp)
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
What is your process of installing twrp?
If you have any passwords etc. installed delete them until after setting up you phone.
spawnlives said:
Mounting data errors in twrp generally ( but not always ) means your device is encrypted/re-encrypted when booting into system. Twrp has issues with encrypted devices.
What version twrp are you using?
Have you flashed the no-verity-opt-encypt zip in twrp. This zip file will prevent device from re-encrypting when booting phone back into the system ( after the Format Data stage / reboot back into twrp)
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
What is your process of installing twrp?
If you have any passwords etc. installed delete them until after setting up you phone.
Click to expand...
Click to collapse
I am using version twrp-3.3.1-1-dream2lte and no i have not flashed that no-verity-opt-encypt zip. I assume i should flash this one the same way flash the Lineage ROM right?
No passwords used on the phone.
My process:
i put the phone in download mode (POWER+BIXBY+VOL DOWN)
I use ODIN to flash twrp-3.3.1-1-dream2lte, and when the phone reboot i press POWER+BIXBY+VOL UP to enter TWRP menu,
Then i go to WIPE and Advanced Wipe and i select the data, system and davlik cache. Then swipe to wipe it.
Then i go to INSTALL and flash lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303
TheGeneral said:
I am using version twrp-3.3.1-1-dream2lte and no i have not flashed that no-verity-opt-encypt zip. I assume i should flash this one the same way flash the Lineage ROM right?
No passwords used on the phone.
My process:
i put the phone in download mode (POWER+BIXBY+VOL DOWN)
I use ODIN to flash twrp-3.3.1-1-dream2lte, and when the phone reboot i press POWER+BIXBY+VOL UP to enter TWRP menu,
Then i go to WIPE and Advanced Wipe and i select the data, system and davlik cache. Then swipe to wipe it.
Then i go to INSTALL and flash lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303
Click to expand...
Click to collapse
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
spawnlives said:
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
Click to expand...
Click to collapse
how do i make a complete TWRP backup? and what is rmm bypass and how do i know if it is neccessary to install this zip file?
TheGeneral said:
how do i make a complete TWRP backup? and what is rmm bypass and how do i know if it is neccessary to install this zip file?
Click to expand...
Click to collapse
In twrp main menu
Select backup menu - select ( all ) partitions - select storage location ( bottom left of screen ) - then swipe to backup.
Note:
1. If backing up to internal storage copy/move backup to an external storage ie: PC, sd card.etc.
2. Since you want a custom rom backup of the EFS partition is important.
Rmm state can be found in download mode. It will have a line ( near the top ) saying RMM state. It will either say prenormal or normal /disappeared.
It won't hurt to flash it just in case.
See OP in the thread I sent before:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
Click to expand...
Click to collapse
I am really trying to do what you are saying...but when i try to "Format Data" (Step 2) it shows an error "Failed to mount '/preload' (Invalid argument). When i try to install no-verity-opt zip (step 4) at the end it shows the same error "Failed to mount '/preload' (Invalid argument). Which is probably because format data failed?
I am installing the zip from an USB stick with an USB-C to USB-A Converter. I don't think that could be the problem?
As Expected the "Data (excl. storage) is still showing 0MB.
TheGeneral said:
I am really trying to do what you are saying...but when i try to "Format Data" (Step 2) it shows an error "Failed to mount '/preload' (Invalid argument). When i try to install no-verity-opt zip (step 4) at the end it shows the same error "Failed to mount '/preload' (Invalid argument). Which is probably because format data failed?
I am installing the zip from an USB stick with an USB-C to USB-A Converter. I don't think that could be the problem?
As Expected the "Data (excl. storage) is still showing 0MB.
Click to expand...
Click to collapse
Failed to mount preload seems to affect some users.
You could try after the format data and reboot back into twrp ( using twrp 3.3.1.1 ):
Select wipe menu
Select advanced wipe
Select Preload
Swipe to wipe
Reboot back into twrp
Then try flashing no-verity/rmm zips files - reboot back into twrp.
Normally, for me , after this stage If i still get 0mb I will reboot into the Android system and then back into twrp. Then check in backup menu storage. If ok then try to flash custom rom.
spawnlives said:
Failed to mount preload seems to affect some users.
You could try after the format data and reboot back into twrp ( using twrp 3.3.1.1 ):
Select wipe menu
Select advanced wipe
Select Preload
Swipe to wipe
Reboot back into twrp
Then try flashing no-verity/rmm zips files - reboot back into twrp.
Normally, for me , after this stage If i still get 0mb I will reboot into the Android system and then back into twrp. Then check in backup menu storage. If ok then try to flash custom rom.
Click to expand...
Click to collapse
Yes Yes!! After doing the Preload i am able to flash no-verity/rmm zips file.
But Data is still showing 0MB.....
I thought why not give the lineage OS rom flashing another try. That worked, but now the phone seems to hang on a Lineage OS logo with a small circle moving around not straight line.
So i wiped everything again and flashed no-verity/rmm zip file, and will wait what for some advice and what do to next.
TheGeneral said:
Yes Yes!! After doing the Preload i am able to flash no-verity/rmm zips file.
But Data is still showing 0MB.....
I thought why not give the lineage OS rom flashing another try. That worked, but now the phone seems to hang on a Lineage OS logo with a small circle moving around not straight line.
So i wiped everything again and flashed no-verity/rmm zip file, and will wait what for some advice and what do to next.
Click to expand...
Click to collapse
Have you tried to reboot into system through twrp ie: reboot menu - system. Let it start normally, reboot into twrp, then check storage size. ( This is after the flashing of the no-verity/rmm zip and rebooting back into twrp ).
As I said I' m not familiar with custom ROMs. I do know that some custom ROMs do take some time to boot up on installation.
But out of curiosity I have a spare S8 and will give it a go.
Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.
start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008
Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.
Try using sp flash tools flashing the boot.img