Related
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Terminal Command didn't work ...
AtriosM3 said:
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Click to expand...
Click to collapse
I repeated this three times, and no luck... any suggestions?
I did it a tad differently. I am running Windows 7.
First I downloaded these universal drivers so my phone was recognized under Device Manager, went to my adb directory with command prompt and typed the following:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
I just preferred using the keyboard, but your directions will work, too.
secure booting error
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
eddie 2t said:
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
Click to expand...
Click to collapse
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
bleedingthru said:
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
Click to expand...
Click to collapse
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
eddie 2t said:
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
Click to expand...
Click to collapse
Ive never used cwm on this device only twrp so i dont know about that recovery
boot
I have philz touch and all my phone will do is boot to philz?
Hi there.
I thought i'd try and get the 4.4 update for my Xperia SP as it was lagging a lot and causing me a lot of headache. So spent most of the day trying to figure out how to download CyanogenMod.. and i've got up to Now send the package you want to apply to the device with "adb sideload <filename>... I don't even know how to do that as I'm not techy at all
Was i supposed to send the package to the sd card before doing all this process? I wiped the data rom thing but had backed it up onto SD card before doing that. I restored it so I could try and move the package from the computer to my SD card but my phone just stays on a black screen
Have I broken my phone? Someone please help me as frustrated is an understatement right now. Not to mention crying like a little baby.....
Thanks in advance.
You must connect your sd card to pc through recovery or sd adaptor ( if your phone isn't booting), and extract kernel (boot.img) from the rom zip to your pc and flash the kernel (boot.img) with flashtool on fastboot mode, then enter on recovery and flash the rom zip
Methods
thewinterman said:
Hi there.
I thought i'd try and get the 4.4 update for my Xperia SP as it was lagging a lot and causing me a lot of headache. So spent most of the day trying to figure out how to download CyanogenMod.. and i've got up to Now send the package you want to apply to the device with "adb sideload <filename>... I don't even know how to do that as I'm not techy at all
Was i supposed to send the package to the sd card before doing all this process? I wiped the data rom thing but had backed it up onto SD card before doing that. I restored it so I could try and move the package from the computer to my SD card but my phone just stays on a black screen
Have I broken my phone? Someone please help me as frustrated is an understatement right now. Not to mention crying like a little baby.....
Thanks in advance.
Click to expand...
Click to collapse
Your phone is broken. Now you can throw it away and hope for the best.
Okay I was kidding!
To get your phone back, you may need to at least know how to use a Flashtool. But don't worry I'll point out one by one.. I recommend viewing this post on a desktop browser, as Tapatalk does not show nested [ hide ] correctly.
The prerequisites are a Williams Kernel v7 (Direct DL link) and Flashtool and a custom ROM's .zip of your choice.
Put the custom ROM zip into your SD card by any means possible. Or you may use a OTG cable to connect to a flash drive.
Install flashtool
Execute the drivers installer located within "drivers" folder inside Flashtool's install directory (default C:\Flashtool\drivers)
Tick "flashmode drivers", "fastboot drivers" and lastly scroll down a little bit, find "Common drivers for Viskan board" and tick that as well. Finish the installation
Open flashtool. Make sure you ran it as an administrator to avoid conflicts.
Hit the lightning icon
Choose fastboot mode
Hit "Select kernel to flash"
Navigate to and select the downloaded kernel earlier. You may unable to see your kernel. Please change the file type from "*.sin" to "*.elf".
Continue. This will ask you to connect your XSP in fastboot mode. To do so, make sure your phone is turned off completely, hold volume rocker up and connect it to your computer. Once the LED bar lights blue, you may release the volume rocker.
Flashing process will run. It is important not to interrupt the process!
Once complete, remove the cable from your phone and turn it on.
Hit volume up when the lights blink to get into CWM recovery
From another guide:
3) Flashing the custom ROM
You can navigate in CWM by using the volume and power keys or by swiping the screen up, right, down, left.
NOTE: Please understand methods are vary for different ROMs. Please prioritise steps provided in a custom ROM thread. This guide however, can be regarded as a "logic" for you to flash such custom ROM.
Wipe everything you can.
WARNING: Please be careful to not wipe the /boot.
go to "Mounts and storage"
Format /system
Format /data
Format /cache
Go back to main menu
Get into "Advanced" > "Clear Dalvik Cache" (this is quite optional)
Go back to main menu
Attempt "Wipe data/factory reset"
Flash the custom ROM zip you've downloaded.
Go to "Install zip"
Choose "Choose zip from /storage/sdcard1" (I am assuming you've put the zip into your SD card)
Navigate to the zip you've copied, and select it
Choose "yes"
Flash gapps. The flashing process is similar to how you flashed the custom ROM zip based on the steps above.
Reboot the phone
You now have your preferred custom ROM installed! Congratulations! Set up your phone as usual now.
Restore your applications backup if you wish to have your apps back.
Your steps end here.
Click to expand...
Click to collapse
If you want to learn more: [Guide] How to use Flashtool
TechnoSparks said:
Your phone is broken. Now you can throw it away and hope for the best.
Okay I was kidding!
To get your phone back, you may need to at least know how to use a Flashtool. But don't worry I'll point out one by one.. I recommend viewing this post on a desktop browser, as Tapatalk does not show nested [ hide ] correctly.
The prerequisites are a Williams Kernel v7 (Direct DL link) and Flashtool and a custom ROM's .zip of your choice.
Put the custom ROM zip into your SD card by any means possible. Or you may use a OTG cable to connect to a flash drive.
Install flashtool
Execute the drivers installer located within "drivers" folder inside Flashtool's install directory (default C:\Flashtool\drivers)
Tick "flashmode drivers", "fastboot drivers" and lastly scroll down a little bit, find "Common drivers for Viskan board" and tick that as well. Finish the installation
Open flashtool. Make sure you ran it as an administrator to avoid conflicts.
Hit the lightning icon
Choose fastboot mode
Hit "Select kernel to flash"
Navigate to and select the downloaded kernel earlier. You may unable to see your kernel. Please change the file type from "*.sin" to "*.elf".
Continue. This will ask you to connect your XSP in fastboot mode. To do so, make sure your phone is turned off completely, hold volume rocker up and connect it to your computer. Once the LED bar lights blue, you may release the volume rocker.
Flashing process will run. It is important not to interrupt the process!
Once complete, remove the cable from your phone and turn it on.
Hit volume up when the lights blink to get into CWM recovery
From another guide:
If you want to learn more: [Guide] How to use Flashtool
Click to expand...
Click to collapse
Sorry for the late reply. But thank you so much! Spent 15 hours trying to fix the darn thing. Only got 3 hours of sleep :-/ I am enjoying a fresher new faster phone. So thank you so much, you are awesome!
thewinterman said:
Sorry for the late reply. But thank you so much! Spent 15 hours trying to fix the darn thing. Only got 3 hours of sleep :-/ I am enjoying a fresher new faster phone. So thank you so much, you are awesome!
Click to expand...
Click to collapse
Nice! Have fun with your fixed phone!
Bravo!!!
You are a life saver man..I got my Xperia SP back by your guide.
Best Wishes..
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
mclovin9091 said:
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
Click to expand...
Click to collapse
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
stonedpsycho said:
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
Click to expand...
Click to collapse
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
mclovin9091 said:
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Click to expand...
Click to collapse
Have you enabled "usb debugging"? in developer settings (tap the build number 7 times) Do you have ADB installed? If so did you open CMD in the ADB folder?
FCorvin said:
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
Click to expand...
Click to collapse
Cheers, any info on what files need modding?
Was rooted, managed to get adb to work last night and managed to reinstall twrp but now i can't get the rom to load and can't flash any CROM.
So used the all in one tool to re install stock 5.0.2.
Going to grab a brew and chill for a bit.
Aiight, once you downloaded the zip on your PC, go to:
1. ...titan.zip\META-INF\com\android
Drag the "metadata" file on a notepad page and replace 0x4882 with 0x4821 (your phone's bootloader code) and save.
2. ...titan.zip\META-INF\com\google\android
Drag the "updater-script" file on a notepad page, hit "Search and replace" for any of the XT's in there with yours, XT1072.
You will have 3 hits.
Example: Search and replace XT1069 with XT1072 ->
getprop("ro.product.device") == "XT1069"
getprop("ro.build.product") == "XT1069"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069
will become:
getprop("ro.product.device") == "XT1072"
getprop("ro.build.product") == "XT1072"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1072.
(3 - while still here)
Search and replace the initial 0x4882 bootloader with yours, 0x4821.
Save the changes.
And... you're good to go.
Some native Moto apps won't show up in PlayStore because of this, but you can get all the Moto stuff from here (if you really love them).
Once installed, enjoy the full power of your brand new Android 6 phone.
Don't forget to do all the things you did as a kid once: activate the developer options as mentioned above, set the SuperSu permissions and so on.
However: screw-ups occur mainly because of conflicts between the new and the old, so you will have to perform a clean install as advised here, which means wiping everything you had - so you won't be able to return to your Lollipop Stock through any recovery.
So chill some more and consider everything thoroughly.
Cheers.
bloody phones, dunno ewhat happened but seems like reinstalling the SROM for the 2nd time allowed me to boot into recovery, twrp and load the CROM. Only issue this time was that apparently stock gapps was too big for the phone so had to download and install the mini version.
Will see how CM13 goes and download the Temasek for install later once im happy everythings working.
Hello!
This thread is to teach you how to flash TWRP, along with a custom ROM on your T-Mobile Galaxy S5 WITHOUT root!
DISCLAIMER:
Read the whole thread at least one before trying!
Anything you do to your device is your own decision. I am not forcing you to do this. If you screw something up during the process, that isn't my fault.
Custom ROMs can sometimes be unstable. PLEASE make sure you are downloading the correct file for your device model.
Tampering with your device's firmware, including custom recoveries, ROMs, or rooting your device WILL VOID THE WARRANTY.
Flashing a custom ROM WILL DELETE YOUR DATA. Consider backing up your apps, photos, videos, files, etc. online or to an external storage.
Before we start, we need to download a few things.
*Do not download anything with Safari! Safari unzips zip files, but we want them to stay zipped. DO NOT RE-ZIP THE FILE YOURSELF!!! It will not be zipped in the correct format!*
1. Odin v3.12.3: (Odin)
2. The TWRP recovery tar file: (TWRP)
3. Your custom ROM zip file. (There are many ROMs out there, but Lineage is a pretty good one: (Lineage OS klte) Choose the most recent release.) IMPORTANT: Make sure you download this to your phone's internal/external storage to an easily accessible location.
4. A GApps package. This is required if you want to be able to download apps from the Google Play Store. Go to the Open GApps page and choose ARM, and Android 7.1. You shouldn't need anything more that micro. IMPORTANT: This file also goes onto your phone's internal/external storage.
5. Your device drivers. Most of the time, Windows will automatically install the required drivers once you put in the device, but in the case this doesn't happen, try googling your devices model number and "windows drivers." Follow the process to install.
Alright, with that out of the way, let's install TWRP.
1. With your phone unplugged, boot into "Download mode." Power off your device. Then hold down the Power, Home, and Vol- buttons until you see a warning pop up.
2. Accept the warning by clicking Vol+.
3. Run the Odin exe file we downloaded earlier. (You may have to unzip the file first.)
4. Go to Options and disable auto reboot. Go back to the Log tab.
5. Plug your device into the computer. You should see Odin say "ADDED!" on the side.
6. Click "AP" and locate the TWRP recovery tar file we downloaded earlier.
7. Once you select the file, click "Start."
8. When finished, it should say "PASS" at the top. This is where you unplug your phone and remove the battery.
9. Wait 10 seconds before putting the battery back in.
10. Try booting into recovery by holding down the Power, Home, and Vol+ buttons. If it reads "Team Win Recovery Project" at the top, then congrats! You've successfully flashed TWRP! If it says at the top "stock recovery," try the whole process again from step #1.
Now we can flash your custom ROM!
1. This is where we wipe your phone's data. Click on "Wipe." Then Swipe to factory reset.
2. After you have wiped your device, click on "Install"
3. Now navigate to the ROM zip file and select it.
4. Click on "Add more zips"
5. Navigate to the GApps zip file and select it.
6. Swipe to install. This can take some time, so grab a cup of coffee and maybe check out my Youtube channel?
7. The moment of truth: click on Reboot, then System. The first boot can take a minute. If it doesn't show up after 5 minutes, remove the battery and try wiping and flashing again.
CONGRATULATIONS!! You've installed a custom ROM! Enjoy! :laugh:
EXTRA:
If you want to enable root on your Lineage OS device, you must flash an additional file first.
1. Go to this link and download the first su (arm) file and save it to an easily accessible location.
2. Boot into recovery mode once again by powering off your device, then pressing and holding Power, Home, and Vol+ until TWRP appears.
3. Click on install.
4. Select the su zip file we downloaded earlier.
5. Swipe to install.
6. Once it is installed, boot back into system.
7. Navigate to developer options in settings.
8. Scroll down to"Root Access" and change it to either Apps, or Apps and ADB.
Awesome, now you have root!
Thanks for the help:
[url]https://forum.xda-developers.com/tmobile-galaxy-s5/general/root-how-to-root-sm-g900t-firmware-t3358190[/URL]
I did not work for me, when I go recovery mode it shows:
Could not do normal boot
Odin mode.
I'm definitely not an pro at this, so can anyone help me please
Worked perfectly on the latest stock OTA!
Doesn't work for me. When I reboot in recovery ode, instead of TWRP loading I get a generic Android Recovery screen with a few options - reboot system now, reboot to bootloaded, apply update from ADB apply update from SD card, wipe data/factory reset, wipe cache partition, mount /system, view recovery logs, power off. Now sure how to proceed....
bradmccoy said:
Doesn't work for me. When I reboot in recovery ode, instead of TWRP loading I get a generic Android Recovery screen with a few options - reboot system now, reboot to bootloaded, apply update from ADB apply update from SD card, wipe data/factory reset, wipe cache partition, mount /system, view recovery logs, power off. Now sure how to proceed....
Click to expand...
Click to collapse
We’re you sure to unplug and remove the battery? This is essential to ensure the phone powers down. If you just power down the phone will reset the recovery to avoid TWRP. You have to remove any power source to force a shutdown before it can reset. Please feel free to respond and I’ll be happy to help to the best of my abilities!
Thank you so much for this tutorial. It worked perfectly in my SM-G900MD, and it's easier than the method suggested by the Lineage OS page itself. :good:
Thanks, these steps worked just fine on an SM-G900T, and were very easy to follow.
Thank you! This worked beautifully.
Only thing that didn't work the first time is, is that it told me to download the Gapps Android 8.1 file instead of 7.1.
I hear people talking of unlocking the bootloader in order to install a custom ROM. Why haven't you mentioned that in this article?
Had the "FAIL! (Auth)" problem with flashing TWRP with Odin.
It seems that after I have disabled Reactivation Lock (the standard feature that requires activation of the phone with Samsung account) it helped to succeed flashing TWRP.
Hi All,
Thanks for a great and useful guide. Whilst it says this can be achieved without root, which is fantastic... It doesn't mention anything about tripping Knox or not?? I assume this will trip the Knox counter, won't it ?? Or do this method bypass that ??
Thanks, Lister
adult supervision needed for Samsung S5 Lineage 17 install
Hi, I'm good with adb and fastboot, running Linux with the commandline Odin4. I can get the phone to the warning screen about the danger of installing other Roms. How do I proceed? What are the commandline options to use to flash the LineageOS 17 with odin4 ? The Odin4 help file isn't very helpful.
Could not do normal boot
I am not an expert at this and I am having the same issue as The Verg
I have a message at the top "Could not do normal boot" same as him
I've been at this for 2 days now I'm just about at my ends wit
My phone is a Samsung S5 Active model SM-G870W
and I can easily rooted it or reinstall the stock file and put it back to original
and I've done that hump time but this TWRP file I just can't install it
to update this phone to a more recent software and basically install
an S8 or S9 software in it (mind you version 9 Pie would be OK0
and make this old phone a real beast.
I read somewhere about the OEM button which does not exist on this phone
whatever explanation they are giving to unlock it and make the button appear
all of a sudden is bs in my book.
Now please help me with this phone and the other guy by the same token
Is there another way I can get into this phone and wipe it clean and
boot it with thru the abd file or access the sd card or the internal
storage of the phone.
How can I add a picture of my phone to this thread
Before you start, make sure to put all of the files that you need in the same folder as your adb.exe and fastboot.exe because it will make things easier when you have to fastboot files to your phone. Make sure to follow the directions from the original developers of the tools below. Also, in the windows file explorer, right click on the "Name" tab, in the pop up click "More," select "Path," and also select "Folder Path," then click "Okay." This will make it easier to find the file path name if you need it when you are flashing a specific file to your phone using ADB.
Once you navigate to your android fastboot/adb folder, at the top of your file explorer, click in the address bar, this will highlight the text blue in the address bar, delete the text in the address bar, type CMD and then press enter. The adb/fastboot command window will pop up and be ready for you to use. You may as well leave that command window, the MSM tool, credits: Lucifer6: https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ and the Tool all in One, credits: mauronofrio: https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ , https://toolaio.tk/ open in case one of these tools decides to bite you in the brain so hard your phone melts into booting itself properly.
You'll be needing this Twrp.img from this post if you're on android 11 like I am, credits: Nebrassy:
https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
And Magisk, credit: topjohnwu, which can be downloaded from Step 1 in this article https://www.xda-developers.com/how-to-install-magisk/
Credit: Sumukh for the article (code word the instructions in this article are for a different breed of TWRP then the one needed for rooting android 11 OnePlus 7 Pro, so please after booting into TWRP go to "Advanced," then in the list click "Flash Current TWRP," then reboot straight back to TWRP, flash Magisk, then reboot straight back to TWRP, then flash Magisk again, and then reboot the system ((if possible at this time)) or you'll have boot loops for breakfast), credits: topjohnwu for Magisk
And the android 11 stock rom of your oneplus 7 pro which can be found here, credit OPTeam: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/
I wasn't able to use MSM Tool by Lucifer6 because my phone didn't want to be recognized by my computer and I am not sure the files exist for android 11 to work with the MSM Tool, but if they do exist or there is a way to use the android 11 zip with the MSM Tool, please someone post it with detailed instructions so that everyone can find it.
I couldn't get the Tool All in One to work because I don't know, however, there are important files in mauronofrio's zip file in this post: https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ Grab the zip file from the link next to "All Roms on AFH." This can help get your phone back from the nightmare of the qualcomm crashdump scenario. If you are on android 11, do not flash the images in this zip folder because the zips in this post are for android 10 and I don't think you can downgrade. There are more directions about this in number 3 of this post.
If at any point you are able to boot your phone into the system, DO NOT put a password, fingerprints, facelock, swipe pattern, nudey collage on your phone to lock it up until AFTER you are sure you are completely done using TWRP, because Nebrassy's TWRP, as far as I know, is not supposed to be able to decrypt the phone once it has a nudey papier-mâché password on it. So, once you put a password on your phone, you may not be able to use TWRP again unless you like pain.
And yes, I did try, in the past week to clean install my rom, made sure to not create a password, flash TWRP and magisk, make a password for the phone, realized I needed to do something else in TWRP, deleted my papier-mâché password and the fingerprints to go along with and then try to get back into TWRP. It's really a hit or miss. You may get back in, you may end up flashing something only for it to get stuck in a TWRP booting boot loop like I did.
It's risky. Take off your password to your phone, then TWRP it up, say your goodbyes to TWRP and then finish setting up your phone with a password. Also, you may have to try plugging the OEM charging cable into different USB ports on your computer at specifically any time.
There are three different recipes that I tried to get my phone to work again after crash dumping. Any one of these could help. For me, it took doing all three, trial and error and error and error for my phone to get booted and rooted after the crash dump so you can try doing the easiest looking ones first, which are number 1 and number 2, see if that works, and then move on to the harder one.
Read all three recipes first before you try anything because some things from number two you can use in one or three. You're in for a real one right now so relax and get comfy. Take your time and make sure you follow the directions in the original posts by the developers because it will waste less of your time if you make sure you extract everything and other scientific ratchet. And you'll make less of a mess of your phone than it already is.
It's bricked, not dead. Hopefully. Hopefully, it's not dead. And I'm not much for hope nor am I much for being blamed if your phone slips into an endless hell pit, it contacts a plane's black box and directs said plane to land onto your roof, or some other maniacal nonsense backwater dribble okay let's get started.
1.) Easy: I used a combination of movements buttons including power off and volume down, only volume up and volume down which did other things, and power off and volume up. At first, none of these movements buttons would take me to fastboot mode. It would just keep rebooting to qualcomm crashdump mode no matter what.
Flustered, red, breathing hard because I don't walk enough, I tried these movements buttons again and again and again and again and not always in the order I wrote them down. I kept trying until I saw some Chinese writing.
Choose the first option even if you can't read the text. Guess where the "Okay" (bottom right) is and click it. The text--the first option--is highlighted in blue, which I should have said in the first place. Hopefully after twitching that phone for a good 30-45 minutes or more depending on how long you like crying, it will finally boot into fastboot mode. Plug the phone to the windows, fastboot boot the twrp.img from Nebrassy in the CMD window. If you are still trying to root, grab a usb or an external hard drive that has the rom zip and the latest magisk.apk that you need for your phone (directions below). If you are not trying to root, grab a usb or an external hard drive that has the rom zip and just flash the rom and that's it (directions below).
Plug the USB storage into your phone. On twrp go to "Mount," click the checkbox next to "USB Storage," click "Select Storage," then in the pop up click the circle next to your USB or external hard drive or whatever you're using. Go to "Install," select the zip of the rom on your USB Storage, click "Install."
You can then flash twrp afterwards by going back in the past and selecting to have TWRP flashed automatically after a rom installation; it's in the options. Or by going to "Advanced," then click "Flash Current TWRP" (mind you this is for the Oneplus 7 Pro using the TWRP 3.5.2_11-Nebrassy image in October of 2021, so if you're reading this and have a different phone or you're from the future, please, don't laugh at me if the current way of flashing TWRP is outdated by the time you read this).
Then you must flash magisk, reboot to TWRP recovery, and then flash magisk again or else the phone won't boot. After flashing magisk that second time, you may reboot the system. Once you get past those sussy terms and voluntary agreements, magisk will look like an android 1 icon. Click it.
The phone will ask you for your hand in marriage by asking if you are truly ready to jump off the deep end by allowing magisk to install unknown apps. Click I do, and magisk will install. Then, magisk will ask you to install the other half of itself, and again, make that app yo baby momma by saying yes, yes, yes. And now you have a new phone with none of your old life to spy on you and tell you how good you weren't in the past or whatever.
3.) Not so easy, but manageable. Caution, read slowly: Another thing I did try was to flash all of the images in the stock rom zip. You can download the correct rom for your phone in this post, credit OPTeam: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/ ,search the googles, or use the OEM website. Then, use the payload dumper method from here: credits to djsubterrain
https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/
After I djsubterrained my payload, all of this sounding unnecessarily dirty, I put it in this other thing that I tried (directions below): credits to mauronofrio
https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
I downloaded the zip file from the above post in the link next to "All roms on AFH." Extract it. Once I did the dump on my payload, I took all of the extracted images from the "payload_output" folder, put them in a new folder inside of mauronofrio's extracted zip folder, named that new folder "images," and just renamed the original "images" folder that was in the zip file to something else.
In mauronofrio's extracted zip folder, I copied the file named "flash-all-partitions-fastboot.bat" from the "Others_flashall" folder and pasted it into my new "images" folder. I double clicked on the "flash-all-partitions-fastboot.bat" file. An alluring window opened and I typed "Y" for yasss and then clicked "Enter."
And then that flashed most of the images to the phone. Not all of the images flashed. Some of them said "failed," but the important ones like the system.img and boot.img, among others, flashed successfully. I have no idea if using that specific ".bat" file was the right one for my situation because I wasn't sure if I was wearing comfy enough pants to be seen by the oracle.
After that, I did the the whole fastboot boot to TWRP and flashed the zip rom over again using my USB storage because it was easier for me to do that than to figure out how to adb sideload when the adb sideload button in TWRP wasn't working and while I was crash dumping for qualcomm, my phone refused to be recognized by the Tool All In One and the MSM Tool. Then I flashed TWRP, then I flashed magisk, rebooted to recovery, flashed magisk again, and then I tried to reboot to the system. But my phone booted back to twrp, a lot, a lot of times before the end of this story.
2.) Also easy: I think from TRWP (or you can use the power and volume buttons mantra from number one) I clicked on reboot the bootloader from fastboot mode. I used the up and down volume buttons to select "Bootloader" or "Start" (do both until the "Boot Reason" screen shows up for you).
For whatever reason I clicked "Boot Reason" and the reason was something made up like fs_mgr_mount_all. I clicked "Next" at the bottom of the screen and it asked me to wipe everything like music and photos which I already thought were long gone. But I have a backup of my music and my photos so no big deal.
I clicked on "wipe all data," and my phone finally booted back up into the OS. I went through the completely voluntary terms and conditions and voluntarily, completely voluntarily, and no one else is here with me, agreed to the voluntary terms and conditions. And then I clicked on the android 1 icon for magisk and...
At some point in time I formatted the system using TWRP after flashing the zips and the stuffs and now even though my phone says encrypted, the first time I booted back to twrp after finishing setting up my phone and putting a password on it, TWRP said that it decrypted USER 0 after putting my password into TWRP. I have no idea how it happened.
Nebrassy's TWRP is not supposed to be able to do that for android 11 as far as I know. About 30 mins later I booted back to TWRP just to see what would happen, and sure enough it took my password and decrypted my phone. Even though I am on android 11, rooted with a TWRP that is not supposed to be able to decrypt USER 0. I don't know how. Maybe I'll try to upload a log file so that can be figured out, or maybe by now it has already been figured out. Don't know.
So, that was fun, I hope you were able to get out of the crashdump by any of the means used here or not here. If you were able to get out of the qualcomm crashdump some other way or have advice on how any of the recipes could have been cooked better please post it in a forum or in this thread or sector B.92-80 of space so that no one ever comes close to using the very last tears their body has to offer.
I'm sorry if I forgot to give credit to anyone but at this point you'll have to flash me into recovery to get it. Or just say "I belong in here too," and post a link to your something helpful.