Develop Bugs

Help with GNex Toolkit 7.6

Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.

AdelaisAer said:
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
Click to expand...
Click to collapse
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058

gpfnzl said:
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Oh. Sorry about that. Well, my main question is how to back user data up using the toolkit. I see options for applications and nandroid and stuff, but I don't see userdata such as contacts, sync accounts, etc. The most important stuff.
That's my main concern first and foremost. Also, I'm checking the guide right now; thanks.

I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.

gpfnzl said:
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
Click to expand...
Click to collapse
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.

AdelaisAer said:
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
Click to expand...
Click to collapse
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.

gpfnzl said:
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
Click to expand...
Click to collapse
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...

AdelaisAer said:
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
Click to expand...
Click to collapse
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
back your sd card up to PC, from memory i think the unlock part wipes your phone

gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png

I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app

ttahatt said:
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh. Derp. Well, I edited my post before yours, and I saw it has two images in it (one of them is radio) and a zip file. So yeah, I guess that contributed a lot to my confusion.
Also, I think my phone is still locked. I have done literally nothing to it yet.
Also, I want to flash it because it's currently in a Rogers/Samsung-type OS, where updates aren't pushed because it takes them months to get the A-Okay, for whatever reason. I want to flash it to the Google-line so I can get regular updates without waiting. :S

AdelaisAer said:
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
Click to expand...
Click to collapse
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Plug your phone in to pc....reboot your phone into fastboot (vol+/vol- and power) see if drivers install (should see bottom right hand side of computer)

gpfnzl said:
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Click to expand...
Click to collapse
My goal is to back my contacts and app data up, and then flash my phone with the new factory os that I got from Google Developer. :S But this whole guide is ajfkjsdkjfksjfkwejfkjsdkjfakw. Also, sorry for ranting. >___<;
See, if Samsung had just pushed updates to Canadian Android phones in the first place like normal people, I wouldn't be here. But instead, they hold onto updates until they (and Rogers) can stamp their names all over it and then takes a few more months just to approve it a second time, for whatever reason. :S
Instead, I have to come here, try to do this whole thing, and then install that factory Google-line OS so I can get regular updates.
Go look in the Rogers community forums - nothing but threads complaining about it. I'm one of very few who actually came to a forum like this.

OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Alright, will do.
Also, sorry if my replies get a bit slow now - eating.
EDIT: Ugh, this is getting reaaly confusing now. o-o; Especially the part where you make a backup of the phone build. @[email protected];

When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.

gpfnzl said:
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
Click to expand...
Click to collapse
Alright. Thank you. :3
So far, I synced my contacts, browser, etc. up with my Google+ account, so that's backed up, and I can go into fastboot no problem and have the toolkit detect it.
I just wanna make sure that there's nothing else that needs backing up (if there is, then what do I backup, and how?), and then just flash my phone with the new 4.1.1, and be done.
Also, thank you so much for actually putting up with me. A lot of people would normally be rather mean/hateful towards new-comers like me, so thank you.
EDIT: Why must this be so complicated... @[email protected] Curse you, Samsung.

Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.

gpfnzl said:
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
Click to expand...
Click to collapse
Er, how do? o-o;

Plug your phone into your PC
open *my computer* select the *galaxy nexus*, select *internal storage* and copy every thing to your computer.
unlock your lock screen on the phone or your computer wont see the internal storage

Creating a Backup/Recovery/Dump

Forum:
If this specific question is in another thread, please forgive me and redirect me.
If not, any instruction would be greatly appreciated.
Equipment:
Visual Land, Prestige 7
Model # VL - 107
ICS 4.0.3
Baseband 1.0
Kernel 3.0.8+
Build # 86F5-D1-H1-MO1-1718.20120327
Objective:
To create a backup/recovery img/dump of the existing stock ROM, without having to add "clockwork", "cynogen", etc...
Software on Hand:
Windows 7
Livesuit 1.09
Virtualbox
Ubuntu via Virtual Machine
Please detail everything and speak to me as if I were a little child...
Thanks in advance!

I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !

