Was on NCG with root, unlocked the Developer mode http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
ProSeriesRacing said:
Was on NCG with root, unlocked the Developer bootloader http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
Click to expand...
Click to collapse
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
smokerbond said:
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
Click to expand...
Click to collapse
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
smokerbond, Thank you . Back up & running again
ProSeriesRacing said:
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
Click to expand...
Click to collapse
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
al50 said:
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
Click to expand...
Click to collapse
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
ProSeriesRacing said:
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
Click to expand...
Click to collapse
Ok. Glad to hear that you've gotten your device up and running.
Related
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
I just flashed the OK4 tar via odin to go back to stock and take the MM update again. I wiped everything but internal and external storage in TWRP first. It's currently downloading the MM update.
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
pyrochance said:
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
Click to expand...
Click to collapse
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
djxn40 said:
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
pyrochance said:
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
Click to expand...
Click to collapse
I assumed you couldn't revert. That's awesome though thanks
Sent from my SM-G900P using Tapatalk
I can also confirm that too, I just did a downgrade to OK4, after I unsuccessfully tried to downgrade to OA6. I assume that pyrochance (http://forum.xda-developers.com/showpost.php?p=66266625&postcount=138) is right.
If i was helpful, feel free to hit the thanks button on those posts
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
ZedDedd said:
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
Click to expand...
Click to collapse
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Kreatur3 said:
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Click to expand...
Click to collapse
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
ZedDedd said:
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
Click to expand...
Click to collapse
They could allow it but won't. It's obvious with the direction they are going with the s7. I can see why maybe providers don't want you to have that power but don't know why the manufacturer cares. Beyond the pressure from cell phone companies. I don't care about knox personally. I'm way beyond the warranty period and trip it every time the day I gety phones.
highspeedfelon said:
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
Click to expand...
Click to collapse
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
alphadude said:
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
Click to expand...
Click to collapse
You are welcome.
I'm having a bit of trouble. I was on MM, then the phone started freezing up. So I went back to OK4 but I can't get past the Samsung boot up logo. It stays on there forever and doesn't move past it. I even tried to replays through Odin multiple times but still not working. I'm stuck.
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Had the same issue. Rookie mistake. I accidentally left the developer option OEM unlock disabled and viola! Had to do a reset. Also, if you had any fingerprints while using the Rom you used, You might come into issues when resetting using Odin. You might have to format your internal memory using TWRP. Im not saying its something slcertain. I just had to. The only firmware I had available was a 6.0.1 MM stock Rom and I came into issues when unlocking the phone. Remember, this was a full reinstall in Odin and the screen was locked. When I unlocked the screen it would just reboot. So, lesson learned. Make sure if you go and root your phone again never ever, ever, ever disable that option in developer.
But try it. You can follow the steps from the root guide for nougat in the threads and go up until the step where you install TWRP. Boot into TWRP and see if you can restore the backup. Chances are it might work without having to do the extra steps like reinstalling the stock firmware. If that doesn't work and you run into issues in TWRP you might need to reinstall everything from scratch again.
Thanks! Already figured it out ?
please explain
izou1838 said:
Thanks! Already figured it out
Click to expand...
Click to collapse
my note 5 is at custom binary blocked by frp lock. i think I also turned off the option of oem unlock in developers option by mistake.
I have twrp back up on pc only. please help me how to unbrick the phone now.
Unfortunately the TWRP back is no help ):
However if you have the stock full system image you can just flash that through ODIN and then re-root? easy fix.
Look for the image here in XDA I've seen it
Sir i have note 5 with csc n920pvps3bpk1 shows in phone aftar dialing *#1234# but on the box of this cell phone is printed as n920fvps3bpk1 and n9200 will u plz tell me which csc is correct and i want to upgrade it to 7.0 and its knox waranty has voided.
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Hi, I have the same problem with an SM-520F, did you manage to solve it?
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
so its safe to say that the new modem ql2 is pretty much the same sa the previous update?
Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse
For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
You will also have to re-flash TWRP via Odon.
kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.
I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.
I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!
purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??
purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:
Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks
Hello!
I want to make my phone completely stock again. (Or as close as possible if completely stock isn't possible)
I unlocked, installed TWRP, and then rooted my phone yesterday (thanks to shashank1320's guide which made it very simple), but quickly found out that safetynet will prevent me from downloading and playing certain games on the Google Play Store.
After poking around online, it seems that even switching over to Magisk instead of using SuperSU will leave intermittent gaps in time where the app will be inaccessible due to the new workaround eventually being blocked.
So I want to go back. But like a derp, I forgot to create a backup beforehand.
So far I've unrooted through the SuperSU app itself, and flashed the BOOT.img and RECOVERY.img from Dazed No More's links in the Honor 6x Repository here.
After this is where I'm not sure what to do.
I think I need to find a factory system image to flash (and the vendor.img)?
I've seen a few threads saying that putting the UPDATE.APP in a dload folder into the phone and have the phone run the update worked (This did not work for me, although I'm not sure I have the right files; I downloaded it through a tech guide site here). I extracted the system.img and vendor.img from the update.app off that website using the Huawei Update Extractor, but I am afraid of flashing them in case they are the incorrect ones. But what if they are correct? Would I be able to recover if they are not?
Also, should I download and use unSU?
I know there is this guide on the front page right now. I've downloaded the Huawei Firmware Finder, but I... don't know how to use it. I narrow it down to the model number and that is where I get stuck. How... do I use it?
Some other basic questions I have in addition to this are:
Would I just have to flash the system.img and vendor.img through adb and then it will be stock again?
Would there still be leftover SuperSU files in my phone? I want to remove every trace of it. Would flashing be enough?
Am I even on the right track? And if not, where should I go from here?
Is the term "ROM" here firmware? Are the two terms interchangeable?
Ultimately, I would want to flash stock and then lock the bootloader again.
Thank you very much in advance. I appreciate it.
Edit: Wow I forgot to put any information, sorry about that.
Honor 6x
Model Number: BLN-L24
Build Number: BLN-L24C567B360
EMUI version: 5.0
Android version: 7.0
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
shashank1320 said:
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
Click to expand...
Click to collapse
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Faifie said:
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Click to expand...
Click to collapse
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
shashank1320 said:
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
Click to expand...
Click to collapse
Okay, since those have been flashed with stock, that means I'm set to re-lock the phone! Will get around to it sometime tomorrow c:
Thank you so, so much ^^