Database Info

[HELP] HTC on e8sd MM update install ERROR

hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic

Might be due to bad zip file! Download the update again and try!

Kianush said:
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Click to expand...
Click to collapse
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.

generalugh28 said:
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
Click to expand...
Click to collapse
thank you for the information, but as I mentioned in op my phone is already all stock, I havent ever moded or rooted or anything, it's stock locked bootloader

Have the exact same issue. My device is compelitely stock. Tried flashing the recovery from the downloaded OTA but still got the sama error. Hopefully someone will be able to resolve the issue.

if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.

@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.

sam5154 said:
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
Click to expand...
Click to collapse
Hi, thanks for this. I will try this once i got home.
But i have one questions, mine is Vietnam MEC_DUGL with stock lollipop 5.0.2. The RUU only available for stock lollipop 5.0.1. Can I use this RUU or should I look for specific RUU for lollipop 5.02?
Thanks!

Kianush said:
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
Click to expand...
Click to collapse
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.

sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else

Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Have you tried the suggestion above? Let me know the result! Thanks man

sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??

Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Kianush said:
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Click to expand...
Click to collapse
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html

bataskhayal said:
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
Click to expand...
Click to collapse
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!

Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Yes bos, i also did the recovery trick but still cant make it work. So the only solution we havent try is to flash RUU which i doubt also will make it work since my phone also factory stock. So i guess will stay in 5.0.2 for a while.

Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Hi, I have managed to finally update my Vietnam HTC One E8 dual SIM (MEC_DUGL) to Android 6.0. The problem that cause the error is the error recovery file, hence I re-install the RUU to get the correct recovery.img file. Below are the steps :
Note : Try with your own risk
1. My device is currently stock 5.0.2 no root and locked. Before starting the update process please make sure to backup all of your important data. Im using the stock HTC backup software, when you restore your device after you finished your update process, it will re-install your currently installed apps , contacts, settings, etc.
2. Download RUU for your device here : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I downloaded :
[Vietnam][DUAL][M8sd][mec_dugl][CID HTC__059][OPAJ20000] :
[Lollipop 5.0.1][2.35.425.2] : LINK
Seems not match with my current software (5.0.2), but eventually it will do the magic.
3. Flash RUU. NOTE : You will lose all of your data in your internal phone memory. Make sure to backup all of your important files.
Steps:
1) Download RUU.
2) Rename RUU to 0PAJIMG.zip (the first character is a zero, NOT A LETTER O)
3) Put renamed 0PAJIMG.zip on your external_SD
4) Boot into your bootloader and make sure your in hboot and let it update its RUU.
5) No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed RUU file to external_sd
6) After you have updated your RUU, make sure to remove the 0PAJIMG.zip from your external_sd because it will ask to update your RUU everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing RUU again).
7) Done!
Source : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
4. Reboot your phone, now your phone is back to factory stock, connect it to wifi, no need to set up any account, just go directly to software update from Settings > About > Software Updates. Just install all the available software updates (5.0.2 > 6.0 part 1 > 6.0 part 2).
5. BOOM! Your HTC One E8 now runs Android 6.0.1 Marshmallow.
6. Restore your phone from the stock HTC Backup Software.
7. Done

Managed to flash MM 6.0.1 T-mobile firmware on Verizon S5 with CID 11