Can this be done with ADB?
ruscan.calin said:
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Click to expand...
Click to collapse
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.

gth826a said:
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
Click to expand...
Click to collapse
I understand now this is a tablet so it's common problem for some
well you have to find a way to root device to get access to system files then use a rom dumping tool just take a look here or here
nobody can tell you for sure how to do that this is device specific I do not know to much about that particular tablet just try

I just got this tablet today, and it's rooted out of the box.
Not sure if that helps you, but I wanted to contribute if I could.
[signature]

Recovery for Galaxy Ace 2 - i8160
Hi,
Any chance of a simple recovery for the Galaxy Ace2 i8160 ?

VL107 Update Down To 4.0.3/4.0.4
Hello,
I've been trying to figure out how to change my VL-107's OS, and a Recognized Contributor pointed me to this thread.
I've downloaded LiveSuit, but I can't figure out how to make it work. If at all possible, I need two things: an .img file for 4.0.3 or 4.0.4, and instructions on how to apply this update via command prompt or a program that utilizes command prompt.
I have Windows 8.1, my VL-107 (Visual Land Prestige 7), and LiveSuit (which I'd really rather not use).
The only experience I have in flashing involved using command prompt, and I'm much more comfortable doing this than relying on a program to do everything "behind the scenes". Otherwise, I would also be willing to put an .img file on my tablet's "SD card" and apply the update through Recovery mode.

[Q] Lollipop 5.0.2 Update via TWRP

Hi Guys
I am running stock Android 5.0.1 LRX22C on my Nexus 2013 which is rooted and has TWRP installed.
I just got a notification that an update (9.8Mb) to 5.0.2 was available - however when I accept the update & the device reboots - it boots to TWRP?
Do I have to unroot / uninstall TWRP (go back to stock recovery) to be able to update to 5.0.2 or is there an easier way?
Thanks in advance for any help

You don't have to uninstall twrp.. You do have to unroot though.. If you use wugfresh's nexus root toolkit, it's pretty easy.. You just need to backup your important apps /data, and click the unroot /back to stock button. Select which version of Android you are currently running, and it will unroot your tablet. Then go back in and become a developer (settings, about, and tap on the build number 8 times) .. Then go into developer options, and re enable usb debugging.. After that, install the update.. Finally go back into nexus root toolkit, and re root the device... Fairly easy

BSnapp said:
You don't have to uninstall twrp.. You do have to unroot though.. If you use wugfresh's nexus root toolkit, it's pretty easy.. You just need to backup your important apps /data, and click the unroot /back to stock button. Select which version of Android you are currently running, and it will unroot your tablet. Then go back in and become a developer (settings, about, and tap on the build number 8 times) .. Then go into developer options, and re enable usb debugging.. After that, install the update.. Finally go back into nexus root toolkit, and re root the device... Fairly easy
Click to expand...
Click to collapse
Nice one - thanks very much. Not tried the WUGFRESH toolkit as I have always used the MJSkip version - so will give it a whirl

I unrooted (manally.. toolkits.. meh) and did the OTA last night, but just got bloops...
I downloaded the full package and flashed system.img, back up and running.

khaytsus said:
I unrooted (manally.. toolkits.. meh) and did the OTA last night, but just got bloops...
I downloaded the full package and flashed system.img, back up and running.
Click to expand...
Click to collapse
What did you use to flash the system.img? Will Flashify or Odin do it or do you have to hook up to a Windows PC and do it that way?

jellywobbles said:
What did you use to flash the system.img? Will Flashify or Odin do it or do you have to hook up to a Windows PC and do it that way?
Click to expand...
Click to collapse
fastboot for Nexus devices. Always.

khaytsus said:
fastboot for Nexus devices. Always.
Click to expand...
Click to collapse
could you upload the sytem.img file?
keep running on root and no delete any apps after update to this way?

zikario507 said:
could you upload the sytem.img file?
keep running on root and no delete any apps after update to this way?
Click to expand...
Click to collapse
If you download Factory Images 5.0.2 (LRX22G) then you can extract only the system.img from the pack.
You have to flash su.zip

khaytsus said:
fastboot for Nexus devices. Always.
Click to expand...
Click to collapse
Cheers - am in business - now running 5.0.2 & TWRP 2.7.1.1
Have a weird issue - I have made a TWRP backup which I can see in the TWRP folder on my SD card when I use the built in file manager in TWRP.
However - when I boot Android 5.0.2 & use ES File Explorer the TWRP directory on the SD card of the Nexus 7 is not visible.
I have an iMac & when I connect the Nexus 7 to the Mac (using Android File Transfer (special app for Mac) I still cannot see the TWRP directory
How do I make this visible to Android? I need to copy over the TWRP backup to the PC for safe keeping & the free up some space on the Nexus 7.
Thanks

jellywobbles said:
Cheers - am in business - now running 5.0.2 & TWRP 2.7.1.1
Have a weird issue - I have made a TWRP backup which I can see in the TWRP folder on my SD card when I use the built in file manager in TWRP.
However - when I boot Android 5.0.2 & use ES File Explorer the TWRP directory on the SD card of the Nexus 7 is not visible.
I have an iMac & when I connect the Nexus 7 to the Mac (using Android File Transfer (special app for Mac) I still cannot see the TWRP directory
How do I make this visible to Android? I need to copy over the TWRP backup to the PC for safe keeping & the free up some space on the Nexus 7.
Thanks
Click to expand...
Click to collapse
Try this:
SwoRNLeaDejZ said:
Download terminal emulator and run the commands below.
Code:
su
Code:
restorecon -FR /data/media/0
Should be fine after that.
Click to expand...
Click to collapse

jellywobbles said:
Cheers - am in business - now running 5.0.2 & TWRP 2.7.1.1
Have a weird issue - I have made a TWRP backup which I can see in the TWRP folder on my SD card when I use the built in file manager in TWRP.
However - when I boot Android 5.0.2 & use ES File Explorer the TWRP directory on the SD card of the Nexus 7 is not visible.
I have an iMac & when I connect the Nexus 7 to the Mac (using Android File Transfer (special app for Mac) I still cannot see the TWRP directory
How do I make this visible to Android? I need to copy over the TWRP backup to the PC for safe keeping & the free up some space on the Nexus 7.
Thanks
Click to expand...
Click to collapse
Any reason you went with a version of TWRP from six months ago instead of the latest version? http://techerrata.com/browse/twrp2/flo
As for pulling stuff from SD, I have no idea, maybe try the thing someone suggested with selinux (restorecon). I don't use MTP to do any transfers, all of my sd card backup stuff is done using rsync and automated by Tasker.

kilroystyx said:
If you download Factory Images 5.0.2 (LRX22G) then you can extract only the system.img from the pack.
You have to flash su.zip
Click to expand...
Click to collapse
@kilroystyx lrx22g puts me in a boot animation loop and all above versions on my nexus 7 2013. Only 4.4.4 factory image works for me but google play services and store crash. How can I upgrade without being stuck on the boot animation? This is driving me nuts. Tried cleaning cache, factory resets, formatting, etc. Please help! Thanks, Cindy

Nexus 7 (2013) LTE is not coming up

Hi there,
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...

vadim_se said:
Hi there,
Do not PM me for questions. Next time I'd not reply to PM questions.
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...
Click to expand...
Click to collapse
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply

Hnk1 said:
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply
Click to expand...
Click to collapse
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...

vadim_se said:
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...
Click to expand...
Click to collapse
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

Hnk1 said:
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.

vadim_se said:
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.
Click to expand...
Click to collapse
I'm glad everything is working fine. Unlocked boot loader isn't a problem at all. All of my devices are developer unlocked . So it isn't a problem if you like flashing/changing Roms.
Just keep it as you feel comfortable. If you have any other queries /questions, quote me and I be glad to answer your questions.

Bricked Phone After Magisk Install

Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James

Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.

jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."

Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk

Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....

Make sure you are trying to open from the correct location, and put .\fastboot

EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?

simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?

Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.

Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...

simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!

Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.

Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!