Hi all
Seems I cannot "Xpose" my chinese A2017 in B13 firmware, ad seems our american colleagues have managed to xpose their phones, so I request some help to make the trip.
First of all would like to make some questions to avoid a shoot in my foot, and, may be, others wonder the same questions.
The start point is a Bootloader unlocked, TWRP'd rooted chinese in B13 Fw.
The target is a Bootloader unloked TWRP'd rooted chinese hardware with A2017U firmware with Xposed
What I know
- There are many separated partitions (areas) in a mobile phone, and in those areas lay different and autonomous softwares for different purposes. Some of those areas are very tied to the hardware anod other areas are not so tied. In my case, I recognise
Boot: This area is used to chosse which of the important areas are to be "active" depending the things you want to do.
Is a key area and have some checks to assure the later success of the process. Unlocking the boot means some of those checks are NOT to be performed. Screwing with this area is bricking the phone. You must be VERY careful when messing with thisRecovery: Another key area. Is activated by the boot and allows you to modify other areas. We use this to gain control of the phoneSystem: Where the phone software stays. No system ==> no phoneSystem image: The same..data: Where all our apps stay, and photos and other stuff. Is not so criticmodem: Very critic area, where the "controls" of the radios live. Hardware relatedBluetoothEFS: Another critic area, as here stay the phone identification
Please confirm if this process is possible, which areas of those are not to be touched when changing from Chinese Fw to US firmware, and how would be the process.
And another question.
Being B13 Unlocked TWRP:
What happens if I execute the stock B13 SD firmware instalation procedure?
Will I loose TWRP?
And what happens with the bootloader?
Thank you very much for your help. Will try to build up a guide if successful...
Related
Hi, I have been trying to get my s4 i9505 networked unlock. It's currently on EE. I bought it from someone who has gone abroad so can't ask them to get ee to do it. I have tried 3 online unlocking sites, the last was recommended on here but non of them can do it. I have tried to install several firmwares but hoping that would remove the ee lock But they all seem to be ee firmware. Is there a firmware that you can tell me about which will do what I want. Or is there a way I can conect to my computer and do a hardware unlock. Hope someone can help as getting desperate now.
A friend of mine has a insurance supplied s4 i9505 Which is unlocked. Is there a way we can copy the firmware on his and install on my or completely clone the phone . ?
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Strephon Alkhalikoi said:
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Click to expand...
Click to collapse
Thank you for the reply, can I install a modem . I think I have read that you can't down grade the firmware ? If this is wrong. Where can I find the 4.2 firmware . Thanks
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Strephon Alkhalikoi said:
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Click to expand...
Click to collapse
Ok thanhs you the info , looks like I'm a bit stuck . I don't really understand why the unlocking sites can't generate a Code. If I put another sim into the phone it doesn't tell me I an incorrect sim .
unlock
Is there anyone on here in uk who can offer to unlock this phone for me
I believe (but can't swear to it) that I've managed to change my build number with flashing various roms. My number now is NXT-C900xxxx where xxx= software version. Before it had a more random set of numbers. I'm beginning to think this change has stopped my ability to apply standard ota updates.
I've downloaded the full B133 Rom, flashed the four partitions as stated on the unlock / unbrick tool. I also flashed the userdata.img file so I'd have my themes.
I then re-locked the boot loader using the method where your phone stated its locked, not relocked.
I thought as this point I should be able to apply the full b133 update.app file yet I get an error saying incompatible device. I've tried other update.app versions and I get the same issues. Also tried the ota update check and that states no updates available.
Does anyone have any ideas to get me back to a valid build number?
Thank you.
for that, ull first have to check which regional firmware u had in the first place unfortunately, we are not at a stage yet, where we can fully convert a phone as to be able to receive OTA updates, thus fool the update servers that this is the actual phone. were only capable of crossflashing firmwares, but this still makes it a modified phone, more or less...
this is why were tinkering with oeminfo backup and flash in others thread atm, this is a step towards enabling a user to fully change a phone model!
Is there any way (it's not printed on the box or anywhere else that I can see) I can find out my original region?
This may be help.
hw/eu for Europe and...
Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.
Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.
Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK
My confusion is that I thought they were for US models.
Well US version has no NFC but had a compass.
Has yours?
Mine has NFC and no compass lol!
darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.
I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
Hello guys I'm new and partially retarded. I can compute quite well but modding phones on this level is very new to me. I severely need help..
I SDcard loaded the Oreo fw from the ZTE English site and the support area mentioned nothing about "don't upload this Oreo fw to your Chinese a2017 b15 on 7.1.1 or you'll lose all modem function" and so I loaded it no problem and now the phone reports I don't have a sim card installed. When I downgraded to 7.1.1 again using another u fw I noticed it found the sim card but it can't get service still. Also now, when I tried to sdcard load the b15 nougat firmware from the Chinese zte site in recovery mode, I get footer error 21 and I can't upload the Chinese firmware now either. I'm seemingly stuck as an a2017u on a Chinese a2017 hardware chassis. I can only use the Wi-Fi and everything else on the phone. I get no cell service.
Apparently it's not bricked but I severely need guidance on returning this to its former a2017 b15 firmware so I can go back to using it with only 3g on my 4g LTE plan.
That's actually why I updated. I've had this phone second hand from a friend who claimed he had the 4G and LTE service when he was still with Cricket last year. I am starting to doubt that being truthful as Cricket reps could not get me 4g service no matter what.
Please help thank you.
@jdk309: You say Cricket (owned by AT&T) is your carrier, so I'm assuming you live in the US. But you have a Chinese A2017. As I see it, you have 2 viable choices:
1. Flash A2017 pure stock firmware. But then you will not have the Google apps, like Play Store. The A2017 doesn't support most of the 4G LTE radio bands that most US carriers use. I have heard talk elsewhere of adding new bands with QPST/QFIL, but never heard of anyone being successful with an A7. Mostly for other phones that use a Qualcomm chipset, of which the A7 is one of many. So you will still be limited to 3G.
2. Flash A2017U stock firmware, then you will have native English support and the Google apps. As I understand it, you will then need to flash a Chinese modem to get your SIM card and cell service working on the U ROM. Which modem you need depends on the firmware (Marshmallow modem for MM, Nougat for Nougat, Oreo for Oreo). But you will still be limited to 3G. Easiest way to flash a modem file is to use Axon 7 EDL tool. Or you can unlock bootloader, flash TWRP, then install the proper modem zip file.
I recommend using EDL and A7 EDL Tool or MiFlash to flash the firmware.
Other options are to flash a non-stock custom ROM, like LineageOS. Then you will have much more customization capabilities. But you will still need to use the proper Chinese modem. You call also sell your A2017 and use the money to buy an A2017U. Then you will have full 4G support.
I myself own an A2017U, live in the US, and have T-Mobile as my carrier. I have full 4G LTE service, no issues at all. But I have never tried to use the Chinese/Global A7 variants on a US carrier. I am mostly just repeating what others have said, so take it with a grain of salt.
Hope this helps!
AnonVendetta said:
@jdk309: Hope this helps!
Click to expand...
Click to collapse
More than you know! Thanks!!
@jdk309: A modem file will usually be named as NON-HLOS.bin. Install/unzip A7 EDL Tool, put the file in the right folder, boot to EDL, then flash. I'm not sure if flashing EDL zips requires an unlocked bootloader, I have read that you can brick the phone if it is BL-locked. Not sure, be careful. My BL is always unlocked, so I never have to worry about/consider it.
AnonVendetta said:
@jdk309: A modem file will usually be named as NON-HLOS.bin. Install/unzip A7 EDL Tool, put the file in the right folder, boot to EDL, then flash. I'm not sure if flashing EDL zips requires an unlocked bootloader, I have read that you can brick the phone if it is BL-locked. Not sure, be careful. My BL is always unlocked, so I never have to worry about/consider it.
Click to expand...
Click to collapse
Thank you I will keep that in mind. Yes Im in the states just as you are. I just remembered and located two screenshots I took of my old phone's firmware info page and I was wandering if you could glean any information from it that might help locate the original firmware that I was running. The two photos are in my username's page under a new photo album I created.
A2017v1.1.0B15 was the build info. Have you ever seen that anywhere on here where it has zero chinese bloatware or incomplete translation (chinese language remnants) and full 3G capabilities? Its so odd that I cant find anything like it online. Your help is greatly appreciated!!
@jdk309:
For B15 Oreo Firmware:
https://androidfilehost.com/?fid=1322778262903996734
I found another B15 file:
https://androidfilehost.com/?fid=745425885120758937
One file was published in 2017, the other in 2018. I would use the newer file, if you want Oreo. Both are Chinese firmware for the A2017, 100% original and untouched, you should even be able to install OTA updates when they are released.
You may also be able to get an A2017 Oreo SD Card zip from the ZTE China support site. I don't know Chinese so you'll have to find it yourself. Not sure if they released an SD Card update for the A2017 though. Just place on SD Card and install from stock recovery. Or you can install from TWRP with my steps (just substitute the A2017U file with the A2017 file, all other steps are the same, and remember to install Chinese modem afterwards):
https://forum.xda-developers.com/showpost.php?p=77890409&postcount=4
My Name is Maxton. I am 11 years old and trying to flash a lineage OS Equivalent on my LG V20. Any advice?
Hi Maxton,
Glad you made it here.
1.You might want to read this:
H918 - lafsploit works - trying to install latest official Lineage
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an...
forum.xda-developers.com
to decide if the LOS (Lineage OS) on H918 is for you or not.
2. And if more information needed after that, try searching for H918 Lineage (or, replace H918 with your own model)
3.
You need to start by finding out:
a. what model is your V20: (In settings and also on the label under the battery)
models with unlockable boot loaders WITHOUT using the engineering aboot:
H918 - (use fastboot oem unlock)(T-Mobile)(engineering bootloader dont work on TMO - instant brick!)
US996 - (use unlock.bin from LG) (GSM Unlocked for US Cellular with CDMA)
models that can use "engineering aboot" (leaked dev version of bootloader)
using the engineering aboot: "BUT we have an engineering aboot for the rest of V20s,
and we can just push the engineering aboot, and twrp just like back when dirtycow worked"
H910 - (AT&T) - some reports of issues
H990 - (T-Mobile, Verizon, Unlocked, AT&T for HK[Dual SIM 990N], Global[Dual SIM 990DS and Mexico[990T])
VS995 - (Verizon with CDMA)
LS997 - (Sprint with CDMA)
b. what ARB you're on, ARB0 or ARB1
dial: *#LGMENU#*model# , so if your model is H918 then ( *#546368#*918# )
choose SVC Menu
choose Version
scroll to bottom
c. what software version you are running:
SETTINGS > ABOUT PHONE > SOFTWARE INFO
d. what Android OS you are running - see that in About Phone as well, it is either Nougat 7x or Oreo 8x
With this information about your phone, a lot more of what you read will start making sense.
4. I can't give you the exact step by step, because I don't know it. However, I can give you this advice:
Do not do anything until you fully unlocked your bootloader (if it applies to your model), and verified it is unlocked. Because if you do, you may get in to a catch 22 situation where to fix it you need the unlocked bootloader, but you can't unlock it because the phone won't boot. Once unlocked, think twice before locking it back, accept OTA, etc. Read about that before doing it.
5. Try to read as much as you can before you do anything to it, especially about every situation that causes a "brick" , and about ways out of a brick. There is so much info here, but all dispersed in so many threads, you might want to think of a method of how to make sure that once you read something, you will never have to read it again, or at least be able to instantly find it. You will appreciate that over time.
6. For your second thread, try naming it in a way that has your main question, like "How to get the latest Lineage on H918?". Thing is, people are busy, they read thread titles and open only those they are interested in. Whats worse, sometimes they only search for threads titles containing certain keywords. So, that way more people are likely to read your thread.
On the other hand, some of the best guys here learned what they know by doing it, and breaking many phones in the process. The trick is that this way, you never forget and you don't waste time, so if this way suits your personality better, it is not a bad way to go, it is only things, you'll have many more.