Related
For A701 users only running Jelly Bean Only.
Boot image used: AV051_A701_1.021.00_WW_GEN1. Should work fine on other JB builds.
New Version 3 uploaded 23/10/2012
Should fix ADB commands for /System Remount Thanks Vorbeth
2 Parts. Part 2 is full /system RW.... also know as ROOT for the A701 on JB who took the OTA
Part 1 is For people using the previous "andlommy" image flash..... For JB OTA see part 2...
Part 1
This is meant to replace your boot.img after performing the Root image flash from this thread by andlommy;
http://forum.xda-developers.com/showthread.php?t=1911437
Ok people, as some may realize, the current "root" procedure of fastbooting images doesn't allow full /system remount. This can be seen if you try to update your superuser binary. Superuser can't remount /system. Yes, you can probably delete some files via file manager, however, if you use a root app that calls for a /system remount, well, it's not going to happen. Not like it should be.
Also, the 701 doesn't have a reliable CWM, so we do things the old fashioned (and safer) way.
This method has been around in the 500 forums for some time now. Recently, I gave info to the 210 users to get the /system remount working on their tabs. I currently use the same. Why nobody tried it here, well.....
Basically it involves modifying the zimage to change security, and allow remounts. It does not involve the kernel itself, as it remains stock.
Replaces Stock A701 Boot.img
1. Allows for full /System RW
2. Increased IO over stock.
And yes, I do use the modified boot image, 2nd revision.
As always, you have to thank people who helped you in the past and present:And I owe a lot to these guys. (which is why I hit the Donate button for them)
Vorbeth
Civato
EZTerry
Skrilax_CZ
LinuxSociety
NOTE" You must have unlocked bootloader"
Also, you do this at your own risk.Most of you know this already.
Installation:
For previous somewhat Rooted JB installations.
Download the following package and unzip to your system.
FIX-JB-ROOT
1. Connect your tablet
2. USB Debugging is on
3. Open a command window where you unzipped the Fix-JB-Root
4. Type: adb reboot bootloader
after tab reboots to bootloader download, Type;
5. fastboot flash boot JB_701V3_boot.img
6. After success, reboot tablet.
7. Start Superuser and update binaries.
Part 2
AS A ROOT PROCESS. 701 only After OTA to JB.
Note that this is an alternative to the image flash method. You need only to OTA to JB, then follow the instructions.....
Needs Testing on a Stock JB 701 Make sure you've unlocked your bootloader
1. Follow the above procedures in part 1
2. After restart, with tab connected, open a CMD Window where you unzipped the package.
3. Type the following commands;
a. adb devices (and hit Enter. You should see your device listed)
b. adb remount /system (and hit Enter. You should see remount successful)
c. adb push su /system/xbin
d. adb shell chmod 6755 /system/xbin/su
e. Get Superuser and Busybox from the Playstore. Start Superuser, check for updating binaries. Install Busybox.
Hopefully this roots and grants /system RW. I don't have a stock 701JB, so would appreciate feedback if this works or not.
MD
Works perfect Thank you. Now we only nee CM10 for our 701
Thanks MD! Going to give the 4.1.1 another go this weekend, using this boot. Will let you know how it goes )
MD are you able to delete apk from "/system/vendor/app"?
IronFly said:
MD are you able to delete apk from "/system/vendor/app"?
Click to expand...
Click to collapse
Absolutely. Just moved Solitaire.apk into /Data/app
Use your root explorer and check for RW.
Remember, this just fixes a shortcoming in the original "pre-rooted image flashing" from 4.0.4 to 4.1.1 where you can't get system remounts from some root apps.
As stated near the end of the post, I haven't tried it on a "stock non-rooted" JB build.
MD
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse
fishwood said:
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
Click to expand...
Click to collapse
I answered in your original thread.
MD
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
misteral1970 said:
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
Click to expand...
Click to collapse
Yeah, I meant to tell you yesterday it won't help your situation. Your issue, is you're stuck on the ICS bootloader and it won't update to the JB one. Not to mention now, you have that "Hybrid Mix". Maybe one day can come up with a solution for it. Trying to get my hands on a 701 Service Rom.
Acer won't fess up the SBK (Secure Bootloader Key), so it sort of makes NVFlash non-usable unless we have it.
The service rom uses NVFlash, which in theory will change bootloaders (it's what we used in the 500 forums).
But until then, we're sort of stuck. I still have one trick up my sleeve, but's it's a long shot, and not even sure it'll work. Might perma-brick your tab. Will look at my old files.
MD
MD got your method working thanks for sharing this MOD!
RiceDie said:
MD got your method working thanks for sharing this MOD!
Click to expand...
Click to collapse
Which method? Experimental Root? Or just the full System RW?
Also, which build Rom are you running Mate?
MD
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
bschrib said:
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
Click to expand...
Click to collapse
The root method should work the same as with ICS and JB.
Basically need an 700 ICS and JB boot.img. to do the mod. Takes about 10 minutes. Fastboot the boot image, download SU and BB. Should be good to go.
MD
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Vorbeth said:
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Click to expand...
Click to collapse
Should have a modded boot image in a day or so. Seems the boot images are the same for all builds for 700 JB.
It's the weekend, so some family time is on order.
Thanks for the GB full update rom.
MD
Hi,
I was one of the first people who updated their A701 with the unrooted JB ROM which was posted on XDA forums. The update was flawless and smooth using the external SD card and normal recovery method. Last night I tried to unlock my device and root it using step by step instructions given on OP. Device has unlocked but it is still not rooted. I checked using Root Checker app. Have I missed any steps in performing the root operation? Please help.
Additionally after doing all the steps in the OP I reinstalled the original JB update ROM using external SD card and recovery method. Bootloader is still unlocked and device is still not rooted. Device is working fine as far as I can tell.
Awaiting expert advice and help!
Best regards,
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
farazjk said:
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
Click to expand...
Click to collapse
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Moscow Desire said:
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Click to expand...
Click to collapse
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
farazjk said:
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
Click to expand...
Click to collapse
The unlocked bootloader will have no effect on normal day to day operations.
I'll try and get a 700 or 701 stock user to run a couple of things to get the SU issue sorted out. Shouldn't take that long. Probably a matter of using adb to push it through.
The 700 already has a JB Full rom update package, so hopefully the 701 will get one soon as soon as somebody locates it
Think it's time to bother Acer, and see about a SBK......
MD
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Beret67 said:
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Click to expand...
Click to collapse
bump
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
sbdags said:
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
Click to expand...
Click to collapse
I have reverted and upgraded 3 times and never "temp unrooted"
If you have a file explorer look for: /system/usr/we-need-root/su-backup
If that exists and if the perms are correct you can regain root. There are guides (I don't know where) but they walk you through regaining root.
Try the instruction here
http://forum.xda-developers.com/showthread.php?t=1926147
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
MartyHulskemper said:
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
Click to expand...
Click to collapse
Yeah, several guides suggest that you might have "partial root" and that rmoving/reinstalling supersu restores full root access.
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Beret67 said:
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Click to expand...
Click to collapse
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
bluewr said:
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
Click to expand...
Click to collapse
Update binary? How exactly do i do that? thanks for advice
Beret67 said:
Update binary? How exactly do i do that? thanks for advice
Click to expand...
Click to collapse
The trick is once you rooted, you need to launch superuser, and it will auto update your binary, then install OTA root keeper., then save root, then temp unroot, then upgrade, then use ota to restore root.
http://forum.xda-developers.com/showthread.php?t=1241517&nocache=1
Original devs op instructs to temp unroot.
Oops... double post.
Where'd the delete option go?
[CWM][Xperia J][JB] CWM for Jelly Bean 11.2.A.0.31 & 11.2.A.0.21 LOCKED bootloader
YOU MUST HAVE ROOT!
CWM by termobulbulator (for Jelly Bean 11.2.A.0.21 & 11.2.A.0.31 Works with locked bootloader)
0a Download THIS
0b Download THIS(for .21) or THIS(for .31)
1 Download THIS and extract
2 Enable USB debugging
3 Connect your phone to your computer
4 Turn on install.bat
To use the CWM:
5 Turn on Flashtool
6 Flash with Flashtool "recovery.ftf"(In Flashtool in "Branding" is written:""Aby uzywac CWM sflasuj to") When flashtool finish, unplug Your phone from USB.
7 Turn on phone. When you see the Sony logo, click Vol -.
To use Android:
8 Take the battery out for 5 seconds.
9 Turn on Flashtool
10 Flash with Flashtool "JB.ftf"(or "JB31.ftf)(In Flashtool in "Branding" is written:"Aby uzywac TELEFONU sflasuj to"). When flashtool finish, unplug Your phone from USB.
11 Turn on phone
12 And the most important point (for me), click "THANKS" if I helped
13 Done.
How to flash via flashtool: http://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
Way to CWM for Jelly Bean does not allow copying.
Controls: "Vol +" - Up, "Vol -" - down, "power" - confirm.
I am not responsible for damage..
Original: http://forum.android.com.pl/f779/st26i-root-cwm-twrp-xperia-j-ra-wniea-dla-11-2-a-0-21-a-240340/
I'v test it and this is working!
So this method is swapping kernels? And is not a permanent recovery
Yeah, this is not permanent recovery, its just like, we flash Vengeance's kernel include CWM (for unlocked bootloader) and flash it back to JB's kernel.
Sent from my Xperia J using xda app-developers app
Good job CWM working
thx so much! its working great for flash mods :victory:
I don't know if this is related or not, but with (or without this) still impossible to flash a custom rom with a custom kernel on locked bootloader?
So its not permanent, right?
Does backup&restore works?
Sent from my ST26i using xda premium
Hello, so this is only for bootloader unlocked, beacuse in the files.zip the ext.. is xxxx.sin, how flashed
sack3 said:
Hello, so this is only for bootloader unlocked, beacuse in the files.zip the ext.. is xxxx.sin, how flashed
Click to expand...
Click to collapse
Name of thread say thats for locked bootloader too
Sent from my ST26i using xda premium
Backup and restore works perfectly.. This is not pernament recovery but is really helpful for install custom roms and flashable zips
ROS!U said:
Backup and restore works perfectly.. This is not pernament recovery but is really helpful for install custom roms and flashable zips
Click to expand...
Click to collapse
All cwm recovery which are posted before your was helpful for flashing roms... But b&r dont work. Will try one day
Sent from my ST26i using xda premium
IDSG said:
I don't know if this is related or not, but with (or without this) still impossible to flash a custom rom with a custom kernel on locked bootloader?
Click to expand...
Click to collapse
Anyone?
IDSG said:
Anyone?
Click to expand...
Click to collapse
You can't have a custom kernel on a locked bootloader, only custom roms.
Mata_Ratos said:
You can't have a custom kernel on a locked bootloader, only custom roms.
Click to expand...
Click to collapse
That's what I thought its a shame, at least there's a great stock based rom thanks to gavster
A giant step!!! :good: :good: :good:
One inconvenient though... to exit CWM we need to take the battery out, isn't it?
Eduardo C. said:
A giant step!!! :good: :good: :good:
One inconvenient though... to exit CWM we need to take the battery out, isn't it?
Click to expand...
Click to collapse
Yes, You need take the battery out.
This method work with LOCKED and UNLOCKED bootloader!
Backup and restore work perfectly.
Hello
thank you very much
Works great :good:
termobulbulator said:
YOU MUST HAVE ROOT!
CWM by termobulbulator (for Jelly Bean 11.2.A.0.21 & 11.2.A.0.31 Works with locked bootloader)
0 Download THIS and THIS
1 Download THIS and extract
2 Enable USB debugging
3 Connect your phone to your computer
4 Turn install.bat
To use the CWM:
5 Turn Flashtool
6 Flash with Flashtool "recovery.ftf" after finishing unplug the phone from the USB.
7 Turn when you see the Sony logo, click Vol -.
To use Android:
8 Take the battery out for 5 seconds.
9 Turn Flashtool
10 Flash with Flashtool "JB.ftf" after finishing unplug the phone from the USB.
11 Turn on the phone
12 And the most important point (for me), click "THANKS" if I helped
13 Done.
Way to CWM for Jelly Bean does not allow copying.
Controls: "Vol +" - Up, "Vol -" - down, "power" - confirm.
I am not responsible for damage..
Original: http://forum.android.com.pl/f779/st26i-root-cwm-twrp-xperia-j-ra-wniea-dla-11-2-a-0-21-a-240340/
Click to expand...
Click to collapse
I already downloaded the 3 files and i do not see any file named "recovery.ftf" or "JB.ftf", i have this 3 files cwm_j_v6.1, JB and Recovery the 3 file are compresed files and inside of them there are not any files named as you mention. As i know we can not flash files that are not .ftf using flashtool unless i am wrong. Please some one clarify the procedure installation so whoever dumbass like me can use this.
i cant seem to properly install CWM on my xperia J. when i run install.batch it displays the following
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
797 KB/s (817 bytes in 0.001s)
1908 KB/s (9736 bytes in 0.004s)
4858 KB/s (2703360 bytes in 0.543s)
3323 KB/s (735308 bytes in 0.216s)
211 KB/s (681 bytes in 0.003s)
=============================================
Step3 : Setting up files system partition.
=============================================
/system/bin/sh: su: not found
Finished!
Press any key to continue . . .
but when trying to start CWM it just dosent do anything and boots the cellphone normally.
Can someone help me out on this one please? I would love to be posting this on the right place but xda rules don't let me to
hey guys i just got a new htc m8 i got the new firmware update for it but i havnt installed it yet and was wondering if the htc tool kit would still work with it to root it or if there was an easier method for it now thx in advance
Bierce22 said:
hey guys i just got a new htc m8 i got the new firmware update for it but i havnt installed it yet and was wondering if the htc tool kit would still work with it to root it or if there was an easier method for it now thx in advance
Click to expand...
Click to collapse
From what I have seen, you cannot have just root on 4.4.3. Verizon has patched that exploit. The only way to have root on 4.4.3 is to be s-off and unlocked.
With that being the case, if you choose to go s-off route, I would try and s-off with 4.4.2 version using firewater to see if that works first. If that does not work, you will need to use sunshine and pay $25 to get s-off and then you can root your device using a couple of different methods. Sunshine will work on 4.4.2 or 4.4.3 so it would not matter if you updated your phone before or after.
Somebody correct me if I am wrong, but that is what I have been reading.
jsaxon2 said:
From what I have seen, you cannot have just root on 4.4.3. Verizon has patched that exploit. The only way to have root on 4.4.3 is to be s-off and unlocked.
With that being the case, if you choose to go s-off route, I would try and s-off with 4.4.2 version using firewater to see if that works first. If that does not work, you will need to use sunshine and pay $25 to get s-off and then you can root your device using a couple of different methods. Sunshine will work on 4.4.2 or 4.4.3 so it would not matter if you updated your phone before or after.
Somebody correct me if I am wrong, but that is what I have been reading.
Click to expand...
Click to collapse
okay i finally managed to get s off using the firewater method but im confused on were to go from here
Bierce22 said:
okay i finally managed to get s off using the firewater method but im confused on were to go from here
Click to expand...
Click to collapse
Are you looking to just root your stock rom or installing custom rom's?
jsaxon2 said:
From what I have seen, you cannot have just root on 4.4.3. Verizon has patched that exploit. The only way to have root on 4.4.3 is to be s-off and unlocked.
With that being the case, if you choose to go s-off route, I would try and s-off with 4.4.2 version using firewater to see if that works first. If that does not work, you will need to use sunshine and pay $25 to get s-off and then you can root your device using a couple of different methods. Sunshine will work on 4.4.2 or 4.4.3 so it would not matter if you updated your phone before or after.
Somebody correct me if I am wrong, but that is what I have been reading.
Click to expand...
Click to collapse
jsaxon2 said:
Are you looking to just root your stock rom or installing custom rom's?
Click to expand...
Click to collapse
i actually dont mind sense right now i just came from an s3 with cm11 so its a nice change i just want permanent root and a recovery for now my main concern is its wanting to update it to 4.3 i delayed it untill tomorow but im not sure if that would ruin everything
Bierce22 said:
i actually dont mind sense right now i just came from an s3 with cm11 so its a nice change i just want permanent root and a recovery for now my main concern is its wanting to update it to 4.3 i delayed it untill tomorow but im not sure if that would ruin everything
Click to expand...
Click to collapse
You are fine to let it update. You will not loose s-off.
What I would do is let it update, then I would install a custom recovery, TWRP from here http://forum.xda-developers.com/showthread.php?t=2717928. You can download the image and try this to install:
You will need temp root to install recovery with Flashify. Sunshine http://theroot.ninja/ will allow you temproot when you run it, install flashify and flash recovery.
Once recovery is installed, flash SuperSU.zip
If that does not work, follow this to install.
Download the above file into your platform-tools dir.
Turn off your device.
Turn on the device and keep holding volume down until a menu shows up.
Select fastboot from the menu list.
Plug the device into your computer.
If you have the right drivers installed, your screen should now say FASTBOOT USB.
Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Next you could install the SuperSU zip through recovery from here: http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip. Here is the thread if you have questions on SuperSU. http://forum.xda-developers.com/showthread.php?t=1538053
Boom, you are stock HTC Sense w/Android 4.4.3 with root.
You can stay on stock from there or flash a custom rom that already has root built in.
jsaxon2 said:
You are fine to let it update. You will not loose s-off.
What I would do is let it update, then I would install a custom recovery, TWRP from here http://forum.xda-developers.com/showthread.php?t=2717928. You can download the image and try this to install:
You will need temp root to install recovery with Flashify. Sunshine http://theroot.ninja/ will allow you temproot when you run it, install flashify and flash recovery.
Once recovery is installed, flash SuperSU.zip
If that does not work, follow this to install.
Download the above file into your platform-tools dir.
Turn off your device.
Turn on the device and keep holding volume down until a menu shows up.
Select fastboot from the menu list.
Plug the device into your computer.
If you have the right drivers installed, your screen should now say FASTBOOT USB.
Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Next you could install the SuperSU zip through recovery from here: http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip. Here is the thread if you have questions on SuperSU. http://forum.xda-developers.com/showthread.php?t=1538053
Boom, you are stock HTC Sense w/Android 4.4.3 with root.
You can stay on stock from there or flash a custom rom that already has root built in.
Click to expand...
Click to collapse
sweet i managed to get trwp using fastboot method is there a clean sense rom debloated that i can use that has an updater and cpu stuff like cyanogen?
I've been through all the threads on rooting my new M8 but they're all out of date since 4.4.4 dropped. Is there any prospect we'll see an updated thread or new simple method to root?
mk3 said:
I've been through all the threads on rooting my new M8 but they're all out of date since 4.4.4 dropped. Is there any prospect we'll see an updated thread or new simple method to root?
Click to expand...
Click to collapse
There will be when there is a way. Right now there's not
How about unlock the boot loader on HTC dev site ?
finanandroid said:
How about unlock the boot loader on HTC dev site ?
Click to expand...
Click to collapse
Verizon don't allow that.
Yes please
I also would like to see a new something to help with rooting. I have been running root on my M8 for a while and went through the weaksauce method until that was no longer available them I switched to the Towelroot method and also used sunshine. Now after the update to 4.4.4 (which I knew I should not have done) I cannot use any method. I am hoping the update to Sunshine 3.0 comes soon and that fixes the problem. Also some better instructions to turn of the firmware updates and stop those dumb notifications would help a lot.
reaperslay said:
I also would like to see a new something to help with rooting. I have been running root on my M8 for a while and went through the weaksauce method until that was no longer available them I switched to the Towelroot method and also used sunshine. Now after the update to 4.4.4 (which I knew I should not have done) I cannot use any method. I am hoping the update to Sunshine 3.0 comes soon and that fixes the problem. Also some better instructions to turn of the firmware updates and stop those dumb notifications would help a lot.
Click to expand...
Click to collapse
If you used sunshine you are s off. Boot into fastboot and flash a custom recovery and then flash a supersu.zip. If s off you are beyond needing exploits.
Thought after I donated for unlock and S-off with Sunshine, I tried to flash twrp recovery as usually do all my flashing through computer (adb)
well it was no possible, weird thought to gain root I just need to flash custom recovery and superuser. Nope It was my M7 At&t with 4.4.2 Sense5.5, (hboot 157000) was untill I installed and run TowelRoot (after Sunshine) it did the root. then i flashed inmediately twrp and sense6 OTApkg.
So i hope that jcase-beaups instruct to or write a guide how to root the M8 4.4.4 after Sunshine 3 be released . It will help alot of users that think Sunshine will root as well and awesome will be if they include the root exploit along with sunshine, I know some people do not want to root just unlock-s-off but without root privilege it make no sense a least for me. I will be waiting for Sunshine3 to unlock _S-off-root my new HTC m8, I took the ota knowing that Sunshine will not work for a while ( I wanted to take the M8-firmwares-4.4.4 from VZW) truested that sunshine will do after.
I did with my M7 as well took the ota and then used Sunshine a small support to those great developers that put all their work at our hands. Thank you.
dottat said:
If you used sunshine you are s off. Boot into fastboot and flash a custom recovery and then flash a supersu.zip. If s off you are beyond needing exploits.
Click to expand...
Click to collapse
I wish people would learn this and pay attention when it's said. Once unlocked, or in HTC's case, S-off there's no longer a need to you use a root exploit ever again.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
I wish people would learn this and pay attention when it's said. Once unlocked, or in HTC's case, S-off there's no longer a need to you use a root exploit ever again.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That's what I though but some users run into Root annoyances included me even after flashing Recovery and Su.
and yes I used root exploit in order to root. (towelroot)
so I hoped Sunshine for 4.4.4 fix the small problem. jcase said will include su in the next version
http://forum.xda-developers.com/showpost.php?p=55985887&postcount=1218
http://forum.xda-developers.com/showpost.php?p=56167285&postcount=1341
http://forum.xda-developers.com/showpost.php?p=56119893&postcount=1312
http://forum.xda-developers.com/showpost.php?p=55874823&postcount=1176
http://forum.xda-developers.com/showpost.php?p=55884505&postcount=1179
finanandroid said:
That's what I though but some users run into Root annoyances included me even after flashing Recovery and Su.
and yes I used root exploit in order to root. (towelroot)
so I hoped Sunshine for 4.4.4 fix the small problem. jcase said will include su in the next version
http://forum.xda-developers.com/showpost.php?p=55985887&postcount=1218
http://forum.xda-developers.com/showpost.php?p=56167285&postcount=1341
http://forum.xda-developers.com/showpost.php?p=56119893&postcount=1312
http://forum.xda-developers.com/showpost.php?p=55874823&postcount=1176
http://forum.xda-developers.com/showpost.php?p=55884505&postcount=1179
Click to expand...
Click to collapse
The problem is users who are s off are trying to use hacky (towelroot etc) means of getting root back after taking an ota.
They should be using twrp or cwr flashed via flashboot. Then flash the su.zip of choosing in recovery. That's the only way you should be rooting a rom after getting s off or being s off and taking an ota.
Can't tell you how tired it gets trying to explain to an s off user who keeps trying to run an exploit to get root. First link you posted the guy used towel root after flashing twrp. Wtf. That's not how it works. That's how it breaks. /rant
dottat said:
The problem is users who are s off are trying to use hacky (towelroot etc) means of getting root back after taking an ota.
They should be using twrp or cwr flashed via flashboot. Then flash the su.zip of choosing in recovery. That's the only way you should be rooting a rom after getting s off or being s off and taking an ota.
Can't tell you how tired it gets trying to explain to an s off user who keeps trying to run an exploit to get root. First link you posted the guy used towel root after flashing twrp. Wtf. That's not how it works. That's how it breaks. /rant
Click to expand...
Click to collapse
I don't know if they are trying to hack ? i just point to a annoying may be a little bug with the intention to enrich info about sunshine and users
experiences. In my case I did Sunshine on the wife M7, never rooted, pure stock, she took the OTA, and I want to try Sunshine.
after s-off and unlock I couldnt flash recovery and Su have no binaries , use to flash from recovery su.zip to correct this problem but this time
with out custom recovery you cant. I was s-off unlocked. then I recall towelroot, run it grant me root inmediately, flash recovery and Su binaris updated immediately.
finanandroid said:
I don't know if they are trying to hack ? i just point to a annoying may be a little bug with the intention to enrich info about sunshine and users
experiences. In my case I did Sunshine on the wife M7, never rooted, pure stock, she took the OTA, and I want to try Sunshine.
after s-off and unlock I couldnt flash recovery and Su have no binaries , use to flash from recovery su.zip to correct this problem but this time
with out custom recovery you cant. I was s-off unlocked. then I recall towelroot, run it grant me root inmediately, flash recovery and Su binaris updated immediately.
Click to expand...
Click to collapse
What prevented you from flashing a custom recovery?
An unlocked s off phone will flash recoveries and firmware for that matter all day long without a complaint.
And by hacky I mean a hacky method to root. It's not clean.
dottat said:
What prevented you from flashing a custom recovery?
An unlocked s off phone will flash recoveries and firmware for that matter all day long without a complaint.
And by hacky I mean a hacky method to root. It's not clean.
Click to expand...
Click to collapse
wells ADB was giving me a error, I changed cables but wait I was with the original usb cable so
I try a second time, same error it wont let me flash nothing, weird i was s-off and unlocked! so
i did towel root, su, busybox. then I was able to flash
finanandroid said:
wells ADB was giving me a error, I changed cables but wait I was with the original usb cable so
I try a second time, same error it wont let me flash nothing, weird i was s-off and unlocked! so
i did towel root, su, busybox. then I was able to flash anything i want like allways do.
Click to expand...
Click to collapse
You would be using fastboot to flash. If you want I can help you get a working fastboot/adb setup via team viewer at some point it works for both of us.
dottat said:
You would be using fastboot to flash. If you want I can help you get a working fastboot/adb setup via team viewer at some point it works for both of us.
Click to expand...
Click to collapse
Thank you! but i have a working set up adb from long time ago updated last year, I only flash through fastboot adb you know its a piece of cake
an secure than anything, thanks again
PD: my retired HTC DNA is working on my adb, so my new HTC m8 as well.
the M7 after sunshine was the problem...solved.
finanandroid said:
wells ADB was giving me a error, I changed cables but wait I was with the original usb cable so
I try a second time, same error it wont let me flash nothing, weird i was s-off and unlocked! so
i did towel root, su, busybox. then I was able to flash anything i want like allways do.
Click to expand...
Click to collapse
finanandroid, I received an error using fastboot when flashing a recovery. Turns out I was using a fastboot.exe from 2011. Once I found a newer fastboot dated 1/17/2014 the error went away. Might want to check that. dottat knows what he is talking about. There is no need to use towel root to gain root access on an S-Off Unlocked M8.
- Just flash twrp (http://teamw.in/project/twrp2/164)
- Boot into recovery
- Hit the reboot button
- Hit the system button
- twrp will prompt you to install SuperSU. Allow twrp to install SuperSU
- Once finished boot into your phone and open SuperSU to complete setup.
Darth Grimnir said:
finanandroid, I received an error using fastboot when flashing a recovery. Turns out I was using a fastboot.exe from 2011. Once I found a newer fastboot dated 1/17/2014 the error went away. Might want to check that. dottat knows what he is talking about. There is no need to use towel root to gain root access on an S-Off Unlocked M8.
- Just flash twrp (http://teamw.in/project/twrp2/164)
- Boot into recovery
- Hit the reboot button
- Hit the system button
- twrp will prompt you to install SuperSU. Allow twrp to install SuperSU
- Once finished boot into your phone and open SuperSU to complete setup.
Click to expand...
Click to collapse
Thanks for your input, I don't doubt that Dottat is right about it, I didn't post a problem to seek a fix I fixed it since I posted, Just wanted to share sunshine user experience. however the problem wasn't fastboot adb.
the problem was with the HTC M7. state it in my first post.
So I have sun shine on my m8 and its rooted and working great. Verizon keeps trying to push the 4.4.4 ota update on me.. Is there an update i should grab or let it install since I have sunshine..
Thanks Kyle
Greetings,
Thread cleaned.
Not everyone in these threads are at the same level...if you can be helpful then please do so if not move along.
After all we were all noobs at one point.
Thanks,
BD619
i think this is the information i was looking for also.
is the problem only that sunshine wont unlock a 4.4.4 device?
but if, like me, you are s-off and unlocked already you can update by any method without worry and still be unlocked and s-off.
if you then re-lock your device (for whatever reason) after updating to 4.4.4, then you cannot re-use sunshine (until sunshine is updated)
please correct if i am wrong.
i am waiting to update to 4.4.4.