Related
I had been using adb successfully, then it stopped working.
adb devices would only report no devices.
Finally I reviewed the runmefirst.bat from the rooting howto and noticed there is a check in there for
"%userprofile%\.android\adb_usb.ini"
This file needs to exist and it needs to contain the following
0x2080
Once I updated that ini file adb started working again.
chupper said:
I had been using adb successfully, then it stopped working.
adb devices would only report no devices.
Click to expand...
Click to collapse
In my case, I'm connecting my NT for the first time and the command adb devices doesn't show anything
chupper said:
Finally I reviewed the runmefirst.bat from the rooting howto and noticed there is a check in there for
Click to expand...
Click to collapse
where is this file "runmefirst.bat" my the extension i take it that it is a windows batch file, Since i'm running UbuntuPangolin which file should i refer to..
chupper said:
"%userprofile%\.android\adb_usb.ini"
Click to expand...
Click to collapse
Do i need to create this file manually, Coz i didn't find it Under my $HOME/ and is the file same for Linux(Ubuntu) too?
chupper said:
This file needs to exist and it needs to contain the following
0x2080
Click to expand...
Click to collapse
I understand that this number here, is vendor Id which i saw and followed the instructions from 51-android-rules(codeDOTgoogleDOTcom)
Can you let me know whats going wrong with my NT, even after following the instructions form the above link. Do i need to follow your instructions too? Please Help me....
I think you might have better luck if you posted your questions in the nook tablet forum. This is the forum for the nook color.
Sent from my NookColor using xda premium
My partner has a bricked A500. It will NOT boot so any utilities utilising adb/dmesg fail. I can boot into fastboot mode (v0.03.11-ICS) but fastboot returns USB write errors stating invalid partition format "." So, I assume I have to use nvFlash to re-write the partition table but this still requires the SBK that I can not generate as I do not know what my CPUID is.
I have read so many threads all offering tweaked variations of the same process but I haven't found as yet a definitive how-to on re-creating your CPUID/SBK on a bricked device as they all assume you either know your CPUID or the tablet stills boots so you can retrieve it easily.
Does anyone have any links to resources to assist? I currently can boot into fastboot and APXmode. Attempts to factory reset seem to kick off OK but then fail with errors erasing data/cache etc... I have both windows/linux and the tablet is recognized in APX/fastboot mode on both OS's.
Thanks
1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE
Error: Failed to open device
Dr.GM said:
1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE
Click to expand...
Click to collapse
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!
dishoom said:
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!
Click to expand...
Click to collapse
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.
Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse
dishoom said:
Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse
Well, if I'm not mistaken, it should be 16. You can try it either way.
Click to expand...
Click to collapse
SUCCESS!!
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:
dishoom said:
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:
Click to expand...
Click to collapse
Speaking for the rest of the mentions, you are most welcome.
EDIT:
Now you can follow the same process into rogro82's kernel, thanks to Forzaferrarileo. Note that you can just flash the kernel, if you already put it to work with sp3dev's kernel. There's no need to repeat all process.
I've, also, changed some structures for better visualization.
This tutorial is using the sp3dev's precompiled kernel from here or rogro82's precompiled kernel from here. If you want to use rogro82's from scratch or from internal storage, please look, also, some instructions at here. Please note that you will have to build that kernel from sources before proceed. You should be able to use internal storage also, with some changes into this tutorial.
I used a phisical usb keyboard into this tutorial, but bodhi offers an onscreen keyboard into tablet profile. To change into this profile, look at here.
It's partially based into this tutorial. I'll refer to number of steps on that, so please open it. Please read everything before doing anything, and make sure you have no doubts about the process before doing anything. I'm not responsable if it damages your tablet!
First of all, download the Bodhi rootfs from here.
Then, run the first 3 steps from the tutorial above. Please note that if you'll run the rogro82's kernel, the step 2 should be flashing that kernel. For infos about how to flash the second kernel image, please read this thread's first post.
After, extract the Bodhi rootfs into the ext4 partition from your sdcard (I needed to be logged as root or use sudo for doing this step). Make sure to extract directly into the root of the partition (the result of a ls into the root of the partition should be just like running ls /).
Now, you need to donwload the zip file from step 6 from the tutorial. Note that it's not needed to install the packages asked by the step 6, just extract the donwloaded files and copy them into your sdcard's /lib/firmware folder. I just copied the brcm folder into /lib/firmware/brcm and it worked.
Now you are able to boot into the image. Put sdcard into the tablet and then boot from second kernel (hold VOL UP while powering on until it shows bootmenu and select boot into second kernel).
After complete booting, you should have the E17 home screen. For tutorials about this interface, please look into Bodhi website.
For being able to connect into wifi, I needed to open terminology (terminal application into bodhi) and run, as root, the following. Please note that it may not be necessary, but recommended:
- rfkill unblock all
- ifconfig
Now please see what number your wifi got loaded, for me, it was wlan2. I'll call it wlanx, so just change x for the number you got.
- ifconfig wlanx up
To make sure it worked, run "iwlist wlanx scan". It should bring some network details into terminology.
Now open wicd, open preferences and make sure the wifi network is correctly set into wlanx. The default value is wlan0. Then, close preferences and click into reload. Now you should be able to select your network, set up the network preferences and then connect into it.
Now you should be able to install everything you want. As I read, bodhi uses a debian base for armhf version, so you can install anything you can install from debian. Chromium web browser is broken, and firefox is named iceweasel. The default midori web browser works fine, but I personally prefer iceweasel.
Thanks:
sp3dev, rogro82, Kevin Roscom, Forzaferrarileo (if I forgot someone, please tell me, I'll put your name here!)
i'd love to try this! does this run fairly well?:good:
For me it does. I have a class 10 sdcard.
guimendes said:
For me it does. I have a class 10 sdcard.
Click to expand...
Click to collapse
root password?
Tautvaldas said:
root password?
Click to expand...
Click to collapse
Please take a look at here: http://jeffhoogland.blogspot.nl/2012/12/bodhi-linux-armhf-rootfs.html
You can use sudo bash to root access. The password is bodhilinux. Then you can set root password.
Hey this is my first time installing linux on a tablet. Ive got the partitioned sd card, rootfs, kernel ready to go. just not famaliar with how to flash the kernel. Could you maybe give me an idea of those steps? For a first timer as far as android is concerned, the instructions can be a little vague. Thanks
adrock74 said:
Hey this is my first time installing linux on a tablet. Ive got the partitioned sd card, rootfs, kernel ready to go. just not famaliar with how to flash the kernel. Could you maybe give me an idea of those steps? For a first timer as far as android is concerned, the instructions can be a little vague. Thanks
Click to expand...
Click to collapse
Please, first, make sure you're using this bootloader for dualboot. Into the thread there are all instructions for flashing the kernel into secboot, on dualboot section, into first post.
Ive been on v8 unlbootloader for awhile. Just never flashed a sec kernel before.
adrock74 said:
Ive been on v8 unlbootloader for awhile. Just never flashed a sec kernel before.
Click to expand...
Click to collapse
download the fastboot package ( from xda , or search on google ) , next connect the tablet with usb to the pc , reboot the tablet with the bootloader menu and select fastboot ...... the pc will install drivers , when it finish , go in the fastboot folder click SHIFT + right click and select "open command window here " and type this :
fastboot flash secboot <nameofkernel> ex : fastboot flash secboot boot.img
Forzaferrarileo said:
download the fastboot package ( from xda , or search on google ) , next connect the tablet with usb to the pc , reboot the tablet with the bootloader menu and select fastboot ...... the pc will install drivers , when it finish , go in the fastboot folder click SHIFT + right click and select "open command window here " and type this :
fastboot flash secboot <nameofkernel> ex : fastboot flash secboot boot.img
Click to expand...
Click to collapse
Thanks for the reply! Ive flashed this tablet seven ways to sunday within android, but this is kinda new to me. Recently installed 12.04 on my desktop as my intro to linux without a hiccup. I cant seem to get the tablet to respond to my computer. Have the sd card setup ready to go, terminal only says file does not exist ( in regards to secboot) should sd be in tablet or usb? Ive been at it all day. Should i rename anything? Thanks again.
---------- Post added at 04:43 PM ---------- Previous post was at 04:35 PM ----------
I Simply cant seem to get the kernel flashed. Once i get past that, i believe its smooth sailing..
adrock74 said:
Thanks for the reply! Ive flashed this tablet seven ways to sunday within android, but this is kinda new to me. Recently installed 12.04 on my desktop as my intro to linux without a hiccup. I cant seem to get the tablet to respond to my computer. Have the sd card setup ready to go, terminal only says file does not exist ( in regards to secboot) should sd be in tablet or usb? Ive been at it all day. Should i rename anything? Thanks again.
---------- Post added at 04:43 PM ---------- Previous post was at 04:35 PM ----------
I Simply cant seem to get the kernel flashed. Once i get past that, i believe its smooth sailing..
Click to expand...
Click to collapse
Please look if fastboot recognized your tablet. Run fastboot devices. If there's an answer, then your tablet was recognized. It can be missing drivers. From acer site it's possible to find the correct drivers.
ok. so not having the acer drivers seems to be my issue. But, Im trying to do this using my pc running ubuntu, and I'm not sure how to get the acer drivers installed on it. I'm sure there is a trick, but the downloads are for windows. And also the downloads are for honeycomb and ics and im running 4.2.2.
Well I cannot help you installing drivers into ubuntu, I made it into Windows.
on android terminal emulator:
cat /proc/mounts
make sure that data is on /dev/block/mmcblk0p8 not p7
if so then:
dd if=your_second_boot.img of=/dev/block/mmcblk0p7
do it within android, not within linux or initial ramdisk console on you tablet, because linux recognize data as /dev/mmcblk0p7. sorry for bad English.
Tautvaldas said:
on android terminal emulator:
cat /proc/mounts
make sure that data is on /dev/block/mmcblk0p8 not p7
if so then:
dd if=your_second_boot.img of=/dev/block/mmcblk0p7
do it within android, not within linux or initial ramdisk console on you tablet, because linux recognize data as /dev/mmcblk0p7. sorry for bad English.
Click to expand...
Click to collapse
thanks for the response, what will this be doing??
adrock74 said:
thanks for the response, what will this be doing??
Click to expand...
Click to collapse
It'll flash the kernel into the correct partition, via android.
guimendes said:
It'll flash the kernel into the correct partition, via android.
Click to expand...
Click to collapse
ok gotcha. Sorry to be a bother, but i want to do this. Right now ive got my kernel and rootfs on a partitioned sd card in my extsd slot. If I flash the kernel using terminal, where should it be?
adrock74 said:
ok gotcha. Sorry to be a bother, but i want to do this. Right now ive got my kernel and rootfs on a partitioned sd card in my extsd slot. If I flash the kernel using terminal, where should it be?
Click to expand...
Click to collapse
If you follow strict what Tautvaldas said, it'll be placed in the right place for dualbooting, the same if you use fastboot tool.
Thanks for your help guys. But mixing and matching this and that, i give up. Ive flashed the sh*t out of this tab, but without a unified tutorial, i cant make sense of this. Ive been running linux on my pc and laptop, so this isnt foreign to me, but i need a more straight forward tutorial. Thanks though again. We all have to learn sometime:good:
I ran a dist-upgrade on it and my wifi now seems broken - rfkill can unblock it but ifconfig returns SIOsomething something error, permission denied. Ideas?
Guide to making a Raring Ubuntu-core image on a Linux PC/laptop (NOT a virtual machine (VM)) for the purpose of installing it on your TF101.
All credit goes to the time and consideration x3maniac took to assist me with doing this!
OP for Tubutnu by x3maniac
This guide allows you to create a CORE Ubuntu image on your Linux box and then install it using the Tubuntu application for Windows. ***Please note, a CORE image does not contain a GUI. The gnome-core guide in the next link will walk you through the steps of installing the gnome-core GUI after you have made your fresh Raring Ubuntu-Core image.***
http://forum.xda-developers.com/showthread.php?p=37803357
***Why do I want to do this when the OP by x3maniac already has a Raring image for download? This guide is helping you make your own UPDATED image. There are daily builds of Raring and the image in the OP by x3maniac is over 2 months old as of this last update to this post.***
Please note that I am using a stock Ubuntu 12.10 laptop. I believe any variant of Ubuntu on a laptop or PC should work with this guide just fine.
Download the files first and then open Terminal to input our commands.
Download: http://cdimage.ubuntu.com/ubuntu-core/daily/current/raring-core-armhf.tar.gz
(You may optionally choose any date time from the Ubuntu-core folders. Ensure you are using the armhf tar.gz file.
Download (Recommended): https://www.dropbox.com/s/dqn9aa94oeju9kf/modules.tar.gz
Alternate Download: http://goo.im/dev/x3maniac/mod_firm_ext.zip
Alternate Download: http://www.novaspirit.com/downloads/mod_firm_ext.zip
After the downloads are complete, open Terminal and let’s get the image built!
A side note, I did not know that using ~ represented the user folder so if you do great, if not it will help you understand that /home/thomas can be represented using ~. So any subfolders of /home/thomas are included using the ~. I will specify my full paths and you can substitute the directories you wish to use. (Linux is still new to me too, I know enough to be dangerous!)
1. mkdir /home/thomas/images/ubuntu-raring
2. cd /home/thomas/images/ubuntu-raring
3. sudo apt-get install qemu
4. sudo apt-get install qemu-user-static
5. Now type this command: qemu-img create raring.img 200M
a.The Ubuntu Raring core image is approximately 186MB. So you understand at 186MB you only have 14MB available of extra stuff you can put into the image. You can resize up later but never down. You may specify any MB size you wish to use for the image. Experiment later, for now just make it 200M.
6. fdisk raring.img (you will see an error about invalid flag, this is ok, step 7 below is w for write, do proceed to step 7)
7. Type w to quit
8. Determine the file system you want (I used ext4)
a. Now type: mkfs.ext4 raring.img (according to config file of Tubuntu app, the partition is set up as ext3, you can use that as well)
b. A warning that your image is not a block special device (when choosing ext4) hit Y to proceed.
c. From /Ubuntu-raring directory type: mkdir mount
9. Now type: sudo mount –o loop ./raring.img ./mount
10. Now type: cd mount
10a. Now type: ls (you are only listing the mount directory to verify you have the lost+found directory) Go up one directory to /home/thomas/images/ubuntu-raring
11. Now type: cp /home/thomas/Downloads/raring-core-armhf.tar.gz /home/thomas/images/ubuntu-raring
12. Now type: sudo tar xvvf raring-core-armhf.tar.gz –C ./mount (you should not be in the mount directory)
13. Now type: sudo tar xvvf modules.tar.gz -C ./mount (you should not be in the mount directory)
14. sudo cp /usr/bin/qemu-arm-static /home/thomas/images/ubuntu-raring/mount/usr/bin (enter)
15. Now type: sudo chroot mount (if successful you will see /#)
16. Now type: passwd and make a password and confirm it.
17. Now type: exit
18. Now type: sudo umount ./mount
19. You should now be in the /home/thomas/images/ubuntu-raring/ directory. From here use the ls command and see your raring.img file.
20. You will need to copy this file your Windows box and use the Tubuntu installation application OR wheelie and nvflash commands. (Wheelie and nvflash commands are for more advanced users).
21. Click on this link for the next guide: http://forum.xda-developers.com/showthread.php?p=37803357
Hi, I have no problems creating the image and mounting it. But when chrooted:
apt-get update
0% [Working]qemu: Unsupported syscall: 374
Err http://ports.ubuntu.com raring Release.gpg
Something wicked happened resolving 'ports.ubuntu.com:80' (-11 - System error)...
I am on Ubuntu 12.10 64-bit. What could it be? qemu & qemu-user-static installed, qemu-arm-static copied...
Thank you and sorry for my CZ-english
onmail said:
Hi, I have no problems creating the image and mounting it. But when chrooted:
apt-get update
0% [Working]qemu: Unsupported syscall: 374
Err http://ports.ubuntu.com raring Release.gpg
Something wicked happened resolving 'ports.ubuntu.com:80' (-11 - System error)...
I am on Ubuntu 12.10 64-bit. What could it be? qemu & qemu-user-static installed, qemu-arm-static copied...
Thank you and sorry for my CZ-english
Click to expand...
Click to collapse
I need to update my guide. After the image is created on your Linux box you then install it on your tablet using tubuntu application. From the tab is where you run apt get commands. Sorry about that.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
I need to update my guide. After the image is created on your Linux box you then install it on your tablet using tubuntu application. From the tab is where you run apt get commands. Sorry about that.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Oh, I see, but I think I will not be able to install apt-utils wpasupplicant if the wlan0 adapter is not working (I mean when wpasupplicant is not installed in the image).
onmail said:
Oh, I see, but I think I will not be able to install apt-utils wpasupplicant if the wlan0 adapter is not working (I mean when wpasupplicant is not installed in the image).
Click to expand...
Click to collapse
Yes you will because the core image has everything you need except the supplicant. You can make your own supplicant or copy from your working dual booted prime image of android. Let me try and update the guide later tonight.
Sent from my SGH-T999 using Tapatalk 2
onmail said:
Oh, I see, but I think I will not be able to install apt-utils wpasupplicant if the wlan0 adapter is not working (I mean when wpasupplicant is not installed in the image).
Click to expand...
Click to collapse
Ok, made several changes to my guide. Here's a couple things to note in case you missed them.
1. This guide helps you make an image of Raring Ubuntu-Core. This means there is no GUI and an additional post I have linked to for installing Gnome-Core (your actual desktop environment) for Raring.
2. After the Raring.img is made, you need to start on the Raring Gnome-Core guide and follow those instructions. That installation takes about 2 hours to download and answer questions because it is such a core install.
3. About the wifi, you will be using x3maniac's Tubuntu Windows installation application and starting from fresh with Prime Android and your new Raring image and if you follow the second guide it will walk you through setting up your wifi (do make sure you boot into Prime Android and set up your wifi first before booting to Raring.
4. Please familiarize yourself with the OP I have linked to for the x3maniac Tubuntu application.
It's not as hard as it may seem. After you do it a few times it's rather quick. Installing gnome-core by yourself is kind of slow and a bit tedious but the purpose of doing this was to have complete control of your image.
Later on if you are brave you can also build your own kernel as well and make changes. See my guide in my xda signature.
Hope this helps, thanks for using my guide. Hit the thanks button a couple of times and I'll make sure you get up and running.
TomTcom said:
Ok, made several changes to my guide. Here's a couple things to note in case you missed them.
1. This guide helps you make an image of Raring Ubuntu-Core. This means there is no GUI and an additional post I have linked to for installing Gnome-Core (your actual desktop environment) for Raring.
2. After the Raring.img is made, you need to start on the Raring Gnome-Core guide and follow those instructions. That installation takes about 2 hours to download and answer questions because it is such a core install.
3. About the wifi, you will be using x3maniac's Tubuntu Windows installation application and starting from fresh with Prime Android and your new Raring image and if you follow the second guide it will walk you through setting up your wifi (do make sure you boot into Prime Android and set up your wifi first before booting to Raring.
4. Please familiarize yourself with the OP I have linked to for the x3maniac Tubuntu application.
It's not as hard as it may seem. After you do it a few times it's rather quick. Installing gnome-core by yourself is kind of slow and a bit tedious but the purpose of doing this was to have complete control of your image.
Later on if you are brave you can also build your own kernel as well and make changes. See my guide in my xda signature.
Hope this helps, thanks for using my guide. Hit the thanks button a couple of times and I'll make sure you get up and running.
Click to expand...
Click to collapse
OK, thanks a lot, I will try. I have been playing with Tubuntu for some weeks and now I just started playing with building the image (and thinking about kernel...). Just now I am on Lubuntu (with xfce4 which I prefer) with 2.6 kernel and I am trying on my son's TF101 Raring with Gnome and 3.1 kernel. I am just thinking about the possibility when one system is "fine tuned" if it would be possible to copy it from one TF to the other one (I mean just the Linux partition).
onmail said:
Hi, I have no problems creating the image and mounting it. But when chrooted:
apt-get update
0% [Working]qemu: Unsupported syscall: 374
Err http://ports.ubuntu.com raring Release.gpg
Something wicked happened resolving 'ports.ubuntu.com:80' (-11 - System error)...
I am on Ubuntu 12.10 64-bit. What could it be? qemu & qemu-user-static installed, qemu-arm-static copied...
Thank you and sorry for my CZ-english
Click to expand...
Click to collapse
Replying to my own post because I must say - sorry, I am ehm an idiot... Because the only problem was - I have not edited the /etc/resolv.conf in the mount/etc directory. So now I can easily apt-get anything in the chroot! So it seems I can easily "prepare" an image with everything inside
onmail said:
Replying to my own post because I must say - sorry, I am ehm an idiot... Because the only problem was - I have not edited the /etc/resolv.conf in the mount/etc directory. So now I can easily apt-get anything in the chroot! So it seems I can easily "prepare" an image with everything inside
Click to expand...
Click to collapse
Did it work? I couldn't not without finding a way to inject VI into the image for editing the file. You can mess with permissions but it ultimately doesn't work from the Linux box.
If you are able to do it without the tab, post the instructions and I'll add it to my OP and give you the credit.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Did it work? I couldn't not without finding a way to inject VI into the image for editing the file. You can mess with permissions but it ultimately doesn't work from the Linux box.
If you are able to do it without the tab, post the instructions and I'll add it to my OP and give you the credit.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It works I am just in the middle of installing xubuntu-desktop... I have made a quick & dirty bash script which will help to set hostname for the new TF101, root password, make a new user with password and add him to sudo group, automatically enable all the deb repos (universe etc.), set cpu freqs in rc.local and install some usefull utils (sudo cpufrequtils bash-completion wpasupplicant nano mc net-tools). And there is a second script you can run on the first run on TF101 which will resize the linux partition to its limit, copy the wpa_supplicant.conf from the android partition and starts wlan0 I will send this to you asap but will test this first. Hope my English is understandable
onmail said:
It works I am just in the middle of installing xubuntu-desktop... I have made a quick & dirty bash script which will help to set hostname for the new TF101, root password, make a new user with password and add him to sudo group, automatically enable all the deb repos (universe etc.), set cpu freqs in rc.local and install some usefull utils (sudo cpufrequtils bash-completion wpasupplicant nano mc net-tools). And there is a second script you can run on the first run on TF101 which will resize the linux partition to its limit, copy the wpa_supplicant.conf from the android partition and starts wlan0 I will send this to you asap but will test this first. Hope my English is understandable
Click to expand...
Click to collapse
Xubuntu on raring is working without any problems. Now I would like to get the nvidia accelerated drivers working. I have tried 2 or 3 3.1 kernels but still without success. Googling for some help on compiling 3.1 kernel.
onmail said:
Xubuntu on raring is working without any problems. Now I would like to get the nvidia accelerated drivers working. I have tried 2 or 3 3.1 kernels but still without success. Googling for some help on compiling 3.1 kernel.
Click to expand...
Click to collapse
Awesome! If you go to the op for x3maniac, you can view his github that has 3.1 kernel source. Take a look and see of it helps.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Awesome! If you go to the op for x3maniac, you can view his github that has 3.1 kernel source. Take a look and see of it helps.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
By the way, I have instructions for compiling the 2.6.36 kernel in my xda signature if that helps you.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
By the way, I have instructions for compiling the 2.6.36 kernel in my xda signature if that helps you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I know, I have already checked that. The 2.6 kernel is ok but I would really like to see the nvidia drivers working...
Had an issue mounting raring.img in step 9, had to run sudo fsck.ext4 "path to file" afterwards it mounted smoothly, dont know why tho.
JoinTheRealms said:
Had an issue mounting raring.img in step 9, had to run sudo fsck.ext4 "path to file" afterwards it mounted smoothly, dont know why tho.
Click to expand...
Click to collapse
Hmmm...did step 8a work ok?
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Hmmm...did step 8a work ok?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Afaik it did, gave me the mentioned prompt, and finished without error. Might have something to do with me running a x64 vm ? as i wasnt able to chroot either. Im trying to get this running on my tf300t, but its alot different to installing it on the trusty tf101
Cheers for the guide tho, help me understand the whole process :good:
JoinTheRealms said:
Afaik it did, gave me the mentioned prompt, and finished without error. Might have something to do with me running a x64 vm ? as i wasnt able to chroot either. Im trying to get this running on my tf300t, but its alot different to installing it on the trusty tf101
Cheers for the guide tho, help me understand the whole process :good:
Click to expand...
Click to collapse
I believe our dev x3 mentioned there were differences on a VM so it probably has to do with that.
Glad the guide is helpful. Welcome!
Sent from my SGH-T999 using Tapatalk 2
Nice guide ! I just crated a 13.04 raring img. ( Used VM Kubuntu 12.04 )
Need some updates but nice
And there is a problem with actual release, wpa supplicant is not pre installed and now I'm in the begining of your second guide and cant set up wifi.
I had to download package with chroot, then install with my tab same for nano
Anyway, it's just FYI I dont really need help
Kingzak34 said:
Nice guide ! I just crated a 13.04 raring img. ( Used VM Kubuntu 12.04 )
Need some updates but nice
And there is a problem with actual release, wpa supplicant is not pre installed and now I'm in the begining of your second guide and cant set up wifi.
I had to download package with chroot, then install with my tab, and now it doesnt find iwlan0
Anyway, it's just FYI I dont really need help
Click to expand...
Click to collapse
This guide wasn't designed to use wifi, only to correctly package it for flashing 13.04 directly to the tab. The next guide adds the gui and requires your Android to be set up to copy over the wpa_supplicant file before executing those commands.
Onmail was able to script more changes to the image from "chroot" but I didn't go that far, he was able to get the supplicant and other abilities such as adding to the package better than I did.
Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT
This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.
How is this any easier than the original method....if anything this requires even more work
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.
psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP
Can this be used to inject Xposed as well for those of us with locked BLs.
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.
psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!
Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.
The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem
hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx
How to calculator extractly bs/seek/count ?
Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013
optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.
ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.
hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?