Database Info

can I install a custom rom with unlocked bootloader?[SOLVED]

hi, I just got an unlocked htc inspire and I would like to know if there is any way to install a custom rom without root access. I tried to root it with several tools including the Easy Ace Root Tool and I can't get it rooted. tried from windows with several tools and from linux too with no success. I have rooted other phones in a few minutes ; but for some unknow reason I can't root this one. the bootloader is already unlocked (is has a big pink "unlocked" at the top of the bootloader) and it has also cwm v 5.x... installed. I was thinking of wiping all data and install a custom rom from the sd card, after all I guess I don't need su privileges from the bootloader. but I have found some threads where people who has done it, get stuck on htc screen at boot. so at this point I don't know what to do. any suggestion?

When flashing a ROM on a phone with an unlocked bootloader, you need to flash it in recovery, then fastboot flash the boot.img in the ROM zip.

you need to flash it in recovery
Click to expand...
Click to collapse
should I wipe all data first?
then fastboot flash the boot.img in the ROM zip.
Click to expand...
Click to collapse
now I got lost at this point
it sounds like...flash again?
would you mind to break that down in steps so I can understand it?

Info in the Ace Think Tank.

bananagranola said:
Info in the Ace Think Tank.
Click to expand...
Click to collapse
Ok I'll check it out
Thank you!
Sent from my Desire HD using xda app-developers app

Get it figured out?
< Coming to you live from the planet One X >

enigma2446 said:
Get it figured out?
Click to expand...
Click to collapse
Yes I did. I searched for Ace Think Tank and found this good thread:
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396&nocache=1&z=8270731476524836
but for some reason it didn't work for me. When it started the 4ext Touch Recovery flashing, it stopped with an error. I guess it was in conflict with CWM which I had installed, I am not sure. But he also explains on his post that the "recommended way" is to flash it with the Advanced Ace Hack Kit; but first you need to get the bootloader locked back. That was what I was trying to avoid but since I had no option I used Easy Ace Root Tool to lock the bootloader (Option 5). Then I downloaded AAHK(the last version I could find googling) and I finally got the phone rooted and installed a custom rom. Here are the links for the tools I used:
Easy Ace Root Tool
file-size:21mb
http://goo.gl/IhT7Fc
AAHK(Read the efffen-manual inside the folder for instructions)
file-size:96mb
http://goo.gl/QnjSsx

[Q] Android Lollipop: How do I gain recovery? [Need Help]

I have not rooted my phone yet and previously come from using nexus devices.
I'm on stock lollipop rom and was wondering how I should proceed.
step one would be backing up the TA partition.
following that, unlock the bootloader. After that I was wondering if I need to downgrade to kitkat to continue or if I could flash a kernel with twrp and try to get into twrp, wipe everything and flash cm12.1 + gapps + supersu and proceed from there.
My question is, do I need to downgrade to kitkat stock to proceed or is there a way for me to gain recovery and flash a rom without downgrading?

you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in

Richy99 said:
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Click to expand...
Click to collapse
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.

Arju007 said:
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Click to expand...
Click to collapse
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1

gregbradley said:
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
Click to expand...
Click to collapse
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).

Arju007 said:
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Click to expand...
Click to collapse
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12

gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app

ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
There are plenty of reasons to flash it, only one of them is if it is stable....

gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
Thank you! Makes much more sense now.
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Well there are unofficial builds with fixes from members who has the Leo build. The official one does not have all fixes as of yet. There are cm12.1 unofficial builds out now. Being able to test out the latest and greatest is the beauty of it.

gregbradley said:
There are plenty of reasons to flash it, only one of them is if it is stable....
Click to expand...
Click to collapse
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app

ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
For some its a first step into something new, it is always a learning curve. Some just like to have the "latest" version.

ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.

Arju007 said:
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Click to expand...
Click to collapse
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app

ondrejvaroscak said:
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
That's fine, I totally understand you! Hope to be pro xperia user soon haha :silly:

@gregbradley Had a noob moment here and now I'm stuck. I tagged you incase you would know how to help me.
So I downgraded to .93 kitkat. All worked well.
Then I managed to root it using giefroot. All worked well.
Then I installed xzdualrecovery. It booted into twrp, I wiped everything beside internal storage and tried to flash cm12.1. I received an error.
I forgot to unlock the bootloader (ofcourse).. which is the mistake I did.
So now I'm stuck. When I turn on the phone the sony bootsplash screen comes on and it does not go past that, due to my device not having a rom.
I tried holding down the volume key and plugging in the device to my computer. My computer does not recognize what device it is but it does make a notification sound saying that I have connected a device to my computer. Fastboot doesn't work on lockedbootloader as far as I know. The flashtool recognizes the device as a flash device for around a minute when connected to the computer using volume down. After a minute my device just turns off and on leaving flash mode. So that's the current status.
Do you or anyone else have any suggestions to how I can revive my phone?
and yes I know, I feel like a noob!

