Related
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
I've already unlocked the bootloader and am about to flash cwd but my computer won't recognize the phone in the bootloader while plugged into USB. So when I try to enter the command "fastboot flash recovery <recovery.img>", the command prompt comes back with an error. I bet I'm missing something simple here, but it's getting pretty frustrating.
I have the HTC drivers installed and I'm using bootcamp, if that matters.
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
jonesin said:
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
Click to expand...
Click to collapse
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
feperlman51 said:
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
Click to expand...
Click to collapse
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
jonesin said:
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
Click to expand...
Click to collapse
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
feperlman51 said:
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
Click to expand...
Click to collapse
"just ran the "fastboot flash recovery" command again"
Lol thats what I said man! Glad it worked! CWM and TWRP should both work, I bet a nickel to a dime you werent actually in fastboot mode the first time! anyway happy flashing! Get comfortable with ADB and Fastboot because they will be our primary utilities for the foreseeable future!
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
There are call recording apps on playstore. Along with the rooting is so simple I did it the same day I got my v10 T-Mobile variant
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
First things first, you don't need root to record your phone calls. Like Wadamean said, there are call recording apps in the play store. I personally use "Call Recorder ACR", but you can use whatever you prefer. Most call recorders won't require root access.
As for rooting, if you type the adb command and it says that it's waiting for your device, the most likely cause is that you do not have the proper drivers installed on your computer. An easy way to check this would be to type the command "adb devices" and make sure that your V10 appears under "List of devices attached". If you don't see your h901 device listed, your computer doesn't know that the V10 is connected, and it'll be difficult for your computer to issue commands to a device it can't see
Follow each step in this guide. That doesn't mean click this link, skip to the downloads, and then proceed to root like you've always done. It means click this link, READ THE POST, then once you have finished reading it, read it again to make sure you didn't miss anything. It will guide you through setting up adb with a universal driver. It will also guide you through doing things like enabling USB Debugging, which is required for issuing adb commands.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
If you are still having issues after reading this guide and FOLLOWING THE INSTRUCTIONS, post there to let them know where you're getting stuck at and someone will help you out.
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
dillonorden said:
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
Click to expand...
Click to collapse
No worries, that's why we're here :good:
If you can see your V10 listed on the ADB devices list, then something else is up. Make sure that USB Debugging and OEM Unlock are checked in Developer Options... What command are you getting stuck at?
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
dillonorden said:
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
Click to expand...
Click to collapse
Ahh, sounds like you aren't in fastboot mode. Make sure that your USB connection type is set to PTP rather than MTP or charge only. Before you issue ANY other adb commands, run "adb devices" and make sure that you see your v10. It should read something like this:
List of devices attached
LGH901blahblah device
Click to expand...
Click to collapse
See it on the list? Good. You should be able to run "adb reboot bootloader". At this stage, your phone should reboot to a mostly dark screen. Once in the bootloader, you should be able to run "fastboot oem unlock". Be forewarned that it can take a few minutes. If you see "waiting on device," you're either not in the right mode (your phone won't acknowledge fastboot commands if it's not in Bootloader mode) or the drivers on your computer are screwy and need to be reinstalled. If you can issue adb commands but not fastboot ones, you probably need additional drivers - more info here: http://android.stackexchange.com/questions/46142/fastboot-doesnt-see-device
This should get you started in the right direction, feel free to PM or post in the guide if you're still having trouble. :good:
ok so i followed the guide, reinstalled the LG drivers. and re setup the ADB system wide. I put my phone in usb ptp and ran command ADB devices. It listed my device, so i ran the ADB reboot bootloader and it rebooted. the screen i get is the LG boot screen but in the top left corner it shows fastboot mode and list the commands to unlock the bootloader. I run command fastboot oem unlock and I get the same waiting on device and waited an hour and got nothing. I even tried unplugging it restarting command prompt held the vol down button when i plugged my device back in to make it boot into FASTBOOT mode. i run the command fastboot oem unlock and still get nothing.
What am I doing wrong? I follow the guide to the very T and still get nothing. Could I possibly get someone to make a file with everything done and flash it using Odin? Im not new to this and dont understand why this V10 H901 is giving me so much trouble. Ive rooted a Motorola OG droid, Droid 2, Bionic, Samsung Note 2, 3 and Grand Prime and never had this much trouble. I really enjoy having root privileges but this is getting ridiculous but I also refuse to give up. If anyone can help me I would much appreciate it. Also Thanks to the ones who have tried helping me so far, this is why I enjoy XDA so much
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
dillonorden said:
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
Click to expand...
Click to collapse
Are you the administrator of the pc? What OS are you using?
I am administrator and im using windows 7 so i dont see where im having an issue at
Iv'e been looking around for a root for my device and I can't seem to find a root. Is there even a root for it yet?
Guys come on. Its been almost 4 months now and still no root. I just want to delete all the bloat ware off my device so that I can use it more.
Well I guess there isn't a root for my device. If anyone needs to root this device your out of luck.
Perfectly fine Android build per se; you want to change what?
You were joking, right? Going into the about/device and tapping on the kernel version lets you pick a ROM from microSD.
One supposes that you would use adb to make verify all your build assumptions are OK, grab Android developer kit and blobs on your development box of choice, and build your new improved ROM. Boot to glamour-shot portfolio FTW.
Separately, Internet reports are that Kingroot.net works, at least from the Windows side (perhaps after a little name tweaking from that side of adb resource names; see the perfectly serviceable P10A7100 note on Reddit. On the Android side I'm still looking at a spinner and '01%' root acquisition progress. But then I should give Kaspersky and Malwarebytes the day off while this is going on, right?
Hello,
New to the adb thing. I want to say first off, that this tablet has to be the worst POS I have even had. Its has 32 gb of memory but I can only use 6 of it for apps before it slows to a complete useless doorstop. Could anyone reccomend a good rom image?
I have the same issues. Can't believe they would sell such a POS! That's Best Buy a crap store that used to be one of the best.
Insignia NSP10A7100 rooting
Any luck finding more info on root for this device? I've only tried kingroot so far from the apk but no luck. Also trying to find more info on how to root manually (without a script) or how to write my own script? I've enabled developer options, enabled bootloader unlocking. I can run adb from my ubuntu box but adb reboot bootloader just reboots? I see the option when tapping kernal to update a .zip file but what file? I haven't seen any roms or recovery's for this device. Any help is appreciated!
Insignia NSP10A7100
I was playing around with adb and fastboot tonight and did learn a few things. I had to use "sudo fastboot flashing unlock" to get the bootloader unlocked. Whatever that switch is in developer options to unlock did not seem to unlock anything. I did a getvar all and the output showed it as locked. sudo fastboot with no options gave me the list of commands to use. After reboot there was a screen that warned about the bootloader being unlocked and that it was not safe. I thought it was going to be stuck there but it did finally reboot into a fresh system. I've got files with the output of getvar all and bugreport if any of that info would help anyone with the rooting. If anyone can point me to more research I'll continue to play with this.
mjhack said:
I was playing around with adb and fastboot tonight and did learn a few things. I had to use "sudo fastboot flashing unlock" to get the bootloader unlocked. Whatever that switch is in developer options to unlock did not seem to unlock anything. I did a getvar all and the output showed it as locked. sudo fastboot with no options gave me the list of commands to use. After reboot there was a screen that warned about the bootloader being unlocked and that it was not safe. I thought it was going to be stuck there but it did finally reboot into a fresh system. I've got files with the output of getvar all and bugreport if any of that info would help anyone with the rooting. If anyone can point me to more research I'll continue to play with this.
Click to expand...
Click to collapse
I just got one and trying to access fastboot. I have model p10a7100. When I pick fastboot from recovery mode, I momentarily get resting android with "no command" and get recovery mode again. Because of low ram, I would like root access to install magisk for modules. Please explain your unlock method.
Fred Simm said:
I just got one and trying to access fastboot. I have model p10a7100. When I pick fastboot from recovery mode, I momentarily get resting android with "no command" and get recovery mode again. Because of low ram, I would like root access to install magisk for modules. Please explain your unlock method.
Click to expand...
Click to collapse
I have had no success trying to get root access. I only got the bootloader unlocked. I used adb to reboot into fastboot mode.
mjhack said:
I have had no success trying to get root access. I only got the bootloader unlocked. I used adb to reboot into fastboot mode.
Click to expand...
Click to collapse
Teach us your adb method. I have tried everything and it won't enter fastboot mode. If I type adb reboot fastboot, it just bypasses fastboot and boots up the tablet to android.
Update: I entered the adb command adb reboot fastboot and I get a giant green screen with a walking android robot in the center. Then I lose contact with the tablet. Never saw that before.
fastboot
Fred Simm said:
Update: I entered the adb command adb reboot fastboot and I get a giant green screen with a walking android robot in the center. Then I lose contact with the tablet. Never saw that before.
Click to expand...
Click to collapse
That is what I did also although I used "sudo adb reboot fastboot". Still not sure if the sudo is required? The giant green screen means you are in fastboot mode now. Type "fastboot" at the terminal to see a list of commands. The one I used to unlock was "sudo fastboot flashing unlock_critical". Type "sudo fastboot flashing get_unlock_ability" to find out if you are able to unlock the bootloader. This is as far as I got. Apparently I could now flash an image if I could find one that would be compatible. If you get any further or find one let me know.
mjhack said:
I have had no success trying to get root access. I only got the bootloader unlocked. I used adb to reboot into fastboot mode.
Click to expand...
Click to collapse
mjhack said:
That is what I did also although I used "sudo adb reboot fastboot". Still not sure if the sudo is required? The giant green screen means you are in fastboot mode now. Type "fastboot" at the terminal to see a list of commands. The one I used to unlock was "sudo fastboot flashing unlock_critical". Type "sudo fastboot flashing get_unlock_ability" to find out if you are able to unlock the bootloader. This is as far as I got. Apparently I could now flash an image if I could find one that would be compatible. If you get any further or find one let me know.
Click to expand...
Click to collapse
I lose all connectivity at fastboot. PC doesn't see it anymore.
Fred Simm said:
I lose all connectivity at fastboot. PC doesn't see it anymore.
Click to expand...
Click to collapse
Are you on Windows? I'm on Ubuntu. Not sure what would cause that. Maybe someone out there with more knowledge will chime in. Good luck.
Here is a link to a temp cwm recovery and root instructions for a nuvision 8 inch tablet. According to the post it might work on other intel based tablets. Disclaimer: You may brick your device. I still can't establish an adb connection to test this. I have adb with the tablet booted. I lose it in fastboot or recovery. I was able to unbrick my nuvision after 2 years of waiting for a method.
https://forum.xda-developers.com/android/general/nuvision-tm800a510l-info-root-recovery-t3471186
mjhack said:
Are you on Windows? I'm on Ubuntu. Not sure what would cause that. Maybe someone out there with more knowledge will chime in. Good luck.
Click to expand...
Click to collapse
Winblows 10. I think it's a driver issue.
Fred Simm said:
Winblows 10. I think it's a driver issue.
Click to expand...
Click to collapse
I was wondering if it might be a driver problem. You could try Virtual Box and run Ubuntu that way. I may try that cwm down the road. Thanks for the info.
insignia ns-p10a7100
tony5100 said:
Iv'e been looking around for a root for my device and I can't seem to find a root. Is there even a root for it yet?
Click to expand...
Click to collapse
i am waiting on thumb drive from insignia with source code
wmhaganjr1013 said:
i am waiting on thumb drive from insignia with source code
Click to expand...
Click to collapse
Did you ever get the source code for this tablet?