Database Info

Trying to root my g-slate

So I got bored with waiting around for someone else to do it, and decided to take a shot at rooting my G-Slate. I figure it's basically the same as the Xoom, so the same sort of process should work....
My initial game plan was this:
Get into Fastboot
Flash a recovery image
Boot the recovery image
Now "adb shell" is a root shell
Copy a "su" binary into /system/bin
Declare victory
That started out pretty well. Powering on and holding down volume-up gets into fastboot. The fastboot binary on my laptop sees the device. Typing "fastboot oem unlock" claims to work. Flashing the Xoom recovery image [1] claims to work.
But... I can't seem to boot to recovery. Running "adb reboot recovery" just reboots normally. Doing "fastboot boot recovery.img" freezes the device. Booting with down-volume gets me to some sort of LG updater state that might as well be freezing the device. Booting with both volume buttons down either 1.) doesn't boot or 2.) brings me to fastboot. That's all the button combinations.
So I guess my question is this: does anyone have any suggestions for how to proceed?
I really don't want to just blind-flash the Xoom boot.img from the unlock thread, because if that doesn't work my device is bricked until someone either makes a working kernel or somehow extracts the current one.
On the up side, my g-slate is *claiming* to have working fastboot that can flash images. It could be totally lying though.
[1] http://forum.xda-developers.com/showthread.php?t=1038870

Tried the same method. No dice. Right now there has been no luck on anyone's part that i know when it comes to rooting. Shoot we havent even been able to get one of the xda mods to create us our own forum for that matter...i had to go out and create my own. I have tried other methods that worked on my nexus one when none other would but alas still no luck.
I imagine since the g-slate is brand new that its not a question of if it can be rooted, but how and when. I'm going to try one more method i know of that worked on the lg optimus tonight. I'll post here if it works.

Soure code seems to be available too
It also appears the source code is available from LG here .lg.com/global/support/opensource/opensource-detail.jsp
I just did a search under mobile phones for the model number 909
Don't know if that will help anyone here.
I have been hunting all over for root access. fastboot says I unlocked the bootloader but nothing seems to want to take.
XDA Mods, please create a G-Slate Section
HA. member since 2006 and my first post just add a www in front of that link

When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command. I have rooted a lot of devices, but never have done anything on an LG device and it is awkward. Vol+ and power gets some form of fastboot. Vol- and power gets download mode, which I am used to from Samsung devices (if we can get an interface like Odin then this becomes a lifesaver and makes the device "virtually" unbrickable). I cannot find any form of recovery. 'Adb reboot recovery' just restarts the device. One interesting this is that pushing both Vol+ and Vol- and power puts the device into what would seem like a bricked device (just use reset button). This same button combination worked on some Samsung devices so something is happening there, but I have not tried enough combos yet to figure it out.
So far as root, well, I have tried z4 (works with nearly all Sammy devices and LG seems to be using a lot of Sammy ideas or at least it looks that way), but to no avail. Gingerbreak apk might work or even the Xoom Root, but the rootboot.img might be different and I have not opened any of that up yet. I did get SU loaded once and in the system, but I could not reproduce it.
I will be working on this some more this weekend (returning the device at some point as it reboots on its own about 5 times a day), and looking into the recovery issue. If anyone has any ideas then please post.
Also, it looks like LG hacked the crap out of the thing to get the SD card to mount and it is weird, so please be aware of that. The SD card mounts every time you plug the device in and there is no way to turn that off. The reason this is important is that some root methods require that the SD card not be mounted, so you will have to unmount the SD card via ADB and with the card being internal I am not too sure it is a good idea, but . . .
I will mark this thread as a favorite and update if I get any where. I know that Cyanogen and Kmobs got G-Slate's recently, so hopefully they can give us a little insight once the device gets to them. I have also contacted LG and @TheLGGirl and asked them to confirm that the bootloader is locked, but have not heard anything back.

Also, the the Acer HC tablet was rooted yesterday using the Gingerbreak root method, and so that is helpful, but it has an SD card (see above).
Sent from my LG-V909 using Tapatalk

I tried the Acer method (GingerBreak) and it does not work. Will look at the logcat in a bit.
Sent from my LG-V909 using Tapatalk

