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
Related
I'm trying to use my backup from CWM to restore my device, but I only get MD5 errors and I don't get Fastboot USB. My device is not recognized at all by my pc. What can I do?
I have the HTC One X+ international, europe.
Any help at all is very appreciated.
have a look at this
http://forum.xda-developers.com/showthread.php?t=1835914
btw i suggest you use TWRP as it's more compatible with our device
Thanks! but now an entirely different problem has risen. The phone isn't detected in "adb devices" so I can't get access.
But when I type fastboot devices it lists my device.
What can be done to rectify this?
DumbHoarder said:
Thanks! but now an entirely different problem has risen. The phone isn't detected in "adb devices" so I can't get access.
But when I type fastboot devices it lists my device.
What can be done to rectify this?
Click to expand...
Click to collapse
ADB seem's to only work on LINUX....something that really needs to be looked into in recovery...also if your in HBOOT then adb wont work only FASTBOOT
Thanks for the help. Being new to this as I am, I thought adb would be accessible through hboot. Therefore, I spent some time trying to set that up. I did actually end up just flashing stock on it to fix all my problems.
I have the tmobile lg v10 h901. I'm trying to unlock the boot loader. I have adb and fastboot files installed and the lg drivers. I have the oem. Unlock and usb debugging checked in the setting. I can open the command prompt and use adb devices and it sees my device. I can use adb reboot bootloader and it will take me to the fastboot bootloader unlock screen. From here the command prompt no longer sees my device. I type fastboot oem Unlock and it says waiting on device... Any one have a idea what's going on. Am I missing something?
Try booting into fastboot manually by turning off the phone and holding vol down while plugging it in,then try it but make sure you fastboot devices first to make sure its even detecting it
No that didn't work. When the phone is on adb devices it sees the phone I type fastboot devices and it does nothing. But when the phone goes to fastboot even volume down then plug the phone In it won't recognize the phone just says <waiting on device>
Yeah I keep uninstalling everything and reinstall everything fast boot threw cmd fastboot with the volume button and always get waiting on device when I get to the "fastboot oem Unlock"
So sad ...
Use nexus toolkit for it all. I did. Works great.
Exconvict said:
Use nexus toolkit for it all. I did. Works great.
Click to expand...
Click to collapse
Wugs nexus toolkit ? That will work with the v10?
cwalton4077 said:
Wugs nexus toolkit ? That will work with the v10?
Click to expand...
Click to collapse
I used Mfastboot and it worked like a champ. Could not get nexus toolkit to see my device.
Yes. It boots temp recovery,flashes recovery and root. Also used it to relock the boot loader for sh*ts and giggles. To get it to see my phone I had to download LG bridge on my computer and run it.
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
If you run Windows, you may be missing the USB driver for fastboot. If possible, use Linux where all the USB drivers are included from the start.
I'm having the same problem as well.
cwalton4077 said:
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
Click to expand...
Click to collapse
When starting all of this (essentially becoming addicted to learning rooting) I noticed that no one mentioned to make sure to enable the "usb tethering" option on their device!! Once I did that, an entire plethora of additional options opened up. That being said, this option won't necessarily make rooting possible, but I think it may help out in this particular situation.
? I really hope this works for you.
1500 years ago, everybody "knew" that the earth was the center of the universe. 500 years ago, everybody "knew" that the earth was flat. And 15 minutes ago, you "knew" that humans were alone on this planet. Imagine what you'll "know" tomorrow.
-Kay
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Glad you got it rooted
Great!
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Now can you post a YouTube vid for us who are still having this issue! ?
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "
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?
Hey all i dont know what the deal is but ive got an lg g5 that just will not boot to the bootloader. I've tried factory resetting it and all the methods to get to bootloader just reboots the phone fully. Adb reboot booloader, key combos, nothing seems to work. Any ideas??
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
russy23 said:
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
Click to expand...
Click to collapse
Did all that.. I mean I've flashed custom recoveries and roms to other phones before and never really had a problem i couldn't google..this has me stumped. It simply refuses to even access the bootloader.
If it helps it was a koodo phone and is running the latest official patch from lg on nougat. The only thing i could find online was that sprint supposedly removed all access to the bootloader on theirs, but i cant find any real info on that either. It reboots when i send the adb reboot bootloader but its like fastboot just isn't there..?? It reboots right back to the android home screen. Ive tried all possible key combos as well... Ugh
Which model is it..mines the h850
Ive got the h831
I think I've sort of answered my own question. From browsing the forums it appears the Canadian variant has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
bproulx said:
... has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
Click to expand...
Click to collapse
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
logg.sar said:
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
Click to expand...
Click to collapse
Unless you're from Canada apparently ..lol