I can't connect my nexus 7 to any PC because my USB port is broken SO is there any chance I can root my device (boot loader is already unlocked)
Please help
Jim Omar said:
I can't connect my nexus 7 to any PC because my USB port is broken SO is there any chance I can root my device (boot loader is already unlocked)
Please help
Click to expand...
Click to collapse
Pretty sure there's a way because you could flash a recovery if your boot loader is unlocked and there's a tool to root your device just look in the android development section of the nexus 7
Sent from my HTC Sensation using xda app-developers app
Yes it is. But no matter how, you got to use a pc to unlock your bootloader 1st.
Sent from my Nexus 7 using Tapatalk 2
Jim Omar said:
I can't connect my nexus 7 to any PC because my USB port is broken SO is there any chance I can root my device (boot loader is already unlocked)
Please help
Click to expand...
Click to collapse
What pc do you have?
Wrong forum.
jcollier said:
Wrong forum.
Click to expand...
Click to collapse
Moved to correct one...
What you need is a "root exploit" that can be executed from the normal OS. (For instance kernel exploits).
Under the presumption that a root shell can be obtained you can simply use a "dd" command to write the raw partition for the recovery. The way this normally works is that you run an exploit from a terminal emulator, and if the exploit succeeds (gains root privilege) it exec's a root shell. From there it's a single command ("dd") to writing to the root-owned block device (e.g. recovery partition) with a replacement recovery image file.
The problem with devices whose manufacturer provides an easy route to flashing - e.g. an "unlocked" or "S-OFF" bootloader (as with the Nexus 7) - is that nobody bothers to go looking for root exploits for that device; they just take the course of least resistance for rooting, and move on to ROM building, customization, or other tweaking... they don't spend time looking for yet another rooting method.
I guess what I am saying is that you are probably on your own & need to figure out how to use a NDK (or similar) cross-compiling toolchain to compile native binary exploits and attempt to use them.
Note there is a recent exploit for a JellyBean device: the Moto Atrix HD - an Arm v7 (Snapdragon MSM8960) processor. I don't know what the root-exploit binary ("pwn") does in that case - it is possible that it leverages a recent kernel exploit. It is also possible that the same exploit has already been patched in the kernel on your tablet.
good luck
OK.... but what about wireless adb ?
Jim Omar said:
OK.... but what about wireless adb ?
Click to expand...
Click to collapse
AFAIK that requires root
You could use another Android device that supports USB otg and has the arm fastboot binary installed.
Sent from my Nexus 7 using Tapatalk HD
Jim Omar said:
OK.... but what about wireless adb ?
Click to expand...
Click to collapse
What about it? At best that gets you an unprivileged shell on an unrooted device - the same result as using a terminal emulator. (If you get wireless adb to work, it might be convenient for transferring files or side loading non-market apps, but really nothing that can not be accomplished with other means, e.g. emailing yourself zipped-up files)
korockinout13 said:
You could use another Android device that supports USB otg and has the arm fastboot binary installed.
Click to expand...
Click to collapse
How exactly does that overcome a damaged USB port on the N7?
@Jim Omar
How are you charging the device - using a dock?
Yes I change the device using a dock
korockinout13 said:
You could use another Android device that supports USB otg and has the arm fastboot binary installed.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Could you please explain further
---------- Post added at 05:37 AM ---------- Previous post was at 05:27 AM ----------
How can I do that " use another Android device that supports USB otg and has the arm fastboot binary installed."
Mashhoor Itayem said:
Could you please explain further
---------- Post added at 05:37 AM ---------- Previous post was at 05:27 AM ----------
How can I do that " use another Android device that supports USB otg and has the arm fastboot binary installed."
Click to expand...
Click to collapse
Sure... the Nexus 7 supports USB-OTG, so using a USB-OTG cable the Nexus 7 can connect to and charge other devices. Since the adb binary is included in android, the Nexus can send adb commands over USB to other devices just like a pc would. It doesn't have fastboot support by default, but you can simply add a fastboot binary to /system/bin/. To get it, do a search for "arm fastboot binary" and place it in your device's above directory. Once installed correctly on the host device, it will be able to send fastboot commands to connected devices.
Sent from my Nexus 4 using xda premium
OTG stuck Nexus
Hi, your solution would be perfect if my N7 (2012) were not stuck in OTG mode! Is there a way to switch modes?
Thanks in advance!
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d15b4f85c0611
SIGNING - not defined yet
LOCK STATE - UNLOCKED
Related
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
jasonmiracle said:
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
Click to expand...
Click to collapse
Hi if you're using the Android sdk and it's all configured properly then make sure that tools and platform tools are up to date. rev 21.1. It's in a separate category in the sdk manager to the base sdk.
jasonmiracle said:
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
Click to expand...
Click to collapse
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
Click to expand...
Click to collapse
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
DrFredPhD said:
Hi if you're using the Android sdk and it's all configured properly then make sure that tools and platform tools are up to date. rev 21.1. It's in a separate category in the sdk manager to the base sdk.
Click to expand...
Click to collapse
yup it is r21.1 i checked it... in fact i downloaded all components in android sdk and they are all updated
thats why im puzzled why the adb still not updated(not detecting device)
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
Click to expand...
Click to collapse
thanks bryant, your first post helped
seems like we need to use the command prompt to let the pc know our device code?
just felt strange why google implement 4.2.2 update and not telling users to update their adb on their pc as well..
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
Click to expand...
Click to collapse
I finally managed thanks to you ..
✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪
EVERYBODY!
WE ARE BACK DUE TO POPULAR DEMAND!!!
Kwongger's All-In-One FLO Noob Root/Restore Kit FOR PC and Mac
YES! We are ADB FREE!!!
Why we are back:
I really feel accomplished when I acutally do the commands myself! Apparently so do others, we are back B****ES!
I felt that I didn't get the help I needed/wanted as a n00b on XDA, this is a new account FYI, so I like to make n00b kits with AWESOME instructions, ENJOY!!!
FYI: I want to provide the best possible support that I can (even though this is free)
DOWNLOAD v3
Hey! The ONE-CLICK/Restore update is currently uploading!
Instructions in post #2, Change-log in post #3.
DISCLAIMER:
By downloading the files, you accept the fact that I am NOT in anyway responsible for what YOU do to YOUR device, unless it starts shooting lasers at iOS devices, then all the credit is mine . Really,in all seriousness, this procedure is a BEGINNER procedure, I am simply providing instructions and TOOLS! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!!!
Manual ROOT Instructions!
(If you want One-Click, then Just double-click either the Flo ROOT by Kwongger.bat (to root) or the Flo RESTORE.bat for a out-of-box restoration!
I’ll make a video soonish.
Driver Installation!
To Install The Drivers Fresh
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to install the driver.
Follow the Instructions!
Upgrade Existing Drivers
Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to upgrade the driver
Follow the Instructions!
Click to expand...
Click to collapse
Unlocking The Boot Loader!
1. Enable USB Debugging on your Nexus 7 in Development Settings
2. Open yourself a Command Prompt (or Terminal for MAC) in the Kwongger Nexus 7 folder!
a. Hold down shift
b. Right Click in the folder
c. Click Open Command Window/Prompt here
3. Boot into the bootloader using:
Code:
adb reboot bootloader
!!!!!!!!!!!NOTICE!!!!!!!!!!!!!!!
The next step will FACTORY RESET your device!!!
4. Once it is in the bootloader, enter this:
Code:
fastboot oem unlock
5. It will now ask you if you do, in fact, want to unlock your bootloader. Use Volume up/down to select YES and hit power to Confirm.
6. Your Nexus 7 FHD now has an Unlocked Bootloader.
7. IMPORTANT:
Reboot the device!
Click to expand...
Click to collapse
Choose either TWRP or CWM!
Installing TWRP!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7twrp.img
note: if you change the name use that in the .img part
3. Done!!!
Installing Clockwork Mod Recovery!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7CWM.img
note: if you change the name use that in the .img part
3. Done!!!
Click to expand...
Click to collapse
Rooting on Android 4.3!!!
.01 Copy The SuperSU.zip to the internal storage of your device.
1. Boot in to your bootloader and use the volume keys to select Recovery and use the Power button to confirm.
1a. RECOMMENDED: Tap BACKUP and Swype to confirm to make a backup of your current, UNROOTED n7.
2. Tap INSTALL.
3. Navigate to where you put the SuperSU.zip
4. Tap the zip.
5. Swype to confirm the flash!
6. If all goes well (no reason that I know that it shouldn’t) YOUR NEXUS 7 IS ROOTED!!!!
Click to expand...
Click to collapse
CONGRATS!!!!!!!!!!!!!
v1
Nothing New! This is 1.0
Click to expand...
Click to collapse
v2
I updated the Fastboot and ADB because some people were having some issues, it seems to have fixed the issues.
Click to expand...
Click to collapse
v3
I added the ever popular Mac Support! AND Clockwork Mod Recover, I don't know it is touch or not XD, could someone check? Just type
Code:
fastboot boot recovery nexus7CWM.img
and let me know! Thanks in advance.
Click to expand...
Click to collapse
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
That's weird. I will update it.
Sent from my HTCONE using XDA Premium HD app
Actually!
Are you on 32bit? I included 64bit.
I like that you moved it to General!!!
I always thought that the DEVELOPMENT threads should be only used for KERNELS/ROMS
THANK YOU
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
EvanVanVan said:
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
Click to expand...
Click to collapse
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Kwongger said:
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Click to expand...
Click to collapse
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
EvanVanVan said:
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Click to expand...
Click to collapse
AWESOME!!!!!!!!!!
I feel better now XD
jmill75 said:
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
Click to expand...
Click to collapse
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Kwongger said:
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Click to expand...
Click to collapse
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
RubenRybnik said:
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
Click to expand...
Click to collapse
Thanks! I will find it and add it to the instructions with credit.
Sent from my HTCONE using XDA Premium HD app
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
androidfr33k said:
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
Click to expand...
Click to collapse
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Looks like SuperSU came with the TWRP image(no need to copy it over separately). I tried to reboot from TWRP after updating the recovery and it forced me to flash SuperSU to root.
Nxxx said:
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Click to expand...
Click to collapse
I included Mac ADB... But not fastboot, you would need Fastboot as well, i'll get a Mac pack up tonight.
disregard....
working great! thanks OP
Hello,
My N4 is soft-bricked. Well, hopefully that's all it is.
I want to sideload a ROM onto it, via Mac OS X 10.9.3
I have found plenty of instructions on how to do that with a Mac.
But I can't get ADB or fastboot to see the device.
When I go to the system information on this Mac and looked at the USB devices, I see the Nexus there... along with its serial number, etc. But in Terminal I get a device not found error in ADB and nothing at all in fastboot.
It is my understanding I don't need to install any special drivers on Mac for it to detect the device. Is that correct?
If not, does any one have any suggestions on how I might get this device connected properly?
Thank you...
With further research, I have made some progress. I found this: http://stackoverflow.com/a/7169048
It says:
Also, if that does not work, check to see if the device shows up under USB in the System Profiler (included in OS X). If it is showing up there, but not in ADB, try adding the USB Vendor ID of the phone to ~/.android/adb_usb.ini
This file can be created if it does not already exist. The Vendor ID of the Nexus S is 0x18d1. Please make sure the last line of the file is a Vendor ID, do not leave a blank line at the end.
Click to expand...
Click to collapse
After doing that, I can now see my N4 listed. Well, at least it does when I am in recovery mode.
Now I shall see if I can make some progress with pushing a ROM to this thing (I am new to all this, so I'll see how this goes...)
Can you get to the bootloader screen? Only there fastboot will work.
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
coolqf said:
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks. I have a VM on this Mac... so i'll try doing this through that.
AndroidWelcome said:
Thanks. I have a VM on this Mac... so i'll try doing this through that.
Click to expand...
Click to collapse
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Thanks
coolqf said:
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Click to expand...
Click to collapse
Sorry I never replied. Thank you. I got it sorted. Nice to have my N4 up and running again.
I have managed to boot ubuntu successfully from usb. I have not installed just ran a live session. There was no sound, no touch and no internal wireless though a wireless usb stick worked fine.
https://youtu.be/KmDWoKvqodk
Sorry about the crappy video! It is slow to boot, probably because of the useless usb stick. I used. Also a powered hub was a must.
I also tried booting a windows 10 winpe img. It started loading but failed with bluescreen. This also happened with a windows to go usb stick that boots fine on my other machines. Problem seems to be with bios, have tried many things but nothing seemed to help. The error was...
ACPI_BIOS_ERROR
All versions of linux that I have successfully booted have no sound, touchscreen, screen rotation.
Also the ubuntU version I used was one tweaked for cherrytrail devices by linuxium, the standard one seemed to have kernel panic. The iso can be found here......
http://linuxiumcomau.blogspot.com/2016/10/running-ubuntu-on-intel-bay-trail-and.html
To get linuxium to boot I deleted "quiet splash" from grub.cfg and replaced with "nomodeset".
Also found another tweaked version and this one has working wifi out of the box, also it boots a little faster. Can be found here.....
http://xjesus.net/xjubuntu/xjubunta...izable-distro-based-on-xubuntu-14-04-64-bits/
To get xjubuntab to boot I deleted "quiet splash" from grub.cfg and replaced with "i915.modeset=0"
Sound--
Looks like sound might be an issue
https://ubuntu-mate.community/t/intel-22b8-sound-chip-no-soundcard-found-on-hp-x2-210-g2/10673
Although a pair of usb headphones worked fine in both distros so I am guessing that would include usb soundcards.
To get wifi working in linuxiums distro...
Install...
https://launchpad.net/ubuntu/+sourc...d/9020816/+files/linux-firmware_1.156_all.deb
Download, right click and install. Then..
sudo apt-get purge bcmwl-kernel-source
sudo modprobe -r brcmfmac
sudo modprobe brcmfmac
Mint 18 boots with the nomodeset flag....Wifi works out of the box. Still no touch or sound.
Android x86cm boots with nomodeset flag....same as above, wifi works, no sound, touch or rotation.
Touchscreen....
From what I can gather from Android the touch screen identifies as Hideep and is working as /dev/input/event3. I could not get any response from any /dev/input/event* in linux. Not being a linux wiz I can only guess this means there is no kernel module for the touchscreen. Though I did find this on github, its android stuff don't know if its any help really....
https://github.com/alexzeitgeist/YT2/
WARNING!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR TABLET!!!
Here is some instructions to get this going.
I am going to suggest you only try this if you are not a complete novice.
Let me stress again that you try this at your own risk. Be careful in the bios as you don't want to do anything to create a nice paperweight.
Manual boot to bios,
Try this at your own risk!!!!
This is magic code from Microsoft apparently. Feel free to google it.
These commands need entering one by one from adb shell. They need to be exactly right!!!!!!!!!!!
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
reboot
Tablet should boot to bios but you might need to manuall turn it back on, you can navigate the bios with the buttons. POWER=enter, vol+/- =navigate menus and long press vol+=Esc.
If you have TWRP recovery installed; after using the commands from adb once the reboot to bios option in the TWRP reboot menu should work, so next time you want to boot from bios just reboot from twrp.
To get keyboard and usb boot support, in bios
Device manager......
System setup........
android.......
Uefi secure BOOT=disable.
South cluster configuration.......
Usb configuration.....
default drd CONFIG=hostmode
Usb VBUS=on.
that's it save changes and exit. Next time you boot to bios you can use keyboard connected via otg to use bios. You can also select next boot device in bios boot manager.
If you want to be able to interupt boot process to select boot device also disable fast boot under boot category in bios . This will mean you get a black screen with progress bar on power on but allows use f7 to select boot device.
After booting another os from usb it often takes 3 boots to get back to android, don't panic.
Oh and lastly a powered usb hub is needed needed if you want to use mouse and keyboard in linux etc.
Sent from my Nexus 6P using Tapatalk
Love to see this working with no bugs :good:
EDIT:
did you use a unmodified iso of ubuntu or did you have to do something to it?
Qcraft said:
Love to see this working with no bugs :good:
EDIT:
did you use a unmodified iso of ubuntu or did you have to do something to it?
Click to expand...
Click to collapse
I used a version that was already modified by linuxium, he has added alot of stuff to get it working on intel compute sticks.
I also had to add a "nomodeset" flag to get it to boot.
Sent from my Nexus 6P using Tapatalk
So would it work on the 2gb tab 3?
Qcraft said:
So would it work on the 2gb tab 3?
Click to expand...
Click to collapse
I don't see why not. I should warn you that changes have to be made in the bios to allow usb booting. I never managed this on my 2GB version but the bios does look the same.
Sent from my Nexus 6P using Tapatalk
Can you post the link to the place that you found the iso?
Qcraft said:
Can you post the link to the place that you found the iso?
Click to expand...
Click to collapse
http://linuxiumcomau.blogspot.co.uk/2016/10/running-ubuntu-on-intel-bay-trail-and.html?m=1
Sent from my Nexus 6P using Tapatalk
Thanks
Updated first post a little.
Sent from my Lenovo YT3-X90F using Tapatalk
Added some instructions to first post. This has worked for me but do be careful when playing around with your bios. I accept no responsibility for any damage.
Sent from my Nexus 6P using Tapatalk
it is just an emulating i used to run windows ubuntu kali linux windows 7 with the limbo app
bouyhy01 said:
it is just an emulating i used to run windows ubuntu kali linux windows 7 with the limbo app
Click to expand...
Click to collapse
No it's native boot.
Sent from my F5121 using Tapatalk
joesnose said:
I used a version that was already modified by linuxium, he has added alot of stuff to get it working on intel compute sticks.
I also had to add a "nomodeset" flag to get it to boot.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hi,
Do You know how to make bootable pendrive from Windows?
I've tried many configs but always get message "Certificate Validation Error!!" (or sth like that)
Any suggestions?
(sorry for my bad english)
I use "rufus" and "unetbootin".
Sent from my F5121 using Tapatalk
joesnose said:
I use "rufus" and "unetbootin".
Sent from my F5121 using Tapatalk
Click to expand...
Click to collapse
which ISO file you used?
PSkrp said:
which ISO file you used?
Click to expand...
Click to collapse
I have used many. Most just need the nomodeset flag adding to get them to boot.
Sent from my F5121 using Tapatalk
Can you provide me the magisk root plz
bouyhy01 said:
Can you provide me the magisk root plz
Click to expand...
Click to collapse
Slightly off topic. Lol
Look here for magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my F5121 using Tapatalk
Any news to install, boot other OS with full working tablet?
Hi
Is this (link bellow) an opportunity for our tablet?
Windows on ARM
Anyone get ADB working? I'm getting a no permissions (udev rules) on my linux machine. I'm guessing we need to add the device into udev
EDIT: Solution for Ubuntu/Linux here: https://forum.xda-developers.com/showpost.php?p=73619079&postcount=20
hmm it works on my Mac though..
did you use Sudo?
stewa2jm said:
did you use Sudo?
Click to expand...
Click to collapse
Yeah, it's not working.. I tried adding the dev in my android.rules file and still nothing. I'm going to play with it more now
Sent from my PH-1 using Tapatalk
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
stewa2jm said:
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
Click to expand...
Click to collapse
I'm always on the latest version since I do a lot of Android development. I don't get why it's not working.. I've had to add devices in udev so many times, never did it give me an issue before. I'll see if I can figure it out though
Sent from my PH-1 using Tapatalk
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
IM0001 said:
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
Click to expand...
Click to collapse
Really? Lol I did mention it works on my Mac, so yeah.. It's turned on.. I've even tried turning it off and then on again. [emoji1] [emoji1] [emoji1] [emoji1]
stewa2jm said:
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
Click to expand...
Click to collapse
Will do!
Sent from my PH-1 using Tapatalk
any idea whats causing adb to not work?
drocny87 said:
I found a work-a-round to transfer your files from one phone to the Essential.
create a folder on your desktop and copy and paste all files you want transferred to the PH1. Once you have completed that just copy and paste those files from that folder to the phone.
Click to expand...
Click to collapse
wow, an extremely obvious solution to a problem no one asked about and has nothing to do with this thread!!
I've got ADB to connect somewhat. Instead of cd\sdk\platform-tools just run cd\sdk. ADB devices shows my phone, but once I ADB reboot bootloader, it will boot into the bootloader, but that's it.
I can't get it to work at all windows 10
Sent from my PH-1 using Tapatalk
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
skw5115 said:
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
Click to expand...
Click to collapse
What is your usb setting? Charging, file transfer?
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
I tried on both already
Sent from my PH-1 using Tapatalk
I got ADB working on linux. You need to add this to your 51-android.rules
#Essential
SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="plugdev"
I still can't get fastboot to work yet though. To get it to work I need to run: sudo $(which fastboot) devices
I'm going to play around with it more to see if I can get it to work just using fastboot devices
ADB is working on Windows 10, but as mentioned above, fastboot isn't recognized. Can't unlock the effing bootloader without that dammit.
---------- Post added at 08:20 PM ---------- Previous post was at 08:14 PM ----------
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
File transfer
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
skw5115 said:
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
Click to expand...
Click to collapse
Same here, just manually installed Google USB Driver and installed it as "Fastboot Interface" and it worked.
Ok I got adb and fastboot both working on Ubuntu/Linux now. Instead of adding the line I posted in my previous post just run this:
sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
Then
sudo service udev restart
Then ubplug your device if it's plugged in via USB and then plug it back in. adb works as well as fastboot