Hello all, forgive me if this has already been posted somewhere but i cannot find the answers, I am desperately trying to downgrade Marshmallow to Lollipop so I can install CM 12. This phone i had purchased from Amazon so it already had 6.0.1 installed and seems to have already had the bootloader unlocked so I rooted straight out the box without a problem, though I later realized that CM 12 was not compatible with 6.0.1, so then I had "unrooted" (I simply used SuperSU Full Unroot Method) and appears to have been unrooted, I had shifted between using Odin 3.09 and 3.11.1, I dont know if that makes a difference, I had already downloaded what I believe are the STOCK firmwares for 5.1.1, but Odin cannot seem to flash them onto the device.
Here are the device details:
Model Number: SM-G900T
Android Version: 6.0.1
Android Security patch level: May 1, 2016
Baseband version: G900T3UVS3GPK3
Kernal Version: 3.4.0-7500527, [email protected] #1, Thu May 5 16:18:20 KST 2016
Build #: MMB29M.G900TUVU1GPE1
SE for Android status: Enforcing, SEPF_SECMOBILE_6.0.1_008, Thu May 05 16:23:03 2016
Security software version: MDF v1.1 Release 6, VPN v1.2 Release 6.1
KNOX Version: KNOX 2.6, Standard SDK 5.6.0, Premium SDK 2.6.0, Customization SDK 2.6.0, Container 2.6.0, CEP 2.0.1, Enterprise Billing 1.2.0, OTP2.6.0, SE For Android 2.4.0, SSO 2.5.0, Shared Devices 2.6.0, TIMA 3.2.002, VPN 2.2.4
First I rooted using this guide:
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
Then I simply "Unrooted" using SuperSU.
I had tried using files from here:
https://forum.xda-developers.com/tm.../compilation-s5-g900t-stock-firmware-t3042400
And later Flashed the ROM in this guide using TWRP:
https://forum.xda-developers.com/tm...t/how-to-update-to-g900tof6-5-1-1-pc-t3141404
And ones I have found on sammobile.com
After that I've simply been trying to wipe/reset, and use Odin to downgrade, but it fails everytime, and at one point I used the "recovery" feature when you first initialize the phone as if for the first time and it download all of my apps from my old phone, and somehow it was rooted again(?) Here is a description of what it says in Download Mode:
ODIN MODE
PRODUCT NAME: SW-G900T3
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
KNOX WARRANTY VOID: 0x1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A3, P1
SECURE DOWNLOAD: ENABLE
UDC START
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 1
After this I simply reboot the system using the same method to initiate download mode. The boot sequence always hasSecurity Bit: Kernal up at the top when ever I reboot the system.
These are the files I have tried using in Odin 3.09 so far:
G900T3UVU1FOG6_G900T3TMB1FOG6_TMB
> G900T3UVU1FOG6_G900T3TMB1FOG6_G900T3UVU1FOG6_HOME.tar.md5
G900TUVS1FOL1_G900TTMB1FOL1_TMB
> G900TUVS1FOL1_G900TTMB1FOL1_G900TUVS1FOL1_HOME.tar.md5
G900TUVU1DOB1_G900TTMB1DOB1_TMB
> G900TUVU1DOB1_G900TTMB1DOB1_G900TUVU1DOB1_HOME.tar.md5
I have made sure they were complete downloads and have been using these files AS IS, I don't know whether or not I am supposed to rename them or anything.
Up at this point I no longer know what I am doing or what I had even flashed, I really don't know what I did wrong at this point. The biggest reason why I want to downgrade to 5.1.1 and install CM12 is because I have read that it is one the most stable custom ROMS available, hence the dire need to downgrade and REALLY want a good custom rom instead of STOCK android firmware.
If anyone would be kind enough to spend a little bit of your time to point me in the right direction I would greatly appreciate it,
OR if anyone can definitely recommend a VERY STABLE customizable ROM that would also be appreciated, as that would toss out the need to downgrade. Again, forgive me for such a long post, Thank you for your time.
I believe that means you can't downgrade. Not sure why you'd want to anyway. If you want to go to CM, install one of the CM-based Nougat builds, they're stupendous. I'd also stick with Odin 3.09, nothing later than that that I've tried has worked on my T3. Lollipop was the worst ever Android release.
invisiblewave said:
I believe that means you can't downgrade. Not sure why you'd want to anyway. If you want to go to CM, install one of the CM-based Nougat builds, they're stupendous. I'd also stick with Odin 3.09, nothing later than that that I've tried has worked on my T3. Lollipop was the worst ever Android release.
Click to expand...
Click to collapse
Thanks friend, I had now settled and decided to stay on 6.0.1 and just now installed Vanir, barely getting a first impression, I'll see how it goes, and would you say they work on 6.0.1 or would I have to upgrade to nougat? Also I really appreciate your time in reading my post as well as your input.
Iota1942 said:
Thanks friend, I had now settled and decided to stay on 6.0.1 and just now installed Vanir, barely getting a first impression, I'll see how it goes, and would you say they work on 6.0.1 or would I have to upgrade to nougat? Also I really appreciate your time in reading my post as well as your input.
Click to expand...
Click to collapse
Not sure what you're referring to. Would what work? I don't know what Vanir is. As I said before, I would strongly recommend going to a CM-based Nougat rom (I'm on Resurrection Remix), I don't think you'll be disappointed.
invisiblewave said:
Not sure what you're referring to. Would what work? I don't know what Vanir is. As I said before, I would strongly recommend going to a CM-based Nougat rom (I'm on Resurrection Remix), I don't think you'll be disappointed.
Click to expand...
Click to collapse
Apologies for the late reply, Vanir as I've come to find out IS actually one of those nougat based ROMs you speak of, though resurrection remix DOES sounds quite interesting and would like to give it a try, if I wanted to install RR, would I have to uninstall my current rom to get stock OS and THEN flash RR? or could I simply enter Recovery mode and FLASH RR directly without any changes? Also, what can you tell me about custom Kernals?
Thanks.
There are plenty of instructions and tutorials out there, the OP of every rom usually has flashing instructions. Briefly, there's no need to uninstall anything, ever (well, almost). Backup your apps with Titanium (at least the ones for which you want to preserve data), do a full recovery backup, flash the latest stock firmware for your device, let it do a full reboot, then boot back to download mode and flash the new rom and (optionally) the Google apps, then do a full wipe and reboot. After booting, go through the Android device setup, let it restore your apps from the cloud, then restore the apps you backed up. As new versions of your rom are released, just flash them, no wiping, data & google apps will be preserved. With your level of expertise, I'm not sure why you'd want a custom kernel. The Boeffla kernel works on the GS5 and has a lot of customization in it, but with Resurrection Remix you don't need it because there's so much customization in the ROM (for example, the only real reason I flash custom kernels is to control LED brightness at night, but I can do that with RR anyway). The kernel included with RR is just fine.
invisiblewave said:
There are plenty of instructions and tutorials out there, the OP of every rom usually has flashing instructions. Briefly, there's no need to uninstall anything, ever (well, almost). Backup your apps with Titanium (at least the ones for which you want to preserve data), do a full recovery backup, flash the latest stock firmware for your device, let it do a full reboot, then boot back to download mode and flash the new rom and (optionally) the Google apps, then do a full wipe and reboot. After booting, go through the Android device setup, let it restore your apps from the cloud, then restore the apps you backed up. As new versions of your rom are released, just flash them, no wiping, data & google apps will be preserved. With your level of expertise, I'm not sure why you'd want a custom kernel. The Boeffla kernel works on the GS5 and has a lot of customization in it, but with Resurrection Remix you don't need it because there's so much customization in the ROM (for example, the only real reason I flash custom kernels is to control LED brightness at night, but I can do that with RR anyway). The kernel included with RR is just fine.
Click to expand...
Click to collapse
Thank you, this has actually given me a lot more insight on flashing Roms, I'll definitely be giving RR a try, it probably should have been my first choice haha.
Iota1942 said:
Thank you, this has actually given me a lot more insight on flashing Roms, I'll definitely be giving RR a try, it probably should have been my first choice haha.
Click to expand...
Click to collapse
I should have included that after flashing the latest stock firmware, you'll need to re-flash a custom recovery first before you can install the rom (which is flashed from the custom recovery, not from Odin).
I hope I didn't mess up my phone for not doing so (Re-Flashing custom recovery), I had "successfully' and had also updated the ROM to the latest version
"RR-N-v5.8.2-20170304-klte-official"
Android version 7.1.1
Build # RR Nougat 7.1.1_r21 - NOF26W
I had wiped cache, dalvik, system, and dalvik cache and then simply flashed RR and GApps without Installing Stock rom, rebooted, and started as normal, downloaded new RR version, updated, flashed, forgot to download NEW GApps, went through with downloading THEN flashing, and now everything seems to be in order, except not quite, I have tried resetting the APN as well as wiping the cache in recovery, but I can't seem to get my mobile data to work, I have tried looking in many places but can't seem to find the answer, I'm sorry for being such a bother.
invisiblewave said:
I should have included that after flashing the latest stock firmware, you'll need to re-flash a custom recovery first before you can install the rom (which is flashed from the custom recovery, not from Odin).
Click to expand...
Click to collapse
Scratch that, I managed to get it working by reflashing 7.1.1, and I sincerely thank you for your advice, it really has served me well. Cheers
Related
My stats: Fairly comfortable with computer and other forms of tech, but have only recently began diving into the Android system. I have limited development/programming experience, however, I'm not a novice or noob to it but definitely not advanced. Importantly for those willing to help I understand most terminology and can follow instructions. Thanks in advance.
Phone Stats: AT&T Samsung Galaxy Note SGH-i717
Android Version: 2.3.6 (Gingerbread)
Baseband Version: i717UCLF6
Kernel Version: 2.6.35.11
Build number: GINGERBREAD.UCLA1
Root Access: Yes
Stock Rom: Unsure, bought online.
Carrier/Service Provider: Straight Talk (U.S.) Phone was previously used on the AT&T network exclusively, and done so with an AT&T provided SIM card. After I purchased it, I ordered a new SIM card from Straight Talk (U.S.) and reprogrammed the APN settings under their instruction in order for my phone service to work correctly, and have had no problems with that.
I can't stand being on Gingerbread any longer. I guess, since my phone is an AT&T phone but I'm using it through Straight Talk I can't get any of the OTA updates. I've tried downloading the OTA's several times, both, prior to and post Root access without success in either case.
So here are my questions:
1. Am I doing something incorrectly which might be keeping me from getting OTA updates? Please remember, I've tried downloading the OTA's several times both with and without Root Access and the conclusion is the same each time: "No Updates Available At This Time. Your Phone Appears To Be Up To Date. Try Again In 24hrs."
2. Is my only option at this point to manually update to a newer firmware? If so, should I update to a newer STOCK version or a custom ROM version?
3. If a manual update is the option, after reading my above outline of my own experience with the Android system, what would be way to go? Simple, not overly complex yet doesn't assume the user is either a complete moron or can write code in his sleep. I've checked into a couple of options. Rom Manager seems like it would be a nice route to go, but in the Recovery Setup portion I basically get told I can't use that application because my specific device isn't supported.
I checked out GooManager and, unless it's just me, it seems like it's an app that likes to do all the work without telling you what it's doing exactly, but when it does ask me or tell me information, I'm not always sure how to answer or react to it's warnings.
Plus, I've noticed that sometimes when downloading a ROM, sometimes I have to "flash" the gapps myself and other times I don't.
4. Is it easier to download everything separately and apply them one by one, for example the ROM then gapps then Kernal...etc? Or look for something that has it all in one package?
I have a laptop in which I can download/transfer programs and apps between it and my Note so download space and internet access isn't a problem.
Also, it most likely isn't information that is going to help in anyway, but I live in Oklahoma, United States of America.
Thanks for all the feedback...UnluckyOnion
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
studacris said:
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
Click to expand...
Click to collapse
Thanks for all the information and help...more importantly, thanks for taking the time. I have ODIN on my laptop and have always used it when needed but I saw a highly rated and positively commented Mobile version of ODIN in the Play Store that claims you can do everything from the convenience of your phone which sounds appealing, however it's kinda pricey, especially if it doesn't work. Would you recommend the mobile version or PC version? Also, I have been doing a lot of ROM and Root research as of late, and wondered something...Why so many different Galaxy Note's? It seems as though I have the least popular version with the most popular being from the Galaxy Note "N" series, specifically the N7000. If I download and use an application that says it's meant for the Galaxy Note N7000 and I use it on my Galaxy Note SGH-i717, what will happen? Nothing, something, brick, work perfectly, etc...?
The N series is not carrier branded and sold internationally, so naturally it's more popular compared to a north American variant.
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
The international version has a different cpu, gpu and antenna, for north American LTE bands to work those key components needed to be different.
So I say again just to stress:
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
As for Odin, you're either going to flashing a stock firmware, or if you choose a custom Rom, you'll only need Odin once to flash TWRP. Then all the rest will be done in recovery on the phone itself. No need for it after you've either manually updated to the latest stock rom, or flashed a recovery for use of custom roms
So... imo mobile Odin, though being nifty, is a bit pricey for how little you'll need it, whereas it's free on pc.
I don't think mobile Odin is even available for the i717. It's not listed in supported devices.
I tried installing mobile odin and it's not supported
Thanks for the reply. And an even bigger Thanks for downloading the app and checking. I admire sacrificing your own work just to help me out. So what about yourself? Would you suggest, advise or heed caution to anymore of my questions?
By the way, what are you two running?
As long as you read the op of threads and all other important posts that follow BEFORE ever touching your phone, I'd say try a custom Rom...if you decide you don't like any of them, you can Odin flash the stock jellybean firmware at any point.
I myself am running unofficial aokp compiled and posted by a fellow team member BlownFuze.
Oh yeah, how's it running? Nice and stable or crawling with bugs? Any key selling points?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm on the stock 4.1.2 release and rooted.
Everything works, no bugs, but battery sucks. Even after removing and freezing useless processes a stock rom will never be as light and battery friendly as a custom rom.
I just upgraded to the same version. Planned on rooting over weekend. Any success since your last post? Do you nave preferred Root method?
Thanks
Unlucky Orion
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
studacris said:
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
Click to expand...
Click to collapse
Hey man, thanks, it worked like a charm. I appreciate the help from both you.
Hi y’all,
Firstly, I’m a newbie. I did some forum reading / reviewing before posting this and I hope I’m posting to correct section (take it easy on newbie ). So anyways, my question is as follows:
I have a N910CQ purchased from Turkey (currently running android 5.1.1). I want to root it but keep stock ROM for two reasons: 1) I am used to touchwiz based stock ROM and I am generally satisfied with it except the bloat ware, and 2) I want to run Cerberus on it... and actually 3) all roms I came by have certain features missing (i.e. camera / pen / fingerprint sensor does not work etc).
But after doing much research (and trial and error for the last 2 days), it seems it is not possible to root a N910CQ device running 5.1.1 android and keep stock rom on it. You can either: 1) root it and flash a 5.0.1 stock rom (and when you later try to upgrade to 5.1.1 you’ll get an error message basically telling you that unauthorized modification was made to OS and therefore you’re no longer entitled to OTA upgrade) OR 2) you’ll have to flash a 5.1.1 rom other than stock rom (such as Team Eos Rom – which has many flaws). But, so far, it seems impossible to root N910CQ and flash 5.1.1 rom.
Do any of you have any recommendations? Thank you.
anybody? any clue???
It looks like your best option would be to install TWRP recovery and use it to flash a custom kernel that auto roots your device such as this http://forum.xda-developers.com/note-4/development/n910c-kernel-5-1-1-stock-tw-permissive-t3206548 The important thing to note is your Build Number as there are many different builds of 5.1.1. You want to make sure the kernel supports the specific build you have installed otherwise you'll soft brick and need to recover either with a nandroid backup or via Odin and the full firmware/OS tar file. Use TWRP to make the nandroid backup before installing any mod so you can easily restore if you run into issues.
es0tericcha0s said:
It looks like your best option would be to install TWRP recovery and use it to flash a custom kernel that auto roots your device such as this http://forum.xda-developers.com/note-4/development/n910c-kernel-5-1-1-stock-tw-permissive-t3206548 The important thing to note is your Build Number as there are many different builds of 5.1.1. You want to make sure the kernel supports the specific build you have installed otherwise you'll soft brick and need to recover either with a nandroid backup or via Odin and the full firmware/OS tar file. Use TWRP to make the nandroid backup before installing any mod so you can easily restore if you run into issues.
Click to expand...
Click to collapse
I did this (except I flashed using Odin) and it totally worked. Thank you!
---
Just for the record though: this kernel triggered "Security Notice Unauthorized Actions Error" and so I had to change it. I'm using SpaceX now, no errors, works smoothly: https://www.androidfilehost.com/?fid=24052804347823851
Cool. I prefer TWRP so I can make backups in case something goes wrong, but whatever works.
This is the Odin ROM for the PL1 update. Requires the the use of Odin, computer, and USB cable to use. This is the stock ROM pulled from Samsung Kies3. I've flashed it inside Odin, and it upgraded my device without wiping contents, but I cannot promise the same result for everyone.
To (re)root, follow this:
https://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382/page2
The file:
https://drive.google.com/file/d/0B2iEgzRTFjrQdlhNSlg5bkE4WVE/view?usp=drivesdk
So what does the PL1 update get you? Does it improve the radio modem operations? Is it just so it will work with Nougat?
It's a security update, that's all. Note 3 is done with OS upgrades. 5.0 will be the last official
Sent from my SAMSUNG-SM-G935A using Tapatalk
Hya there..
I have been following all your posts about flashing the PL1 update through either Odin or TWRP. I am familiar with both, but wanted to ask for insight on my particular setup.
Model SM 900P (Sprint)
Im still on 4.4.2 Kitkat Killer and has been doing well but looking to upgrade if I can find a good ROM.
I am still on baseband version NC5
Kernel 3.4.0 BeastMode
I figure I would be smart to flash the Baseband and Modem to the PL1 but would of course like to keep root and keep my TWRP recovery.
Ultimately I would like to flash the DarkLord ROM or even Resurrection Remix ROM for the Note 3 on CDMA (Sprint)
This is my daily driver, and cannot afford to frag my phone so I want to be sure I make the best choices.
If I follow your posts I would do best to downlowad your TWRP Stock Pre Root zip file, and simply "recover' the file as if I was doing any normal TWRP recovery. This would then put me back to Stock Lollipop and upgrade my Modem and Baseband and get me the latest security updates (well fairly recent anyways).
In lieu of that, I can ODIN the PL1 file offered by you and this would in effect 'factory reset' my phone as if I just bought it from Sprint (well you know what I mean) and would re install all my apps etc (through Titanium Backup etc).
From there I can try Resurrection or DarkLord Mod's and load them like any ROM install?
Thanks for double checking my train of thought...
Dave
Thanks! This helped me out.
@Unidave199 -
Use ODIN to push Greaper88's PL1 file to your phone. (now you are updated.) (I just used it, it works.)
Use ODIN to push a recovery to your phone like TWRP
Find yourself a ROM you like (Darklord's is good.)
Flash ROM via TWRP (Read the ROM's OP's entire instructions for flashing.)
Final step....Enjoy!
2manyhobbies said:
Thanks! This helped me out.
@Unidave199 -
Use ODIN to push Greaper88's PL1 file to your phone. (now you are updated.) (I just used it, it works.)
Use ODIN to push a recovery to your phone like TWRP
Find yourself a ROM you like (Darklord's is good.)
Flash ROM via TWRP (Read the ROM's OP's entire instructions for flashing.)
Final step....Enjoy!
Click to expand...
Click to collapse
I hope this is the right thread for this...
Pardon my ignorance here, it's been a few years since I frequented this forum, or even XDA...
Is this what I want to use to get back to total stock, unrooted for resale?
(I've been rocking the Note 3 since it came out, FINALLY upgraded to something newer, and want to sell this to a sprint user.)
Yes it is
Just use the "CSC" file and not the "HOME_CSC." This should completely reset the device and clear user data.
Note: You can try this with EU ROMs but I'm not sure if it will work, and won't be testing to see if it works, since I see no reason to flash EU ROMs anyways.
I knew this from day 1, but was switching between various LOS ROMs so didn't have much inspiration to make a guide. Now i'm switching back to Stock-based ROMs (due to other roms having no dolby, no voice capture,...), I'll be making a guide
I'm not responsible for bricked device.
This is a guide for those who are facing issues when trying to flash US, EU stock and stock-based ROMs on the chinese axon 7 (no signal, no wifi, worse battery, or simply not booting after splash screen). Since downgrading is also a part of this guide, I will also be covering how to downgrade Nougat 7.1.1 ROMs back to 6.0.1 Marshmallow.
Important thing to note:
You must be on B13, 6.0.1 marshmallow with stock recovery, and please, DO NOT UPDATE TO B10 China NOUGAT or anything above ! This will cause a lot of problem, as from what I've deduced, US B19 is based on the China B09 update, anything above B10 won't be backwards compatible. and will cause problems like not booting, (or no wifi, signal etc after you recover the boot partition through recovery)
Now, if you're already on Nougat and want to try this guide, downgrade back to Marshmallow using EDL. Try this guide:
- Download B13 EDL (credits to djkuz from 4pda), extract it
- Download and install the latest Xiaomi MiFlash (stable or beta)
- Turn off your phone, plug it in to your PC, Hold Power + Vol Up + Vol Down, go to device manager, look for the "Port" section, and you will see something like Qualcomm HS-USB QDLoader 9008., if you see it, proceed down below. If not try again.
- right click , open properties on the Qualcomm HS-USB QDLoader 9008, go to port settings, if you see the speed is at 9600 bits per second (bps), change it to 128000 (you can skip this step, but doing it will increase your flashing speed)
- Open MiFlash, press select and pick the folder you extracted a few steps ago.
- Press refresh, if you see your device appearing on the list, press flash. (if some random errors appear, unplug the device, plug it back and immediately press refresh and press flash)
- After flashing you'll be back on B13 China Marshmallow.
REMEMBER, DON'T OTA UPDATE IF YOU WANT A SMOOTH TRANSITION TO US ROMS:
Now, to the good part:
- Download the B09 China OTA package from here (credits to Demons-77)
- put the package into your EXTERNAL sd card, internal won't do.
- reboot to recovery (Power + Vol Up)
- select the option with the word "sd" on it
- now go and pick the package that you just put in
- It will begin flashing and after that, you will have B09 China Nougat
- reboot to bootloader and install recovery (fastboot flash recovery *your file name*)
- after that you can install any roms you like, no need to backup and restore the boot partition every time you flash a US ROM, and you won't encounter strange issues like no boot, no wifi, etc.
TL;DR for those who already know how to do most of these: go back to China Marshmallow through EDL, update to B09 China Nougat with stock recovery, install TWRP and then flash whatever US stock or stock-based roms you want (just like how you would with a US phone)
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
otaconremo said:
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
Click to expand...
Click to collapse
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
spiwar said:
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
Click to expand...
Click to collapse
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Fuilares said:
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
Click to expand...
Click to collapse
Downgrading IS a part of this operation if you're already on Nougat (you need to go back to MM before you can go B09 Nougat). Why relock your BL though? Magisk root can work with Android Pay, Pokemon Go AFAIK, not sure though (since I don't use any of those apps)
tigrey said:
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Click to expand...
Click to collapse
Yes that stock ROM will be okay. Personally I'm using the latest version of BadBoyz ROM.
No you can't. Because OTA updates requires the stock recovery, and your phone probably won't boot if you flash the US Stock recovery
otaconremo said:
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Click to expand...
Click to collapse
Magisk won't work if you're using B10 Chinese as a base (as mentioned above), if you flash on B10 you'll have to flash the boot portion from the stock Chinese ROM for the US ROMs to even boot, and then you just lose magisk.
I see. Thanks for the tips. But I don't think I'll be coming back to b13 mm for that. I hate restoring data ang all the files in my internal storage.
Hi!
Could you please clarify me a doubt?
To follow this guide, must my device already be rooted?
Thanks!
Well, first part went well. After a lot of effort, because device was recognised as DFU. Anyway, I got it back to B13 with stock recovery.
On second part, when I try installing the FOTA update, it fails, giving me error: status 8. In update history, it says that the system package did not match the phone. Obviously I have A2017.
Any suggestions?
Hi guys!
At first I hope to be at the right place with my questions here. I've searched some Threads about my questions but I'm still not 100% sure how to go further now. Instead of "just trying and see what happens" I thought of "better ask again before you brick your phone! Safety first". So even if theres an answer I haven't seen, please be patient and take some consideration.
So thats whats actually running on my System:
* Stock OS (Software Version: V20d-EUR, Build OPR1.170623.026, Safetypatch March 2018)
* rooted with Magisk (v16.0; Manager 5.8.3)
The first question is about updating Magisk. Can I just update the Magisk (Mangager App and root) within the app in the meantime? There were several problems some month ago by just updating it without removing the old version before. Or do I need to remove old copies of Manager and magisk root before and flash it clean via TWRP?
Second question is about updating the ROM. How do I do this? I guess, its not possible to just click "update" in the update section of the settings, right? Do I need to unroot before? Just flash it the mentioned way or via twrp? Reflash stock recovery, unroot and then update? Or do I even have to do a clean install of the updated ROM?
I hope you understand all my questions, due to my english isn't the best. It's the first time I use a phone with just a rooted Stock Rom. Before I always used custom Roms (AOSP and stock based), and there the Update and flash-instructions are pretty clear and "simple".
Thanks in advance!
clsmn said:
Hi guys!
At first I hope to be at the right place with my questions here. I've searched some Threads about my questions but I'm still not 100% sure how to go further now. Instead of "just trying and see what happens" I thought of "better ask again before you brick your phone! Safety first". So even if theres an answer I haven't seen, please be patient and take some consideration.
So thats whats actually running on my System:
* Stock OS (Software Version: V20d-EUR, Build OPR1.170623.026, Safetypatch March 2018)
* rooted with Magisk (v16.0; Manager 5.8.3)
The first question is about updating Magisk. Can I just update the Magisk (Mangager App and root) within the app in the meantime? There were several problems some month ago by just updating it without removing the old version before. Or do I need to remove old copies of Manager and magisk root before and flash it clean via TWRP?
Second question is about updating the ROM. How do I do this? I guess, its not possible to just click "update" in the update section of the settings, right? Do I need to unroot before? Just flash it the mentioned way or via twrp? Reflash stock recovery, unroot and then update? Or do I even have to do a clean install of the updated ROM?
I hope you understand all my questions, due to my english isn't the best. It's the first time I use a phone with just a rooted Stock Rom. Before I always used custom Roms (AOSP and stock based), and there the Update and flash-instructions are pretty clear and "simple".
Thanks in advance!
Click to expand...
Click to collapse
You're asking two separate questions and they have been answered before -- the updating stock stock ROM part I've answered many, many times in many, many threads.
1) update rooted stock rom which TWRP.
You cannot use "upgrade" because you are not pure stock, you have TWRP custom recovery.
You flash with dev patched LGUP in DL PARTITION mode and UNcheck recovery partitions to keep TWRP. Then boot to TWRP and reflash Magisk, as well as the no encryption and no root check files -- just like when you first unlocked bootloader and rooted.
If you use DL Partition mode and do not UNcheck the recovery partitions, then you will end up with pure stock and have to reinstall TWRP. If you somehow mess up, then that is also the fallback procedure -- flash the new KDZ in DL Partition mode (overwriting ALL partitions) and then reinstall TWRP and go from there.
1A) alternatively, RIGHT NOW you can just flash this 21A stock ROM (made from EU 21A KDZ by @westwood24) and just re-flash Magisk.
LG-H930 OPEN EU 21A ROM
https://forum.xda-developers.com/lg-v30/development/rom-eu-lg-h930-21a-rom-t3830169
No, it's not the latest EU KDZ, but it's almost the latest. It's much newer than Europe 20D. You just flash it in TWRP and then re-flash Magisk. It's also much easier than using dev patched LGUP and DL Partition mode.
2) to update Magisk from 16.0 to 17.x, first flash the Magisk uninstaller in TWRP. Google it, download it. It will be a TWRP-flashable zip file. Uninstall current Magisk before you do #1, just to have it ready.
At this point in time I recommend Magisk 17.3. It has the latest Magisk Manager which doesn't crash on the Hide interface.
clsmn said:
Hi guys!
At first I hope to be at the right place with my questions here. I've searched some Threads about my questions but I'm still not 100% sure how to go further now. Instead of "just trying and see what happens" I thought of "better ask again before you brick your phone! Safety first". So even if theres an answer I haven't seen, please be patient and take some consideration.
So thats whats actually running on my System:
* Stock OS (Software Version: V20d-EUR, Build OPR1.170623.026, Safetypatch March 2018)
* rooted with Magisk (v16.0; Manager 5.8.3)
The first question is about updating Magisk. Can I just update the Magisk (Mangager App and root) within the app in the meantime? There were several problems some month ago by just updating it without removing the old version before. Or do I need to remove old copies of Manager and magisk root before and flash it clean via TWRP?
Second question is about updating the ROM. How do I do this? I guess, its not possible to just click "update" in the update section of the settings, right? Do I need to unroot before? Just flash it the mentioned way or via twrp? Reflash stock recovery, unroot and then update? Or do I even have to do a clean install of the updated ROM?
I hope you understand all my questions, due to my english isn't the best. It's the first time I use a phone with just a rooted Stock Rom. Before I always used custom Roms (AOSP and stock based), and there the Update and flash-instructions are pretty clear and "simple".
Thanks in advance!
Click to expand...
Click to collapse
Not sure what to tell you on your first question as I'm still running magisk v16.0; Manager 5.8.3 myself.
To your second question, and I'm sure @ChazzMatt will speak when time allows, we don't take partial ota's while running custom recovery. The process will fail. We wait for the full updated kdz to be posted by LG, and then they eventually show up here in the forum. We have enjoyed flashable TWRP zips for some of the recent updates from @westwood24 ,20D for example. Otherwise you have to install the kdz using LGUP. There are instructions on how to do this in the forums.
Hope this helps a little. I'm pretty new to offering assistance, but still trying.
Sent from my LG-US998 using Tapatalk
awesome, thanks for your quick and helpful response! really, thanks guys!
in case of flashing westwood24's ROM.. clean installation (wiping all needed partitions) or dirty flash over my running system? (i know, always backup before )
clsmn said:
awesome, thanks for your quick and helpful response! really, thanks guys!
in case of flashing westwood24's ROM.. clean installation (wiping all needed partitions) or dirty flash over my running system? (i know, always backup before )
Click to expand...
Click to collapse
in your situation, dirty flashing should work. You're already on Europe firmware with TWRP.
But yes, backup first and then clean flash if dirty flash doesn't work right.
so meanwhile I updated Magisk and the stock-ROM with your help and your instructions! everything is working without any problems
updated the ROM with westwoods24 zip, dirtyflash
so thanks again!