Thanks hourst
I am used to odin (also have a vibrant). Something like that would be a life saver.
Makes sense about the fastboot commands seeming to take.
I was also having reboot issues with mine. I had a handful of reboots each day (about 3 or 4) for the first two days but they have stopped completely now. I have had it for about a week now and have not noticed a reboot since day 2.
I will keep poking around to see if i can come up with anything as well.

Could this help?
Under the impression the G2x root method maybe helpful since they are both LG devices with somewhat similar hardware.
Does anyone know or tried this http://forum.xda-developers.com/showthread.php?t=1056847 to see if it works?
Not sure if I am brave enough yet. But it could be possible the vol up+vol down+power button combo that seems to lock the device is putting it into the mode needed to run the nvflash application.
This really is mostly speculation but could be something to try.

Success
So i got brave.
vol up+vol down+power Device seems to freeze. Plugged in the usb and got a new hardware pop in windows. Listed it as APX device using the drivers in the file listed in my previous link installed successful and the device was found.
That is a far as I went.

im doing the NVFLASH right now... wish me luck and see how far I can go

Any Luck?
Suzannemscott
How did it go? any results or do you have a large brick?

ok i tried. and no luck , i did manage to brick it tho, but i was able to unbrick it phew, back to square one

Did it seem like anything happened? Also what did you do to unbrick it?

To unbrick it i just press the reset button, in the back, quickly hold down Vol+ and Vol- then it goes to a the Gslate screen with the square and then i hold down the reset again and it reboots, maybe i am doin to much but hey it get my Tab back it works!

Gah! Why does it claim to have fastboot when *any* fastboot command except "fastboot devices" just makes it freeze?
I went ahead and built the kernel that LG released and packed it into the clockwork recovery image for the Xoom. Fastboot boot... freeze.
Computer always says this, but I think it's just making fun of me:
downloading 'boot.img'... OKAY
booting... OKAY
I also tried to build and boot a custom kernel with a fb console enabled just to get some feedback, but all it wants to do in response to "fastboot boot" is freeze.
I'm starting to get discouraged here. My 14 day return period ends on Tuesday and I don't really want to get stuck with an unrootable device.

Chandon, would you be able to send me the kernel you built?

I'm sure someone with more expertise and knowledge will be able to root this thing eventually...but right now it seems to be a lot trickier to root than I initially thought. It's not unrootable...just complicated. Over my head by a lot. I don't think I'm going to return it...but I've now resigned to the fact that I may not ever be able to find a working method to root the damn thing myself.

SmellyTunic -
I've uploaded the two kernels I built [1].
They're both built from the v909 kernel source posted by LG[2], following the instructions posted by adrynalyne[3] for building custom android kernels, but I don't have any way to test them aside from the fact that "fastboot boot" doesn't work either straight, with a ramdisk, or with a rebuilt recovery image using the tools in [4].
[1] http://pandion.ferrus.net/gslate/kernels
[2] http://opensource.lge.com
[3] http://forum.xda-developers.com/showthread.php?t=1039854
[4] http://forum.xda-developers.com/showthread.php?t=915808

hourst2 said:
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command.
Click to expand...
Click to collapse
Not entirely true. You said that if you try simply typing in "fastboot unlock", it tells you "OK" as well, right?
Not for me. That only ended up displaying the whole list of fastboot commands.
I agree with you that "fastboot oem unlock" is not unlocking the device though. But what are the alternatives? Everything I've ever rooted has used "oem unlock". I've never even heard of a different command that can be used to unlock a bootloader. I tried a google search and came up with nada.
Hmm...

wich you the best make happen

help- bricked it, no recovery, what now?

Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...

Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.

matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.

Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.

matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp

I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.

I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app

matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?

matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.

befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?

matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?

befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....

Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.

You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app

You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app

Insignia Flex

Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?

Employee here and I had to pouch one up as well for the price of $80. Now to figure out root.
Sent from my SPH-L710 using xda app-developers app

Let us know if you get it.
I've tried Bin4ry, doomlord, tpsparky, played around with it myself a bit. Still not luck. Closest I got is normal on Bin4ry. Just when it reboots, it has no root privaledges. su is in /data/local/tmp but it fails to do anything...

