Related
Hi guys,
I'm thinking about rooting my Nova. But I'm new to the Huawei brand. (used HTC before)
I know, if I would root it, my warranty would be lost.
Is it possible to root it, flash TWRP and unroot also delete TWRP it if there appears hardware defects and I have to send it back to the factory? Will they know (like a flash counter in Samsung)?
Thanks in advance.
Well, if you flash full update.app it will wipe all and relock bootloader. So, no root and bootloader locked. There is no counter. This does depend on what kind of hardware defect of course, some types may prevent you from flashing the update.app. I am not really sure how strict Huawei is about denying warranty on modified devices. My friend took his (huawei but not nova) into a service center because his screen suddenly died. It was rooted, bootloader unlocked, etc. They did not bother checking all that, just confirmed screen was not working and replaced it for free. This was in China though, and here rules are often seen as suggestions, so results probably vary by location
in the read me of when installing nougat,it says that we can roll back to the previous version (mm)...thing is,in settings/fastboot,its not mentioned/available anywhere ,,,i mean the option to roll back
the text is also available in firmware finder under whats new (for the selected firmware)...
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 yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?
arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)
If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs
SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.
Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .