Newbie advice needed on region changing P20 Pro - Huawei P20 Pro Guides, News, & Discussion

(Please delete, post moved to other forum)
Hi all,
So i,ve been reading the forums here for a little while, gathering as much info as i possibly could. This is my first post, in hopes of getting a little more clarification from some of the more experienced people on here.
Im currently living in China, where I plan to buy a couple of P20 pro’s, one for me and the other for the wife. The phones here in China are normally locked down, with no google play, and normally installed with a whole bunch of local apps.
I would like to flash an international stock firmware back to the phones. From what I’ve read, i will need to first need to install TWRP. Im using a MBP, so im guessing ill need to install the Android Debug Bridge.
Im a little confused when it comes to the firmware file versions. I realise that the handset model changes somewhat, so I guess im asking what do I need to be careful of in this regards? What do all of the different letters and numbers in the firmware file mean? I’ve worked a few out, but a definitive guide would be much appreciated.
If I want to get to a non-country modified version, of the stock firware, then what file should I be looking for? Im guessing its a non-region specific version. Is it fine to just flash this to the phone using TWRP, as long as its the correct version, dual sim, 6Gig mem, 128G storage, and the P20 Pro. Or do I also need to be aware of some other differences?
Finally what is the preffered method for unlocking the bootloader? I’ve seen different post, some mentioning registering with Huawei, and other talk about an unlock tool... what do you use?
Any help gratefully appreciated.
Bp_tec

Bootloader
Deleted

Related

[Q] Need the Rom for SHV-E150S

I have been looking for the official firmware of SHV-E150S for the past three days, and I came up empty.
I have tried various methods, such as the KIES hack, without any luck.
In case you are wondering SHV-E150S is the Korean version of the Galaxy Tab 7.7 LTE
The problem with SHV-E150S is that since it's not a popular phone in Korea, Samsung is neglecting its support for the phone.
Thus, there has not been a single firmware update since its release early this year. So I do not think I can use KIES to obtain the firmware
I am really desperate right now, and any help to find a firmware for SHV-E150S will be greatly appreciated.
By the way, according to the KIES registry information, the Software Revision version is E150SKRFB25, which I'd assume it to be the firmware version.
Also, if other (foreign) firmwares can be used for the phone, please give me some pointers or directions.
I really don't care about maintaining the locality or korean-specific aspects of this phone
Thanks in advance.
I didn't even know there was a Korean LTE version, let alone one with PHONE functions. I wonder if a dev can hack an image of that tab to work on the i815 to gain phone functionality. The E150S seems to have different LTE bands tho ;[
E150S: http://pdadb.net/index.php?m=specs&id=3436&c=samsung_shv-e150s_galaxy_tab_7.7_lte_m16
i815: http://pdadb.net/index.php?m=specs&id=3257&c=verizon_samsung_sch-i815_galaxy_tab_7.7_lte
I can dream, right ?
Sorry tho. I Wish I could help.
Maybe a dev here can help you obtain CWM for the device so that you can create a stock nandroid image?
Actually all I need to do is root the phone, since I need it for development.
Since a rooted firmware does not exist, I just assumed that I would need the stock firmware for rooting.
Please correct me if I am wrong, and let me know how to root it without getting the stock firmware.
This root method has worked so far for the 6800, 6810 and i815 versions. Maybe it would work for you?
http://forum.xda-developers.com/showpost.php?p=21584547&postcount=1
ngeroons 41.75.
Thanks for the input,
But it says,
E:signature verification failed
Installation aborted.
And, something funny about my tablet is that it seems like it's not reading from the SD card. I had to save it in the tablet for the recovery tool to see the file.
Problem Solved!!
I finally got the firmware thanks to
samsung-update.com
SAMMOBILE
The firmware for SVH-E150S can now be found at either
sammobile.com
samsung-updates.com/latest-firmware
It seems like I can't post the urls since I am new to this forum....
So can't write down the full URL, but I figure most of you should know these websites already
GalaxyTab 7.7 LTE - ICS_UH11
http_://www_.mediafire_.com/_?aqt3cf3pijp9j
Rom file download via the following link.
Ps. '_' Delete
must root shv-e150s
Dear kthlee,
It appears you were able to download the ROM image and root your galaby tab. I bought a shv-e150s in Korea last year. And I very much want to root it to get rid of several annoyances that are useless if you are not in Korea. Can you perhaps post a step-by-step of how you did it? I know how to download the image from sammobile, that is not the problem. What to do afterwards is what I do not know. I fear I will just end up with a newly formatted tablet, still not rooted. Thank you in advance.

