Will a factory reset remove the v8.4 update?
No, it will not. If you installed the 8.4 update then you are stuck with 8.4. When you updated the phone, you replaced the old ROM with the new ROM. The old ROM is not retained or saved anywhere on the phone. Factory reset just resets all the 8.4 ROM default settings and removes any google accounts added to the phone, but it will still be the 8.4 ROM.
And you can not flash anything else because SP Flash Tool has been disabled by the ROM and the bootloader is locked. You should not have updated the phone if you wanted to unlock the bootloader and root the phone.
Sorry, but that's just how it is!
Related
Hello everybody,
My phone has had various problems lately and I thought that reverting to factory settings and then installing an official OTA update was a good idea.
I did a factory reset from the settings and unrooted the phone with Super SU, but it keeps telling me that the phone has been modified. I figured out I should flash a stock firmware through ODIN, but which one should I pick? I currently have I8190XXAMA4, which seems to be an Iranian firmware (WTF? I bought this phone in Italy!). The latest Italian firmware ends with ANI4, can I flash that one? Will it allow me to update OTA after that?
Remove bloatware in one click. Works on the all model with the unlocked bootloader.
Instruction:
1. Connect the device in bootloader mode
2. Run Z2_debload.exe
If after application of the program, the phone will cause an error, make a reset to the factory.
Updated 26.09.2017:
- fix t-mobile logo
Link to download:
mega.nz/#!Sp1HUZwJ!cOOON3CZtMD7XUEMP2m-GhLXt-Dp9bTvzbQo6nyxyQs
Tried this just now, works great! Cannot say exactly what it removed, but the most stock BS that I remember is gone.
Mine gets stuck on blue Motorola splash screen (unlocked, super su root, latest twrp, xposed (no modules installed))...going to go for twrp / factory reset (may just try clear data)
Did not work, could not mount OEM message in TWRP over and over...
Had to wipe & re-install from stock ROM
...fortunately back to stock is ok.
says its a virus to me......no thank you.
Could you please add the list of apps that would be uninstalled with this?
ben_jiang said:
Could you please add the list of apps that would be uninstalled with this?
Click to expand...
Click to collapse
this debload wipes completely the oem partition, in which all the operator's software lies, depending on the operator and patch logo.bin on the tmo model.
serg_gangubas said:
this debload wipes completely the oem partition, in which all the operator's software lies, depending on the operator and patch logo.bin on the tmo model.
Click to expand...
Click to collapse
You might want to disclaimer that on Sprint that will disable WiFi calling as that's embedded into the OEM partition.
*debloat
No luck. It didnt delete anything I could realise. 1st I need to delete Voicemail, CallerID, CarrierHub, MobileID but it didnt delete any of them. Version Android 8.0 OCXS27
Doesn't work on 1789-05.
All it did for me was restore the bootloader warning message I'd previously replaced and reboot half a dozen times or so. T-mobile app still installed and taking memory.
edit: apperantly it also removed the latest system update too. I think what it did was cause it to switch to other slot after failing to boot.
edit2: so I did a flashall then ran debload before even booting the first time - and it works. But I can't perform OTA updates, says no update available.
edit3: flashing magisk after this causes boot failure too
after seeing that debload worked after flashall, I decided to flashall then OTA update (then try debload again)... however after flashall it won't install the update (althought it will download then). So I decided removing tmobile stuff more important to me than update, so moved on to rooting after running debload.
serg_gangubas said:
Remove bloatware in one click. Works on the all model with the unlocked bootloader.
Instruction:
1. Connect the device in bootloader mode
2. Run Z2_debload.exe
If after application of the program, the phone will cause an error, make a reset to the factory.
Updated 26.09.2017:
- fix t-mobile logo
Link to download:
mega.nz/#!Sp1HUZwJ!cOOON3CZtMD7XUEMP2m-GhLXt-Dp9bTvzbQo6nyxyQs
Click to expand...
Click to collapse
It work like a chram , but my dailer app is removed how to get it back ?
Good Morning,
I have a carrier unlocked Australian N950F Exynos Note 8 running 7.1.1 with OEM Unlock showing in developer settings (took a week or so). My phone has downloaded but not yet installed this OTA:
N950FXXU3CRC7/N950FOLN3CRC7/N950FXXU3CRC7 (1021.03MB)
I think it'll be Oreo but I haven't checked which exact version.
I have not installed TWRP or rooted this phone yet but I'd like to do so. I'd also like to move to Oreo before I proceed as my battery life could be better.
What is the best way to proceed? I've read through some long threads and ended up confused about exactly what's the best procedure.
Is some kind or decryption required at some point? Will I lose the data currently on my phone?
I haven't installed the OTA update yet.
Thank you.
CRC7 is Oreo, 8.0 which is currently the latest for Note8 (8.1 may be a long while out if we even get it officially).
The process for rooting Oreo is basically the same as Nougat, for Oreo just be sure you are using the updated TWRP that fixes the data mount issue.
If you root Nougat first, you won't be able to update OTA so you'll then need to install a custom rom to get Oreo.
You can update to Oreo via OTA first & your data will be intact but regardless if Oreo or Nougat, after installing TWRP you'll need to wipe data to remove encryption. So yes, you will loose data. You won't loose internal or external storage unless you choose to format them but it's a good idea to make a backup of them just in case.
As for data, you'll need to use smart switch, helium, etc if you want to back it up. I have no experience with backing up data without root so I'm not sure what methods work best.
It seemed to work. I restored all my contacts, apps etc in Oreo. When I went to restart the phone and enter TWRP to flash magisk I get a message about only official binaries are allowed. Now the phone won't even boot. I'm guessing I now need to re-flash official firmware with odin just to get my phone working? Another week for OEM unlock? I waited this long because I thought the problem was resolved
Unfortunately if you have the OEM lock issue, that will never go away. So yes, you have to flash official firmware to boot again. If you were on Oreo, you can try flashing Nougat to see if you might get lucky & get OEM unlock back.
Since you have the OEM lock issue, remember to always flash the RMM state fix even if you flash a custom rom that has the fix built in. Always flash RMM fix right after flashing a custom rom. If not flashing a custom rom, flash RMM fix before booting to system after you install TWRP.
Thanks for the reply.
Was I supposed to install Samsung AntiRoot Removal and RMM State Bypass as per this guide? Is this guide the correct method?
galaxynote8root.com/galaxy-note-8-root/how-to-root-galaxy-note-8-on-android-8-0-oreo/
I'm currently downloading Oreo 8.0 XSA (unbranded Australian rom) to reload my phone and wait another week.
I would like to use the XSA Samsung rom rather than a custom rom. Is OEM Unlock available in Oreo after a week?
Thank you
I use the method listed in any of the TWRP threads. I've never heard of Samsung Anti Root Removal. By the sound of it on the page it sounds like dm no verity. You need to flash that & RMM state fix. Flash the XSA firmware you want to use. Log into your Samsung account, don't reboot for 168hrs & OEM unlock should appear. Then follow a guide for installing TWRP.
Hello everyone,
I have my phone rooted with Magisk.
I want to update the rom, but I have a doubt.
I know that after updating the phone, I have to re-install the recovery and root it again, but since it was unencrypted (with "no-verity-opt-encrypt-6.0"), I do not know if after the update the device is decrypted or it is re-encrypted (which would mean re-decrypting it with a hard reset).
Thanks in advance.
Hey guys,
So just a quick one - I got that annoyed about the BSG Google Camera not working on the global stable rom, so much so that I unlocked bootloader and flashed the global developer rom
Everything works good, Magisk is in, Google Pay etc works, but I'm not at another issue.
I get the automatic update notifications for the Developer weekly updates, so I thought ok sweet let's update it. It downloaded fine, and installed fine via TWRP, but it got stuck in a boot loop. I tried flashing Magisk, and that kind of stuff, but it would just boot loop still.
I still had the original Developer ROM that I originally flashed on Internal Storage so I just flashed that back, wiped cache, and I'm back to where I was prior to updating.
So my question is - how do you successfully update, or is there no way to do so? I'd like to update the developer rom as and when there are updates, but also maintain Magisk.
Thanks!
Try a data wipe, could be an incompatibility in the old and new ROM versions