I haven't messed around with it until this very moment. I will admit that the price is killer but initial impression with the device could be better. I was impressed and I mean really impressed with its quadrant score. I'll root this device later today. Black Friday sales and I am tired.
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
I found a link to root this device on both ICS and jellybean. I will personally look into it tomorrow but I will post it if you would like to go ahead. The guide itself was written for ICS but later down the thread you will find another link to a working root for jellybean.
http://androidforums.com/insignia-flex-all-things-root/661247-how-root-insignia-flex.html
Please root at your own discresion and I sure hope you purchased a protection plan (GSP) for your tablet.

also picked this up at my BB, was surprised when i walked in at 3pm and they still had about 10. i want to root too

We had a large quantity to sell as well and they all went. It is honestly not half bad. And I would really recommend getting the GSP for the tablet in case of anything. Will report back after rooting.

Let us know if you have any luck. I found the link you posted before which led me to try Bin4ry. The script seems to be updated for JB in general but still had no luck. I'm on a Mac and haven't tried any of the windows rooting apps, like posted at the bottom of that thread. I do have a windows partition and would be willing to try that method if needed. That chinese one at the bottom seems shady regardless though.. I hope there is an alternative to that

Is there a way to flash clockworkmod onto this tablet?

rekagear20 said:
Is there a way to flash clockworkmod onto this tablet?
Click to expand...
Click to collapse
I managed to get the CX-803 version of CWM for Rockchip 3066 from AndroTab.info to work by replacing its kernel with ours by unpacking and repacking with RK3xxx-Firmware-Tools by Sergio.
Note: This is for the Insignia NS-14T002 (aka iRiver NS-14T002) tablet that shipped with Android 4.2.2
Be EXTREMELY careful! Highly recommend you dump your current kernel and recovery partitions and save them somewhere before flashing anything.
If for some reason the recovery doesn't work, you can flash your stock recovery back as long as you can get back into root shell. But, if it fails to boot normally, I have no idea how to fix it. I have not been able to get any of the Rockchip flashing utilities to recognize the tablet so far, in bootloader mode (these devices have no fastboot) or otherwise. So don't blame me if you somehow brick your tablet.
You have been warned!!
CWM & Stock* Recovery image for NS-14T002
* if for some reason you can't back up your own, but again highly recommend backing up your existing recovery in case it's different from mine
You need root, and you need to do the install from root shell (don't forget to su) as described here.
I used /data/local instead of /dev - anywhere writable should be okay.
To boot into recovery:
adb reboot recovery
power off tablet, disconnect USB, press and hold Vol+ and Power until recovery comes up.
USB disconnect is not a strict requirement, but the battery status thing tends to get in the way.
In stock recovery, push Vol+ and Vol- simultaneously to bring up the menu. CWM menu should be visible at launch.
install petrus's Reboot App and use it to Reboot into recovery
Note: In CWM recovery you can swipe up for Vol+ (move up), swipe down for Vol- (move down), swipe left for Power (select), and swipe right for Back.

Re:Insignia Flex Tablet
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a problem thus far!
http://www.kingoapp.com/

cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers.
Click to expand...
Click to collapse
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.

bhiga said:
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Yes my device came with 4.2.2 Jelly Bean! My first attempt using Kingo Root it did not see my device. Windows would not install the drivers needed. So I installed PDA net for windows and choose other in the program and once it was done installing it had configured the necessary drivers for Kingo Root to find my tablet and it rooted fine within a couple minutes after that! :good:

help!
klowdhaus said:
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Click to expand...
Click to collapse
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.

arahmahndy said:
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
Click to expand...
Click to collapse
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.

Thank you!
bhiga said:
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Click to expand...
Click to collapse
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!

arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
If you can access ADB then try loading the CWM recovery I posted above. If you can at least get CWM up, at worst case I can give you a copy of my stock backup to restore.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.

arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
Did you get things sorted out?

If anyone is interested or needs it, Insignia sent me the GPL source.
You can also request it directly from them like it says on the website but it took a week or two (they might not have had a procedure in place yet, the agent had to forward my request to a different department) and I had completely forgotten until an unexpected package arrived.

Performance NS-15at10, ta120, ITQ701
Just thought someone might want to know, kingo root works, updated to 4.4.2, Booster plus battery saver pro is worth the money, better than 3c so far, still looking for more sources, any advice or help is appreciated especially for a recovery, dual bootloaders, ugh

cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a proble
Can I install drivers without PC?
Click to expand...
Click to collapse

Unlocking and Rooting AT&T LG V10 H900?

Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out

T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?

I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.

sharky481232 said:
I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.
Click to expand...
Click to collapse
How'd you manage to do that? I've tried a combination of buttons, but nothing.

RobertVanHagar said:
How'd you manage to do that? I've tried a combination of buttons, but nothing.
Click to expand...
Click to collapse
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.

sharky481232 said:
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.
Click to expand...
Click to collapse
Really hope you find the work around. Alot of people say at&t isnt going to allow rooting of new devices.......if theres a will theres a way!good luck

no updates?

I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?

betovanbuuren said:
I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?
Click to expand...
Click to collapse
I have the same problem with my AT&T H900. I'm on 90009e and wanted 90010f. AT&T Tech support couldn't get it to upgrade either which I find very odd. We really need some phone mastermind to unlock the secrets of the AT&T LG V10 H900. I'm unable to get it into download mode or unlock the boot loader either.
Thanks,
Silver

professorpoptart said:
T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?
Click to expand...
Click to collapse
Hmmm that's wiered because mine has stayed checked since I got the phone,although I don't t think it matters since it isn't unlocked. What's funny is i don't know why you can check it if bootloader is locked, I'm still lost on that one .

kotafoxx said:
Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out
Click to expand...
Click to collapse
This has been asked and answered here

How to get into stock recovery
1) Enable USB dubugging
2) Plug phone into computer
3) Set USB connection type to MTP
-Now the "USB debugging connected" notification should appear.
4) Entering "sudo adb reboot recovery" into the terminal will reboot you into the stock recovery.
Note: Entering "sudo adb reboot bootloader" will only reboot your phone...
Using: at&t LG V10
Model Number: LG-H900
Android Version: 5.1.1
Build Number: LMY47V
Computer OS: Ubuntu 15.10

