Related
Full Rom link
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip (89.9 MB)
Link for GRH78C
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
Link for GRH78 only
http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip
As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389
I figured I'd get this unburied for everyone interested (which is likely a lot of folks).
If you're stock and unrooted - download this and place it on the root of the SD card - named update.zip. Boot into recovery. Hold Pwr and then Vol up and then choose to apply update.zip.
just got it on mine too.
does anyone know if this build is still rootable in the same method of 2.3.2? just curious
krohnjw said:
http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip
As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389
I figured I'd get this unburied for everyone interested (which is likely a lot of folks).
Also Mirrored if the download breaks for some reason:
http://hotfile.com/dl/107285073/f39f21c/e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip.html
Click to expand...
Click to collapse
WOW - didn't think I'd see this so soon - thanks for digging it out man.
Guess I'll be the guinea pig
jaker.the.skater said:
just got it on mine too.
does anyone know if this build is still rootable in the same method of 2.3.2? just curious
Click to expand...
Click to collapse
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.
If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.
With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.
Download the SU binary zip and place that on the SD card.
The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)
When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
ok my bootloader is unlocked. so basically i just do like before where you rename the install recovery.sh file so that cwm sticks? if so then cool beans.
jaker.the.skater said:
ok my bootloader is unlocked. so basically i just do like before where you rename the install recovery.sh file so that cwm sticks? if so then cool beans.
Click to expand...
Click to collapse
Yes sir. 10 chars
very cool.
Can i dowload this on a stock Ns
Sent from my Nexus S using XDA App
doesnt work for me - failed at file_getprop("/system/build.prop"
this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3
Im on 2.3.2 .......
any idea's???
moon-unit said:
doesnt work for me - failed at file_getprop("/system/build.prop"
this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3
Im on 2.3.2 .......
any idea's???
Click to expand...
Click to collapse
same here..... hmmm
krohnjw said:
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.
If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.
With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.
Download the SU binary zip and place that on the SD card.
The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)
When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
Click to expand...
Click to collapse
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
Same here, update fails. I am on 2.3.2 and Stock non-rooted.
hutzdani said:
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
Click to expand...
Click to collapse
Yes - if you're unlocked then you'll only need to remove the isntall-recovery.sh and reflash CWM/su and you're golden.
It's a bit trickier for users who rooted without unlocking the boot loader and do not want to unlock at this point.
Looks like this is for GRH78, NOT GRH78C- we'll have to wait for that package still.
Update is for build number GRH78 only :-(
Wow!
Thx)
SupaDupaFly24 said:
Update is for build number GRH78 only :-(
Click to expand...
Click to collapse
Yeah, that is, only for 2.3.1 until now.
We'll have to wait for the GRH78C (2.3.2) build update.
this really pisses me off. i was on 2.3.2 and i got the ota but when i tried to install it from cwm it didn't work. so then when i saw this one i gave up on the one i had and now its gone. turns out i should've just did a logcat and got the one for 2.3.2.
oh well it'll be up soon
Sweet. I was trying to get to stock ROM and i was on 2.3.1
2.3.3 Flashed just perfectly
I did a nandroid backup to 2.3.1 and then installed the update and it worked fine.
Please, Could you make step by step guide, how to apply update from that link on stock, nonroot device. Thanks.
Sent from my Nexus S using XDA App
Hey everybody! I went to stock from CyanogenMod Nightlyes, and flashed stock 2.3.2 nandroid.
Then I flashed the 2.3.3, it works just fine! But my bootloader is still unlocked!
First thing that i thank was just to install Superuser, but it doesen't work.
I connected it to Pc in fastboot mod, and ran install-superboot-windows.bat (one click root)
But now, it just stuck in Google logo, and I don't know what to do next... I tryed to pull out the battery, nothing...
Update: just reflashed recovery via fastboot flash recovery recovery.img, and got the CWM. Now restoring to 2.3.2.
I think that we can just flash CWM after update, and then install superuser. I'll try and will ask you about any changes.
Update 2:: So, it ran just fine, first installed 2.3.2, then updated it to 2.3.3, and then flashed CWM. It boots up just fine, but in CWM I tried to install superuser.zip, it says: invalid to install
maybe reinstall your backup from CWM?
also the one click root you need to be in a rom and using adb
I did the same thing and ended up in the same situation...ive fixed like this...downloaded odin got back to stock 2.3.1 then downloaded the update,flashed it through stock recovery then flashed recovery.img....flashed su and everything is back on normal now
Hope it helps
Sent from my Nexus S using XDA App
If you unlock already, it is very easy to root again
1. fastboot boot recovery.img
2. flash su.zip
3. reboot
all done
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
2.3.3 root question
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
This does not belong in development.
Sent from my MattedBlues CM7 Google Nexus S!
I have a question is there a way to make the phone as if it was never messed about with, just incase it was ever needed to get repaired under the warrenty
Trinitronik said:
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
Click to expand...
Click to collapse
mount /system inside of clockwork then try.
Sent from my Nexus S using XDA App
Jnowak1981 said:
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
Click to expand...
Click to collapse
Try this..
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>Do not reboot ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
4) Reboot..
Click to expand...
Click to collapse
I am just posting the concept..you need to find out the details steps
Ill keep 2.3.2 until than
Sent from my Nexus S using XDA App
Follow the link, i managed to retain root after 2.3.3 update.
http://forum.xda-developers.com/showpost.php?p=11626567&postcount=70
Code:
I manage to keep the root for 2.3.3 with the flashing sequence listed below.
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>After applying update DO NOT REBOOT ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
=> This step is to reapply Superuser.apk permission setting
4) Reboot..
I am highlighting the concept, for details inter steps..please refer to the first post on the link.
2.3.3 root
is there a method to root 2.3.3 or is it to early i tried allgamer way but it failed
Or you can simply restore 2.3.3 its in the development forum. It had root already on it
Sent from my Nexus S using XDA App
There is a 2.3.3 rooted nandroid backup in development section.
Sent from my Nexus S using XDA App
well tryind to do from 2.3.3
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
kaimyn said:
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
Click to expand...
Click to collapse
If I were currently locked bootloader, I would run a full titanium backup of apps+data, and copy over your entire sdcard contents to your pc, along with the titanium backups (remember, the oem unlock wipes the sdcard also, not just internal space).
Then unlock the bootloader. Easiest way to deal with custom recovery in the future.
There are steps in the 2.3.3 link thread here describing how you can update and get root back even with the locked bootloader; which might be less of a hassle then going through a wipe.
squattingb said:
I tried to do this in clockwork but the installation kept failing, I was getting some messages about "assert failed", wasn't quite clear so I couldn't really make out what the problem was, does anyone have any insights into this? I downloaded the update from http://forum.xda-developers.com/showthread.php?p=11566707 for Nexus S.
Click to expand...
Click to collapse
I'm having the same issue. Any idea how to fix this?
Just load the Nandroid as charlieb620 said. If your already on 2.3.3 you won't lose nowt, just backup your data first.
Hey all,
So I've managed to upgrade to FW 4, Doom's latest kernel, & Doom's autoroot also. Thanks Doom
I still can't seem to get root working. When I go in to Superuser to try to update, I get the following:
su-2.3.1-bin-signed.zip
reboot into recovery and flash it
I can't reboot into recovery (not sw cuz it's not rooted, hitting back key when powering on ignores me).
Anyone else know what I could try?
If you flashed to 4.0 first, then autoroot, then use kernel you will keep root and data.
Sent from my Xperia PLAY R800i using XDA App
Cat_On_Droid said:
If you flashed to 4.0 first, then autoroot, then use kernel you will keep root and data.
Sent from my Xperia PLAY R800i using XDA App
Click to expand...
Click to collapse
Logseman told me to flash 4, kernel, then autoroot. Is this the wrong order? Have I lost my chance to root until Doom releases a new kernel?
I kept my data ok, just lost root... which is pants cuz the bloatware needs wiped before my sanity does :-/
Rixter757 said:
Logseman told me to flash 4, kernel, then autoroot. Is this the wrong order? Have I lost my chance to root until Doom releases a new kernel?
I kept my data ok, just lost root... which is pants cuz the bloatware needs wiped before my sanity does :-/
Click to expand...
Click to collapse
If you have superuser you are rooted, if your using doomlords kernel there is no need to auto root as it comes with root. you dont need to update the app just the binaries, but you have the latest version with doomlords kernel so an update is not needed
worst comes to the worst, connect your device to flashtool and hit root
AndroHero said:
If you have superuser you are rooted, if your using doomlords kernel there is no need to auto root as it comes with root. you dont need to update the app just the binaries, but you have the latest version with doomlords kernel so an update is not needed
worst comes to the worst, connect your device to flashtool and hit root
Click to expand...
Click to collapse
Thanks for taking the time to reply.
I agree, def still rooted because i can delete sys apps through root explorer. I can't get Titanium to run - it reports I'm not rooted. Their "problems" link me to update Superuser but it compains re my 1st post that it can't update.
I uninstalled su, new install is 2.3.6.3 but it still refuses the update. Why I can't get into safe mode by hitting the back key on boot is strange too.
Don't know how to run Root from Flashtool, it's greyed out & sounds like I might lose data?
More idea's welcome
Rixter757 said:
Thanks for taking the time to reply.
I agree, def still rooted because i can delete sys apps through root explorer. I can't get Titanium to run - it reports I'm not rooted. Their "problems" link me to update Superuser but it compains re my 1st post that it can't update.
I uninstalled su, new install is 2.3.6.3 but it still refuses the update. Why I can't get into safe mode by hitting the back key on boot is strange too.
Don't know how to run Root from Flashtool, it's greyed out & sounds like I might lose data?
More idea's welcome
Click to expand...
Click to collapse
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
AndroHero said:
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
Click to expand...
Click to collapse
Works like a charm FW 4.0.A.2.368_World successfully rooted. Thank you and all those dev's & guides that made it possible.
AndroHero said:
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
Click to expand...
Click to collapse
You Sir, are an absolute legend
Worked perfectly, I'm good to go. Thanks very much for your patience.
Thanks also to all the Devs for their brilliant work
azuell said:
Works like a charm FW 4.0.A.2.368_World successfully rooted. Thank you and all those dev's & guides that made it possible.
Click to expand...
Click to collapse
Rixter757 said:
You Sir, are an absolute legend
Worked perfectly, I'm good to go. Thanks very much for your patience.
Thanks also to all the Devs for their brilliant work
Click to expand...
Click to collapse
WooHooo glad your sorted
This METHOD was developed ONLY for an UNLOCKED Motorola Droid Razr Maxx HD XT926m phone that is already updated to the last version of KitKat 4.4.2 (System version "183.46.15.XT926.Verizon.en.US").
IF YOU HAVE AN LOCKED BOOTLOADER AND TRY THIS METHOD IT WILL BE ONLY YOUR RESPONSABILITY IF YOU DAMAGE YOUR PHONE !!!
My Motorola XT926m had an UNLOCKED BOOTLOADER (ICS 4.0.4) and I flashed via RSD Lite the last stock firmware, "183.46.15"... After that, I was, of course, unhappy, because I read on different forums that this firmware version didn't support root... I tried to download the Hydrogen Peroxide xt926 application that others users recommended here on XDA forum, without success.
But now, after I applied this method, my phone is again rooted... Enjoy the steps, but be carefull, it was developed for XT926 phones with UNLOCKED BOOTLOADER!
1. Download the files "VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml" and "VZW_XT926_4.4.2-KDA20.62-15.1_CFC_1FF.xml" from the Motorola firmware site: "motofirmware.com/files/file/"...
2. Unpack the files...
3. Substitute/replace the "gpt", "tz" files (FROM the folder with "15.1" version TO the folder with "10.1" version)... You should replace all the files that "RSD Lite" will tell you that don't fit when you try to flash the new stock firmware. You will obtain a MODIFIED version of "183.46.10" stock KitKAt 4.4.2 firmware!!!
4. Flash this MODIFIED "10.1" firmware with "RSD Lite v6.1.5 Multi-Flash" (without using Rsd Script Generator.jar), but don't forget to remove the first two 'getvar' lines in the xml file.
5. Download and install the "Towel Root.apk" and root the phone...
6. Now your phone should be ROOTED.
What to do NEXT:
7.Download from the Play Store and install "Superuser.apk" made by ClockWordMode and after reboot the application will ask you to update SU binary. In my case, the SU binary didn't support an online update and I installed the "Superuser.zip" file downloaded from the ClockWorkMode site, via recovery method, in order to gain this update (you can do this as well, if you already have a TWRP or CWM recovery installed on your phone). With the other version of superuser, like "SuperSU.apk" or "Superuser.apk" ("eu.chainfire.supersu-2.apk", the last version, 5.6mb, for example) you will need to follow the same steps...
8. Using "Total Commander.apk", you can go to "File System root"/"Etc"/"installrecovery.sh", and finally rename this last file... Or you can use "ES3 File Explorer.apk" in order to rename the same "installrecovery.sh" file in "Device"/"Etc" folder (choose, for example, the name "installrecovery.shbak")...
9. Flash with "Flashify.apk" (downloaded form PLay Store) a new "recovery img.": "TWRP.img" (2.8.3.0) or "CWM.img" (6.0.4.8) for KitKat... You can find them on "rootjunkysdl.com/?device=Droid%20Razr%20HD&folder=Firmware"...
10. If you flashed "TWPR recovery.img" you will need to install "Stericson.busybox-1.apk" (from Play Store...), because TWRP works with this busy box... (You could install "TWRP.apk" as well, but you must be careful, because you will need to be able to boot into Recovery mode directly from your phone (with the combination key), not from this app... Many times, the phone is able to boot into recovery mode from TWRP application, but not from the bootloader... That's why it is better to uninstall TWRP application if you have this problem). If you flashed a "CWM.img" you can install "RomManager.apk".
11.Now it is the time to backup your system to SD card!
That's it. My phone was unlocked, and I didn't have any issue following all this steps... If you're locked don't try it.
But.. If you're locked you could instead use an application named 'Safestrap' for some purposes (read more here on XDA forum please), because is destinated for the phones with locked bootloader...
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
jackeagle said:
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
Click to expand...
Click to collapse
THANKS!
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
RikRong said:
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
Click to expand...
Click to collapse
Thank you, I wasn't able to find another downgrade method, could you give me the link, please?
http://forum.xda-developers.com/showthread.php?t=2789743
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
joel_sinbad said:
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
Click to expand...
Click to collapse
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
RikRong said:
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
Click to expand...
Click to collapse
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
joel_sinbad said:
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
Click to expand...
Click to collapse
This method is for an XT926 with UNLOCKED BOOTLOADER, with the last 183.46.15 update and the root access lost. I only described the steps that I already done with my phone. My Maxx HD is working and has root access again... I flashed custom recovery too (TWRP 2.8.3.0), I haven't any other problem.
RikRong said:
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
ciprianv. said:
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
Click to expand...
Click to collapse
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
RikRong said:
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
Click to expand...
Click to collapse
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
ciprianv. said:
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
Click to expand...
Click to collapse
Thanks for doing that, I just want to make sure no one messes up their phone.
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.
Why not just download the image and flash it? Plenty of guides on how to do this
lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?
I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine
I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)
Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.
would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance
The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.
efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...
etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.