Hi.
Could someone tell me about the root consequences for the mate 9 ? ie; will it still receive updates with root?
Is it possible to roll back to stock?
Is there any need to relock the bootloader in case it is needed to get the updates?
I know they are noob questions but I don't know anything about the mate 9 after root.
Help is appreciated.
DADER said:
Hi.
Could someone tell me about the root consequences for the mate 9 ? ie; will it still receive updates with root?
Is it possible to roll back to stock?
Is there any need to relock the bootloader in case it is needed to get the updates?
I know they are noob questions but I don't know anything about the mate 9 after root.
Help is appreciated.
Click to expand...
Click to collapse
You may get notifications for updates but they will fail in TWRP just like any other phone. You would need to flash stock recovery in order to update and the update will more than likely lock your bootloader as it installs. You can unroot and go back to stock, but you will want to read thru all the threads pertaining to root and getting back to stock that way you get a feel and a heads up on everything you're wanting to know. Make sure to read CAREFULLY AND THOROUGHLY and when and if you feel comfortable enough to root jump on in. This community is good at answering questions and helping out.
sent from my rotary phone
jr313 said:
You may get notifications for updates but they will fail in TWRP just like any other phone. You would need to flash stock recovery in order to update and the update will more than likely lock your bootloader as it installs. You can unroot and go back to stock, but you will want to read thru all the threads pertaining to root and getting back to stock that way you get a feel and a heads up on everything you're wanting to know. Make sure to read CAREFULLY AND THOROUGHLY and when and if you feel comfortable enough to root jump on in. This community is good at answering questions and helping out.
sent from my rotary phone
Click to expand...
Click to collapse
Thanks a lot. One more question. What about funky huawei? Is it like for restoring software bricked huaweis?
Sent from my Mate 9 using XDA Labs
I don't know if it'll bring back a hard bricked phone, but if can help you bring back your phone to life or help rebrand it to another region. @duraaraa can answer it better. Hit him up in private message about it
sent from my rotary phone
Related
Im very new and just switched over from webOS and have questions but im not sure if this is the right section to post if not sorry and bare with me.
Ok I have the NS4G just updated to 2.3.5. It killed tethering so I want to root to fix that problem.
Question #1... I did a little research before posting and I believe I need to unlock my bootloader then root it with SuperBoot?
Question #2... Is there more than 1 way to root my phone?
Question #3... Once rooted what do I do to actually get the tethering back. Do I download an app after the rooting if so is it in the market?
Question #4... What exactly is CM7 I see that in the forums everywhere. Is it important to have once you root your phone?
and finally #5... Will rooting my phone cause any problems with future updates, what are the pros/cons?
thanks guys I hear the Android community is as great as the webOS community.
1. Yeah, you need to unlock your bootloader to root
2. Yep
I used the standard way with pdanet and adb all that jazz, but now you are seeing more and more 1 click roots, superboot, etc.
3. I have no idea, I have gsm
4. CM7 is a firmware distribution of android, basically a type of custom rom you can install on your phone. A ROM is basically the read only memory, or os installed on ur phone. It's not important to have it, it's an option.
5. No, I don't have any problems with it. Just I think you need to make sure to go back to stock when there is an ota, or u wont get it
mathkid95 said:
5. No, I don't have any problems with it. Just I think you need to make sure to go back to stock when there is an ota, or u wont get it
Click to expand...
Click to collapse
Thanks mathkid. How would I go back to stock and do I need to do any kind of backup before or after rooting? Im sure these are very stupid questions I just really want to learn everything before I attempt messing around with my phone.
I think BuglessPete has a thread on that, or you could look at michaelpeerman's thread as well.
here ya go:
http://forum.xda-developers.com/showthread.php?t=1078213
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
No you dont need to be unrooted to update your android version.
You need to have the stock recovery and rom. The update isnt available for everyone yet
you will get a update notification just wait
ayush88 said:
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
Click to expand...
Click to collapse
You technically voided your warranty when you rooted. But no big deal.
You can download the update and sideload on your own, or wait for the OTA to come to you. If all you have is root, stock recovery and no system mods it will update on its own.
ayush88 said:
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
Click to expand...
Click to collapse
Hi do not worry. Those posts really do not apply to you yet. You have a phone that is stock meaning, you bought it and using it. If you keep it like that you never have to worry about update. Google will automatically push the update to your phone by next week. Incidentally the phone is also a developer phone, so people usually play around with it. Root, custom roms, kernels etc. Now for these enthusiasts to get the update, they have to unroot, ,to stock just like your phone. After getting the update they will start messing with it again:laugh: this forum being the developers forum of the Internet is the reason why you are seeing all those posts.
Now you are sitting on a Ferrari phone, using it as a Honda. Some day in the future you will let it run at indy500
ayush88 said:
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
Click to expand...
Click to collapse
Did you mean to ask "do you need to root to get the 4.4.1 OTA"?? If not, your question doesn't seem to add up....
You definitely do NOT need to root to get the OTA. You can wait for the update to be pushed out, or, if you are impatient, you can sideload using ADB or install from recovery.
If you are rooted, as the other folks explained, you may need to get back to stock before you can install 4.4.1
To add to this, I only rooted my Nexus 5 so I could use BetterBatteryStats and some other monitoring apps. Is there any way to go back from TWRP to stock recovery without wiping data/losing root?
I'm quite happy with everything stock and don't plan on doing any mods.
Also, I sideloaded 4.4.1, but would I have gotten the OTA with TWRP?
mmmmBACON said:
To add to this, I only rooted my Nexus 5 so I could use BetterBatteryStats and some other monitoring apps. Is there any way to go back from TWRP to stock recovery without wiping data/losing root?
Click to expand...
Click to collapse
Yes, get the recovery.img from the factory image and: fastboot flash recovery recovery.img. That'll put the stock recovery back on your device
donentl are
thnks alot you guys!!
this really helped me out!
i know i am new to android right now and dont know the ins and outs of this os completely... i really liked a reply which said i am sitting on a ferrarri and using it like a honda..lol...i will run it like a veyron in some time but for now my car comes with a "L" sign and a speed limiter on it
thnks again you guys!
Hey there!
I was wondering if rooting via towelroot would affect OTA updates? Someone told me you don't get OTA if the system files, bootloader or kernel have been changed. I am completely on stock now. Will apps like Droidwall, Titanium Backup or Greenify make any changes to the system files, hence rendering my phone not eligible for OTA?
Thanks
Read the OTA helpdesk thread about OTA. Link in my signature. Those apps should be fine but you should root properly and use a custom recovery of you're going to be rooted and forget about OTAs.
Sent from my Nexus 5 using Tapatalk
I agree! Being rooted without a custom recovery and/or not knowing how to use adb/fastboot is almost asking for trouble.
@rootSU gave you the best info.
You have a Nexus. You can flash stock in minutes when you need to do an ota. Or forget that and flash the update through fastboot. I've never taken an OTA on any device.
Thanks for the replies folks. I just dont feel like unlocking my bootloader at this very moment since there's stuff to backup and I am at the peak of my laziness ( and also very busy to do stuff with my phone)
Edit: Yeah, I sideloaded the 4.4.4 update. Can I sideload any update like this in the future even if I don't receive automatic updates? (i.e doesn't sideload verify that all original files are intact?)
Probably best avoid root in that case then.
Sent from my Nexus 5 using Tapatalk
Nice. You relax and we'll figure it out? That's not how XDA works my friend. Ask for help, put some effort in after you get answers. That's how it works.
I'd leave the phone as is and call it a day.
The question has been answered and the thread is going the wrong direction, so I'm going to stop it here.
@Moonheart All the info about OTA's are here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
It outlines what you need to do and how to prepare your phone for updates.
Thread Closed.
Ok, so I've been in the root/flashing scene for a while.
I'm very experience with locked bootloaders like my Verizon Note3, but I'm not so sure about my Shield tablet.
I know root is easily attainable, and flashing should be about the same as the others.
My question is, in the event things go badly, is there a way to get back on the stock/non-rooted image?
What about updating the software via OTA to keep being able to gamestream? Does it break root and just force me to root again
or does it not allow me to update? If my Shield dies for whatever reason and I have to RMA, can I return it to 100% stock?
I looked over the forums and couldn't find any full answers, so hopefully you guys can help me.
Thanks in advance.
Josh
ForeverZ3RO said:
Ok, so I've been in the root/flashing scene for a while.
I'm very experience with locked bootloaders like my Verizon Note3, but I'm not so sure about my Shield tablet.
I know root is easily attainable, and flashing should be about the same as the others.
My question is, in the event things go badly, is there a way to get back on the stock/non-rooted image?
What about updating the software via OTA to keep being able to gamestream? Does it break root and just force me to root again
or does it not allow me to update? If my Shield dies for whatever reason and I have to RMA, can I return it to 100% stock?
I looked over the forums and couldn't find any full answers, so hopefully you guys can help me.
Thanks in advance.
Josh
Click to expand...
Click to collapse
NVidia posts complete factory images on their website for restoration.
Also, all of their OTAs are full system images instead of patches/deltas. So you can safely update via OTA, root and other modifications won't break the OTA (but the OTA will get rid of any modifications including root.)
First, I'd like to say that while I'm not new to this, I AM quite rusty. So before you call me retarded for doing what I did, I already know. Now...
I have been just daily driving along on 4.4.2 for a good few years on my phone but I just got a Tab4 and rooted it and noticed that the TWRP version I wound up with was newer than on my phone, and had a few more options. Sooo, I tried to Odin the TWRP to my phone and caused all kinds of problems. Wouldn't boot. So I downloaded everything I could get my hands on to try to Odin onto the G900V to get it up and running again. The ONLY this I could flash was this...
PD1_Full_Factory_Restore_No_Aboot.tar
So now the phone is on the 6.0.1 which I figured was great but quickly noticed that not everything was working. No WiFi, no Camera, no Back and Recent keys, and no extsdcard recognition, so obviously unacceptable. Is this too new to be undone? I spent all night last night and today reading through the various forums, and I haven't seen it directly addressed.
Here are my questions...
1. Can I root this and fix the issues from there? If so, with what tool?
2. If I cannot yet root this, how do I downgrade from this kernel/firmware to something that is at least stable for this device?
Point me in the right direction, I'm not a total newb. I've rooted many devices, many times, but I really haven't been keeping up on anything for some time. Any help would be awesome, I'll pour some beer out for you, Thx in advance.
~Chris
I tried all of these, none will flash via Odin but the one that got me to where I am (PD1)
mods, please delete this post #2.
I edited it all into #1
Odin back to stock
I did something similar, which is what I get for just reading the instructions instead of the warnings at the top of a post.
I tried a number of things, but ended up using odin to do a complete wipe and go back to stock.
Thanks for the reply.
AFAIK this IS a stock ROM, but as I said this was the only thing I could get to flash after I tried to flash a new TWRP. Nothing else will go.
Being a bit rusty myself, it caught my ear when you mentioned the full wipe, I never performed a wipe of any sort during my efforts.
Could that be the problem?
Also, someone please refresh my memory, what piece is it that actually determines whether a device is rootable?
Is it the kernel? Is this one rootable? What is the modern method for acquiring root? I was using towelroot back in the 4.4.2/4.4.4 days.
Thanks
UPDATE : It also will not make a phone call. Hitting the CALL button or trying to answer when it rings will cause the phone to reboot, lol
Someone please get me back to a custom recovery, I've got some great TWRP backups and a ****load of titaniumBU
Just downgrade to PB1 using the stock TAR and unlock your bl from there...
Thank you for the PB1 advice.
Should I be able to accomplish this via Odin?
Is a full wipe/reset required?
Thank you for the PB1 tip
Got that handled, all is up and running, but not rooted
Gunna have to wait till after work for that stuff
Thanks again
OK so now I'm fully stock PB1, where do I want to go from here to acquire root?
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
I ask because above I was advised to "downgrade to PB1 using the stock TAR and unlock your bl from there..."
My question arises from the fact that I had this phone rooted for YEARS before I messed it up, and the thread proclaiming that "S5 bootloader unlock is here!" seems to be only 3 months old. Leading me to wonder, do I need an unlocked bootloader, or merely to acquire root? Seems like a valid question to me. I just want to make sure in advance before proceeding.
SO in summary, this is the question...
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Also, what file system do I want for my SDcard?
Thank You
cjschriver3 said:
OK so now I'm fully stock PB1, where do I want to go from here to acquire root?
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
I ask because above I was advised to "downgrade to PB1 using the stock TAR and unlock your bl from there..."
My question arises from the fact that I had this phone rooted for YEARS before I messed it up, and the thread proclaiming that "S5 bootloader unlock is here!" seems to be only 3 months old. Leading me to wonder, do I need an unlocked bootloader, or merely to acquire root? Seems like a valid question to me. I just want to make sure in advance before proceeding.
SO in summary, this is the question...
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Also, what file system do I want for my SDcard?
Thank You
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=WS86FHqY6rE with appropriate files worked! Tremendous help for me.
Miilliiee said:
https://www.youtube.com/watch?v=WS86FHqY6rE with appropriate files worked! Tremendous help for me.
Click to expand...
Click to collapse
Thx for that. Being able to see the video helped a lot, not because I can't read, but just because I was able to see what was SUPPOSED to happen at each step.
All fixed up now. Thx again.