I've just seen a video on Youtube where a user has rooted his SGS II using Gingerbreak available here at XDA.
Am wondering if anyone has been brave enough to try it with their retail unit??
Sent from my X10i using XDA Premium App
+1
... Seeing as this is the make or break in my decision to buy.
Didn't work for me, sadly :-(
Given the latest attempts to secure root by Samsung, it may prove to be a task. The Indulge required that su be recompiled, and Superuser.apk be modified.
The above changes did not work on the ED12 leak of Gingerbread for the Samsung Epic4G.
This is probably going to be quite annoying.
Also note that the adb exploit we have been using has been patched in GB, so rageagainstthecage is not going to work at all.
I thought the bootloader was unlocked in the SGS2?
Gingerbreak 1.2 did not work on my retail unit. It sat at the "this may take a few minutes" screen indefinitely.
QuboidRC said:
I thought the bootloader was unlocked in the SGS2?
Gingerbreak 1.2 did not work on my retail unit. It sat at the "this may take a few minutes" screen indefinitely.
Click to expand...
Click to collapse
Bootloader being unlocked/locked has nothing to do with running an exploit to obtain root within the actual system...
But yeah, Gingerbreak does not work either on my SGS2... Neither the apk or the manual version via adb...
My comment was in reply to Dameon87 saying "Given the latest attempts to secure root by Samsung, it may prove to be a task." - is this not referring to the bootloader being locked? I'm a bit hazy on the technical side of this so perhaps I'm way off.
QuboidRC said:
My comment was in reply to Dameon87 saying "Given the latest attempts to secure root by Samsung, it may prove to be a task." - is this not referring to the bootloader being locked? I'm a bit hazy on the technical side of this so perhaps I'm way off.
Click to expand...
Click to collapse
No, all reports say the bootloader is unlocked. Samsung also confirmed they would not lock bootloaders unless it was requested by google.
QuboidRC said:
My comment was in reply to Dameon87 saying "Given the latest attempts to secure root by Samsung, it may prove to be a task." - is this not referring to the bootloader being locked? I'm a bit hazy on the technical side of this so perhaps I'm way off.
Click to expand...
Click to collapse
Root is the equivalent of "Administrator" privileges in windows. Android uses Linux, in linux one of the first things you learn in the terminal is how to gain root priviliges. You either temporarily use root with "sudo [command]" or you permanently take root through "su --".
Once we gain root, we can do anything on the phone since the bootloader is unlocked.
I know what root is but I don't know what a boot loader is and the significance of it being locked. Is it like BIOS?
Look, I don't have an SGS2 yet, nor do I have a flashable firmware in hand.
If I (or another hacker) can get my grubby little hands on an original flashable zImage from a retail device (sooner or later), AND I can figure out how to dump and fix the contents (I did it for SGS and SGT, so I hope I will again have success), it is possible to patch the zImage to include su and Superuser.apk. This will then be flashable with ODIN.
This is exactly why and how CF-Root on both SGS and SGT works. If the bootloaders are indeed unlocked, this shouldn't be all that difficult to do. I will hopefully be able to do it, I don't doubt Supercurio will be able to, and probably at least 50 others here on XDA know at least the basics for how to do this.
I'm betting (I ordered 2 SGS2's, but I won't get them 'til end of May) on this to be true and work. You'll just have to be patient a little until some of us devs get our hands on the device and some flashable firmwares.
I would be _really_really_ surprised if this isn't rooted within the next 4 weeks, using this or another method.
EDIT: Note that rooting has little to do with the bootloaders. The bootloaders generally decide if you can flash a custom kernel (the above method - cannot be done on protected bootloaders). NAND-lock or S-ON means that the /system is protected and cannot be modified. Root means you gain superuser priviliges, which can be accomplished in various ways, either with or without a locked bootloaders. It's damned difficult to do with NAND-lock though
QuboidRC said:
I know what root is but I don't know what a boot loader is and the significance of it being locked. Is it like BIOS?
Click to expand...
Click to collapse
Boot loader is code that is executed before any operating system starts to run. It reads data stored in ROM and starts to load it into RAM so that your CPU can execute the code.
By having the boot loader unlocked, we can change what is executed at boot.
Thanks.
S-On is a *****, I had that on my HTC Desire. I installed Cyanogen Mod with it still on, it was only when I tried to do things like change the host file that I ran into problems. I eventually had boot my PC from a boot CD and run some special software, goodness knows why it needed a boot CD! I got there in the end.
?
http://www.youtube.com/watch?v=9lVft5HoKP8
sun-drop said:
?
http://www.youtube.com/watch?v=9lVft5HoKP8
Click to expand...
Click to collapse
Patched.
Paul O'Brien (Modaco) has already tweeted he has pre ordered a SGS2 from Amazon and expects delivery next week.
Given his track record, I say he'll have it rooted in 48hours lol! Just need to pull him off the LG O2X first!!
Regards.
Chainfire just rooted a SGSII. So yes, it's possible. No, boot loader isn't locked.
Your wallets going to be sad ;-)
bilboa1 said:
Chainfire just rooted a SGSII. So yes, it's possible. No, boot loader isn't locked.
Your wallets going to be sad ;-)
Click to expand...
Click to collapse
Link? Screenshot? Tweet?
Anything?
Regards.
It's not rooted yet (but with luck in 10 minutes or so it will be). We did flash an unsigned kernel, and THAT worked, which confirms UNLOCKED bootloaders.
woops i though i read root too :s
well uve 5min. get to work.
Related
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
can some1 clarify the process tree to get to a new rom?
http://transformerprimeroot.com/tra...ow-to-unlock-bootloader-on-transformer-prime/ <--- how hard is it 2 succeed this without bricking it?
b3ava said:
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
If any1 can redirect me 2 the appropriate topics I can never spot out what I want :/ and can some1 clarify the process tree to get to a new rom?
Click to expand...
Click to collapse
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
omac_ranger said:
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
Click to expand...
Click to collapse
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
If you are planning to flash a custom rom, check out androwookie v1.2 its good.
Unlock gives you the ability to install a custom recovery e.g. cwm, you then use this to flash a pre-rooted rom. Root just means having access to the root directory. It enables access to features and functions that are normally made inaccessible.
Using the fastboot method is pretty simple and guides can be found easily. I just did it yesterday after having previously only rooted and installed cm 7+9 on my sgs2.
Thats my understanding anyway
b3ava said:
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
Click to expand...
Click to collapse
It's just one of their stipulations. Most manufacturers are like that in regards to using their unlock tools.
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
I hope I cleared it up for you a bit
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
It's just one of their stipulations. Most
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
b3ava said:
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
Click to expand...
Click to collapse
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
b3ava said:
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
Click to expand...
Click to collapse
No problem! And yep, the link in the first post is a great looking guide for unlocking. Nice and easy, step by step. And after you have unlocked, just download ROM Manager from the market and you can flash CWM through the app itself. From my understanding that's the easiest way to do it, at least. Sorry it's been a few days since I responded, I haven't really been checking out the Q&A section lately
Sent from my Transformer Prime TF201 using XDA Premium HD app.
Bootloader unlock:
Custom Kernel possible
Official updates impossible
Waranty impacted
CWM backups possible
Need to use community ROMs in future
improved but not great chance of recovering from bad ROM flash (really needs NVFLASH)
Rooted:
Now possible with firmwares up to .28
Permits write access to /system partition
Makes it easier to brick and block OTA updates
Should be reversable
Allows most tweaks to be applied except for replacing kernel (which is a prerequisite for some kernels)
Going to make this a FAQ I think...
For those of you looking to root your N3, @Chainfire has updated his one-click app for N3 variants. No official support for the Verizon variant yet, but it's something to keep an eye on. No word on the bootloader as it's not anyone's hands yet.
http://forum.xda-developers.com/showthread.php?t=2466423
That's good to know. Thx.
Sent from my SCH-I545 using Tapatalk 4
unlocked BL NEEDED.
Indeed. This method will not work with a locked bootloader. We have to wait for an exploit in order to root.
suzook said:
unlocked BL NEEDED.
Click to expand...
Click to collapse
I was not aware that this method needed an unlocked bootloader. I should have read more.
Banggugyangu said:
Indeed. This method will not work with a locked bootloader. We have to wait for an exploit in order to root.
Click to expand...
Click to collapse
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
This is great to hear!!1
It sounds as if within days of release we are likely to haveca method for rooting. I would be grateful for unlocking but expect to use Safestrap
docnok63 said:
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Read what I said again.... And you're wrong. You can't write to the recovery image on a locked bootloader phone. That means no custom recovery. What you CAN do.... is bootstrap a recovery. Different process, different results.
If you had read my post more closely, I said that we are going to have to wait on an exploit for root capabilities. Once we have root, I'm sure a bootstrap will follow. Hopefully, exploitative rooting won't trip knox. If it doesn't, then a bootstrap recovery also shouldn't. At that point, a custom ROM (especially if hashcode creates a safestrap) should bypass the software side of knox preventing tripping from that as well.
Banggugyangu said:
Read what I said again.... And you're wrong. You can't write to the recovery image on a locked bootloader phone. That means no custom recovery. What you CAN do.... is bootstrap a recovery. Different process, different results.
If you had read my post more closely, I said that we are going to have to wait on an exploit for root capabilities. Once we have root, I'm sure a bootstrap will follow. Hopefully, exploitative rooting won't trip knox. If it doesn't, then a bootstrap recovery also shouldn't. At that point, a custom ROM (especially if hashcode creates a safestrap) should bypass the software side of knox preventing tripping from that as well.
Click to expand...
Click to collapse
Since you want to argue sematics and I'm just in that kind of mood, my post never stated that SafeStrap involved writing to the recovery partition; simply that it was possible to have a custom recovery run on a device with a locked bootloader.
Neither the ME7 root method nor SafeStrap triggers Knox on the S4 and I don't expect them to for the N3. Of course, all this will be unnecessary if we get the bootloader. We only have a few days to wait for the devices and then a few days more to know for sure.
docnok63 said:
Since you want to argue sematics and I'm just in that kind of mood, my post never stated that SafeStrap involved writing to the recovery partition; simply that it was possible to have a custom recovery run on a device with a locked bootloader.
Neither the ME7 root method nor SafeStrap triggers Knox on the S4 and I don't expect them to for the N3. Of course, all this will be unnecessary if we get the bootloader. We only have a few days to wait for the devices and then a few days more to know for sure.
Click to expand...
Click to collapse
You also never stated anything about a bootstrapped recovery. You posted about chainfire's root method, then argued (wrongly) against those that stated that method wasn't possible due to locked bootloader. Not one person in this thread said anything about not being able to root because of a locked bootloader, just that this particular method wasn't going to work. FFS admit that you were wrong and move on...
Banggugyangu said:
You also never stated anything about a bootstrapped recovery. You posted about chainfire's root method, then argued (wrongly) against those that stated that method wasn't possible due to locked bootloader. Not one person in this thread said anything about not being able to root because of a locked bootloader, just that this particular method wasn't going to work. FFS admit that you were wrong and move on...
Click to expand...
Click to collapse
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Silly rabbit. I did admit I was wrong and I my link was for the SafeStrap recovery for the S4. It's time YOU moved on. There's more important issues in life. I'm done with you.
Realistic chance?
I've got an unlocked Droid Bionic. I was chicken and waited till it was out of warranty though. I wanted root so I could do full backups, something I believe was not possibly without it. Like you, I'm waiting for my VzW N3 to come in. I"m not sure how to restore some of my apps, or actually some of the data saved with that. TBpro wont help unless there is root. I've purchase the Asurian extended protection, not to much fine print info on it.. people say manufacturer warranty is voided with root. what about standard extended warranties like Asurian?
Bottom line.. just a guess, and I'll not hold anyone to it. What the odds that the guru's here will unlock our Vzw N3 without tripping knox, or somehow else voiding warrranty.
I'm probably sticking with stock rom for now..but without root, not sure how to get all my app data back. Someone said EZ file could make an apk but didnt see how. Someone else suggested helium makes good app backups without root, but that doesnt work on Motorola..so it wont work for my Droid bionic
Please familiarize yourself with the Forum Rules at the top of every Forum. This is a discussion thread and not a Development thread. It has no place in the Development Forum. I have moved this to the General Section where it should have been all along.
I look forward to your future attention and cooperation.
EFM
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Docnoc we all appreciate this post and are confident the people working on this will find something for us. Fingers crossed and donations ready!
edfunkycold said:
Please familiarize yourself with the Forum Rules at the top of every Forum. This is a discussion thread and not a Development thread. It has no place in the Development Forum. I have moved this to the General Section where it should have been all along.
I look forward to your future attention and cooperation.
EFM
Click to expand...
Click to collapse
When I read your post I hear Nucky's voice from seeing your avatar and sig plus your words is how we would talk lol
Apparently Chainfire's method helped designgears root the AT&T version. This took about 3 days. Good news!
http://forum.xda-developers.com/showthread.php?t=2472760
Does this work for the Verizon Note 3 ? Thanks guys.
Ok so a couple of things to note here.
First off it is about a 2% chance that you can just flash a custom recovery. There was a phone recently where the recovery partition had no verification check. With that being said it would be a big over sight. The next thing is that with Hashcode already working on a qualcomm kexec and SS I would be very supprised to see it not work, or there not be a strap method. As for root, if I'm not mistaken, and i could be, but Chainfire relies on you having an unlocked bootloader, as his image just has an init script in the recovery to boot, change ro.secure to false and then flashback the old recovery. With this being said THIS WILL NOT WORK WITH LOCKED DEVICES. If the bootloader allows for a unsigned kernel recovery to boot you can do it, or if it allows for stacksmashing you can do it, but those are two very iffy things. As for a root on this device, its more then likely going to have to come from a security tag that has been created in the linux kernel, that allows unverified code to run.
Second off I think there's something important to point out here, and I'm going to post it back to the days where there was no android. As of right now we have achieved a semi unlocked state (see loki and SS) however this is much like Musclenerd and geohotz grabbing the source code and finding injection points, the big difference was when geohotz found the holygrail, an architecture level exploit. What this translates into our world is much harder since the iPhone has one chip and we have... well Qualcomm, TI, and Samsung to name some. With this being said, and I know its easier said then done, but I think we are going to need a Qualcomm level exploit to really unlock all of these phones. We have seen in the recent couple of days that there are interrupts early on in the boot chain, see rumrunner, are not impossible. The reality is that our holy grail lies in one of two places, a leek, which in reality is more likely to happen since the other option is not always possible, or a base level exploit. The thing to keep in mind is that it too geohotz 2 years to discover the A4 hole, and he was just one man. While a community is much bigger, I urge everyone looking for exploits on new phones to realize that YOU SHOULD NEVER BUY A PHONE THAT YOU DON'T LIKE STOCK.
Hope you all are enjoying your GN3. They really are a great device with or without an unlock!!!
On a side note:
docnok63 said:
Apparently Chainfire's method helped designgears root the AT&T version. This took about 3 days. Good news!
http://forum.xda-developers.com/showthread.php?t=2472760
Click to expand...
Click to collapse
The reason for this is it seems there is a leek there that is allowing him to run a script that flashes over files to the FS. Look at:
designgears said:
As usual, a big shout out to my anonymous source for the file hook-ups!
Click to expand...
Click to collapse
This means that he most likely has some sort of System dump that is signed and has RO.secure disabled. If you look there's actually a full 2.2 GB image that you have to download and flash, meaning that it most likely has something that allows for root, and not actually an exploit.
Hello everyone,
Right now I have another thread for the root over ADB with DirtySanta, I've that far. I have a potential method but I need more information on it from somebody else so I am waiting on a response from him, once i have that I'll work on it. If you guys have any other potential ideas that'd be great.
Thanks,
Abine45
This is my link to the root on ADB. I will be updating it tonight or tomorrow for the convenience of others. Thanks for waiting.
http://forum.xda-developers.com/verizon-lg-v10/general/temporary-root-adb-t3523538
NEW INFORMATION FOUND! I GOT SIGNIFICANT ROOT ACCESS WITH DIRTYSANTA!!!
SO i used the DirtySanta fearing for my life I wouldn't ruin my device, well the v10 failed it. rebooted and it didn't do anything but reboot back into the normal bootloader and stuff. But what i found is that he go the dirty cow to just work under root, so maybe from there we could do something, anybody have any ideas?
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Haxcid said:
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Click to expand...
Click to collapse
How did Tungkick manage to repackage it then? The dirty cow exploit can exchange recovery though on an unlocked bootloader so shouldn't I be able to replace the boot image if done correctly wouldn't it work? I could possibly unpack everything and modify it all and test it but the issue comes back to repacking and flashing?
Ask him, but if you attempt to do this on a locked and encrypted boot loader then you will brick the phone. I mean think about it, if it was really just that simple every phone would be rooted and rom'd. Most phones running 6 or above have had the security vastly increased to make the phone secure so they can be used by government employees. Hence the introduction to SELINUX polices into the kernel which is why getting root is so unbelievably difficult. The locked boot loader resets everything at boot so getting root and maintaining is so hard combined with SELINUX does not allow standard root to perm. write anything to the system partition and then good old hboot kills anything you did mange to write on reboot... you can start to see how difficult this really is.
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
LG are just not popular devices for hacking due to they make if extremely difficult. LG is a Corp. friendly company it is why Verizon loves them where companies like HTC are a bit more user sympathetic.
Funny you say that
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
Funny you say that! Tungick said to me, and i quote "[email protected]#$g you" and blocked me from Facebook. He also told me that he wouldn't tell me because it's a secret. He didn't speak very great English, that's why there is an ing at the end of the F-bomb. I asked Jcase through XDA and he said he wouldn't and so i put it better explanation of help through an email and he said I was harassing him... In which case before hand he said he doesn't develop for LG because he says basically we are A-holes sadly and that we don't live up to our donation pledges.
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
beavis5706 said:
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
Click to expand...
Click to collapse
True, that's why I'm going to try to do it. If you know anything and want to help could use it.
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
qujuanmiller said:
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
Click to expand...
Click to collapse
For sure, message me on xda.
beavis5706 said:
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
Click to expand...
Click to collapse
Anybody can help! Do some research and send it and whatever you would like to do. Try different things, Try to modify bits of code and see what you can do! Always gotta start somewhere!
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
beavis5706 said:
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
Click to expand...
Click to collapse
The thing with that is the fact that even if I know how systemless root works, I still have no way to install it, so first I need to find a way to get in the system.
Think I might have a way though
From what I understand systemless root will modify the boot image to attain root. Super SU will decide how to flash based on firmware version. Will automatically root normal with Lollipop and down, will automatically modify boot image on Marshmallow and up. How you will be able to modify the boot image on a VS990 without bricking it I don't know.
In order to do system less root we need a unlocked bootloader... It says that everywhere I'm reading
Hi abine45,
Please read this post completely, the guys here are close to obtain the perma root on android 6, using dirty cow.
https://github.com/timwr/CVE-2016-5195/issues/9
Sent from my E2006 using Tapatalk
I looked at this thread... a bit more technical than I am able to do... did it end up working? Looks like no, but I might have missed something.
Thanks!
BUild Number "rct6973w43-android6.0-v20-v1.16.30-e02"
kernel version 3.14.0+
wed nov 9 13:42:37 CST 2016
android security patch level june 1, 2016
android version 6.0.1
i heard someone tried rooting using the w42 root and bricked their's, so i'm reluctant to try it. any clues??
Same problem I bought this tablet at Walmart for 50 bucks and I tried a lot of rooting apps but still can't find anything that works without a computer and I definitely don't want a bricked tablet
did you try the kingroot thing?? or is that app only??
Guys, I'm sorry to say that the RCA Voyager III model RCT6973W43 cannot be rooted at this time. I tried running OneClickRoot to do this and it said it was impossible.
If you do this
https://www.reddit.com/r/tasker/comments/4zsi0e/project_share_toggle_settings_eg_location_mobile/
you can access a lot of unavailable settings as well as use immersive mode in everything including launcher.
MTRX2010 said:
BUild Number "rct6973w43-android6.0-v20-v1.16.30-e02"
kernel version 3.14.0+
wed nov 9 13:42:37 CST 2016
android security patch level june 1, 2016
android version 6.0.1
i heard someone tried rooting using the w42 root and bricked their's, so i'm reluctant to try it. any clues??
Click to expand...
Click to collapse
which w42 method are you refering to?
I have a root method thread out for w42 rca voyager with intel cpu. I also have instructions on the thread to NOT use if the version numbers do not match.
The only thing that should be different from the files provided on my thread and what you need , is your kernel. I have instructions on my github page. At the end of the instructions for root , are instructions to pull your boot.img.
If you follow along and are able to pull your images, I could make you the test files to try.
https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
Yes it is this command on mine. Not confirmed on the w43 model
Code:
"fastboot flashing unlock"
mrmazak said:
Yes it is this command on mine. Not confirmed on the w43 model
Click to expand...
Click to collapse
Which tool are you using?
Can adb be used instead?
Augustoandro said:
Which tool are you using?
Can adb be used instead?
Click to expand...
Click to collapse
Must be fastboot.
Often together with adb.
First enable "oem unlock" from the developers menu, (same menu you enable "usb debugging" from)
To get into bootloader mode on tablet, use adb. Then use fastboot.
Both from same terminal window on PC.
So like this
1. open cmd window(terminal on Linux)
2. Type "adb reboot fastboot"
Once in fastboot, if not already done, you will need to install drivers.
3. Optional, but recommended if you are unfamiliar . Type "fastboot devices" to verify properly connected to tablet.
4. Type "fastboot flashing unlock"
If anyone is still looking to root this tablet. It has been done on this thread
https://forum.xda-developers.com/android/help/how-to-root-rca-voyager-iii-model-t3602102
mrmazak said:
If anyone is still looking to root this tablet. It has been done on this thread
https://forum.xda-developers.com/android/help/how-to-root-rca-voyager-iii-model-t3602102
Click to expand...
Click to collapse
doesn't look like it's been, just looks like they got the bootloader unlocked, but i'm not finding anything
on the process to root the device, or a copy of the SU binary that needs to be installed to achieve root.
MTRX2010 said:
doesn't look like it's been, just looks like they got the bootloader unlocked, but i'm not finding anything
on the process to root the device, or a copy of the SU binary that needs to be installed to achieve root.
Click to expand...
Click to collapse
No it is not laid out , like . here do this ***, then copy this ***.
But the last step people needed for confirmation was proof of unlockable bootloader, then proof the patch tool I gave to the group , would work.
these things are shown in the thread, like I said. but just one user. and he immediately bricked the device. Just proof this chip / device is difficult to manage., but it can be done. But if you haven't figured out by the clues already maybe you shouldn't.
mrmazak said:
No it is not laid out , like . here do this ***, then copy this ***.
But the last step people needed for confirmation was proof of unlockable bootloader, then proof the patch tool I gave to the group , would work.
these things are shown in the thread, like I said. but just one user. and he immediately bricked the device. Just proof this chip / device is difficult to manage., but it can be done. But if you haven't figured out by the clues already maybe you shouldn't.
Click to expand...
Click to collapse
yeah im not good at making those elaborate android hacks work. i usually wait for a stable process before i make the attempt. i can adb, shell in, copy stuff over, and that's about it. ive rooted a number of devices, but i've only been able to do it once there's a reliable, concise method. the more steps-the more likely i am to screw it up.
I gave up on this tablet a while back, because it is aweful. it's so bloated the thing constantly stalls and chokes despite being a quad core atom. my guess is the code isn't even that well optimized. i found it a few days ago, and started playing with it again, then i remembered the thread on xda and the thread i started, but i checked my email, and didn't see a lot of notifications concerning the thread. come to find out ppl been working on it after all.
I got a dual core arm on a samsung lite 3, and it's way faster and slimmer. i haven't even bothered rooting it yet. but this RCA needs a lot of work, not just on the software end, but the hardware too. i gotta get in there and straighten out the crooked camera.
I used to be a windows coder way back in the ancient era of assembly language, but i don't know squat about these androids cept it runs on a linux kernel, and java bite code for the apps. ive never compiled anything for it before, but last i recall i was fixen to attempt compile my own SU binary since i couldn't find one for the atom arch on this tablet. -but i gave up on the tablet, and that's where i left off.
Ill give it a few more reads, and see if i can narrow down the process. if it looks more doable than a stroke of luck ill go for it. apparently there's multiple versions of this tablet, and if you try to do the roots from the RISC chip version of the voyager III you'll insta-brick your tablet, with no recovery. I've already seen a couple of people push the wrong root process on the device, and it got bricked beyond repair. 8(
mrmazak said:
No it is not laid out , like . here do this ***, then copy this ***.
But the last step people needed for confirmation was proof of unlockable bootloader, then proof the patch tool I gave to the group , would work.
these things are shown in the thread, like I said. but just one user. and he immediately bricked the device. Just proof this chip / device is difficult to manage., but it can be done. But if you haven't figured out by the clues already maybe you shouldn't.
Click to expand...
Click to collapse
Looking at this thread makes no sense what so ever, ive looked at it over 3 time and read the whole thing, judging by what has been said so far, it appears it hasnt been rooted, ive followed the whole thing, booting the generic cwm, dumped boot.img, unlocked bootloader, everything! Its not rooted what so ever from what i can see, unless im missing an ESSENTIAL step. Not new to rooting and android, ive messed about with it for a while now, so im just puzzled as to why i can figure this out, or maybe it wasnt ever rooted? Why mention it was? I have no idea! Anyways if it has then id like to be pointed in the right direction, if it hasnt, id be more than willing to help (intel atom voyager III).
Hello guys this guide is for who want to root phone without disabling ota updates.
(BOOTLOODER SHOULD BE UNLOCK)
BIG THANKS FOR MAKING PATCHED BOOT IMg @Jan.Pul
IAM NOT RESPONSIBLE FOR ANY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
1)Download patched boot.img from link below
2)copy that patched boot.img to your adb folder
3) adb debugging should be on and oem unlock should be on for unlock bootlooder
4)turn off your device and go into fastboot mode by pressing holding volume down and power key
5) check whether fastboot detect your device or not by typing this command on (cmd) FASTBOOT DEVICES
6) if fastboot shows that your device is connected your good to go
7) you need to boot into patched boot.img for this type a command FASTBOOT BOOT patched_boot.img your device will boot automatically
8) download magisk manager apk from google and. Open ur magisk manager and install ad direct method and reboot
If you get bootloop dont worry just press your power key for 5sec it will boot automatically
PATCH BOOT IMG : https://drive.google.com/file/d/1cU6qOMiHlGdSAbRtMVgTlHummcGksnt6/view?usp=drivesdk
Guessing this is for the Indian/Chinese version and the bnd-l24 is still sitting on the shelf? And rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Yes..But Why?
maximran said:
maximran said:
this guide is for who want to root phone without disabling ota updates.
(IAM NOT RESPONSIBLE FOR AMY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
Click to expand...
Click to collapse
str8stryk3r said:
rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Click to expand...
Click to collapse
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
RaiderWill said:
maximran said:
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
A Question Sir..
str8stryk3r said:
RaiderWill said:
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
kilroystyx said:
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
Click to expand...
Click to collapse
It will not work
Interesting!
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
Asder.mko said:
str8stryk3r said:
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Well, I got the OTA in December itself but since I had rooted and installed twrp recovery, I wasn't able to install the update.
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Before I went ahead an unlocked my bootloader I checked as many sources as I could about if whether or not I'd still be able ota update and the vast majority of the things I read states that what causes the update to fail is not having stock rom and not having stock recovery. The bootloader being unlocked doesn't modify those or any system files so everything should be fine. Unless Huawei changed things specifically for our Honor 7x then there shouldn't be any problems with ota updates. I guess I'll find out when the L24 people start saying they got updates and I don't receive it or can't install it
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Well, that's quite right. I don't know whether Huawei/Honor implemented THAT thing, but yeah reverting back to stock conditions wand applying OTA wouldn't be an issue!
( P.S - I'm stuck here too as I have OTA update since December but haven't reverted to stock to install it. I don't yet know properly about manual installation! )
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
iammudd said:
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
Click to expand...
Click to collapse
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
str8stryk3r said:
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
Click to expand...
Click to collapse
No need for full fw broh need vendor partitions, device tree, kernel sources
maximran said:
No need for full fw broh need vendor partitions, device tree, kernel sources
Click to expand...
Click to collapse
Lmao, and that's why I'm not a developer. I just know having the stock image files is important so that when something gets screwed up got have something to fall back on.
Bringing Up The Rear...
Asder.mko said:
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
RaiderWill said:
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
Click to expand...
Click to collapse
People like to root and mod their own devices for their own reasons but you're right, a lot of the reasons I modded past devices was because the roms almost always ran better than stock but the 7x imho runs great. Used to be kernels for better battery life and such. I like custom roms because I like to be able to do certain things that stock roms limited as far as customizing goes. A lot of people hate bloat and end up deleting every file on the phone that isn't necessary or to their liking to make the rom as minimal as possible.
But as of now I'm happy with the phone and don't feel the urge to need to root and and a custom recovery. The roms that eventually come would have to offer something worthwhile to flash. But hell, that's subject to change given how I'm feeling that day lol. There's a new AOSP based rom in another thread that sounds promising
RaiderWill said:
Will Huawei / Honor release a stock image of Nougat and Oreo ? ...
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x..
Click to expand...
Click to collapse
I assume that you already know this ... but I should mention it for others that you can run TWRP (if there is a version for one's phone) without flashing it. (I don't have my 7x yet, so I prob really shouldn't be trying to give detailed instructions anyways.) From there, you can make backups of the stock image, stock recovery, etc. (So thx again to this forum for reminding me that I should backup all stock images as soon as I receive my 7x so that MY fingerprints are not all over the backups.)
As to rooting, there ARE at least 2 things that Huawei hasn't provided without root:
Yes, I can make app backups (and/or use the Huawei "easy transfer"... not sure what app that is at the moment) but I'd assume that I won't be able to transfer it to a non-Huawei device. That's why I continue to use Titanium Backup.
USB Mass Storage Enabling (and by extension Selinux Passive mode). I want fast transfer to my desktop, etc.... and I want a drive-letter (yes, there are Win programs which only work with drive letters). Without UMS, I haven't found a way to do that.