I was able to root an LG escape2 with this method. You can communicate and push files to your phone through the download mode without technically using adb. Any chance a method like this would work?
http://androidforums.com/threads/gui...2-2015.937446/

in case you are subscribed to this thread go here..... http://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317/post65864734#post65864734

Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954

jiggajatt said:
Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954
Click to expand...
Click to collapse
Excuse me, what's flux?

manny18pr said:
Excuse me, what's flux?
Click to expand...
Click to collapse
http://techcrunch.com/2016/03/15/popular-blue-light-reducing-app-f-lux-arrives-on-android/

Galaxy amp 2 rootable?

Have done a little research trying to find any thing about an easy rooting for this device but no hits. I do know of some apps that can give root access haven't tried them but don't exactly trust them to much as have had them soft brick a few devices.
But any way here is device specs.
Carrier: cricket wireless
Phone name: Samsung Galaxy amp 2
Model number: Samsung-sm-j120az
Android version: 6.0.1
Baseband: J120AZTUU1APC4
if need any other info on it can supply it

I'm looking for the same thing. No roms no nothing.

@jasperjax Don't worry about it, there's not such thing as a flawless security system.
Universal rooting methods:
Warnings:
You are modifying your own phone on your own risk.
There is a slight chance that your phone may brick,
and if it does I will not be held responsible for whatever you do to your phone.
If you have a warranty, after rooting it will no longer be valid.
If your phone has a flash counter, some methods may trip it
resulting in a void warranty or a bricked phone (or both).
If your phone has KNOX, it may be tripped by some methods,
resulting in, once again, a void warranty.
If your phone is encrypted, the data partition
may be wiped for some methods.
There are more warnings specific to certain devices. Do your own research on your particular device model.
Click to expand...
Click to collapse
Computerless methods:
1. Framaroot
2. Towelroot
3. Kingroot for Android
4. Kingoroot for Android (Not recommended, but often works)
5. iRoot for Android
6. z4root
Methods requiring a computer:
1. iRoot
2. Root Master
3. Kingroot
3. Kingoroot (Not recommended)
4. CF-Auto-Root
Root Checker - Check if your device is correctly rooted
SuperSU - the recommended superuser application
ADB and fastboot drivers:
ADB and fastboot are (extremely simplified) a way for your computer to talk to your phone. And installing them may be a bit of a problem for some users.
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Recovery:
A custom recovery is an important part of device unlocking. It's the best and the most convenient way to fix your device if something goes wrong.
Root is required (in most cases) for installing the recovery.
The two most popular recoveries are:
1. Clockworkmod recovery (CWM) - CWM is a very stable recovery with many useful features. You can use the link here to download and install the official version via the ROM Manager app.
2. Team Win Recovery Project (TWRP) - TWRP is a stable recovery with a very nice UI and many features such as the terminal, partition management, file browser and so on. I personally use TWRP because of it's functionality, but if you're starting out CWM would be a better choice because of it's stability and compatibility. Also TWRP is a tiny bit more difficult to install as there is no one click installer.
If your device is not officially supported you can get an unofficial version, however there is no grantee the unofficial version will work, it might even forever break your device. In most cases it does work, just look at what other people who tested it say.
To find unofficial recoveries Google:
[your phone model] cwm recovery
or
[your phone model] twrp recovery
After installing the recovery the first thing you should do it do a nandroid backup.
If you have any questions first try to Google the answer, but if you can't find it feel free to ask me here with a post (not a PM).
Also remember to quote me or tag me with @janekmuric if you want me to respond.