Not responsible for anything that goes wrong.
Follow the steps Here EXACTLY then install Super-Su Me
(You need Super SU to continue)
Once you're done download Here and
Put 'G900TUVU1GPE1_G900TTMB1GPE1_G900TUVU1GPE1_HOME.tar.md5' in your sd card or phone storage (doesn't matter)
Install Flash fire (allow root) and touch the plus on the bottom right. Select "flash firmware package" and select the file you put in your storage.
Once it is finished you're gonna see it reboot and show a screen telling you it failed. Take out the battery and reboot into Download Mode.
Launch Odin, press AP and flash both the recovery and the boot files.
once done, remove you're battery and reboot into recovery, wipe data and cache.
you're all done!
Boot may take a while (2.40GB Firmware) so make sure it stays in a cool place. It will get hot.
Screenshots coming soon

Can we get a link to the T-mobile firmware? Great find!!! I can't wait to see some nice 6.0.1 roms.

This should have hardbricked your device, you got very lucky.

Lightn1ng said:
This should have hardbricked your device, you got very lucky.
Click to expand...
Click to collapse
No hardbrick just a softbrick. Remember flashfire only flashes the bootloader partition when a checkbox is checked.

Hariiiii said:
No hardbrick just a softbrick. Remember flashfire only flashes the bootloader partition when a checkbox is checked.
Click to expand...
Click to collapse
I believe the bootloader checkbox is checked by default. I use TWRP so I don't quite remember.

Lightn1ng said:
I believe the bootloader checkbox is checked by default. I use TWRP so I don't quite remember.
Click to expand...
Click to collapse
Nah you have to go all the way in to settings to change it and you get a warning confirmation message AND the setting gets reset to not flashing bootloaders every time the app loads.

Hariiiii said:
Nah you have to go all the way in to settings to change it and you get a warning confirmation message AND the setting gets reset to not flashing bootloaders every time the app loads.
Click to expand...
Click to collapse
I wish fastboot did this too *looks at my hardbricked Kindle Fire HD*

Lightn1ng said:
I wish fastboot did this too *looks at my hardbricked Kindle Fire HD*
Click to expand...
Click to collapse
Just flash a debrick image.
============
Nice find OP!
Finally we can enjoy MM with root!
Do all VZ services still work like VZ Messages? Does MMS work properly?

smokerbond said:
Just flash a debrick image.
============
Nice find OP!
Finally we can enjoy MM with root!
Do all VZ services still work like VZ Messages? Does MMS work properly?
Click to expand...
Click to collapse
Ahhh....What!? I see the words MM, Root, And CID 11......This can't be the case. I don't believe it. Need more verification.

Gxzn said:
Not responsible for anything that goes wrong.
Follow the steps Here EXACTLY then install Super-Su Me
(You need Super SU to continue)
Once you're done download (Still Uploading) and
Put 'G900TUVU1GPE1_G900TTMB1GPE1_G900TUVU1GPE1_HOME.tar.md5' in your sd card or phone storage (doesn't matter)
Install Flash fire (allow root) and touch the plus on the bottom right. Select "flash firmware package" and select the file you put in your storage.
Once it is finished you're gonna see it reboot and show a screen telling you it failed. Take out the battery and reboot into Download Mode.
Launch Odin, press AP and flash both the recovery and the boot files.
once done, remove you're battery and reboot into recovery, wipe data and cache.
you're all done!
Boot may take a while (2.40GB Firmware) so make sure it stays in a cool place. It will get hot.
Screenshots coming soon
Click to expand...
Click to collapse
If this is true , then you the men off the year ! Lets wait and see

@Gxzn
Can you verify you are Rooted on a MM ROM with a CID 11 chip please.... Talking about screenshots here.
I only ask because I think some people are misunderstanding what you accomplished. I don't believe you are actually rooted on a MM ROM with CID 11 chip.

Stupifier said:
@Gxzn
Can you verify you are Rooted on a MM ROM with a CID 11 chip please.... Talking about screenshots here.
I only ask because I think some people are misunderstanding what you accomplished. I don't believe you are actually rooted on a MM ROM with CID 11 chip.
Click to expand...
Click to collapse
I have to agree... There's a lot of brilliant minds that put a lot of thought into unlocing the 11 chips bootloader. Which is necessary to run 6.0 rooted roms. To my knowledge u would be the first to actually do it. I just don't imagine it being accomplished in such a sloopy and simple manner.

verification needed, probably unrooted.

Alright, so i recently got stuck on the tmobile screen and won't continue again, tried reflashing and doing everything over and it did not work, this time i tried it with Lolipop (tmobile version) and this one worked this time, not sure what went wrong or what i did to get it, but with MM it boots up to t-mobile screen now

So you can boot a stock Lollipop T-Mobile rom on a Verizon S5? I have to see the proof. Pure stock. Unrooted. Screenshots.

Mattix724 said:
So you can boot a stock Lollipop T-Mobile rom on a Verizon S5? I have to see the proof. Pure stock. Unrooted. Screenshots.
Click to expand...
Click to collapse
Here you go

UPDATE: So I tried MM again and everything boots up to "starting apps" then it restarts and then gets stuck on the tmobile screen

https://mega.nz/#!xFUiDTZZ need a key

Gxzn said:
Alright, so i recently got stuck on the tmobile screen and won't continue again, tried reflashing and doing everything over and it did not work, this time i tried it with Lolipop (tmobile version) and this one worked this time, not sure what went wrong or what i did to get it, but with MM it boots up to t-mobile screen now
Click to expand...
Click to collapse
the base has to be the same if you are on lollipop you can flash a lollipop g900t firmware it has to do with fact that you on a lollipop kernel that's why mm t mobile firmware didn't work
to do this the easy way flash only the system img in flashfire then you can be on g900t firmware on your s5 verizon
you have to use the closest lollipop g900t firmware you might have to try a few until you don't have cell connection problems
for me to have g900f firmware on g900v ok3 and boi3 firmware didn't have cell connection problems

I didn't get it to boot either maybe some one more experienced can get of to boot

Please help: How to return htc u11 to stock

Hi guys,
My phone now is on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
What are the steps to return the htc u11 to stock please?
The original software number of my phone is: 1.11.400.4
EDIT: I went to: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
& downloaded stock recovery & nandroid TWRP backup (for 1.11.400.4).
However, I couldnt flash that nandroid TWRP from TWRP recovery.
Long story short, I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!

dsymbol said:
Hi guys,
What's the process of returning the htc u11 to stock please?
Googling doesn't give me much result.
Long story short but I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
Click to expand...
Click to collapse
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.

purple patch said:
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
Click to expand...
Click to collapse
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks

dsymbol said:
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik. I'm more of a trial and error guy lol. Read guide pages to know for certain, check HTC 10 guides, same steps.

purple patch said:
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik.
Click to expand...
Click to collapse
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch

dsymbol said:
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
Click to expand...
Click to collapse
Get the one from here and follow instructions. That's what the thread is for. https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048. Sorry i don't have time to do the leg work for you (i'm out atm), but it's all there.

download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814

Use the ruu, you might need the HTC drivers but in the future never not make a backup, 15 mins could save u a major headache

AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
I'm downloading it now & will report back very soon.
Thanks for the tip AllGamer!!!

AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you

dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
If you don't have an external SD.
1. Lock your bootloader.
2. Boot to download mode.
3. Open a cmd window and run the below commands.
fastboot orm rebootRUU (hit enter)
fastboot flash zip (drag the zip into the cmd window then hit enter)

dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.

AllGamer said:
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
Click to expand...
Click to collapse
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4

LeeDroid said:
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
Click to expand...
Click to collapse
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now

dsymbol said:
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
Click to expand...
Click to collapse
Added an extra step incase you don't have an external sd

dsymbol said:
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
Click to expand...
Click to collapse
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227

michaelbsheldon said:
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
Click to expand...
Click to collapse
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4

LeeDroid said:
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
Click to expand...
Click to collapse
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice

dsymbol said:
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
Click to expand...
Click to collapse
adb reboot download
fastboot oem lock

LeeDroid said:
adb reboot download
fastboot oem lock
Click to expand...
Click to collapse
Confirmation number: 5G354245BV234401U

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

Nokia 3 fastboot boot loop

In trying to root my Nokia 3, I installed TWRP custom recovery but realised that I forgot to install magisk manager. Upon rebooting the phone out of TWRP recovery mode my Nokia 3 is now stuck in a boot loop such that whenever I turn the device off or reboot it, either from adb or TWRP, the device inevitably only reboots in fastboot mode. Even using the fastboot reboot command doesn't work and only boots it up again only for it to enter fastboot mode immediately.
This means that I can't access the phone as usual meaning I'm unable to download the magisk.zip file I need to install magisk. I tried cloning the git-master and sideloading that from my computer but it said invalid .zip format.
Any idea what I can do?

Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.

andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM

Totalitor said:
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Click to expand...
Click to collapse
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )

andres_vacal said:
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
Click to expand...
Click to collapse
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?

Totalitor said:
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Click to expand...
Click to collapse
idts, have you tried to wipe and install constum ROM again?

andres_vacal said:
idts, have you tried to wipe and install constum ROM again?
Click to expand...
Click to collapse
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.

Totalitor said:
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Click to expand...
Click to collapse
No, you only look for the rom of your specific device, and then just flash it trought TWRP

andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
Ok then. I haven't actually been able to find any ROMS for the Nokia 3 other than the stock ROM.
Do you know of any custom ROMS for the device?

andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.

Totalitor said:
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Click to expand...
Click to collapse
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.

andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
My phone randomly decided it'd revert back to TWRP custom recovery today but I still can't access the main operating mode of the phone. Do you know where I can find either a custom ROM for the Nokia 3 or the stock ROM? All instructions I find online seem to be in broken english so I'm having some difficulty following a lot of the guides as they're rather vague

andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
As mentioned in my previous post, my phone reverted back to TWRP custom recovery for some reason. I tried sideloading the Magisk.zip file and it said it successfully flashed it, but now my Android system has reverted back to the standard Android recovery, booting into it by default.
it says
"alps/NE1_00WW_FIH/NE1
7.1.1/NMF260/00WW_2_15A
/user/release-keys"
at the top.

Totalitor said:
The bootloader was unlocked at some point but I guess it must have locked itself again at some stage when I reset it. Though now that my phone seems to be stuck in bootloader mode and stock recovery mode exclusively, I'm not able to view the serial number in settings as that's something one may only do when the normal mode of the device can be accessed.
I'd use adb to retrieve the serial number of the device but adb doesn't seem to be able to detect my device. I have the necessary drivers on my computer and am running on root privileges but it seems it can't detect it if it's not in the normal operating mode. Any idea how I can get the serial number?
Click to expand...
Click to collapse
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.

andres_vacal said:
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
Click to expand...
Click to collapse
It's a Nokia 3 TA-1032
Sorry, I should've specified.

Totalitor said:
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Click to expand...
Click to collapse
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com

andres_vacal said:
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.

Totalitor said:
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Click to expand...
Click to collapse
Ow, I didn't check that, my bad. Have you tried to flash only LOS?, generally the problem with LOS is that you need to have installed the stock ROM for it to function well, if you wipe and then flash LOS it will say "successful" but it won't start.
Or at least at my experience

andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?

Totalitor said:
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Click to expand...
Click to collapse
Mine was with an Asus, and the only way I could fix the horrible bootloop was managing to install the stock un-official ROM made from a well known developer. I just did a short research on this case, and all the solutions on internet say you need the ROM like I just told you, so I think there is no way if we cannot find a ROM for the device.