Related
I'm having issues getting the Superuser app to grant root to root apps.
The superuser apk is installed but isn't functioning.
Here's what I did. I was coming from pirateghost's CWM root ROM which was built off the stock developer's ICS OTA update (see my signature). I decided to start over since the sync icon would not go away from the notification tab. I know this is a minor issue but it was very annoying staring at it every time I used the phone.
I did the following:
1) Installed Wildchild's recovery using fastboot
2) Wiped all the data from the phone using wildchild's recovery
3) Locked the bootloader
4) Installed the ATT Stock RUU
5) Unlocked the bootloader
6) Reinstalled wildchild's recovery using fastboot
7) Installed the Superuser apk using wildchild's recovery
Everything is working fine and I don't have the sync icon stuck in the notification tab, but now I can't get any root application to be granted root access. The system just times out when the app is requesting root.
I'm guessing that Wildchild's recovery root is not compatible with the stock ICS release, but is this true? I haven't used the vivid all in one kit because it appears to be using the same method to install root. Everytime you install root it blows away all the data on the phone and makes you start from fresh, so I'm reluctant to try anything unless I'm certain it will work.
Any suggestions from the experts?
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Yes, this is exactly what I did to the "T", just as in his video. SU is installed on my device but it doesn't grant any privileges to any root apps. I've been digging around searching for answers for about 3 hours and have found many people posting about the same issue but no fix.
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Wild Child said:
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Click to expand...
Click to collapse
I saw that and was wondering what "engineering Unguarded superuser" was but didn't know. I guess it's worth a try at this point.
FYI, I used the "Install eng (unguarded) su" and all it did was uninstall the Superuser apk.
Now the root apps respond with a different message when they request root. They don't see the SU app and reply with this statement, before they would hang while they requested SU access.
I'll wait until WC figures out what is going on or just download his ROM.
Are there any known bugs with his ROM?
[email protected] rooting....if going through trouble of unlocking bootloader and flashing a recovery....why not just flash a stock custom rom?....This make no [email protected] do this....Im the first to like completely stock builds,as thats what i use personally...but i cannot stand the at&t bloatware....Main problem with trying to root a stock build is the root access to kernel config....ill upload a stock rooted kernel, if having issues with root after using the recovery you need to install busybox from provided link below.
or flash the boot.img provided.
From original [email protected] guide
- ONCE BOOTED, if you have titanium backup installed but it says there isn't root or busybox isn't installed, download a free app from the market called BUSYBOX INSTALLER. Run this program and proceed in installing busybox. After that, try titanium backup again and it should work.
https://play.google.com/store/apps/...DMsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..
I had pirateghost's rooted ICS ROM installed but had the sync notification issue. That's why I decided to go back to the stock RUU. I've always been a stock kind of person. I don't know why, but I've always gone back to stock with my phones then rooted it and debloated it myself.
I'm downloading your ROM right now! Since I already have your recovery installed I'm sure this will be a breeze. Thanks!
megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
samsat said:
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
Click to expand...
Click to collapse
Look at wild Childs post a couple above this.
Sent from my HTC PH39100 using XDA
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
The fastboot flash boot boot.img command is the safest.
samsat said:
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
Click to expand...
Click to collapse
Wild Child said:
The fastboot flash boot boot.img command is the safest.
Click to expand...
Click to collapse
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Something else is going on then, my rom has nothing to do with this....the roms i release are already rooted and debloated stock builds
samsat said:
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Click to expand...
Click to collapse
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
megatronisabeast said:
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
Click to expand...
Click to collapse
Yes done the above but still running RUU ICS stock rom.
samsat said:
Yes done the above but still running RUU ICS stock rom.
Click to expand...
Click to collapse
I would say if you want root, the best thing to do is install one of Wild Child's roms. Once you install it, you will have root. He has an att build just like the att ruu but without the bloat.
http://www.wcxxperia-nce.com/index.php
This is his site. You have to register to see the vivid forum. Also, make sure to read the rules before installing his rom.
Exact process i did and it is rooted with titanium back up working...so flashing from wcxrecovery does work.
Testing procedure:
1 Flashed fastboot oem relock...success
2 Flashed PH39IMG.zip
3 Said Update was complete
4 Phone rebooted
5 My custom ROM was still present
6 Flashed PH39IMG.zip again
7 My custom ROM was still present
8 Attempted running RUU,Failed
9 Entered fastboot via Hboot menu
10 Re ran ruu,ROM updated completely.
11 Ran bootloader unlock command
12 Flashed wcx recovery (provided)
13 Flashed rooted kernel (provided)
14 Booted ROM,fully loaded
15 Rebooted into recovery
16 Installed superuser and su
17 Signed into Market
18 installed stericson Busybox
19 Installed titanium Backup
20 Succesfully rooted with stock att rom
21 Reboot phone after doing said process above Perm root achieved
Thanks WC. I must have been doing the same while you were posting this!
All went according to plan. I now have a rooted phone with unbloated ICS kernel, WCX recovery etc. etc.
Thanks WC, This is great
Nexus 4 OTA Help-Desk
**4.4.4 KTU84P Available**
You want the latest OTA? You don’t want to wait? You received the OTA but it fails? You need help with the installation process? If any of those questions are yes, then this thread is for you.
First, let's talk about what an OTA is:
An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have your phone up and running, with the latest software.
We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.
Now that you have read the important info above, Let's update your Nexus 4!
In order for the OTA to apply successfully, without intervention, you must be completely stock:
4.4.3 KTU84L
Current Bootloader - makoz30d
Current Radio - 2.0.1701.02
Stock Kernel - 3.4.0-perf-ga6edd5e
All system apps are present
No Modifications. AT ALL.
If you meet the criteria above the OTA will complete.
If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.
Current OTA's
4.4.4-KTU84P-from-4.4.3-KTU844L: http://android.clients.google.com/p....signed-occam-KTU84P-from-KTU84L.50b64331.zip Thanks @oldblue910
Legacy OTA's
All legacy OTA links can be found here: http://forum.xda-developers.com/showpost.php?p=33631631&postcount=1 Thanks @oldblue910
These are the 4 most popular scenarios. If you aren't sure where you fit, feel free to ask.
Scenario #1
You are completely stock. Unlocked/locked bootloader. No root
Continue to Section A
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C
Scenario #4
You are running a Custom ROM
Continue to Section C
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It's attached at the bottom.
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Section C: Let’s get back to stock
There are a few ways to do this:
Option #1) Flash the complete KTU84L image. Follow efrant’s guide: http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
OR
Option #2) Replace the stock images or .apk(s) you removed or modified.
After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:
Section A if you are running stock recovery.
Section B if you are running a custom recovery.
OR
Option #3) Forgo the OTA entirely and flash the KTU84P Factory Image in fastboot. https://developers.google.com/android/nexus/images#occam
If you need help with this follow efrant's guide
Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.
Q&A Section:
Q #1: I'm seeing a kernel related status 7 error when trying to apply the OTA
A: Flash the system image along with the boot image. Some kernels (like franco for example) change a file or two in /system. So easiest way would be to re-flash the system. -Thanks efrant
Q #2: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?
A: Flash the custom recovery of your choice in fastboot, then flash the SU.zip in recovery linked in Section B4.
Q #3: I've tried everything but I'm still getting status 7 errors.
A: Unfortunately you may have to start from scratch. Follow Section C1.
Thanks to these members for adding additional info and helping add things I forgot.
TheManii
zim2dive
davdigs
eskeyy
daverup
xaueious
Spaceman860
efrant
Updated: 4/17/14
Re: [INFO] Nexus OTA Help-Desk
I'm currently on stock and rooted. but I deleted a couple of system apps like Google wallet, play books and other 2. will I get the OTA update?
and oh, I did flash the MOD for Battery Circle and Rotation Lock in the notification bar.
Sent from my Nexus 4 using xda premium
Re: [INFO] Nexus OTA Help-Desk
ijustzeke said:
I'm currently on stock and rooted. but I deleted a couple of system apps like Google wallet, play books and other 2. will I get the OTA update?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
No you'll have to add those apps back to /system/app/
Sent from my Nexus 7 using Tapatalk HD
ijustzeke said:
. but I deleted a couple of system apps
Click to expand...
Click to collapse
El Daddy said:
No you'll have to add those apps back to /system/app/
Click to expand...
Click to collapse
You should more strongly point out that scenario 2 is "any modifications/deletions"
Since the update script does not care about added files, only modified and removed (which isn't much different)
The update script technically has a list of files it checks, but it's long enough that it's simply easier to say the entire rom must be completely unmodified.
Rooting depends on the method: some root by modifying the ramdisk, and that is a modification.
Some simply add su to xbin, and it's possible to be rooted and not modified if it only adds files.
I am using the Brainmaster's Stock ROM (which is not stock really), so I guess I must follow Section C.
Is there any advice on how to not loose all the configurations, the home screen, widgets, etc? I love testing ROMs, but I hate that each time I have to download all my apps again (including some couple of Gb on games), configure them, put the widgets with the proper configuration, etc.
JanusDC said:
I am using the Brainmaster's Stock ROM (which is not stock really), so I guess I must follow Section C.
Is there any advice on how to not loose all the configurations, the home screen, widgets, etc? I love testing ROMs, but I hate that each time I have to download all my apps again (including some couple of Gb on games), configure them, put the widgets with the proper configuration, etc.
Click to expand...
Click to collapse
First thing to do when you unbox your new nexus. 1. unlock bootloader. 2. backup stock image - If you didnt backup stock, you have to flash back to stock via fastboot. Guide provided OP
JanusDC said:
I am using the Brainmaster's Stock ROM (which is not stock really), so I guess I must follow Section C.
Is there any advice on how to not loose all the configurations, the home screen, widgets, etc? I love testing ROMs, but I hate that each time I have to download all my apps again (including some couple of Gb on games), configure them, put the widgets with the proper configuration, etc.
Click to expand...
Click to collapse
For the home screen layout with the stock launcher I'm not sure. There might be a few apps out there but, I not sure how well they work. I do know some custom launchers have that ability.
As far as your apps and data there are may backup apps out there. A new one and my favorite is Carbon: https://play.google.com/store/apps/details?id=com.koushikdutta.backup
So if I am on Stock ROM with CWM, and customer kernal, can't I just flash Stock kernal and then flash the OTA through CWM?
I cannot be arsed with doing a full reflash.
I'm rooted on a stock kernel + stock bootloader.
Made a few mods to my system files so we'll see.
Re: [INFO] Nexus OTA Help-Desk
rickykemp said:
So if I am on Stock ROM with CWM, and customer kernal, can't I just flash Stock kernal and then flash the OTA through CWM?
I cannot be arsed with doing a full reflash.
Click to expand...
Click to collapse
Yes you can. Section C,a.
Sent from my Nexus 4 using xda premium
Great post, this is what I will be looking for!
I think it would be helpful to add a link to the SU.zip (to regain root) in the OP, I think it's http://download.chainfire.eu/282/SuperSU/ but please confirm.
Thanks!
Re: [INFO] Nexus OTA Help-Desk
davidgs said:
Great post, this is what I will be looking for!
I think it would be helpful to add a link to the SU.zip (to regain root) in the OP, I think it's http://download.chainfire.eu/282/SuperSU/ but please confirm.
Thanks!
Click to expand...
Click to collapse
Thanks! I'll add it to the op when I get back to a computer.
Sent from my Nexus 4 using xda premium
Might want to warn folks that they'll need the latest SDK for the ADB security
http://forum.xda-developers.com/showthread.php?t=2144709
davidgs said:
Great post, this is what I will be looking for!
I think it would be helpful to add a link to the SU.zip (to regain root) in the OP, I think it's http://download.chainfire.eu/282/SuperSU/ but please confirm.
Thanks!
Click to expand...
Click to collapse
El Daddy said:
Thanks! I'll add it to the op when I get back to a computer.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think the XDA link would be most up to date:
http://forum.xda-developers.com/showthread.php?t=1538053
There is a CWM / TWRP installable ZIP there.
Re: [INFO] Nexus OTA Help-Desk
zim2dive said:
Might want to warn folks that they'll need the latest SDK for the ADB security
http://forum.xda-developers.com/showthread.php?t=2144709
Click to expand...
Click to collapse
Thanks. I don't think they'll need it going from 4.2.1 to 4.2.2. At least I didn't with my nexus 7. But definitely in the future. I'll add links to the op later today.
Sent from my Nexus 4 using xda premium
El Daddy said:
Yes you can. Section C,a.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is mine!
Απ: [INFO] Nexus OTA Help-Desk
I am with stock 4.2.1 rooted with unlock bootloader and cwm recovery 6.0.23. Is there any chance to install the update 4.2.2 normally through OTA?
Send from my Awesome Gnexus using Tapatalk 2
xxSAKISxx said:
I am with stock 4.2.1 rooted with unlock bootloader and cwm recovery 6.0.23. Is there any chance to install the update 4.2.2 normally through OTA?
Send from my Awesome Gnexus using Tapatalk 2
Click to expand...
Click to collapse
Flash stock recovery then you can instal update when you receive notifcation about OTA (if you dont have any other modifications only cwm)
Btw if somebody uses stock rom with modifications then is enough to flash boot, recovery and system via fastboot after that rom is completly stock and all personal settings, apps and data are not wiped
Re: [INFO] Nexus OTA Help-Desk
eskeyy said:
Flash stock recovery then you can instal update when you receive notifcation about OTA (if you dont have any other modifications only cwm)
Btw if somebody uses stock rom with modifications then is enough to flash boot, recovery and system via fastboot after that rom is completly stock and all personal settings, apps and data are not wiped
Click to expand...
Click to collapse
Where can I get stock recovery IMG!? Thanks
Sent from my Nexus 4 using xda app-developers app
Re: [INFO] Nexus OTA Help-Desk
danfalcas said:
Where can I get stock recovery IMG!? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I uploaded it last night. I'll add the link to the op in a bit. For now, here's the link http://d-h.st/Bbp
Sent from my Nexus 4 using xda premium
Just share the ROM using now, for those who want to keep BL locked.
Please note that this is a Japan version, for WiFi models.
STOCK 10.1.C.0.370 JP
Recovery Pre-installed
Pre-Rooted
Reboot issue Fixed (Credit goes to @Carceri, Modified a bit to make it work. Another solution by @[NUT] :[Locked Bootloader] The definitive root Remount-Reboot fix!)
Init.d support
Nothing more～
Download Here：
Part1 Part2
Installation:
1. Backup everything in case of any bad luck.
2a. Flash 370 FTF without system and data.
2b.1. Or update to 370 official with SONY Update Service for more insurance (This will WIPE EVERYTHING if 370 already installed/it failed to update, Confirm your Backup 65535 times before start).
2b.2. Unplug and Flash 344 FTF, system only.
3. Get root with Bin4ry's tool.
4. Install Recovery.
5. Flash the zip.
does bootloader need to be unlocked for this?
shaun.s said:
does bootloader need to be unlocked for this?
Click to expand...
Click to collapse
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Fishmanzero said:
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Click to expand...
Click to collapse
you rock!
thanks downloading now
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
Fishmanzero said:
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Click to expand...
Click to collapse
is this for 16GB version?
I have 32GB LTE
shaun.s said:
you rock!
thanks downloading now
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
is this for 16GB version?
I have 32GB LTE
Click to expand...
Click to collapse
Internal storage size doesn't matter in this case I think, but 10.1.C.0.370 is for WiFi model and LTE model's firmwares use a different build, like 10.1.E.0.265.
It is not recommended to flash a different zip...
If you are already up to date and only want root, reboot fix or recovery, try @DooMLoRD's new root tool and the fix mentioned in the #1.
Fishmanzero said:
Internal storage size doesn't matter in this case I think, but 10.1.C.0.370 is for WiFi model and LTE model's firmwares use a different build, like 10.1.E.0.265.
It is not recommended to flash a different zip...
If you are already up to date and only want root, reboot fix or recovery, try @DooMLoRD's new root tool and the fix mentioned in the #1.
Click to expand...
Click to collapse
Hi Fisherman, your links are down, could you please check it? or maybe create a mirror on another server?
By the way, is this a FTF file? or flasheable ZIP? i guess is a FTF because i read on DoomLord thread that in order to flash recovery you need to have the bootloader unlocked.
Thank you.
juanyunis said:
Hi Fisherman, your links are down, could you please check it? or maybe create a mirror on another server?
By the way, is this a FTF file? or flasheable ZIP? i guess is a FTF because i read on DoomLord thread that in order to flash recovery you need to have the bootloader unlocked.
Thank you.
Click to expand...
Click to collapse
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Fishmanzero said:
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Click to expand...
Click to collapse
Oh nice. I guess he stated that before because the system rw reboot issue, so the best way to achieve that was using fastboot. Thank you man!
I don't understand some points in the installation instructions.
1) Why must the 370 FTF / update be flashed first? When anyway after that 344 must be flashed???
2) When the bootloader is unlocked, I can install / run CWM directly and flash this ROM here directly, or can't I??
hasenbein1966 said:
I don't understand some points in the installation instructions.
1) Why must the 370 FTF / update be flashed first? When anyway after that 344 must be flashed???
2) When the bootloader is unlocked, I can install / run CWM directly and flash this ROM here directly, or can't I??
Click to expand...
Click to collapse
Well in the instructions he said:
1. the .370 without flashing system.sin and userdata.sin, that means, only stuff not related to the system partition and well, you can keep your data because userdata.sin is not selected.
2. the .344 only system.sin because this is the one with most opportunities to root using bin4ry tool.
3. then in the files he provides, you will have the 370 system with all the fixes but that one is a CWM flash file, so you will need to install the recovery and then flash this file. See the attachment he posted here.
If your bootloader is unlocked you can use fastboot to flash the recovery. Also you can skip flashing those FTF files, and just flash the CWM file. But i believe that someone confirmed that you won't need this because if your bootloader is unlocked you can install root and remount /system without any issues.
---------- Post added at 06:58 AM ---------- Previous post was at 06:52 AM ----------
Fishmanzero said:
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Click to expand...
Click to collapse
I had to adapt the script because i'm running Mac OSX 10.8.4. but this worked perfect, i've CWM recovery with a locked bootloader, only problem is that it can mount my microsd card, maybe is missing the exfat module.
Thank you!
juanyunis said:
I had to adapt the script because i'm running Mac OSX 10.8.4. but this worked perfect, i've CWM recovery with a locked bootloader, only problem is that it can mount my microsd card, maybe is missing the exfat module.
Thank you!
Click to expand...
Click to collapse
Yes this CWMR does not have exFAT support, and this ROM includes the same one.
Fishmanzero said:
Yes this CWMR does not have exFAT support, and this ROM includes the same one.
Click to expand...
Click to collapse
So great yeah :laugh:
this means i can root+get recovery on .370 with locked bootloader if i get i right ?
i have a sgp 311 wifi on official 370 installed - wil this work then ??
Greetz
-----------------------
If anyone need a mirror let me know !!
-----------------------
How do i flash in flash tool it dosent reconigze image when put in firmwares?????
spoonymoon said:
So great yeah :laugh:
this means i can root+get recovery on .370 with locked bootloader if i get i right ?
i have a sgp 311 wifi on official 370 installed - wil this work then ??
Greetz
-----------------------
If anyone need a mirror let me know !!
-----------------------
Click to expand...
Click to collapse
Since you have already updated firmware, no need to install this if the new rootkits work, try them.
Find DooMLoRD's above.
Translated Japanese toolkit from 2ch in attachment.
If they don't apply to our Tablet Z, you will have to flash 344 FTF (system only) then do the rest.
Fishmanzero said:
Since you have already updated firmware, no need to install this if the new rootkits work, try them.
Find DooMLoRD's above.
Translated Japanese toolkit from 2ch in attachment.
If they don't apply to our Tablet Z, you will have to flash 344 FTF (system only) then do the rest.
Click to expand...
Click to collapse
thanx
your attched files does say it installs root ok - but when checked after reboot - no root ?
but why not flash 370. pre rooted insted? and not least HOW do i flash it? its not a ftf file
spoonymoon said:
thanx
your attched files does say it installs root ok - but when checked after reboot - no root ?
but why not flash 370. pre rooted insted? and not least HOW do i flash it? its not a ftf file
Click to expand...
Click to collapse
You can not flash a CWM zip without recovery, and it need root to install one, and no root for 370 now
So it's necessary to download a 344 FTF, flash the system part only, and use the old working toolkit to root it.
It may be very likely to fail on different devices because the rootkit uses a kernel exploit, the address for which to run just usually varies from kernel to kernel.
Wait for our great devs to figure out the working address will be the most painless.
Or do the operations in the OP, and of course install a custom kernel after unlocking BL if you don't mind doing so, is way faster atm.
Here's an older rootkit also from 2ch. Try it if interested.
Fishmanzero said:
You can not flash a CWM zip without recovery, and it need root to install one, and no root for 370 now
So it's necessary to download a 344 FTF, flash the system part only, and use the old working toolkit to root it.
It may be very likely to fail on different devices because the rootkit uses a kernel exploit, the address for which to run just usually varies from kernel to kernel.
Wait for our great devs to figure out the working address will be the most painless.
Or do the operations in the OP, and of course install a custom kernel after unlocking BL if you don't mind doing so, is way faster atm.
Here's an older rootkit also from 2ch. Try it if interested.
Click to expand...
Click to collapse
Thanx a lot
tried and same result, says its rooted and its not - but you´re right better wait a bit for better solution , that dosent involve any risk !!
(wife and kid is going to ´kill´me if it f... up soo )
spoonymoon said:
Thanx a lot
tried and same result, says its rooted and its not - but you´re right better wait a bit for better solution , that dosent involve any risk !!
(wife and kid is going to ´kill´me if it f... up soo )
Click to expand...
Click to collapse
And yes, Japanese user got it work:laugh:
370
Fishmanzero said:
And yes, Japanese user got it work:laugh:
370
Click to expand...
Click to collapse
Woooow it f..... works i´ve got root .....wiiiiii :laugh::good::good::good::good::good::good::good::good:
i ow you big time
thanx thanx
is their a possibility for SGP321 with 10.1.1.A.1.307 too?
Fishmanzero said:
Reboot issue Fixed (Credit goes to @Carceri, Modified a bit to make it work. New solution also from him: [Locked Bootloader] The definitive root Remount-Reboot fix!)
Click to expand...
Click to collapse
Heh, you are pointing to a thread by me but refer to a fix done by Carceri ... who's are you using exactly?
Is there any way to achieve double tap to wake on my Nexus 6 and still be able to receive OTA updates?
Probably not, as you have to make a change to a system file in order to achieve it.
I so want double tap, but I don't want to have to give up OTA.
If you're expecting lg style dttw, you're going to be dissapointed
Sent from my Nexus 6 using XDA Free mobile app
No expectations per se, just looking to have access to the original functionality that was pulled, and still have OTA.
Karine said:
I so want double tap, but I don't want to have to give up OTA.
Click to expand...
Click to collapse
Life lesson. You can't always have everything you want. You have to choose based on personal preference.
I'd rather have the ability to use DT2W multiple times a day, than the convenience of an OTA that may happen once every few months.
PaisanNYC said:
Life lesson. You can't always have everything you want. You have to choose based on personal preference.
I'd rather have the ability to use DT2W multiple times a day, than the convenience of an OTA that may happen once every few months.
Click to expand...
Click to collapse
If I go with DT2W is there another way for me to get what I would have otherwise received via OTA?
Karine said:
If I go with DT2W is there another way for me to get what I would have otherwise received via OTA?
Click to expand...
Click to collapse
Absolutely. Just flash the stock rom. It always gets posted here when the OTA is released:
https://developers.google.com/android/nexus/images
PaisanNYC said:
Absolutely. Just flash the stock rom. It always gets posted here when the OTA is released:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Great link; thanks! Do you yourself follow the instructions on the link you provided to flash? And, how have you achieved DT2W?
I believe dt2w is enabled at the kernel level. When an ota comes out i just fastboot flash the bootloader, system, and radio and its like you got the OTA just faster
mymusicathome said:
I believe dt2w is enabled at the kernel level. When an ota comes out i just fastboot flash the bootloader, system, and radio and its like you got the OTA just faster
Click to expand...
Click to collapse
It can be kernel or ROM. Depends which implementation.
mymusicathome said:
I believe dt2w is enabled at the kernel level. When an ota comes out i just fastboot flash the bootloader, system, and radio and its like you got the OTA just faster
Click to expand...
Click to collapse
I'm afraid I don't understand.
Karine said:
I'm afraid I don't understand.
Click to expand...
Click to collapse
The link from Google will wipe your data. Its a full ROM flash.
Actually, you don't need to flash all that. You can extract the full ROM and using fastboot, only flash the system.img (ROM) and boot.img (kernel) to update.
Read about fastboot here. http://forum.xda-developers.com/showthread.php?t=3006500
rootSU said:
It can be kernel or ROM. Depends which implementation.
Click to expand...
Click to collapse
I'm afraid I don't understand.
Karine said:
I'm afraid I don't understand.
Click to expand...
Click to collapse
Its not relevant. We were talking about double tap 2 wake..
rootSU said:
The link from Google will wipe your data. Its a full ROM flash.
Actually, you don't need to flash all that. You can extract the full ROM and using fastboot, only flash the system.img (ROM) and boot.img (kernel) to update.
Read about fastboot here. http://forum.xda-developers.com/showthread.php?t=3006500
Click to expand...
Click to collapse
rootSU, many thanks for all of the thoughtful responses and the great links. You've given me a level of comfort that rooting to get DT2W is the right choice for me. In the All-In-One link inside of the Fastboot link you provided, the instructions state that I can stop at a certain point if I'm not looking to install a custom rom, etc. I'm not looking to install a custom rom; just looking to root to ultimately get DT2W. Am I correct that I don't need to install a custom rom to get DT2W?
Do you personally use DT2W, and if so, how did you achieve it after rooting?
Is there a link or set of instructions available for the rom extraction method you referenced for manually updating my device in lieu of an OTA?
Karine said:
rootSU, many thanks for all of the thoughtful responses and the great links. You've given me a level of comfort that rooting to get DT2W is the right choice for me. In the All-In-One link inside of the Fastboot link you provided, the instructions state that I can stop at a certain point if I'm not looking to install a custom rom, etc. I'm not looking to install a custom rom; just looking to root to ultimately get DT2W. Am I correct that I don't need to install a custom rom to get DT2W?
Do you personally use DT2W, and if so, how did you achieve it after rooting?
Is there a link or set of instructions available for the rom extraction method you referenced for manually updating my device in lieu of an OTA?
Click to expand...
Click to collapse
No problem @Karine.
I'll outline the steps a little.
- unlock bootloader (this will wipe device]
- fastboot flash recovery (TWRP]
- put latest SuperSU zip on your sdcard memory
- flash zip via recovery
To get dt2wake, there are 2 ways.
1) use Google implementation.
Google left this out however someone has managed to recompile the .so file. Many custom ROMs include this. You could also replace the file yourself in stock ROM BUT in my opinion its not as good as method 2 below
2) use custom kernel with dt2wake. This is better as it works more often. Method 1 sometimes just doesn't work.
Personally I use method 2 with elementalx kernel. Like root, it is a zip that you flash from recovery.
Now assuming you are going with method 2, the way to update ROM is below...
- Download full factory image from Google
- extract the zip (twice) to find the system.img
- fastboot flash the system.img only.
- flash the SuperSU zip in recovery to re-root
This should be everything you need.
rootSU said:
The link from Google will wipe your data. Its a full ROM flash.
Actually, you don't need to flash all that. You can extract the full ROM and using fastboot, only flash the system.img (ROM) and boot.img (kernel) to update.
Read about fastboot here. http://forum.xda-developers.com/showthread.php?t=3006500
Click to expand...
Click to collapse
rootSU said:
No problem @Karine.
I'll outline the steps a little.
- unlock bootloader (this will wipe device]
- fastboot flash recovery (TWRP]
- put latest SuperSU zip on your sdcard memory
- flash zip via recovery
To get dt2wake, there are 2 ways.
1) use Google implementation.
Google left this out however someone has managed to recompile the .so file. Many custom ROMs include this. You could also replace the file yourself in stock ROM BUT in my opinion its not as good as method 2 below
2) use custom kernel with dt2wake. This is better as it works more often. Method 1 sometimes just doesn't work.
Personally I use method 2 with elementalx kernel. Like root, it is a zip that you flash from recovery.
Now assuming you are going with method 2, the way to update ROM is below...
- Download full factory image from Google
- extract the zip (twice) to find the system.img
- fastboot flash the system.img only.
- flash the SuperSU zip in recovery to re-root
This should be everything you need.
Click to expand...
Click to collapse
The Nexus 6 doesn't have an external sdcard slot, so when referencing sdcard the reference is to the internal/built-in sdcard, correct? I recall that the references are used somewhat interchangeably, and don't want to make any assumptions.
Will the elementalx custom kernel change my stock Android experience in any way? And, where do I find that kernel?
Would updating the rom manually in lieu of an OTA in the manner you described wipe all of my data?
Karine said:
The Nexus 6 doesn't have an external sdcard slot, so when referencing sdcard the reference is to the internal/built-in sdcard, correct? I recall that the references are used somewhat interchangeably, and don't want to make any assumptions.
Will the elementalx custom kernel change my stock Android experience in any way? And, where do I find that kernel?
Would updating the rom manually in lieu of an OTA in the manner you described wipe all of my data?
Click to expand...
Click to collapse
1. All android phones have /sdcard be it a removable media card or a partition on the internal memory. Regardless of which one the device has, when We say sdcard - we always mean the same thing.
2. It will be quicker. Its in the original development section
3. No.
I may have just found the perfect solution for me, that gives me the ability to turn on the screen without having to press the power button, and without having to root and give up OTA... Wakeup Touch... https://play.google.com/store/apps/details?id=com.wolandsoft.wtlf
Just the question from the title. I just bought one. I can live with ads but not anyone's favorite. But before I start using it, can I simply reinstall it with stock firmware? If so is there some tutorial I can follow?
jacobdu215 said:
Just the question from the title. I just bought one. I can live with ads but not anyone's favorite. But before I start using it, can I simply reinstall it with stock firmware? If so is there some tutorial I can follow?
Click to expand...
Click to collapse
yes you can . I have done it, but have not made an official tutorial.
mrmazak said:
yes you can . I have done it, but have not made an official tutorial.
Click to expand...
Click to collapse
Can you just generally explain the steps? Ill try and do it on my own.
jacobdu215 said:
Can you just generally explain the steps? Ill try and do it on my own.
Click to expand...
Click to collapse
To return to fully stock , locked boot loader, stock system, recovery, out of box condition (V6.1)
You must be on old preloader so you can use sp flash tool to flash these partitons. You probably could put the images into a recovery zip also,
But that is not the way I did it so I dont have the info on it.
1. Verify you have access to flash tool.
if you do not have access will need to roll back with these instructions
http://forum.xda-developers.com/r1-hd/how-to/r1hd-update-6-6-bootloader-roll-t3491096
2. once you have spft access, download my o.o.b. package. from same link as above, click on the "click to show content" button.
3. unpack into one folder. Load scatter file into flsh tool. (DO NOT USE FORMAT DOWNLOAD ONLY)
I dont know of any reason to go this drastic of a restore but here you go.