most of those do not work for 6.0 correct? Amp2 comes with 6.0 stock

Has anyone heard anything more about rooting the Cricket Galaxy amp 2?
Just bought it yesterday for a friend and would love to root and possibly unlock it?

i have tried all the computer less ways of trying for root. none have worked. haven't done much with the ones requiring computer to root But does not mean i wont try them at some point. right now this is mostly a Backup phone Just in case i kill my Galaxy s4 (running goldeneye lollipop 5.0.1 rom) other then that have not seen anything New pop up around the net about it still on my todo list tho

2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?

jasperjax said:
2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?
Click to expand...
Click to collapse
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.

janekmuric said:
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.
Click to expand...
Click to collapse
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.

jasperjax said:
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.
Click to expand...
Click to collapse
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.

janekmuric said:
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.
Click to expand...
Click to collapse
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.

Anyone figure this out? I have a cricket samsung galaxy amp 2 (SM-J120AZ). I've tried every way possible to root it with no luck. I've tried all the methods above and none of them work for the amp 2.

@imagetrekker Not yet. another device very close to this one is the SM-J120A (Samsung Galaxy Express 3) everything matchs up besides the android version is comes with.(6.0) would think if they root that one this one would be able to be rooted same way or if this one gets rooted first should work on other.

Anyone figure out how to root this phone yet? I have never had a device that can't be rooted one way or another but this one is being really tricky...

I'd like to bump this too! I've tried many methods with no success. Any other options to try?

Bump

Where did you find that SM-J120AZ ROM ?
jasperjax said:
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.
Click to expand...
Click to collapse
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.

Can't format SD card for internal use
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...

sorry had some computer issues shortly after a thunderstorm but im back up and running so Sorry for the very late replys
MuzicSoulWorldly said:
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.
Click to expand...
Click to collapse
@MuzicSoulWorldly was actualy able to get it from http://updato.com/firmware-archive-select-model?r=&v=&q=j120az&exact=1
Greywire said:
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...
Click to expand...
Click to collapse
@Greywire Not quite you can do it with out root. commands are as this
Code:
adb shell
sm list-disks
sm partition <DISK> private
reboot
<DISK> needs to be replaced with the output of the previous command. For example sm partition disk:179,64 private. That will format the entire SD card and adopt it. Another way would be to use sm partition <DISK> mixed <VALUE> replace <DISK> same as with other way but value would be in a % of disk you want adopted example "sm partition disk:179,64 mixed 50" would make adopt half your sd card.

thanks..
I actually discovered this right after I posted. Hopefully anybody else having this issue will see your posting though for the solution.
Still would be nice to get root on this phone. Any ideas on how to carrier unlock it?