Never mind, I gave it another go with flashtool and managed to get it boot!
and yes, I feel like a pro!

Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing

gregbradley said:
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
Click to expand...
Click to collapse
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?

Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
Use NDRUtils app to boot to a different recovery
Or just press volume up when the phone vibrates twice when you are booting it to get to CMW

Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
/edited
i would wipe really everything despite usb otg and external sd card in advanced wipe of twrp before succeeding.
tell me if that works for you
um, i read you already had that issue again even after unlocked bootloader, try flashing a rooted lollipop .zip in recovery.
and then try wiping and flashing cm12.1 again if a full wipe (also sdcard) doesn't work
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
well, as you wrote me in pm you did mount "system", just do nothing in the mount menu after entering recovery. i also never did that.

[Question]Updating rooted phone without messing up the phone?

Hi,
TL-DR; I rooted my phone, and want to update with minimal loss of data.
Sorry for this newbie question but I really couldn't figure out everything and wanted to confirm before proceeding.
I have MHA-L29C185B138 and rooted step-by-step via the instructions on this link:
HOW TO ROOT YOUR MATE 9 with Decrypted Data in TWRP without needing a patched Boot.img
I want to update. What should I do? I isntalled Firmware Finder and downloaded MHA-L29C185B172 FULLOTA-MF. (downloaded all 3 files)
I couldn't find a complete tutorial for rooted roms. Read different and partial recommendations on different threads. Somewhere I read that I need to restore my boot and recovery partition before update. I backed my boot partition as it was a step in rooting guide but I didn't back up my recovery partition.
So could you please point me a beginner friendly guide that explains step by step updating rooted mate 9?
Thanks in advance.

I bump up this question as I'm interested in that answer also
Sent from my MHA-L29 using Tapatalk

Updating and keeping root is basically not possible, as far as I know.
Regardless of installation method, your phone will be re-locked and wiped when new firmware is installed on a rooted phone.

Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.

vipivj said:
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
Click to expand...
Click to collapse
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Sent from my MHA-L29 using XDA-Developers Legacy app

jr313 said:
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Click to expand...
Click to collapse
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?

vipivj said:
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
Click to expand...
Click to collapse
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise​ it will fail.
sent from my rotary phone

jr313 said:
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise​ it will fail.
sent from my rotary phone
Click to expand...
Click to collapse
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk

itenos said:
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
Sorry about that, you want to use the RECOVERY.img not recovery2. You fastboot that img and you will have stick recovery, and it will place it in the correct spot so need to worry about where you would need to flash it to. Hope that helps
sent from my rotary phone

Is there anyway for flash .zip files without unlocking bootloader or using TWRP?

I want to use google camera app but it needs camera2API but at the same time I don't want to unlock my bootloader or use TWRP, I searched and I found that flashing .zip files without useing mentioned operations but I couldn't able to find any new threads to do this in android 9.

deniz_nam said:
I want to use google camera app but it needs camera2API but at the same time I don't want to unlock my bootloader or use TWRP, I searched and I found that flashing .zip files without useing mentioned operations but I couldn't able to find any new threads to do this in android 9.
Click to expand...
Click to collapse
What you are trying to do requires flashing to system partition, flashing custom zips to system partition requires either root or TWRP(TWRP requires unlocking bootloader, it may or may not be possible to root the device without unlocking bootloader), you can't do it without one of these two things.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
What you are trying to do requires flashing to system partition, flashing custom zips to system partition requires either root or TWRP(TWRP requires unlocking bootloader, it may or may not be possible to root the device without unlocking bootloader), you can't do it without one of these two things.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply I think I'm going to unlock my bootloader but I'm still not sure because when I look to sony's site it says that if you unlock your bootloader sony can charge lot of money for repair, is that true or there just trying to frighten us to not unlock our bootloader because this is also my first device and daily-driver that I try to do these things so I'm little bit nervous about that. Any advice?

2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover

This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom .​
Downloads
S5_Root_Tools_2023.7z
EMMC_15_Rom.zip -- Stock QL1 6.0
Directions For Unlocking Stock Phone
I would recommend Windows defender is turned of before starting
1. Download S5_Root_Tools_2023.7z and unzip
2. Make sure Usb debugging is enabled on your phone
3. Plug in phone and run Safestrap.exe and follow directions on command window
4. This process is pretty much 1 click all automatic except following command window prompts
5. This will detect if your phone is EMMC 11 or 15
6. If it detects EMMC 15 it will automatically unlock your bootloaders.
7. Once process is done reboot too twrp and flash rom of choice or use provide one and flash root zip of choice
Regular Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk Delta
Releases · HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
ETFSU
EFTSU Root Solutions
The Largest Database for the Root Solutions on the Internet
eftsu.com
Safteynet Fix Module
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Old Method And Old Downloads
EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip -- Rom Zip
EMMC_11_S5_Root_Tools_2022_V7.7z
-- Files Needed To Root Phone
Instructions To Root And Install Safestrap
**If you already have safestrap installed you can skip to Instructions To Unlock Bootloader
**If you are already rooted but do not have safestrap installed download View attachment S5_Safestrap.apk install then skip to Instructions To Unlock Bootloader**
Directions
1. Download both files and unzip EMMC_15_And_11_S5_Root_Tools_2022_V7.7z
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install_One_Click.cmd this should install safestrap. If this method fails countinue with below methods.
8. If above method fails you can reboot and try again or run the Manual_Install_Root_Apps.cmd and try below methods to root
Towel Root Method
These steps are only needed if above root method failed
1. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
2. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
1. You will need to be connected to a network. Click on King root app then click try root
2. Once root is successful don't click on the optimize and close the king root app.
3, Run the Manual_Install_SuperSu.cmd
Installing Safestrap
9. This only needs to be done if 1Click bat method failed. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
10. Busybox must be installed ifirst if you used towelroot method too root
Instructions To Unlock Bootloader
11. Enter safestrap now in safetrap it will ask you to swipe to allow modding system make sure to do this now . If you have not copied the EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip from the EMMC_15_Bootloader_Unlock_Zip folder do so now Click install tab and choose EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip and install.
12. When done phone will power off.
13. Reboot phone to recovery you should now have TWRP recovery installed and the choose wipe the advanced wipe and wipe data only then reboot
14. Phone will reboot and stick on red Verizon screen for probably 15 to 20 min be patient. When finally booted you will have an unlocked bootloader with TWRP recovery running a Deodexed Rooted QL1 stock MM 6.0 Rom Rooted with EFTSU with root hide and safetynet pass module
Disabling Reactivation Lock
Thanks bbsc
1. Follow above directions too obtain safestrap and root
2. Download and flash EMMC_11_NCG_KK_Safestrap_Full.zip in safestrap then wipe data
This has Samsung Setup Wizard removed so you can get through setup
3. Set up a wireless connection or use your SIM-card and internet connection from your provider.
4. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Accept too update app then allow google check when it ask
5. Login to your new account and you will be able to untick Reactivation Lock.
6. When it unticked, Navigate to Settings - Backup Reset - Factory data Reset.
7. Phone will reboot too stock recovery and wipe data and remove current samsung account and you are good too go.
8. Now proceed with unlocking bootloader step 11 you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Credits
beaups Sourcecode and tool
ryanbg
haggertk For his CID
autonomousperson For compiling the source to a app
magic_man185 For compiling the source
GeTex
klabit87 - Basically Everything
@GSMCHEN Lots of stuff
elliwigy Lots of stuff
afaneh92 -Safestrap and too much too mention
Sourcecode
https://github.com/beaups/SamsungCID

Instructions for downgrading or updating bootloaders can be found here
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
​

jrkruse said:
mine
Click to expand...
Click to collapse
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms

stang5litre said:
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
Click to expand...
Click to collapse
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days

@jrkruse awesome job...!! :good:You definitely must be bored... Lol. May try that on an old one for craps and giggles... Lol. Again, awesome to bring a lil history back to life... :good:

jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
Nice job man, much appreciated.
If you ever get bored try to make a pre-rooted rom/safestrap recovery (course no bootloader unlock) for the G930U/G935U with the latest firmware UUESACSI1 (Aug 27 2019), since it looks like Samsung has stopped updating this phone, or better yet a root-patcher for a stock sytem.img like you did for the G950/N950. I have uploaded the latest eng-boot vA/10 here: https://forum.xda-developers.com/sho...postcount=1826

jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.

googlephoneFKLenAsh said:
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve...ent/vzwemmc15chipset-dev-bl-unlocked-t4010757
Sent from some device I modified

the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?

bigstack said:
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
Click to expand...
Click to collapse
What are you extracting it with?
Sent from some device I modified

First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?

Remedy1230 said:
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Click to expand...
Click to collapse
Its really no easy process to flash an international rom if you are using Verizon then data will probably not work with out some editing. You can always try it but Verizon will probably need Verizon csc stuff to work and build.prop edits.
Sent from some device I modified

Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?

SaltedSand said:
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
Click to expand...
Click to collapse
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified

jrkruse said:
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
Click to expand...
Click to collapse
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...

al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but needs device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified

al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Yeah that's what I have in mind.
jrkruse said:
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
Click to expand...
Click to collapse
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.

SaltedSand said:
Yeah that's what I have in mind.
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
Click to expand...
Click to collapse
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified

jrkruse said:
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
Click to expand...
Click to collapse
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.

SaltedSand said:
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
Click to expand...
Click to collapse
If you stop at 12 you will just have king root and some apps work with kingroot but some do not
Sent from some device I modified