All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
So far so good on the dirty flash...
What are you looking for? Validation? An argument? Validation through argument? Help me out here.
Wakamatsu said:
What are you looking for? Validation? An argument? Validation through argument? Help me out here.
Click to expand...
Click to collapse
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.
rabaker07 said:
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.
Click to expand...
Click to collapse
Probably some people are like me and prefer doing it the tough way by flashing files manually, instead of using a tool kit.
Wugfreshes toolkit is the best. As you probably know most of the senior pple discuss and ridicule toolkits. I've never had trouble with his.
ADB is hassle if you are new. We all know driver issues. Thats a nightmare b4 you even start. I've since learnt ADB commands but still would only use it as a last stop. It was the toolkit that found and loaded the driver allowing ADB.
To be honest I think, subconsciously, ADB users see them selves as superior to the rest of us.
I'm happy with the years Rug fresh has been there for me. The tool updates automatically.
Sent from a Toolbox rooted and flashed phone
Sent from my Nexus 5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But seriously:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
boot into custom recovery
flash SuperSU/other stuff if desired
isn't that hard.
Driver issues? If you had driver issues your toolkit wouldn't work either. All it does is literally the above—if that is so hard, then maybe you shouldn't modify your device.
Also, ADB ≠ fastboot, they are separate binaries and have a completely different purpose.
@Elluel
Agreed. Just to notice you - Wug's Toolkit recognize ADB or fastboot by itself.
@rabaker07
Was using Wug's Toolkit for a long time. But I don't prefere anymore that app itself take so much space and not necessary files on my PC. So this is much better solution: @rootSU http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
@zerosum0
To be honest. Yes, there are people that feel superior at XDA. But hey, they have reasons.
Problem is, that if you got a bootloop or something like that, its very hard to help people, because they actually don't know what they were doing with their phones before that happened. And if they are also yellers then we got to much threads here like "OMG, please help. :crying:"
I got the drivers on my computer with the kit,after trying everything. That did it in seconds. I do take notice and have written all the commands needed should something go wrong and no toolkit.
A lot of people just are not computer literate.
If push comes to shove I could do it that way but say I want to flash a factory image. The toolkit fetches it, after sorting out the connection between phone and computer. It then flashes it, with a step by step account. Quick and simple. I've never had trouble with it. Toolkits have come along way and I guess there are bad ones out there. Horses for courses. And if someone screws up with a toolkit OR ADB. They should eat humble pie before asking for help.
Sent from my Nexus 5
rabaker07 said:
All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
Click to expand...
Click to collapse
Thank you for sharing your experiences
Glad it worked for you
Thread closed
Related
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Thank you Adam and I suppose I can speak for every Live owner here when I say we really do appreciate it. I can't wait to start tinkering with it and lets hope we can get that WatchFace API soon. I'm dying for a more sophisticated looking face with a more blue and silver brushed metal look to it. Can't find one anywhere. Thanks again Adam. What would we do without u?
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
Oh and if you add any more green text to your display... just go head on and Follow The White Rabbit....
Sweet Adam, you made a lot of progress since Friday
thanks for all this work! Now to start working on port for Gear 1... Haven't messed with this stuff since HD2 days....Ugh.
Chris
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Contacting now.
Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Incase you missed the link on iirc, http://pastebin.com/5rUD9X0t
Annnnnd this is why i ditched Samsung after the SGSII, Im so glad I got the G Watch instead.
Seems to be a Thing now that Samsung is playing hard to beat with factory images and source, Devs should jump on some form of anti Sammy bandwagon because although this is sure a great feat in hacking but for people here who Crack flash and test stuff for devs on their devices this is a pain and slows down evolution.
if sammy continue with his imagine all the ideas they can't steal from the clever devs here at XDA, I say screw them and buy devices from companies who truly keep android open source
Can this be used in Odin?
Krunk_Kracker said:
Can this be used in Odin?
Click to expand...
Click to collapse
No, it is a fastboot image
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Joe0113 said:
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Click to expand...
Click to collapse
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Boot into TWRP
Mount the system
Use the TWRP terminal emulator
rm /system/app/SuperSU.apk
OK so these are the instructions I was given to root. I am currently sitting in TWRP, system was mounted, when I hit reboot system, it told me I wasnt rooted, so I swiped to root...rebooted back to recovery...clicked terminal command which opened up a directory telling me to choose a starting folder :|
this is where im lost.. Also how do I type anything into the terminal commands once I get it open since theres no keyboard lol
Manually removed it using the file manager though its called superuser.apk and it works..Guess im rooted given I can use the rebooter that Adam posted!
KMyers said:
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Click to expand...
Click to collapse
Do we have to do each individual img? I downloaded the file, extracted it and theres 23 img files lol. I have yet to do anything with a .tar file also
Im debating on returning to stock and taking the watch back to wait for the 360,
Instructions on returning to Stock??
Could someone please post some instructions on returning to Stock? I flash the Octa Rom and did not make a back up and then tried returning to stock by flashing the system.img and it would not boot. I have returned to stock with Nexus devices in the past but looking at the stock firmware image files here I'm not getting how this works. PLEASE HELP
AdamOutler said:
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Click to expand...
Click to collapse
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Tomsgt said:
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Click to expand...
Click to collapse
Hiyas Tom..did you really get your Gear?!?!?!
Tower1972 said:
Hiyas Tom..did you really get your Gear?!?!?!
Click to expand...
Click to collapse
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Tomsgt said:
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Click to expand...
Click to collapse
That's the best news I've heard all day!
Tower1972 said:
That's the best news I've heard all day!
Click to expand...
Click to collapse
Samsung Gear Live Tool is up click here and enjoy
I just received the 5.1 update today. I'm on sprint, if that matters. Immediately after the update, I'm getting bombarded with these force closes, immediately returning after hitting either "ok" or "report". It will continue for 3 or 4 minutes, then clear up for a few minutes, then returning when I open an app.
I'm stock, not rooted. Since I'm not rooted, I'm not sure what I can do other than reboot or factory reset? This is the first phone I haven't rooted since I got into android. I'm feeling like I should just root /wipe/flash, but before I do, any other suggestions to quickly clear up the force closes? Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had the same message after updating to 5.1 from 5.0 when trying to use my camera app.
I had rebooted the phone, and the problem went away.
3f62011 said:
I had the same message after updating to 5.1 from 5.0 when trying to use my camera app.
I had rebooted the phone, and the problem went away.
Click to expand...
Click to collapse
Thanks! Unfortunately that hasn't solved it. I booted into the stock recovery and wiped cache. Still no dice. I'll factory reset next I guess!
I guess if you don't want to root I would get some cache cleaning apps
Sent from my Google N6 on VZ
Well I unlocked the bootloader and flashed the most updated stock image using fastboot, manually. All is well now. It took longer to get my computer and drivers working than actually fixing the phone. Now that my bootloader is unlocked, I guess it's time to root. Thanks for the advice.
Do yourself a favor and get the Nexus toolkit you can run commands by hand or let the tool do it for you.
http://www.wugfresh.com/nrt/
WugFresh trolls this forum pretty often too
Sent from my Google N6 on VZ
You don't need root or any special "app" to see what is going on.
You need a LOGCAT.
And to post it here so that somebody who understands it can interpret it.
doitright said:
You don't need root or any special "app" to see what is going on.
You need a LOGCAT.
And to post it here so that somebody who understands it can interpret it.
Click to expand...
Click to collapse
I 100% percent agree with you but the reality is you could reload the phone and reset everything before you get a definitive answer.
Sent from my Google N6 on VZ
DebianDog said:
I 100% percent agree with you but the reality is you could reload the phone and reset everything before you get a definitive answer.
Click to expand...
Click to collapse
I don't agree. At least not entirely. There are enough people here to interpret a logcat, it could be done in seconds.
But it does come down to how significant of a setup you're dealing with, and how well equipped you are to understand and manage a problem.
My wife's hammerhead did something weird not long ago, google applications continuous force close. A quick examination of the logcat yielded a "can not downgrade database from version 3 to 2" problem on the gms package. Kind of weird, since it just happened out of the blue, she's running factory + root on the thing. So I wiped the database, rebooted, and its back to normal. Took 2 minutes. A wipe and reload and reconfigure would have taken hours.
For my own devices, last time I did a "wipe" was in... 2012. I did a full backup and restore from my last phone to my N6, wiped/adjusted/reset whatever databases and configurations didn't match between the Samsung Relay custom 5.0 build (I did userdata "upgrade" the whole way up from 4.0 on that device, without wiping even ONCE) and the N6. Saved tons of time.
In the time it took you to respond to this message I could have backed up my whole phone on titanium backup. Wiped it. flashed it. Reroot it and restored all my settings and applications. That's my point.
Sent from my Google N6 on VZ
DebianDog said:
In the time it took you to respond to this message I could have backed up my whole phone on titanium backup. Wiped it. flashed it. Reroot it and restored all my settings and applications. That's my point.
Click to expand...
Click to collapse
Except that in restoring your backup, you have also restored whatever the problem was, and are now back to square one.
doitright said:
Except that in restoring your backup, you have also restored whatever the problem was, and are now back to square one.
Click to expand...
Click to collapse
Maybe or maybe not you mean. Caches inconsistent with the current version how Android are usually the cause of this or caches that got corrupted in some manner . And as you know you never restore caches.
My 5 years experience with Android dictates that these problems are usually EASILY resolved with a wipe of the cache/phone. perhaps your personal evidence is different.
Yes I personally would fire up system info and look at the logs before I wiped my caches and if that didn't work I would wipe the phone.
Sent from my Google N6 on VZ
I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.
marsdiamond said:
I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.
Click to expand...
Click to collapse
How are you OTA-ing? OTA checks for modified kernel and should fail... You need edited kernel to have forced encryption disabled.
The best way to update would be to fastboot flash the system.img and then flash a matching boot.img wit forced encryption disabled.
I am using the Wug Fresh Toolkit...
But when I flash an image with encryption disabled, won't that wipe my device?
marsdiamond said:
I am using the Wug Fresh Toolkit...
But when I flash an image with encryption disabled, won't that wipe my device?
Click to expand...
Click to collapse
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
rootSU said:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
Click to expand...
Click to collapse
Do you keep this statement somewhere so you can copy and paste or do you type it out every time?
Evolution_Freak said:
Do you keep this statement somewhere so you can copy and paste or do you type it out every time?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rootSU said:
Click to expand...
Click to collapse
Touché.
rootSU said:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
Click to expand...
Click to collapse
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?
Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.
marsdiamond said:
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?
Click to expand...
Click to collapse
Just go to General > Sticky Roll-up thread.
All "important" threads are there.
marsdiamond said:
Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.
Click to expand...
Click to collapse
You cannot flash OTA if you have any customisations in the ROM or kernel and if you're unencrypted, you have a custom kernel.
If you're wishing to stay rooted or unencypted, you should either install a rom.zip, custom kernel and SuperSU from custom recovery or download the factory image and fastboot flash the system.img, a custom kernel (recovery or fastboot) and SuperSU (recovery)
Hi everybody! Just here to let people know how to gain root on their shiny new Z2 force!
Straight and simple here's what your going to need:
Fastboot and adb installer
Download This for T-Mobile Rooted August Image For T-Mobile
Download this for Sprint Rooted August Image for Sprint
Installation Instructions
1. Make sure your on T-Mobiles latest update (August)
2. Unlocking your bootloader is a MUST!
3. Open the newly installed adb and fastboot you just installed. You should get a blank command screen.
4. Reboot your device to bootloader mode using the command adb reboot bootloader (make sure usb debugging is on)
5. On the bootloader screen your going to type the command Fastboot flash boot and LEAVE IT THERE DONT DO ANYTHING!
6. Next your going to go to the downloaded rooted august image and drag that to the command screen
7. Once that is done you should see something along the lines of "fastboot flash boot "C:\path\to\boot\Magisk_Moto_August.img"
8. Once you see that hit enter and once you see its done on the bootloader screen click start and it should boot up.
9. Once that is done download this Magisk Manager
10. Install it and BOOM you should have root!
Special thanks to:
@topjohnwu for the updated pixel magisk
@Chainfire for everything he has already done for the community.
Awesome! Today is going to go by so slowly waiting for the Sprint image lol
So, now we can work on ways to fix using third party messaging, notifications, etc? After I turned off the Moto Display the screen rarely lights up with notifications.
filthyfnj24 said:
Awesome! Today is going to go by so slowly waiting for the Sprint image lol
Click to expand...
Click to collapse
The T-Mobile one will work fine since it's the exact same device and once I make one tonight you can just reflash the boot img
joemossjr Great job! You give me hope! :good: :highfive:
Woo-Hoo! Glad to see this has finally happened!
Works! I love you person!
joemossjr said:
The T-Mobile one will work fine since it's the exact same device and once I make one tonight you can just reflash the boot img
Click to expand...
Click to collapse
Awesome. Does this wipe data?
Edit: answered my own question. I took the plunge and it does not wipe. I've never used magisk before. Install via the recommended direct install? Sorry for all the questions, this is a little different than rooting my last three Xperias and I don't really want to become the first guy to brick his z2 on xda lol.
Nope
Once you flash this you should just need the manager and it should be rooted. If it's telling you to install then something went wrong
filthyfnj24 said:
Awesome. Does this wipe data?
Edit: answered my own question. I took the plunge and it does not wipe. I've never used magisk before. Install via the recommended direct install? Sorry for all the questions, this is a little different than rooting my last three Xperias and I don't really want to become the first guy to brick his z2 on xda lol.
Click to expand...
Click to collapse
Put a screen shot of your manager here
joemossjr said:
Put a screen shot of your manager here
Click to expand...
Click to collapse
I'm guessing it's installed. I am able to backup with titanium but unable to delete bloatware (tested on Amazon app and received this error message) I'm guessing it has something to do with the r/w permissions but I'm not sure how to change them on this phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to delete some apps try es file explorer and go to the root section and mount system re and / rw if that doesnt work use this app it worked for me
joemossjr said:
I was able to delete some apps try es file explorer and go to the root section and mount system re and / rw if that doesnt work use this app it worked for me
Click to expand...
Click to collapse
Hmmm. I tried both methods and both said I have been granted rewrite permissions but I still get the same error message from tibu. It's not a big deal, just strange. Adaway installed and is working fine. Those are the only two root apps I've tested.
Can you uninstall any other apps?
This is great thank you
Sent from my SM-N930F using XDA-Developers Legacy app
joemossjr said:
Can you uninstall any other apps?
Click to expand...
Click to collapse
I just downloaded an app from the play store and deleted it with tibu with no problem.
A lot of T-Mobile and Sprint talk, no love for Verizon?? lol
Seriously though if you need any testing done I'm here to help out!
filthyfnj24 said:
I just downloaded an app from the play store and deleted it with tibu with no problem.
Click to expand...
Click to collapse
Odd
chetqwerty said:
A lot of T-Mobile and Sprint talk, no love for Verizon?? lol
Seriously though if you need any testing done I'm here to help out!
Click to expand...
Click to collapse
Sadly Verizon doesn't have an unlocked bootloader and that way past my profession lol
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
View attachment 5253543
View attachment 5253545
Click to expand...
Click to collapse
Are you rooted? Did you ever enable usb debugging in developer settings?
Tulsadiver said:
Are you rooted? Did you ever enable usb debugging in developer settings?
Click to expand...
Click to collapse
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
ChrisH78 said:
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
Click to expand...
Click to collapse
Yes, you have to unlock the bootloader and that wipes the data. Your phone would have to be able to boot up for that to happen. Just wondering if you flashed something that didn't agree with your phone. Without usb debugging enabled, I don't know a way to pull anything off.
ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
Click to expand...
Click to collapse
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
v12xke said:
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
Click to expand...
Click to collapse
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
v12xke said:
Wishing you a successful recovery.
Click to expand...
Click to collapse
Would the mount /system option be of any use to me?
ChrisH78 said:
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
Click to expand...
Click to collapse
You would use fastboot to dirty flash a full image, removing the wipe flag (-w) from the flash-all script beforehand. This wipes and replaces the boot partition but leaves your data intact.
ChrisH78 said:
Would the mount /system option be of any use to me?
Click to expand...
Click to collapse
No. Even unlocked and rooted we cannot write to the system partition anymore. Any luck on getting your phone working again?