Hi guys,
I've a brand new Nokia 3 (TA-1032) and updated it OTA with Android 8.0.0 and sec patches from July 5th. Now I'm trying to root that phone and as far as I've understood the various thread, I've to downgrade to Android 7.0. However, it seems I mixed up some guides...
When starting my phone, the following message is displayed: "Orange state, can't be trusted". After a couple of seconds the phone boots normally.
Any ideas how I can root my phone? I'm damn sure the solution is somewhere out there on xda dev, but a wealth of information creates a poverty of attention.... meaning I've no idea where to start.
Thanks and enjoy the weekend
Youser
===
Update: I could successfully go back to Android 7 with OST and root my device. Problem is solved.
Related
Hi all,
I"m living in Germany, but I bought my HAM7 in January in Dubai.
Today I received an OTA which is MT7-TL10_channel_MT7-TL10V100R001C00B128.
I"m wondering if someone already did that update and whether it's 5.1.
Thanks!
Hi, no this is a previous update.
5.1 is 300B
Probably, since 5.1 is an update and not a full OTA, it will come when you have an intermediate updated version of android. So go on, update to this suggested rom and wait for a following one.
guys
I make it root with kingoroot app and has told me its root your device . reboot it and no root on my device and try to install root checker on play Google and also told me no root
OSN play told me there is root on my Device ...
how can un-root my device and this root if existing can make OTA update or not ????
please help me
an71;61354906]Hi, no this is a previous update.
5.1 is 300B
Probably, since 5.1 is an update and not a full OTA, it will come when you have an intermediate updated version of android. So go on, update to this suggested rom and wait for a following one.[/QUOTE]
Thanks for your answer, you"re confirming what I found out as well. This update is 4.4.2.
Currently I can't really see any improvements, maybe they are hidden under the hood.
not sure if I got your question correctly. I rooted my device a week after I bought it in January, following the guidance I found in a different place on a German website. However, the process was a bit more complex compared to other devices I've rooted in the past. Especially the way of getting the id-numbers on a Chinese website was somehow challenging. Anyway, immediately after successfully rooting the mate7, I replaced the CWM recovery with stock recovery and from there I did receive the OTA"s which I seamlessly could install.
If your question is more general on rooting the HAM7 you should consult to the other more specific threads here on XDA
hi, dear xda forumers!
this is my very first post, and i am not very good at tech things, so please bear with me (plus I may unwantingly commit grammatical mistakes because i am not a native speaker and it is 2AM here)
first my back story:
I had a Huawei Mate 8 (nxt-l29c....something) European version, I had it for about 6 or 7 months, then it was stolen. By that time it had automatically upgraded to Nougat and I really liked it, got used to it, could not live without it.... so i decided to buy the same phone again. It came with Marshmallow, and I tried to update it but the OTA had been for a limited time only I guess, I emailed around with official huawei customer service asked them maybe to update my device from their headquarters or something, but they could not help me, they said I should just wait and eventually it would update.
after 3 months still nothing I grew impatient and I really wanted to have my "old experience" back, so I tried a tutorial with updating via filmware finder, using one of the first updates that were about 2GB big. It was successful, so it seemed at first, because there were no errors or interruptions, but finally when I turned it on, I noticed that during the update process my phone has lost the built in keyboard (still has the google), no more bluetooth, alarm clock, date time settings, update option
I downloaded the official rollback to Android 6 from 7 but since I updated with an unofficial update, it failed to fix my phone. now I still have the issues listed above.
Now I ended up with
Model number: NXT-L29C900B500 (originally it was NXT-L29C432B180)
EMUI version: 5.0
Android version: 7.0
Edit:
Now trying to use a new filmware from the official huawei website with the dload method
Edit 2:
it did not do anything. I will try again when I wake up
I kindly ask anyone who has any idea how to fix this to reply.
Mate 8 nougat update as far as I know have 2 update zips, I've experienced that problem when trying to update to nougat, I used twrp to flash the update.zip, I had emui 5 after but Bluetooth didn't work and some settings were missing, after searching I found that there are 2 zips to an update, a update.zip and a hwupdate.zip, basically only one was installed for you, you need to install both
Hi y'all
So kinda happy today, Nokia HMD Global sent out a new security update for the NOKIA 6 (2017) model.
Not a big surprise but glad they are sending out patches for the phone.
Wish they could fix the bug and the lag on the Android Pie software though.
FOR DEVELOPERS,
PLEASE CREATE A CUSTOM ROM FOR THIS PHONE.
FOR USERS,
IF ANYONE WANTS TO DOWNGRADE THEIR NOKIA 6 (2017) TO OREO CHECK MY PAGE
I started to install this update last night and my phone has been on the "Installing security update" screen ta the same progress since.
I've tried restarting with Volume+Up but it comes right back to this screen no matter what. It's not showing up in adb/fastboot list either.
Anyone else having this issue? Is there any way to see extra debug info/what it's stuck on, or just to cancel the update entirely for now. I have some accounts tied to google authenticator on this device so I'd rather not lose data if possible.
Hello, could someone share update archives for TA-1000 cuz I am not receiving OTA after Feb 2019 ?
Try This
OscarOrSomething said:
I started to install this update last night and my phone has been on the "Installing security update" screen ta the same progress since.
I've tried restarting with Volume+Up but it comes right back to this screen no matter what. It's not showing up in adb/fastboot list either.
Anyone else having this issue? Is there any way to see extra debug info/what it's stuck on, or just to cancel the update entirely for now. I have some accounts tied to google authenticator on this device so I'd rather not lose data if possible.
Click to expand...
Click to collapse
Hi there,
I had the same issue, but never cancel an update when it is installing. You May or May not BRICK your device
Regards
KIBS2173
Hello everyone, I bought this phone with Verizon in its original software version, previously it was binary 2 ...
I looked for how to modify it and get the most out of it, but I only found it for the SM-A515F version, I didn't think it would work with my phone, because I couldn't unlock the bootloader ...
so i decided to wait for some modification like: "ROOT, TWRP or Rom"
But time passed and an update arrived that I ignored but 10 days passed and my phone was locked and I was forced to update without any other option.
To my surprise it turned out that my phone was upgraded to binary 3 and I was a little freaked out because I know it can't be downgraded to older binaries,
so i was hoping they would create xda threads soon but nothing, and my surprise was another update came and when it downloaded my phone crashed and the screen specified: "for your safety please update".
and then proceeded to forcibly update ...
And to my surprise, it is now binary 4:
"A515USQU4BTJ1"
November 8 update ...
And now I don't know what future this device will hold for me, I just have to wait ...
I just wanted to share my situation and wait for some brainstorming or answers to this ...
The US versions of this phone will probably never be unlocked. Good luck. Glad you at least had an update.
I bought an unlocked A51 on Amazon ($279) and brought it to Verizon to Activate on their Prepaid service. They told me it couldn't be done. I went to a Verizon Company store (most are mom and pop owned) and was told the same thing. I asked if they would humor me by putting in a working Sim card to show me it doesn't work. To their utter surprise it worked. No issues at all. They immediately added it to my Verizon Account.
Luiszipatla said:
Hello everyone, I bought this phone with Verizon in its original software version, previously it was binary 2 ...
I looked for how to modify it and get the most out of it, but I only found it for the SM-A515F version, I didn't think it would work with my phone, because I couldn't unlock the bootloader ...
so i decided to wait for some modification like: "ROOT, TWRP or Rom"
But time passed and an update arrived that I ignored but 10 days passed and my phone was locked and I was forced to update without any other option.
To my surprise it turned out that my phone was upgraded to binary 3 and I was a little freaked out because I know it can't be downgraded to older binaries,
so i was hoping they would create xda threads soon but nothing, and my surprise was another update came and when it downloaded my phone crashed and the screen specified: "for your safety please update".
and then proceeded to forcibly update ...
And to my surprise, it is now binary 4:
"A515USQU4BTJ1"
November 8 update ...
And now I don't know what future this device will hold for me, I just have to wait ...
I just wanted to share my situation and wait for some brainstorming or answers to this ...
Click to expand...
Click to collapse
There is stuff for F variant but I don't know about U variant. This unlocked bootloader is something that should be now forced. Like I even know 7 year old devices that still dont have an unlocked bootloader.
---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------
Luiszipatla said:
Hello everyone, I bought this phone with Verizon in its original software version, previously it was binary 2 ...
I looked for how to modify it and get the most out of it, but I only found it for the SM-A515F version, I didn't think it would work with my phone, because I couldn't unlock the bootloader ...
so i decided to wait for some modification like: "ROOT, TWRP or Rom"
But time passed and an update arrived that I ignored but 10 days passed and my phone was locked and I was forced to update without any other option.
To my surprise it turned out that my phone was upgraded to binary 3 and I was a little freaked out because I know it can't be downgraded to older binaries,
so i was hoping they would create xda threads soon but nothing, and my surprise was another update came and when it downloaded my phone crashed and the screen specified: "for your safety please update".
and then proceeded to forcibly update ...
And to my surprise, it is now binary 4:
"A515USQU4BTJ1"
November 8 update ...
And now I don't know what future this device will hold for me, I just have to wait ...
I just wanted to share my situation and wait for some brainstorming or answers to this ...
Click to expand...
Click to collapse
P.s. I forgot to say one thing. Just be glad that your phone supports 3 years of updates aka till Android 13
Hi everyone.
I just bought a Pixel 4a and I enrolled in Android 12 Beta version updates and I got on Android 12 Beta, but then I decided to get back to Android 11. I did the flashing with the flashing tools website and then when the phone started and I got connected to the internet right at the beginning of the setup it says that I need to update my phone (I downloaded the latest factory image for September and flashed it on my phone) it says "Your phone needs to download an update and restart. Size 1617.2MB" when I click Next it gets to updating screen but it gets stuck there no matter how long I wait. I though maybe it is because I did it through the website so I did it manually using this tutorial but I have the same problem.
When I continue without a connection to the internet I can get passed this process and start the phone but when I check for the updates same thing happens.
Did I just broke my phone and I won't be able to get the OTA updates anymore?
no no no... You only have to unsubscribe from the website "android beta 12". Afterwards it will no longer ask for an update and everything will return to normal