Related
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Dardwizzle said:
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Click to expand...
Click to collapse
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
>USB debugging off? turn it on. <--- It is and has been turned on in an effort to try to sideload KitKat, but that was a hug fail. But I will leave it on for this discussion.
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Dardwizzle said:
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
Click to expand...
Click to collapse
do check, is it running in background ? check your task manager. if so, kill the process. Kies should not run together with ODIN. Otherwise sometimes will give problem to your ODIN process.
I normally only install the USB driver only, as this is the only thing needed to connect your phone to comp (as MTP, or as ODIN connection).
Dardwizzle said:
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
Click to expand...
Click to collapse
ok, in a very simple word. download mode is basically a state whereby your phone is ready to download system files and install the system files on your device.
This is the only state possible to get a connection to your ODIN PC to flash stock firmware, recovery (in .tar/.md5 format).
How to get the KK ROM ?
1) identify your device. which model it is. N9005? N900T? N900A? N900 blablabla?
2) goto samfirmware.com (register there if you don't have account. it is free). after that you can just find your firmware by typing on the search device textbox your device model (e.g N9005), and it will come out the list of your device firmware (normally they will show for the latest firmware list)
3) choose the firmware that you want to download (if your device N9005 international 32 gb, try to avoid the Hongkong / Taiwan firmware, as they have different PIT partition).
4) once you have the downloaded zip file from samfirmware, extract the zip, and then you will get the (.tar/.md5) file. Now you can use to flash this one over ODIN.
Dardwizzle said:
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Click to expand...
Click to collapse
no. no. no.
This is how to go into download mode in your device
Not yet talking about factory reset.
But yes, you have to backup your internal storage, as sometimes upgrading will cost you to do factory reset, and your internal storage will be gone.
Dardwizzle said:
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Click to expand...
Click to collapse
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
Dardwizzle said:
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Click to expand...
Click to collapse
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
antique_sonic said:
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
Click to expand...
Click to collapse
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Dardwizzle said:
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Click to expand...
Click to collapse
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
http://www.droidviews.com/install-android-4-4-2-kitkat-ota-on-att-galaxy-note-3-sm-900a/
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
(I had to remove the link as the website thought I was adding it and gave me a no no warning that I can't post outside links cause I be a newbie!) BAH!!!
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding. It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight. I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me. I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Dardwizzle said:
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding.
Click to expand...
Click to collapse
No worries and yeah you should try to find first. by this way, you will learn faster, compare if someone do the spoonfeed.
Dardwizzle said:
It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight.
Click to expand...
Click to collapse
My pleasure to help. And no worries for late reply, as I will do the same when I busy with my real life job.
Dardwizzle said:
I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me.
Click to expand...
Click to collapse
you are welcome mate. I'm sorry to read the news about your conditions. I can't say anything about this, but wish you all the best. Don't ever feel down in whichever state you are, just do the best in life, and we will never regret that 1 more day has passed.
Dardwizzle said:
I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Click to expand...
Click to collapse
GOOD !!!
go and grab sales, rather than you brick the phone.
Once again, u r welcome mate.
Hello guys,
I'm a complete novice on rooting or flashing cellphones, I'm just a regular user of a Moto X Play XT1563 (bought in Colombia / South America) that wants to upgrade to Nougat 7.1.2.
I want the 7.1.2 just for a regular usage: apps, internet, bluetooth, NFC, camera, GPS, phone calling and of course a good battery performance.
I want to kindly ask for your guidance in all steps required for the backup and upgrade, so if you can please guide me about the whole process I will appreciate it a lot.
Thanks
jramirezdev said:
Hello guys,
I'm a complete novice on rooting or flashing cellphones, I'm just a regular user of a Moto X Play XT1563 (bought in Colombia / South America) that wants to upgrade to Nougat 7.1.2.
I want the 7.1.2 just for a regular usage: apps, internet, bluetooth, NFC, camera, GPS, phone calling and of course a good battery performance.
I want to kindly ask for your guidance in all steps required for the backup and upgrade, so if you can please guide me about the whole process I will appreciate it a lot.
Thanks
Click to expand...
Click to collapse
Hello!
In short, the process for our phone would be...
0. Backup data.
1. Unlock bootloader. This will void your warranty. Unlocking bootloader allows you to use fastboot mode to flash custom images to your phone from a computer.
2. Flash TWRP Recovery. This is done in fastboot mode. Once you have TWRP, you can flash on to or modify the system partition (and other partitions) of your phone on the go.
3. Format the /system partition to get rid of the existing ROM (stock in your case) and then flash whatever ROM you want. This is done using TWRP.
4. There's no fourth step.
Its pretty straightforward, detailed guides to each of the steps are available in this forum. You should use the Index Thread pinned on the General forum to get the links to the required guides at one place. Use the search if you encounter trouble. Then there's the forum to ask.
DragonClawsAreSharp said:
Hello!
In short, the process for our phone would be...
0. Backup data.
1. Unlock bootloader. This will void your warranty. Unlocking bootloader allows you to use fastboot mode to flash custom images to your phone from a computer.
2. Flash TWRP Recovery. This is done in fastboot mode. Once you have TWRP, you can flash on to or modify the system partition (and other partitions) of your phone on the go.
3. Format the /system partition to get rid of the existing ROM (stock in your case) and then flash whatever ROM you want. This is done using TWRP.
4. There's no fourth step.
Its pretty straightforward, detailed guides to each of the steps are available in this forum. You should use the Index Thread pinned on the General forum to get the links to the required guides at one place. Use the search if you encounter trouble. Then there's the forum to ask.
Click to expand...
Click to collapse
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
jramirezdev said:
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
Click to expand...
Click to collapse
Unlocking bootloader will wipe all your data (it will trigger Factory Reset on your phone). Other than that, your phone will be 100% usable.
Roms are available in Android Development and Original Android Development sections of this forum. Just check the threads that include [ROM] in their title. You have to decide for yourself which rom suits you the best - read its description and what users say in comments.
jramirezdev said:
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
Click to expand...
Click to collapse
As said, after unlocking bootloader the device will be wiped- You will have to reenter your Google account and reinstall applications etc. Not a big deal.
Custom ROMs sometimes take a few iterations until some bugs here and there are ironed out. Sometimes it happens, in others one may end up switching to a complete fresh ROM. In such instances, you will usually have to make a "clean install" (i.e. a factory reset) and then reenter the Google account and reinstall everything again... It sounds irritating, but nowadays it's pretty much straight forward, and if you don't have hundreds of apps it usually is finalized in 10-15 minutes and is semi automatic.
Updating to a newer version of the same ROM sometimes can be "dirty flashed" (i.e. without wiping all your data) so in a couple of minutes you are set up and ready to go. More convenient, but if something isn't working right and you complain in the thread, certain chances are you will be politely asked to make a clean install first amd some users may flame or grill you alive for dirty flashing and complaining at that :laugh:
Most custom ROMs are usually based on either AOSP or Lineage OS (aka LOS) with some custom modifications. The first post in a ROM thread usually mentions all the rich features (or lack of), how to install (pretty much the same: make a backup in twrp, wipe data/system/cache/dalvik, flash ROM zip file, flash Google gapps zip, flash some additional optional zips such as supersu/magisk/whatever for root etc). Then some download links, faq etc.
It's good practice to read the first post (aka OP), then at least the last page to get a feel of the ROM (e.g. see what others are praising or complaining about this or that), then search for specific stuff that may concern you. For example, some ROMs had this cellular data bug that it got disconnected and required restart. You may decide this os crucial for you and choose another ROM, others may use the device for other things and couldn care less about cellular data bug...
Enjoy, it always feels good tp flash a new ROM, a new version . F!ck LeMoto for delaying the update for so long- You may have been waiting for update to Nougat as early as last year's November or October. Well, on custom ROMs it's here for many months!
On the other hand, they usually say stock ROM is more stable, and in many cases it is also true...
Now you know more or les what you're dealing with: free choice vs. waiting forever.
jaibar said:
As said, after unlocking bootloader the device will be wiped- You will have to reenter your Google account and reinstall applications etc. Not a big deal.
Custom ROMs sometimes take a few iterations until some bugs here and there are ironed out. Sometimes it happens, in others one may end up switching to a complete fresh ROM. In such instances, you will usually have to make a "clean install" (i.e. a factory reset) and then reenter the Google account and reinstall everything again... It sounds irritating, but nowadays it's pretty much straight forward, and if you don't have hundreds of apps it usually is finalized in 10-15 minutes and is semi automatic.
Updating to a newer version of the same ROM sometimes can be "dirty flashed" (i.e. without wiping all your data) so in a couple of minutes you are set up and ready to go. More convenient, but if something isn't working right and you complain in the thread, certain chances are you will be politely asked to make a clean install first amd some users may flame or grill you alive for dirty flashing and complaining at that :laugh:
Most custom ROMs are usually based on either AOSP or Lineage OS (aka LOS) with some custom modifications. The first post in a ROM thread usually mentions all the rich features (or lack of), how to install (pretty much the same: make a backup in twrp, wipe data/system/cache/dalvik, flash ROM zip file, flash Google gapps zip, flash some additional optional zips such as supersu/magisk/whatever for root etc). Then some download links, faq etc.
It's good practice to read the first post (aka OP), then at least the last page to get a feel of the ROM (e.g. see what others are praising or complaining about this or that), then search for specific stuff that may concern you. For example, some ROMs had this cellular data bug that it got disconnected and required restart. You may decide this os crucial for you and choose another ROM, others may use the device for other things and couldn care less about cellular data bug...
Enjoy, it always feels good tp flash a new ROM, a new version . F!ck LeMoto for delaying the update for so long- You may have been waiting for update to Nougat as early as last year's November or October. Well, on custom ROMs it's here for many months!
On the other hand, they usually say stock ROM is more stable, and in many cases it is also true...
Now you know more or les what you're dealing with: free choice vs. waiting forever.
Click to expand...
Click to collapse
Thanks for your thoughts,
After reading here and there I finally was able to flash AOSP Extendend v4.4 on my cellphone, it seems to be working fine.
As I said I was not looking something specific I was just annoyed of waiting so long for the official update (it seems it will never happen) and wants to be in touch with Android Nougat, maybe now I will use my piggy bank to save for a Pixel phone
Thanks guys for your guidance
jramirezdev said:
After reading here and there I finally was able to flash AOSP Extendend v4.4 on my cellphone, it seems to be working fine.
Click to expand...
Click to collapse
Hi,
How it is working? Did you found any bugs? eg. problem with battery, with mobile data, lte, camera?
Hello!
New Axon 7 owner here, since Thursday! I had a couple of questions relating to this phone and thought it would be best to ask here since i'm already familiar with XDA from previous devices. First of all, I noticed that sometimes text on the screen will occasionally appear like it is vibrating, juddering or blurring for a couple of milliseconds whilst scrolling, as the page is moving either upwards or downwards. It seems to happen at random and it does not appear to have a connection with the colours or content being displayed.
I read on one website that it might be due to the pixels in the AMOLED display turning off momentarily when black is displayed on the screen, however, it cannot be the cause of the problem in this instance because it happens when there is no black displayed, for example in Boost for Reddit which uses a colour scheme of white text on a navy-blue background. I found that the issue seems to happen more often when flicking/flinging the page to scroll, rather than keeping my finger on the screen whilst scrolling through the content.
Has anyone else experienced the same thing and can comment on whether it is normal behaviour for this device? I have not owned an AMOLED device before, and so don't know whether this is typical for devices with this type of display. It could of course be a software issue; but it strikes me as more of a hardware-related matter. I would assume it is probably completely normal, since the phone is otherwise perfect and was fully tested prior to being shipped. :fingers-crossed:
Also...
The phone came from a Chinese reseller on AliExpress who exported the phone to myself in the United Kingdom. The device is a A2017 with the China Mobile branding on the back of it, but the phone has in their words been 'converted' to A2017G spec and is running the A2017GV1.2.0B01 ROM. (MiFavor UI v4.2 based on Nougat 7.1.1) The baseband version is TH.2.0.c1.9-00104-M8996FAAAANAZM. I have checked for OTA updates but it is showing the software as fully updated. When the phone is plugged into my Windows 10 PC it shows as 'ZTE A2017G'.
I am wondering whether this 'conversation' includes anything other than switching to the A2017G Global ROM that would need to be kept in mind when modifying software on the device. Like, would it be safe to follow the usual tutorials for flashing software for the A2017, or should I be looking at tutorials for the A2017G instead?
I would like to unlock the bootloader, install TWRP, flash the latest MiFavor UI v5.0 ROM and root it with Magisk, but i'm not sure where to start with this since none of the tutorials seem to cover phones which have been 'converted' to the A2017G firmware. I saw a warning in the Axon7Toolkit thread, saying that some A2017G models may be permanently bricked when flashing packages through EDL mode due to slightly different partition tables. I don't know whether this is something I should be worried about with my A2017 since it has been converted to A2017G status.
If anyone kindly offer some further insight on either of these points, it would be most appreciated. Thanks a lot.
P650SE said:
Hello!
New Axon 7 owner here, since Thursday! I had a couple of questions relating to this phone and thought it would be best to ask here since i'm already familiar with XDA from previous devices. First of all, I noticed that sometimes text on the screen will occasionally appear like it is 'vibrating' or juddering for a matter of milliseconds whilst scrolling, as the page is moving either upwards or downwards. It seems to happen at random and it does not appear to have a connection with the colours or content being displayed.
I read on one website that it might be due to the pixels in the AMOLED display turning off momentarily when black is displayed on the screen, however, it cannot be the cause of the problem in this instance because it happens when there is no black displayed, for example in Boost for Reddit which uses a colour scheme of white text on a navy-blue background. I found that the issue seems to happen more often when flicking/flinging the page to scroll, rather than keeping my finger on the screen whilst scrolling through the content.
Has anyone else experienced the same thing and can comment on whether it is normal behaviour for this device? I have not owned an AMOLED device before, and so don't know whether this is typical for devices with this type of display. It could of course be a software issue; but it strikes me as more of a hardware-related matter. I would assume it is probably completely normal, since the phone is otherwise perfect and was fully tested prior to being shipped. :fingers-crossed:
Also...
The phone came from a Chinese reseller on AliExpress who exported the phone to myself in the United Kingdom. The device is a A2017 with the China Mobile branding on the back of it, but the phone has in their words been 'converted' to A2017G spec and is running the A2017GV1.2.0B01 ROM. (MiFavor UI v4.2 based on Nougat 7.1.1) The baseband version is TH.2.0.c1.9-00104-M8996FAAAANAZM. I have checked for OTA updates but it is showing the software as fully updated. When the phone is plugged into my Windows 10 PC it shows as 'ZTE A2017G'.
I am wondering whether this 'conversation' includes anything other than switching to the A2017G Global ROM that would need to be kept in mind when modifying software on the device. Like, would it be safe to follow the usual tutorials for flashing software for the A2017, or should I be looking at tutorials for the A2017G instead?
I would like to unlock the bootloader, install TWRP, flash the latest MiFavor UI v5.0 ROM and root it with Magisk, but i'm not sure where to start with this since none of the tutorials seem to cover phones which have been 'converted' to the A2017G firmware. I saw a warning in the Axon7Toolkit thread, saying that some A2017G models may be permanently bricked when flashing packages through EDL mode due to slightly different partition tables. I don't know whether this is something I should be worried about with my A2017 since it has been converted to A2017G status.
If anyone kindly offer some further insight on either of these points, it would be most appreciated. Thanks a lot.
Click to expand...
Click to collapse
Look, first of all, I never had that problem, but it would be best if you recorded the phone with 60fps or something so that we can see what you mean. I don't really get the thing you're talking about
You should install A2017 firmware on your phone instead of using the G firmware, because:
-You won't get OTAs
-MiFavor 5.0 is pretty damn awesome
-Maybe the screen stuff will get fixed
First of all, go to Display and try to disable "Adaptive Display" which is a good idea but really badly implemented for some reason. If the display stuff gets fixed, you may as well not RMA it, and you can install the Chinese stuff on it. You're gonna lose all your data so back it up.
First download an official ZTE update zip. I think I've sent one to someone not much ago, I'll try to find it and put the link here
Then check if there's another zip inside. If there is, get that zip out (should be called update.zip) and throw it in the root of the internal storage
Go to Settings - Updates, and see if it detects it. if it does, install it.
After having the Chinese firmware, delete the zip from your phone, and go to Updates, and see if you get any OTAs. if you get one, after it gets installed go there again, because sometimes they are just incremental (you might have to do this 2-3 times depending on which version you install via zip)
This way you don't have to unlock the phone's BL. After having MiFavor 5.0 set up, download the Google apps if you want (I recommend Google Installer apk by Xiaomi, google it) and you're good to go.
Choose an username... said:
Look, first of all, I never had that problem, but it would be best if you recorded the phone with 60fps or something so that we can see what you mean. I don't really get the thing you're talking about
You should install A2017 firmware on your phone instead of using the G firmware, because:
-You won't get OTAs
-MiFavor 5.0 is pretty damn awesome
-Maybe the screen stuff will get fixed
First of all, go to Display and try to disable "Adaptive Display" which is a good idea but really badly implemented for some reason. If the display stuff gets fixed, you may as well not RMA it, and you can install the Chinese stuff on it. You're gonna lose all your data so back it up.
First download an official ZTE update zip. I think I've sent one to someone not much ago, I'll try to find it and put the link here
Then check if there's another zip inside. If there is, get that zip out (should be called update.zip) and throw it in the root of the internal storage
Go to Settings - Updates, and see if it detects it. if it does, install it.
After having the Chinese firmware, delete the zip from your phone, and go to Updates, and see if you get any OTAs. if you get one, after it gets installed go there again, because sometimes they are just incremental (you might have to do this 2-3 times depending on which version you install via zip)
This way you don't have to unlock the phone's BL. After having MiFavor 5.0 set up, download the Google apps if you want (I recommend Google Installer apk by Xiaomi, google it) and you're good to go.
Click to expand...
Click to collapse
Thanks for the response, I appreciate you taking the time to respond to my questions. I will try to record the screen problem over the next few days just so everyone can see for themselves what is happening; it might be easier than trying to explain it. In regards to the update to MiFavor v5.0, i'm just a bit nervous about flashing stuff through the stock recovery considering the phone has already been messed about with. It would actually feel safer to flash the entire phone in MiFlash on my computer, rather than just trying to install over the A2017G firmware and hoping for the best. I wouldn't mind having to unlock the bootloader because it's what i'd like to do anyway, since i'm interested in rooting to get things like AdAway which I have used on all of my previous devices. But I will have a search around for that official update ZIP anyway and see whether i'm able to find it.
Just got what you said and tried it. You're right it blurs when I fling to scroll. But this happens on LCD screens too.
Aj-jss said:
Just got what you said and tried it. You're right it blurs when I fling to scroll. But this happens on LCD screens too.
Click to expand...
Click to collapse
Well, if someone else is also having the same issue then that would make me feel a bit better about it, assuming we are talking about the same thing of course. I will try to record a video of the problem over the next couple of days, as it would be clearer than trying to explain it in writing. I should note that the blurring effect only lasts for a few milliseconds (Less than the duration of the fling!) and it only happens once in every 20 swipes or so. But when it does happen it can be quite distracting. I have owned 4 IPS devices before this (OnePlus One, LG G4) and none of them have had scrolling behaviour like the Axon 7.
I have also found the scrolling on this phone in general to be a lot less smoother than my ZUK Z2 which uses a 5.0" IPS screen and SD820. It seems the momentum each swipe has in propelling the page vertically is a lot less effective, and thus it takes more swipes to scroll down to the end of a page. Maybe this is because the screen is 5.5" opposed to 5.0" and so, it requires longer 'flings' or swipes on the screen to make up for the additional space. But this theory seems like a long shot and it still does not explain why the scrolling in general feels so laggy and stuttery.
The thing I saw on my two phones including Axon7 happens with every fling or swipe. Maybe I didn't quite understand you . Try to record and send the video so I get what you mean.
P650SE said:
Well, if someone else is also having the same issue then that would make me feel a bit better about it, assuming we are talking about the same thing of course. I will try to record a video of the problem over the next couple of days, as it would be clearer than trying to explain it in writing. I should note that the blurring effect only lasts for a few milliseconds (Less than the duration of the fling!) and it only happens once in every 20 swipes or so. But when it does happen it can be quite distracting. I have owned 4 IPS devices before this (OnePlus One, LG G4) and none of them have had scrolling behaviour like the Axon 7.
I have also found the scrolling on this phone in general to be a lot less smoother than my ZUK Z2 which uses a 5.0" IPS screen and SD820. It seems the momentum each swipe has in propelling the page vertically is a lot less effective, and thus it takes more swipes to scroll down to the end of a page. Maybe this is because the screen is 5.5" opposed to 5.0" and so, it requires longer 'flings' or swipes on the screen to make up for the additional space. But this theory seems like a long shot and it still does not explain why the scrolling in general feels so laggy and stuttery.
Click to expand...
Click to collapse
Did you root your phone? Do you intend to? If you do, you can use the conservative governor and fix the lag entirely. Many people believe that the conservative governor is laggier than interactive, but on the SD820 that's not the case. I've tried on SD6xx and 4xx devices (the Moto G2 and G4+ namely) and this is clearly not like this on those phones.
As for the fling thing, well I'd like to see a video, since I never noticed such a thing. I'm on MiFavor 5.0 so maybe something has been changed, because this is Chinese firmware (on the G).
And I believe that you have to fling more because ZTE may have messed up with some files, as they always did... probably not because of the bigger screen
But really, change your firmware to stock A2017. It's completely possible to have Google apps on it, but retailers install the G firmware on tbe Chinese just because they sell it to the global market
Here you go: Download this, and after you have the zip, open it with a zip manager such as winrar or 7zip. If you see a PDF and an update.zip inside, pull the update.zip out and put it in the root of the internal storage, then install it via Settings - Updates. If not just put the zip you downloaded on the root if the internal storage. but i think that zip actually has the other one inside.
https://archive.org/download/A2017B1320161104135351692/A2017-B13-20161104135351692.zip
Choose an username... said:
Did you root your phone? Do you intend to? If you do, you can use the conservative governor and fix the lag entirely. Many people believe that the conservative governor is laggier than interactive, but on the SD820 that's not the case. I've tried on SD6xx and 4xx devices (the Moto G2 and G4+ namely) and this is clearly not like this on those phones.
As for the fling thing, well I'd like to see a video, since I never noticed such a thing. I'm on MiFavor 5.0 so maybe something has been changed, because this is Chinese firmware (on the G).
And I believe that you have to fling more because ZTE may have messed up with some files, as they always did... probably not because of the bigger screen
But really, change your firmware to stock A2017. It's completely possible to have Google apps on it, but retailers install the G firmware on tbe Chinese just because they sell it to the global market
Here you go: Download this, and after you have the zip, open it with a zip manager such as winrar or 7zip. If you see a PDF and an update.zip inside, pull the update.zip out and put it in the root of the internal storage, then install it via Settings - Updates. If not just put the zip you downloaded on the root if the internal storage. but i think that zip actually has the other one inside.
https://archive.org/download/A2017B1320161104135351692/A2017-B13-20161104135351692.zip
Click to expand...
Click to collapse
Thanks for the response, once again! I tried to record the scrolling problem with my DSLR camera but it was a lot harder than you'd think to capture the blurring on there. I will have to review the footage on my laptop and see whether there's anything which clearly shows the effect. But having spoke to several people about this, it is probably normal behaviour for the AMOLED panel. I think the best option for me would be like you said, to flash the stock China firmware and see whether it makes a difference to my issues with scrolling lag. If it doesn't then there's no harm done, as the phone will be much better with the China firmware anyway.
I have one question, what would be the difference between the update package you posted and the one from the official ZTE website? I noticed there is one that says '7.1 Back 6.0 ZTE_A2017V1.1.0B11 Dedicated Upgrade Package (All Network Versions)' which would presumably allow me to revert back to A2017 Marshmallow firmware with OTA updates enabled, as you explained previously. Maybe it would be better to use this one since it is dated 20/03/2017 rather than 04/11/2016. And is it definitely 100% safe to use these update packages to switch from A2017G Global firmware to A2017 China firmware?
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
P650SE said:
Thanks for the response, once again! I tried to record the scrolling problem with my DSLR camera but it was a lot harder than you'd think to capture the blurring on there. I will have to review the footage on my laptop and see whether there's anything which clearly shows the effect. But having spoke to several people about this, it is probably normal behaviour for the AMOLED panel. I think the best option for me would be like you said, to flash the stock China firmware and see whether it makes a difference to my issues with scrolling lag. If it doesn't then there's no harm done, as the phone will be much better with the China firmware anyway.
I have one question, what would be the difference between the update package you posted and the one from the official ZTE website? I noticed there is one that says '7.1 Back 6.0 ZTE_A2017V1.1.0B11 Dedicated Upgrade Package (All Network Versions)' which would presumably allow me to revert back to A2017 Marshmallow firmware with OTA updates enabled, as you explained previously. Maybe it would be better to use this one since it is dated 20/03/2017 rather than 04/11/2016. And is it definitely 100% safe to use these update packages to switch from A2017G Global firmware to A2017 China firmware?
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
Click to expand...
Click to collapse
Well, the package that you found will do too. Most people here expect everything to be done for them, and since I had already found a zip, I thought it would be best to share it at least.
You should actually follow the guide that I just posted - the reason why is that you have to unzip the file and put it in the root of the SD card. It's written so that everyone can understand, so sorry if it's too dense. but if you downloaded the package on the PC (and your phone is somehow able to connect via MTP [or FTP, i have to use this] to your PC) it's just unzip and send.
Choose an username... said:
Well, the package that you found will do too. Most people here expect everything to be done for them, and since I had already found a zip, I thought it would be best to share it at least.
You should actually follow the guide that I just posted - the reason why is that you have to unzip the file and put it in the root of the SD card. It's written so that everyone can understand, so sorry if it's too dense
Click to expand...
Click to collapse
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
P650SE said:
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
Click to expand...
Click to collapse
You sure you booted to the bootloader? Most phones have it blocked and you can only access recovery, EDL and FTM.
Whatever, yeah, the Chinese recovery is in Chinese. G's and U's have it in English. But still, the option that you may need to use is the one that says 'sd' between some Chinese ideograms (install update from sd card). Ofc you'd need an SD card for that, that's why using the system option to update is preferred.
Choose an username... said:
You sure you booted to the bootloader? Most phones have it blocked and you can only access recovery, EDL and FTM.
Whatever, yeah, the Chinese recovery is in Chinese. G's and U's have it in English. But still, the option that you may need to use is the one that says 'sd' between some Chinese ideograms (install update from sd card). Ofc you'd need an SD card for that, that's why using the system option to update is preferred.
Click to expand...
Click to collapse
Ah, that's interesting! I'm certain it was the bootloader since I followed a tutorial on YouTube to access it. Basically, all I had to do was to switch the phone off and then hold both the volume-up and power buttons until the ZTE logo appeared, then release the power button and keep holding the volume button until the bootloader came up! Anyhow, i'll definitely follow your advice and use the update method via the settings menu in MiFavor. But first I will have to wait another hour for the update package to finish downloading, as my internet speed is only 3.3Mbps!
P650SE said:
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
Click to expand...
Click to collapse
My phone is A2017 too. This screenshot might help you understand those numbers.
^^^Ah, that's cool. So P996A03_N is basically just further identification for the device to indicate it is the Chinese A2017 version.
At the moment i'm having problems with the ZIP for rolling back to Marshmallow. It came packaged in an archive called 20170320111600705.zip which I extracted using WinRAR on my laptop. I copied the update.zip file to the root of my internal storage and to the root of the SD card, but neither are recognised when entering the 'System Update' screen. Is it possible that the reseller on AliExpress blocked the ability to update the ROM? I don't know whether to try running the update directly from the bootloader instead.
On the AliExpress listing for the phone is has a warning which says 'Please do not try to flash the phone by yourself. Otherwise your phone will be blocked and lose the network'. I assume this is just to discourage people from flashing custom ROMs to their devices rather than an actual physical limitation.
P650SE said:
^^^Ah, that's cool. So P996A03_N is basically just further identification for the device to indicate it is the Chinese A2017 version.
At the moment i'm having problems with the ZIP for rolling back to Marshmallow. It came packaged in an archive called 20170320111600705.zip which I extracted using WinRAR on my laptop. I copied the update.zip file to the root of my internal storage and to the root of the SD card, but neither are recognised when entering the 'System Update' screen. Is it possible that the reseller on AliExpress blocked the ability to update the ROM? I don't know whether to try running the update directly from the bootloader instead.
On the AliExpress listing for the phone is has a warning which says 'Please do not try to flash the phone by yourself. Otherwise your phone will be blocked and lose the network'. I assume this is just to discourage people from flashing custom ROMs to their devices rather than an actual physical limitation.
Click to expand...
Click to collapse
Okay, then you'll have to use the recovery. Put the zip on the SD card (I guess you already have it there), turn it off and hold power + vol up. Select the option that says sd and select the zip.
I guess it doesn't work because it detected that the zip was for an A2017 and it thinks it's a G
Choose an username... said:
Okay, then you'll have to use the recovery. Put the zip on the SD card (I guess you already have it there), turn it off and hold power + vol up. Select the option that says sd and select the zip.
I guess it doesn't work because it detected that the zip was for an A2017 and it thinks it's a G
Click to expand...
Click to collapse
Ah. Good thinking about the reason it wasn't working! Although, I tried that and underneath where it says Supported API: 3, it shows a message which says 'Sorry, you can't sdcard upgrade'.
EDIT: Oh, wait a second. I remember reading something which said you should enable OEM unlocking before trying to flash the ZIP. Maybe that would work!
EDIT 2: Well, that seems to have worked. I was so scared! But the ZIP flashed successfully and it has rebooted into A2017V1.0.0B13 MiFavor UI v4.0 (Android 6.0.1) I noticed the bootloader screen is now slightly different as it now shows the Chinese symbol next to the ZTE text. It is now showing an OTA update to V1.0.0B15, so i'll start by doing that and work through all the other OTA's until I reach the latest version!
Check the edit to my previous post. I managed to get the phone onto A2017V1.0.0B13 and then OTA updated to A2017V1.0.0B15, but unfortunately there are no further OTA updates available from this point. So with this in mind, the next step would probably be to download the A2017V1.1.0B17 archive from the same source and flash that using the same method, via the bootloader? Then hopefully that should bump me back up to Nougat and allow me to OTA to the latest version of MiFavor. (v5.0)
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
P650SE said:
Check the edit to my previous post. I managed to get the phone onto A2017V1.0.0B13 and then OTA updated to A2017V1.0.0B15, but unfortunately there are no further OTA updates available from this point. So with this in mind, the next step would probably be to download the A2017V1.1.0B17 archive from the same source and flash that using the same method, via the bootloader? Then hopefully that should bump me back up to Nougat and allow me to OTA to the latest version of MiFavor. (v5.0)
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
Click to expand...
Click to collapse
Nah, I think you already can use the inbuilt update function. Now that you are on A2017 firmware it should find the zip easily.
The 'bootloader mode' you are referring to is actually the recovery. The bootloader mode is the one on the picture. You can access to it by using adb, and issuing 'adb reboot bootloader', but you might not have it (in which case the phone will just boot to system)
To unlock the bootloader you need to get fastboot on the phone AFAIK, so that's what the axon7toolkit does, it flashes stuff through MiFlash to get fastboot operational. Google it, it's pretty good; if you ever want to unlock, I think it's the way to go.
Just to get everything clear.
Choose an username... said:
Nah, I think you already can use the inbuilt update function. Now that you are on A2017 firmware it should find the zip easily.
The 'bootloader mode' you are referring to is actually the recovery. The bootloader mode is the one on the picture. You can access to it by using adb, and issuing 'adb reboot bootloader', but you might not have it (in which case the phone will just boot to system)
To unlock the bootloader you need to get fastboot on the phone AFAIK, so that's what the axon7toolkit does, it flashes stuff through MiFlash to get fastboot operational. Google it, it's pretty good; if you ever want to unlock, I think it's the way to go.
Just to get everything clear.
Click to expand...
Click to collapse
Whoops! I have no idea why I kept referring to it as the bootloader, maybe because i've become so used to using TWRP on my ZUK Z2 for almost a year and ended up forgetting what a manufacturers stock recovery looked like! That was a very silly mistake. :laugh:
I haven't been able to get an update to Nougat to appear via OTA in the 'System Update' menu, so instead I will download the update package from the ZTE website and see whether that works. I believe once I have updated to V1.1.0B17 via ZIP it should allow me to OTA to the latest version of MiFavor. Thanks for the tips regarding Axon7Toolkit, I already had it installed on my laptop but didn't know about possibly having to enable the bootloader with MiFlash. That is very interesting!
P650SE said:
Whoops! I have no idea why I kept referring to it as the bootloader, maybe because i've become so used to using TWRP on my ZUK Z2 for almost a year and ended up forgetting what a manufacturers stock recovery looked like! That was a very silly mistake. :laugh:
I haven't been able to get an update to Nougat to appear via OTA in the 'System Update' menu, so instead I will download the update package from the ZTE website and see whether that works. I believe once I have updated to V1.1.0B17 via ZIP it should allow me to OTA to the latest version of MiFavor. Thanks for the tips regarding Axon7Toolkit, I already had it installed on my laptop but didn't know about possibly having to enable the bootloader with MiFlash. That is very interesting!
Click to expand...
Click to collapse
Literally you have to get B17 update through OTA when you're on B15. I did, but the reasons you're not is that you or your reseller have converted it to G model. My friend who also had a Chinese Axon 7 and converted it to G had this problem too. And I don't know what to do about it.
---------- Post added at 03:09 AM ---------- Previous post was at 03:06 AM ----------
And I also think that you had to flash B13 upgrade package(second downloadable zip on ZTE website) because B11 was the same B13 but the rollback version meaning for somebody who is already on Nougat and wants to go back to Marshmallow.
Hey guys
I was wondering if someone here is still on the V6 version of the security update, if you are you can make the TOT file out of the V20 Sprint model. Whoever has the Z3X box for LG, follow these steps:
1. Start the LG Tools
2. Select H918
3. Select the Port 1 in Workspace, in connection put it to: AndroidNet USB Serial Port
4. Search phone button will find the LS997 model.
5. Select the Firmware Maker on the bottom of the right box
This will make the firmware of the version 6, the one that has the hidden menu for the unlock, since we cannot downgrade, maybe we can try it this way, it creates a TOT file that is flashable through the Z3X software
Does anyone have the box with this version, before it was updated. Because I lost that in the hidden menu the unlock function and now I cant even get signal, having issues wanna downgrade.
If someone has this LS997V6, create the firmware so we can flash it and maybe we can go back to that security update before it was patched, been looking around for it. But I dont have that version or else would have created the file to share.
ayoshidage said:
Hey guys
I was wondering if someone here is still on the V6 version of the security update, if you are you can make the TOT file out of the V20 Sprint model. Whoever has the Z3X box for LG, follow these steps:
1. Start the LG Tools
2. Select H918
3. Select the Port 1 in Workspace, in connection put it to: AndroidNet USB Serial Port
4. Search phone button will find the LS997 model.
5. Select the Firmware Maker on the bottom of the right box
This will make the firmware of the version 6, the one that has the hidden menu for the unlock, since we cannot downgrade, maybe we can try it this way, it creates a TOT file that is flashable through the Z3X software
Does anyone have the box with this version, before it was updated. Because I lost that in the hidden menu the unlock function and now I cant even get signal, having issues wanna downgrade.
If someone has this LS997V6, create the firmware so we can flash it and maybe we can go back to that security update before it was patched, been looking around for it. But I dont have that version or else would have created the file to share.
Click to expand...
Click to collapse
But didn’t antirollback change? If so firmware or not you cannot downgrade
Sent from my iPhone using Tapatalk
hyelton said:
But didn’t antirollback change? If so firmware or not you cannot downgrade
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes, but I am currently working on it, but I need that firmware version to see what I can do, because I dont have that, I need someone to make a copy of that from their phone using the methods I have provided for me to do the work on it.
ayoshidage said:
Yes, but I am currently working on it, but I need that firmware version to see what I can do, because I dont have that, I need someone to make a copy of that from their phone using the methods I have provided for me to do the work on it.
Click to expand...
Click to collapse
If antirollback did change, there’s no physical possible way to downgrade. It’s not possible, there’s no way around antirollback.
Sent from my iPhone using Tapatalk
hyelton said:
If antirollback did change, there’s no physical possible way to downgrade. It’s not possible, there’s no way around antirollback.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
There is always a way for everything, keep in mind Samsung did the same thing to prevent downgrading the firmware, I have found a way to downgrade that to the first version installed on the device even if you are on the latest version, but took me a very long time to find the exploit for it. So trust me, when I tell you there is always a way. Would I share that, no I wont, because its my business and my hard work alone. But I am willing to share my work for this project.
What is there to lose, you have a person here willing to work for free, and work on this project to share with the community.
ayoshidage said:
There is always a way for everything, keep in mind Samsung did the same thing to prevent downgrading the firmware, I have found a way to downgrade that to the first version installed on the device even if you are on the latest version, but took me a very long time to find the exploit for it. So trust me, when I tell you there is always a way. Would I share that, no I wont, because its my business and my hard work alone. But I am willing to share my work for this project.
What is there to lose, you have a person here willing to work for free, and work on this project to share with the community.
Click to expand...
Click to collapse
Yeah nothing to loose .
Here’s a good post on it. https://forum.xda-developers.com/showpost.php?p=73206763&postcount=3
Here is a post from another thread:
“In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation”
Good luck, If you get anything be sure to post updates!
Without being able to inject code between the CPU and the NAND, it can't be done. I would LOVE to be proven wrong, but here is a quick overview:
The PBL is located in QFPROM on the CPU. ARB is located in QFPROM on the CPU. The RSA key is located in QFPROM on the CPU.
When you power on the phone, the PBL loads XBL and checks the ARB version. If it is less than what is burned into the CPU, it goes into 9008 mode. It also use the RSA key to verify the signature of XBL. If it is modified -- 9008 mode.
When a phone successfully loads XBL that has a greater ARB version than what is burned into the CPU, it immediately burns the greater ARB version into the CPU.
So there are a couple of attack vectors:
1 - Have some cool hardware that can read the RSA key from the CPU and try and brute force the RSA cert with the key and the sig.
2 - Have some cool hardware that can do a MITM attack on the CPU and NAND replying with a valid return so that the CPU will boot no matter what is on the NAND.
Good luck, I will be following this closely....
-- Brian
runningnak3d said:
Without being able to inject code between the CPU and the NAND, it can't be done. I would LOVE to be proven wrong, but here is a quick overview:
The PBL is located in QFPROM on the CPU. ARB is located in QFPROM on the CPU. The RSA key is located in QFPROM on the CPU.
When you power on the phone, the PBL loads XBL and checks the ARB version. If it is less than what is burned into the CPU, it goes into 9008 mode. It also use the RSA key to verify the signature of XBL. If it is modified -- 9008 mode.
When a phone successfully loads XBL that has a greater ARB version than what is burned into the CPU, it immediately burns the greater ARB version into the CPU.
So there are a couple of attack vectors:
1 - Have some cool hardware that can read the RSA key from the CPU and try and brute force the RSA cert with the key and the sig.
2 - Have some cool hardware that can do a MITM attack on the CPU and NAND replying with a valid return so that the CPU will boot no matter what is on the NAND.
Good luck, I will be following this closely....
-- Brian
Click to expand...
Click to collapse
Hi Brian
Thank you for all the information and all the input, I am gonna try to see what I can do from my end, my issue is this, before the update was patched from the hidden menu. This is the problem that has occured. Before the update, when I got this phone, was running on V6, I believe that was the last version that supported the HiddenMenu.apk, that you were able to change production to lab mode. Now since the mistake I did in updating the security software that has been patched and because of it. I have very weak signal and now also the 4G is gone. Before the update, I had full signal bars and 4G service. Now the bars come and go with the data connected. The phone was unlocked this method (temp method) and then was unlocked using Octopus after the update.
These are the issues:
1. The signal bars goes up and down to 0 and goes up again, I am in a very strong signal area.
2. The 4G was working but not the greatest speeds, was doing like 4-8MB a sec down and 0.1Kbs upload. Which is terrible.
I tried Resetting the Security via box and now the 4G is gone and data. Calls are working but same signal issues.
The issue is I know sprint uses the CDMA technologly, and where I am its GSM network, but my service uses WCDMA because it runs on the AWS network 1700/2100. The problem is this. I can get the HiddenMenu to work again, but that special section in the old version does not exist anymore because it has been patched in the new security update.
I am also able to get in to the band selection, AWS and all other bands are there, but the issue is if you select AWS it says FAILED to connect on any band except on AUTO, so this is why I wanted to have the old version extracted on the version 6, so that I could work on it, since Sprint does not have firmware files you can flash.
So this is the problem. Very stupid the way they did this firmware method OVER THE AIR method. The funny thing is that the it supports all the bands that the GSM supports here and the UMTS.
I just want to get this phone back to full bars with the data restored and have the full speed I had when I did the temp fix, but real solution. I know maybe I can flash a custom rom, but I dont know how reliable that is and if it will resolve the issue.
Whats your input on all of this?
Those issues your having are typical issues of using a sprint device on another carrier. Only fix is flashing a different model firmware which won’t ever be possible for the Sprint model. Never rely on a sprint device unless your using it on sprint.
Sent from my iPhone using Tapatalk
Yes I'm aware of these things of Sprint after finding out. But the weird thing is I never had an issue after that fix for the hidden menu patch that unlocks it when out into lab mode and specifying the APN. Never had a dropped signal once or data. This issued occured after the update. This is my first time owning an Sprint phone so I didn't know there were no firmware which is why I wanted to work on this project.
They say the workround is flashing a DirtySanta ROM. But then again if you fladh that rom would u have those old options back in hidden menu and would it fix the issue. That's the real question.
I am also aware that since you unlock the bootloader and lock it again you can brick the device. Luckly I have made a tot of my whole system firmware image latest version.
What's the best approach to getting this back to working state. My network runs on WCDMA that's why AWS is needed.
Just want to know how to get this working...
> would i share that, no i wont, its my hard work alone ...
>i need someone to ...
I see a hiccup in the reasoning here.
Best of luck. Development on this device came to a screeching halt when ARB hit.r
elijah420 said:
> would i share that, no i wont, its my hard work alone ...
>i need someone to ...
I see a hiccup in the reasoning here.
Best of luck. Development on this device came to a screeching halt when ARB hit.r
Click to expand...
Click to collapse
That's phrase is for the Samsung exploit. Not LG two different phones and companies.
If nobody cares to share that firmware version to extract no worries I won't work on it. Worst comes to worst I'll sell the phone that's all.
Good luck finding a way to do it yourself then. Dont questions others people work when you don't know what skills they have in the mobile field.
Thanks for everyone else for their input.
ayoshidage said:
That's phrase is for the Samsung exploit. Not LG two different phones and companies.
If nobody cares to share that firmware version to extract no worries I won't work on it. Worst comes to worst I'll sell the phone that's all.
Good luck finding a way to do it yourself then. Dont questions others people work when you don't know what skills they have in the mobile field.
Thanks for everyone else for their input.
Click to expand...
Click to collapse
Well thank you, but you fail to understand something very basic here. While there may have been a question mark in there somewhere, in no way was your request a request. It was rather demanding. You demanded someone do something for you, with no reciprocity from you. I think attitudes like that tend to rankle rather than disarm.
As far as the last bit of your snarky comment - bear this in mind - I'm not the one looking for a 'way to do it myself'.
Again, best of luck.
elijah420 said:
Well thank you, but you fail to understand something very basic here. While there may have been a question mark in there somewhere, in no way was your request a request. It was rather demanding. You demanded someone do something for you, with no reciprocity from you. I think attitudes like that tend to rankle rather than disarm.
As far as the last bit of your snarky comment - bear this in mind - I'm not the one looking for a 'way to do it myself'.
Again, best of luck.
Click to expand...
Click to collapse
Thanks for you reply, but I dont think you understood the meaning of what request means? Request means " an act of asking politely or formally for something" I think you should understand what the meaning of request means before commenting no sense. Also I didn't demand someone, I was asking if someone had a dump file or if someone could create a dump file for me to work on the project. I am here to help people out to find solutions, you are here for the purpose of starting rant on the forums. By no means, this was demand or any sort of order in bossing people around. But its all good, I dont have the phone anymore, so no need to work on it anymore, have a great day.
Thanks.
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?