Just got a Z3, need help

Hey, so I'm new to the whoel flashing thing. Plus I've been reading that Sony is (finally) going to get Marshmallow out for the DD6616 (yes, silly American here)...
So do I download the FTF from here that says the "T-mobile America" one, and that will debrand it? I don't get the generic global once since that's a different model, right? Finally, should I just root/recover it with the flasher that was linked here? (I'm fine with that), and if so, where would I find a newer rom to flash for 6? (or do I have to wait). (I'm referring t the FTF thread in General)
Right now I haven't done anything to the phone, no bootloader, recovery or rooting.
Actually, I seem to be having some trouble with hte program. It says that my phone "bootloader" cannot be officially unlocked. Also, after a failed attempt to root the phone, it's gving me an "Error: Illegal key size or default perameters"
Not sure what to do about it...
Basically I want to "debrand" the phone. I'm fine with most of the sony stuff (or just disabling it), and hwo to stop "what's new" from popping up, but I want to get rid of the T-mobile stuff since I'm not using it. I'm just trying to get a more "stock" experience with my phone.
Edit: I should add that I'm using Cricket since it's the cheapest with my family's plan and stuff, and that it's beign weird with wi-fi calling, giving me a sim card error with it (hence why I'm trying to "debrand" it)
(sorry for posting this in General eariler, didn't see the Q/A forum)

Flashing Kyocera Duraforce Pro?

Hello, I'm new here.
I purchased a used AT&T Kyocera Duraforce Pro (E6820), and I use T-Mobile. It's the exact same hardware as the T-Mobile version, just a different ROM*, and the T-Mobile one has a few customizations that sound worthwhile as a TMO customer. Anyone have any ideas how I could acquire and flash the T-Mobile ROM?
*(as per Kyocera's website - the page where they post GPL sources e.g. kernel - and the carriers' pages, the ROMs are E6820 6.0.1 (1.802TC) vs E6820 6.0.1 (3.030AT))
If you haven't updated it (software version 1.015AT), then we're both in luck. If it's on anything newer than 1.017AT there's no way for me to do what's necessary to determine/enable crossflashing or downgrading between versions or, in your case, simply enable radio bands 12, 66 & 71... although you could try asking AT&T for the carrier unlock code, which will probably allow at least partial functionality w/a T-Mobile SIM. I might be able to determine the code for your device myself otherwise, but I'll need details you'll have to get from files you can only hopefully access without root, as those kernel sources are mostly useless as far as providing the information needed & nobody gives af about this phone, aside from the handful of people who have posted on here about it that at best don't seem to get what (short of leaked engineering files) it takes to modify something this locked down & recent. In short, "no." E6810 is the only one with consumer flash restore, E6830/E6833 is the only one with provider available OEM service flash ability, and E6820 (your version, if it's an earlier one) is the only one that shipped with firmware which isn't too recently patched to get root without using a yet published exploit or methods that first require files nobody but factory techs & provider/OEM engineers have, or at the very least what you might well be holding (if older & not updated) plus a lot of work & luck on my part or probably eventually some 14yo in Russia, but so far I don't think anyone's even managed to get temporal root on it aside from myself & while you could technically, maybe, hot-flash from that, if it still works on newer builds, it's unstable & there's no image for you to flash unless I can get recovery imageloading over usb or from SD working enough someone can dump one. The only image available is 5.420VZ & that won't flash on anything but E6810 because, if nothing else, you can't get it to where it'll enter the mode to receive it & do so. Likewise, I don't have the Sprint service utility, but it won't work on anything other than E6830/E6833, so I don't even know what means is used on E6820 at all w/o looking at files contained in areas completely inaccessible without root. I might, however be able to get that information from the OTA update file or just get root, depending on your current version
Diactoros said:
Hello, I'm new here.
I purchased a used AT&T Kyocera Duraforce Pro (E6820), and I use T-Mobile. It's the exact same hardware as the T-Mobile version, just a different ROM*, and the T-Mobile one has a few customizations that sound worthwhile as a TMO customer. Anyone have any ideas how I could acquire and flash the T-Mobile ROM?
*(as per Kyocera's website - the page where they post GPL sources e.g. kernel - and the carriers' pages, the ROMs are E6820 6.0.1 (1.802TC) vs E6820 6.0.1 (3.030AT))
Click to expand...
Click to collapse
Did you find a way?
chikosneff said:
Did you find a way?
Click to expand...
Click to collapse
Unfortunately, no. It works on T-mobile with the AT&T ROM, but wifi calling doesn't work, which is really a problem. I'd still be glad of any insight anyone could provide.

Help with downgrade?

What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.

Sprint LG G7 flashed to G710ULM. Want to update. Need help

I got a Sprint LG G7 phone from the bay that has been unlocked and flashed to G710ULM Firmware running Android 8.
I want to update to Android 10 if possible. I've never 'hacked' into a phone but am very familiar w/ hacking gaming consoles and feel like I am in familiar territory. With that said, I've read many existing guides and tutorials but have some questions?
1) How do i create (or find) a backup to my current FW in case of errors, etc.
2) Will flashing a FW from another country (Korea, Canada, etc.) render the network services (w/ Sprint) I have useless? In fact, will updating ANY FW render my networking services useless?
3) Do I attempt to flash an updated FW of the original Sprint model (G710PM) or an updated version of the FW that is flashed on the device (G710ULM)
4) Do i need to do an intermediate step of flashing an Android 9 FW or can i go straight to Android 10.
I apologize if any of these questions are redundant to any currently existing guides or posts. I did my due diligence of looking everything up as best as possible before posting these questions. Any help is greatly appreciated.
War Destroyer said:
I got a Sprint LG G7 phone from the bay that has been unlocked and flashed to G710ULM Firmware running Android 8.
I want to update to Android 10 if possible. I've never 'hacked' into a phone but am very familiar w/ hacking gaming consoles and feel like I am in familiar territory. With that said, I've read many existing guides and tutorials but have some questions?
1) How do i create (or find) a backup to my current FW in case of errors, etc.
2) Will flashing a FW from another country (Korea, Canada, etc.) render the network services (w/ Sprint) I have useless? In fact, will updating ANY FW render my networking services useless?
3) Do I attempt to flash an updated FW of the original Sprint model (G710PM) or an updated version of the FW that is flashed on the device (G710ULM)
4) Do i need to do an intermediate step of flashing an Android 9 FW or can i go straight to Android 10.
I apologize if any of these questions are redundant to any currently existing guides or posts. I did my due diligence of looking everything up as best as possible before posting these questions. Any help is greatly appreciated.
Click to expand...
Click to collapse
I'm newbie, but i try answer you in my understanding, and of course, i take no responsibility if something unfortunate happens :angel:
1/ i dont know any way to backup whole phone, but you can flash current FW (G710ULM) again via cross flash.
2/ i dont use Sprint, but my network service is work properly with Android 10 eu, canada and ulm (lasted is Pie), you can try...
3/ yes, via cross flash (update: there is no KDZ or Dump available. Probably in the future there will be dumps of 710PM but for now there is no).
4/ no, you can flash any version, any model (except tmobile) by cross flash way.
Hi. I know this is an old post, but does op still have Sprint firmware backed up?
If you do, I would love to get it from you. I can't seem to boot off other ULM firmware and I think I need an up-to-date Sprint backup abl, laf, boot, and possibly more. If you don't, have fun with your device and have a good day.

Categories

Resources