Related
Good evening, this is my first post and I'm really happy, I can finally boot a debian on my wildfire, for this I have been guided by manuals for the rest of htc.
As sure a lot of people wanting to play the first thing to do is upload it and explain how it starts, then we can go into details of how and why.
The startup script has a lot to improve and certainly there are some things that are no longer necessary, but I think the first thing is that everyone can enjoy, and after that I dedicate to improve them.
The only thing you need to modify in the phone is to get the root user, I personally used unrevoked for this, besides being very simple, makes available the backup utility nandroid among others, have not tried other methods but I think that any method that can get the root on the adb console, should work
The procedure is very easy and I give you everything you need:
- Compiled binary of busybox
- Start script
- Image file system for ARM Debian Lenny
- ADB download from the official website of android
- Unrevoked 3 there are many guides on how to do, practically only have to download and follow the instructions
Step 1
- Moving files to mobile
-Enter the abd console and create the folder /data/local/bin and /sdcard/debian
-Copy the image file on the sd folder (you can mount as massive storage mode)
-copy Busybox and boodeb.sh to the folder /data/local/bin, for this use
adb push busybox /data/local/bin
adb push bootdeb /data/local/bin
- Set the appropriate permissions, open adb shell and passed to root (in my case just do 'su' and accept the message I apacere on the mobile screen) and run
cd / data / local / bin
chmod 555. / busybox
chmod 555. / bootdeb.sh
Step 2
- Basically enjoy
- In a console as root run
cd /data/local/bin
./Busybox sh bootdeb.sh
and now you are in a debian shell ready to play and break, keep a clean copy of the image file this is the best rollback that I know.
to exit the chroot only do exit, and you can see a restart of the phone, this is to make everything fair, this probably is not necessary because I have noticed that everything was removed successfully, but for now better that way, and later i'll depurare the script to see what can i do.
I'll attach the files and if I have time I put a few catches, excuseme for errors, I will be watching the thread to respond to everything that Ican.
I'll put the filesystem image on mediafire, but is too slow, you can search for debian_aosp21_fisadev zip, it's the same image, i'll put the link when it end, now i go eat
Nice hack! Do you have any need for this or did you just do it because it could be done?
it's ok and running, later wil improve more eficient scripts
with this you can start playing, from this point you can start implementing the rest of guides for debian in G1, ect ... get X11 vnc I will try to bring my own apps server and mail server in my pocket
You stole my idea . Isn't it funny when two people think of the same thing at once and independently? I've also managed to run Debian on my wildfire. My method is much less sophisticated though. it wouldn't even need adb and soft root is perfectly sufficient.
What tool did you use to generate the image? I used debootstrap. Quite easy IMHO, once you have root and busybox binary. But that comes from Debian user.
As far as I can see, your method is more of a chroot than boot. IMHO, only loading your own kernel into the memory would constitute "booting".
xc1024 said:
You stole my idea . Isn't it funny when two people think of the same thing at once and independently? I've also managed to run Debian on my wildfire. My method is much less sophisticated though. it wouldn't even need adb and soft root is perfectly sufficient.
What tool did you use to generate the image? I used debootstrap. Quite easy IMHO, once you have root and busybox binary. But that comes from Debian user.
As far as I can see, your method is more of a chroot than boot. IMHO, only loading your own kernel into the memory would constitute "booting".
Click to expand...
Click to collapse
Well, it's normal, really starting in a chroot, but for me is a good starting point to playing. For me upload or not upload your own kernel is indifferent, with the current android kernel for now is sufficient, since it provides the necessary, currently i'm setting up a new image with debootstrap, initially I used the image posted in one of the G1 tutorial and the busybox binary too, if I find the url of the tutorial I put it.
Really is not necessary to use ADB, you can also do from a terminal on the phone, and as I said any method that allows root think it will be valid, but for me it is much more comfortable working on the pc and get rooted with ureboked.
My next steps are try to provide it with swap, graphical environment, ssh (done), vnc-server, webserver and mail server, refine the scripts and later, when get boring i try other things as dual boot, native filesystems etc ... and of course try to help some people to get running
For now I have enough to play a few days
as I promised, here is the links to donw my initial image filesystem of debian lenny,
h t t p : / / w w w . me d i a f i r e . c o m / ? l 9 t 6 i 2 0 y z 4 g o 7 5 8
h t t p : / / w w w . m e d i a f i r e . c o m / ? l 9 t 6 i 2 0 y z 4 g o 7 5 8
later i'll post links for new images with more things, only need replace the file and go playing to next level
sorry, but I can't post links, drop the espaces and go
everend said:
sorry, but I can't post links, drop the espaces and go
Click to expand...
Click to collapse
Here is the link made for you
Hope that helps
some sceenshots
some sceenshots
Really cool! Great work everend.
Will definetly follow this thread.
Now sawping on file is running, i'll upload the next image when finish the vnc setup and improbe some things in the script to sure the ending of chroot enviroment and i'll create one aditional script to make easy the use of terminal emulator on android, this script will do things as alter pach to get /data/local/bin and make some alias, and i'll post how to configure terminal emulator to autorun this.
thanks, i'm playing, i'm happy, let's play
Thanks a lot.
Before I want to do it but I can't to it hack!
Thanks
Keep your nice work!
:x
Sent from my HTC Wildfire using XDA App
X11 LXDE runnig!!!!
playing, playing
tremendous work! Now I just wish I could find a way to port linux or even better Android to a BlackBerry device!
It's dont work on CM!
Please optimize it for CM.
(and evered, please chek your PM!)
now, i'll resume this, but i can't test on CM because i use the original firmware + unrebocked on my phone.
THE DEBIAN IMAGE FILE IS LINKED HERE.
xc1024 said:
You stole my idea . Isn't it funny when two people think of the same thing at once and independently? I've also managed to run Debian on my wildfire. My method is much less sophisticated though. it wouldn't even need adb and soft root is perfectly sufficient.
What tool did you use to generate the image? I used debootstrap. Quite easy IMHO, once you have root and busybox binary. But that comes from Debian user.
As far as I can see, your method is more of a chroot than boot. IMHO, only loading your own kernel into the memory would constitute "booting".
Click to expand...
Click to collapse
Would you explain your simple method?
You can download it when click here!
http://wildfire.devs.parandserver.com/debian/debian_aosp21_fisadev.zip
You can download it when click here!
http://wildfire.devs.parandserver.co...21_fisadev.zip]
Click to expand...
Click to collapse
@MohammadN.
Are you able to boot the debian?
BACKTOP v0.00001
Click to expand...
Click to collapse
Alright, so this is a guide to finally get the backtrack 5 software running inside of webtop. It uses chroot and xterm to allow full access to the software contained within the backtrack 5 arm image.
Prerequisites:
CWM Installed:
For all version: http://forum.xda-developers.com/showthread.php?t=1138541
WebTopMOD installed:
For 2.3.4 go here: http://forum.xda-developers.com/showthread.php?t=1169457
For 1.8.3 go here: http://forum.xda-developers.com/showthread.php?t=1093790
You do not need to download the Debian disk image. Will we be using the backtrack disk image instead.
BusyBox Installed in /system/bin:
Downloaded "BusyBox Installer" from the app store.
BE SURE TO INSTALL IN /SYSTEM/BIN!
Click to expand...
Click to collapse
The Goods:
BackTop.zip:
Download and un-zip the attached files into /sdcard/bt
BackTop.zip
BackTrack 5 ARM Image:
PART 1 : Download Link : http://bit.ly/p1BT5
PART 2 : Download Link : http://bit.ly/BT5p2
PART 3 : Download Link : http://bit.ly/BT5p3
These download links are from the xperia backtrack project and where I took inspiration to get it working in webtop. After using 7z to unarchive just place bt.img in the /sdcard/bt folder. The archives other contents can be safely ignored.
Click to expand...
Click to collapse
What you should have by now:
WebTOPMOD for Atrix.
BusyBox Installed in /system/bin.
Downloaded scripts placed in the /sdcard/bt folder.
Downloaded bt.img placed in the /sdcard/bt folder.
Click to expand...
Click to collapse
Give it a go:
Step 0: Connect the phone to display/lapdock. Run webtop and wait for it to boot.
Step 1: Open LXTerminal from the dock and type "cd /sdcard/bt"
Step 2: To run BackTop type "sudo bash backtop"
You should be presented with a white xterm screen. You can now use all the utilities built into backtrack 5 with ease. You can even run the gnome desktop environment! (More on that bellow)
Click to expand...
Click to collapse
Running Gnome:
You first need to kill off all the webtop crap do this by typing the following in xterm.
"ps ax|grep awn|awk '{print $1}'|xargs kill"
"ps ax|grep panel|awk '{print $1}'|xargs kill"
Then start gnome by typing "gnome-session" in xterm.
Click to expand...
Click to collapse
Accessing sdcards:
You'll need to make two directories inside of backtrack /sdcard and /sdcard-ext to do this type:
"sudo mkdir /sdcard"
"sudo mkdir /sdcard-etc"
Once you've done this simply reboot your phone and restart BackTop.
Click to expand...
Click to collapse
Known issues:
ettercap causes network connectivity inside of webtop to fail.
If something does go terribly wrong you can always force quit backtop with the following command:
"sudo bash /sdcard/bt/forcekillbt"
Click to expand...
Click to collapse
Cool stuff, I'll definitely check this out. Moved to development.
mate I don't have webtop but as a network engineer I'm giving this a big thumbs up, super cool to have a pen testing suite in your phone!!!
reserved #10Chars
It might just be me but do your links work? Specifically the http://bit/ly ....etc. thanks
Sent from my MB860 using XDA App
edit: had a smart attck and everything is tip top...well done sir...thx!!
that is the most metal thing ever
I'd prefer it actually dual boot on my phone for hac..I mean testing on the go xD
What will this one do that the others don't?
Cheers
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
If you don't know what BackTrack is then you don't need it.
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
its a pen testing Linux suit. its essentially Linux loaded up with hacking tools meant for testing networks to prevent hacking or "penetration". hack your own network. discover the vulnerabilities. and patch them. - to put it simply
This is amazing. Thanks.
7z issue with the bt.7z
Hum... I might be doing something wrong but I am not able to uncompress the 3 volumes posted in the links... I was able to download them all but the only one who actually I can uncompress is the first one and it generate a file bt.7z that I am also unable to uncompress... I am getting the following msg when I try to 7unzip them:
"cannot open file 'x:\xx\xx\bt.7z.002' as archive"
Should I join them all into one then use 7zip?
Forget it I just found it out by myself... is using a program to join them all into one then Unzip it.
My dream come true .............. i assume that we can run kismet and metasploit framework ?!
What kernel and rom were you able to make this run well with as i am having really bad reboots after i undock the phone from the lapdock as i am running faux123 kernel and cherry crust v3.
webtop when connected to hdmi not doing anything...
I was trying to use this backtrack distro on my AT&T Atrix and I must admit that I am a kind of noob on this ... I wasn't seeing big advantage until now that we have bt to use instead of the stock version...
I have no Lapdock so I am using Ronaldo_9 CWM version to run Webtop on HDMI in my GB 2.3.4 ( 4.5.91 from Kenneth Penn ). It was working til I followed these instructions ...
Well a little bit of what I did:
1- Downloaded the WebTopMOD from Joe Ferreira v2 to install with CWM.
2- Got also BusyBox installed through the BusyBox Installer over my /system/bin
3- Downloaed (even knowing it's not needed) the Debian disk from Joe Ferreira link (to install webtopmod).
4- Downloaded the BlackTrack 5 image from the links on the first post
5- Downloaded the BackTop.zip from the first post
6- Created the /sdcard/bt folder and put only the bt.img and forcekillbt and backtop files from Backtop.zip file onto it...
7- Plugged in my HDMI cable over my tv (yes I have no lapdock)
8- The Webtop option pop's up and when I selected it.....
Nothing happened... not even an error msg or stuff... the only thing still working is EC... but webtop none.... Does anyone of you have any clue or hint of what can I do about it?
EDIT: Got it working... it was because of the broken V2 WebtopMOD so I flashed the V1 and everything went fine.... Thank you all for not helping it made me a better researcher
I think I just wet myself I've been waiting for someone to come up with this since they started the ARM archticture and ported it to the XOOM tablet
Sent from my MB860 using XDA Premium App
The built in wifi doesn't support packet injection does it?
baumerman said:
The built in wifi doesn't support packet injection does it?
Click to expand...
Click to collapse
It doesnt....
Sent from my MB860 using XDA App
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
kholk said:
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
Click to expand...
Click to collapse
That would be awesome... just amazing how u dealing with a lot of stuffs simultaneously ....... tyvm for visiting this thread its almost dead...
Doing a simple (means not a complex one) research at Google it seens that there's no much of Monitor mode for android cell phones so far... not sure why if nobody cares or if it's not possible... but u got skill enough to give the last word
Hope to hear something soon...
I wish there was more development for this, and +1 for packet injection
gzrecoil said:
I wish there was more development for this, and +1 for packet injection
Click to expand...
Click to collapse
There is monitor mode for iPhone and itouch... not sure the reason why not for android :-(
Sent from my MB860 using XDA App
Al Credits Goes TO Perceval from Hyrule
Perceval from Hyrule said:
** Currently writing this, please wait !
Hello there,
here is a new tutorial I'm sure you'll like. As usual it took me LOTS of work to get all info and make this to work, so now I share it with you and show how to run custom ROMs within Android SDK Emulator.
Please note it's mainly for XPERIA X10, but process is the same for other Android-powered devices. It will show you the process for Linux.
1. Download the latest Android SDK.
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
3. Go to the SDK folder, then in the folder Tools/. Double-click on Android and choose Run.
4. Go to Available packages, and choose to install (choose at your will !)
Android SDK Tools, revision 8
Android SDK Platform-tools, revision 1
SDK Platform Android {VERSION(S) YOU WANT} (!) You need at least one Platform. For X10, you can download 1.6, 2.1. You can also add 2.2, 2.3.
Once it's done, close the window.
5. Download Xperia X10 add-on for SDK. (?) Read the PDF add-on guide, it is helpful !
Copy the folder (from the archive) XPERIA-X10_r1 inside the folder add-ons of your Android SDK folder ({androidsdk}/add-ons/).
6. Run terminal, go to your Android SDK folder, then in tools folder, and run
Code:
./android list target
.
Note the id number of the Android you want to develop (ie for me, Android 2.3 is
Code:
id: 3 or "android-9"
). (?) You might also want to note the name ("android-X") as it might be useful later.
7. Now, create AVD (a profile for emulator). Usual command (assuming you are INSIDE the /tools/ folder !) is
Code:
android create avd -n NAMEYOUWANT -t {ID}
So, for us, it will be
Code:
./android create avd -n myx10 -t 3
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 160 (correct if I'm wrong ?)
DPad support : no (?)
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 66 (?)
Audio playback : yes
Trackball : no (?)
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 32
RAM : 280
GSM Modem : yes
(?) I recommend you to create one profile for each Android version you want to run (so : you just have to change the ID, and create same profile). If you don't, you won't be able to run custom ROMs using other versions of Android (ie your AVD profile is 2.3 and you run a 2.1 custom ROM).
9. Done ! Take your custom ROM (downloaded, compiled... In this case, files are in {YourAndroidRepoFolder}/out/target/product/generic/. It comes with about 3 files, including a file called system.img. Copy this file into the folder (hidden) .android/myx10{In fact, the name you've chosen earlier "NAMEYOUWANT"}.avd/
10. Run terminal, go to Android SDK folder/tools/ (if you didn't close your current terminal, you're already in and run this command to run emulator WITH your custom ROM :
Code:
./emulator -avd myx10{again the "NAMEYOUWANT" you've chosen before}
Wait and enjoy !
(?) First boot is long - it's NORMAL. Just like on a real device, the OS will be cached and will work faster and faster.
Click to expand...
Click to collapse
Can you please make a video tutorial? I don't have terminal i use Windows
terminal on windows
TodorSRB said:
Can you please make a video tutorial? I don't have terminal i use Windows
Click to expand...
Click to collapse
in windows 7, press the start button, type in cmd, hit enter and viola! you are in a terminal
Great tutorial but the point that confuses me is: If we're creating AVD why do we need and where/how do we used device add-on for SDK?
Thanks
LastStandingDroid said:
Al Credits Goes TO Perceval from Hyrule
Click to expand...
Click to collapse
thanks
Thanks for this tutorial! Thanks +1 for you! :good:
there is a new version of ADT out since this tutorial was written. I am able to run a virtual machine but how can I get a custom rom on it? Please help.
thanks
mrdoc151 said:
there is a new version of ADT out since this tutorial was written. I am able to run a virtual machine but how can I get a custom rom on it? Please help.
thanks
Click to expand...
Click to collapse
You need to download more than one api, it creates the directory for addons and continue from there :beer:
thanks for the tutorial
A question, ¿how to compile a rom? :S
jomigp01 said:
thanks for the tutorial
A question, ¿how to compile a rom? :S
Click to expand...
Click to collapse
A Linux environment is best, and there are a million tutorials all over xda:beer:
Slithering from the nether regions of a twisted mind and tarnished soul
jacobmacek said:
in windows 7, press the start button, type in cmd, hit enter and viola! you are in a terminal
Click to expand...
Click to collapse
That is not terminal. If you need terminal in windows download CYGWIN. http://www.redhat.com/services/custom/cygwin/
Silly post *Removed*
I want to make it to this process for one x. in addition to those for xperia Where can I find one x
I have a flashable zip of the custom rom i need to test. Is there any way i could use that here?
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
* I can't see any archive.
TodorSRB said:
Can you please make a video tutorial? I don't have terminal i use Windows
Click to expand...
Click to collapse
Download cygwin from HERE
It should help you
---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------
OzoGaming said:
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
* I can't see any archive.
Click to expand...
Click to collapse
Here the archive means the flashable custom rom :laugh:
Need a windows tutorial.....
This tutorial looks like for linux......please make a windows version tutorial
Black Screen here, any suggestion?
I saw that the ramdisk.img is also needed, but I dont know how to generate it
You can use fastboot / ADB to pull ramdisk.img for the device brand model you are trying to cook for. Tutorial on youtube- I have to watch it again guy is not a natural instructor - oh well grateful for the seeds and the few Linux tutorials: I want to try setup a profile for Doogee Mix due to little support for it. Think its worthy of a few custom options. [email protected] 'LastStandingDroid" Thank U - I was looking for how to unpack stockmix.rar to fastboot flash for a restore, Can I use those same basic files to create a skeleton profile for custom rom? I'm just frankensteining
Here the archive means the flashable custom rom :laugh:
Click to expand...
Click to collapse
in my "archive" i have only md5 files no folders pls help
Hi folks,
we have some lucky users among us with a generic (Dev) IMEI - some of these are able to get OTA updates, thought for testusers and/or developers from Samsung, after they install latest Test firmware XXLSA from sammobile....some got updates up to XXLSC and already provided a dump. Others got updates up to XXLSD (and maybe higher in future - who knows, where the journey ends...), but don't know what to do to share this firmware with us 'Flashaholics' here on xda and other forums...
Now, as more and more people asking me (why ever me...) how to make a system dump from Stock Firmware, I decided to write a short 'HowTo for Dummies'. So if you know about someone, who has a unknown Test Firmware installed, or YOU are the chosen one, just follow this tutorial and make us happy
This is just one way of several to do this - but as I think, it is the easiest way for newbies (without having to use Android SDK and adb shell on PC --> that's what experienced would do )
Prerequisites:
- at least 1,4 GB free space on internal SDcard
- a brain (and above 80 IQ-points...)!!!!!
Step 1) Rooting your Stock Firmware (thx to Phil for the steps, I just copy/pasted them) --> if you already have Root + busybox installed, go to Step 2) directly
download this Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip and this cwm-non-touch-6.0.1.4-i9100.zip
Put the previously downloaded cwm-non-touch-6.0.x.x-i9100.zip file on your external sd card
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-non-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
(You can easily unroot your device afterwards...it is also described in Phils thread, where I took all these from: [20 Sep 2012][ICS]Universal Rooting for most ICS phones, Any ROM, now with CWM6 )
Step 2) Making a complete System Dump of Stock Firmware:
Install 'Terminal Emulator' from Playstore
Open Terminal Emulator
type 'su' with your internal keyboard and press return button
grant Superuser access on upcoming popup window
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin
==> this will generate 'modem.bin' (= Modem) on your internal SDcard (will be finished after a few seconds)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage
==> this will generate 'zImage' (= Kernel) on your internal SDcard (will be finished after a few seconds)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hidden.img
==> this will generate 'hidden.img' (= preload partition) on your internal SDcard (will be finished after a few minutes, as it is more then 300 mb!)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img
==> this will generate 'factoryfs.img' (= system partition) on your internal SDcard (will be finished after a few minutes, as it is more then 800 mb!)
Now you have the following output / files on your internal SDcard:
modem.bin
zImage
hidden.img
factoryfs.img
==> zip these 4 together and upload them to a hoster ==> post the link here and devs can start building a new ROM (Stock + CustomROMs) and kernel devs (now we luckily have Phil for that) can preroot the kernel + put in CWM recovery.
That's all and really very very easy....
Disclaimer:
I am not responsible for any damages - it is your risk (though it is not a dangerous thing to do!)
hope this will be a very good guide in getting the new leaked rom from sammy
Nicely done my friend this should ease up on some of the users (the ones who get updates for us XD)
Congratulations on this, now you see why community loves you soooo. liebe endet nie !!
es ein vergnugen es zu lesen. gute arbeit eybee :good:
Thank very much boss
Hope you will be one of the prof when xda university will open.
Thank you very much
Hope now when we will see LS(any letter) it will be with the links of the dump
Envoyé depuis mon GT-N7000 avec Tapatalk
Funny
Envoyé depuis mon GT-N7000 avec Tapatalk
Cool bro thanks but you can use the supersu.zip and the busybox.zip from stock recovery
Tapatalking on my n7000
msedek said:
Cool bro thanks but you can use the supersu.zip and the busybox.zip from stock recovery
Tapatalking on my n7000
Click to expand...
Click to collapse
It was easy copy paste for me in the rooting part....you can root and install busybox in 567 different ways...in the end the result counts
Clicked for Newsworthy article. :thumbup:
Sounds really simple for someone who doesn't have the second prerequisite.
Back uped the info.
Sent from my GT-N7000 using Tapatalk 2
Sharing your valuable knowledge and experience is priceless for those who are interested. Well, me, I simply follow pros like you.
Sent from my GT-N7000 using xda premium
In addition to Step 2:
I made the dumps from my PC with a connected device with "adb", so I could copy them to the harddisk directly.
"adb devices" for checking if connection is established, "adb shell" switching to the device, "su" for root access, and then the commands eybee1970 explained in detail.
After that I fetched the files in my file manager from the connected device.
I prefer to work with terminal windows on the PC and not on the device.
With this you do not need Step 1 - because I didn't
another great one from eyebee
great guide for learners like me
thanks
ThaiDai said:
In addition to Step 2:
I made the dumps from my PC with a connected device with "adb", so I could copy them to the harddisk directly.
"adb devices" for checking if connection is established, "adb shell" switching to the device, "su" for root access, and then the commands eybee1970 explained in detail.
After that I fetched the files in my file manager from the connected device.
I prefer to work with terminal windows on the PC and not on the device.
With this you do not need Step 1 - because I didn't
Click to expand...
Click to collapse
That's why I said 'for Dummies'....no PC, no Android SDK, no adb shell...just the device
This is a superb guide! cheers eybee
Deleted
Sent from my GT-N7000 using xda app-developers app
Now the history rolls back...
as people raced to create their own custom roms.
The chosen ones with their great knowledge was kind enough to uncover about the custom rom things and shared it with some tutorials here in xda-dev for people who needed it.
Just like the old time...when WinMo has a bright future here.
Thanks a million for devs and chefs at xda-dev who always spread the lights.
ZacDerbyshire said:
Great guide. A little off topic but I don't know where else to ask and you are an expert in ROM making. How do I put things like all multiwindow apps and 4 way reboot in the ROM build before it goes on the phone? Sorry again for it being in here, can't find anywhere else to ask.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
4Way reboot mod is at the system/framwork/ directory "android.policy.jar" file is responsible for this stuff....
as for all multi apps after an investigation it appeared it looked for a certain statement to know whether its a sammy app patching that code to the launcher and editting the policy for this feature too gets you all apps access (almost all) as some just dont work....
there are plenty of guides and tutorials over the internet and forums... on different phones mostly but with a little time you can manage everything as you want to so READ some enjoy!
i'am guessing we need to start writing more tutorials in the N7000 section in here we have no knowledge sharing mostly developing and some new guys are ready to try their own so we have to share everything it started with eybee (thanks to him) and hopefully will continue with all other guys who do mods.... no matter how small it can be usefull.
believe it or not but even devs assist each other with mods its not like each one was born with all that OP-Code in his head
Ah...good guide eybee.Let me see if i can make a shell script to dump the partitions and make odin roms out of it.I already have scripts to dump and make odin rom for /system,/data partitions.will add preload,kernel and modem to the script.Let me see how my time permits today.Hope the script will help people.But the only drawback is it will work only on linux.Users may use cygwin too for it
Sent from my GT-N7000 using xda app-developers app
eybee1970 said:
That's why I said 'for Dummies'....no PC, no Android SDK, no adb shell...just the device
Click to expand...
Click to collapse
For my case adb shell was not succeed. Device reboots unexpectedly while dumping factoryfs. Maybe file size is too big. Thus I had to use terminal emulator though pc keyboard is much more convenience
Great tutorial!
Sent from my GT-N7000 using xda app-developers app
Two remarks:
Typing something like "dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img" is never something I would call easy. If you do not have Linux shell commands knowledge, than these are about "50 characters without meaning" that you have to type (on the keyboard of your device - which is even more error-prone).
PC or Note: it is never dummy-simple.
Making a batch wich automatically generates an ROM installable with ODIN (so the result are tars) is dangerous.
The difference between "dump" and "dumb" isn't so big - as I just proved myself.
When you make a batch with a complete process from dumping, copying, building to a "blob" installable with Odin there will be no step in the process for quality control.
Example (hurts to write this): If there's something in the original Rom you are dumping that couldn't be shared then it makes its way through the process in to the final Rom. And the dummy user of these scripts will never know or can protect himself from it.
Only pro from this: after learning this the hard way you don't feel like a dummy user anymore.
Optimus Toolkit 6 in 1 v-1.1.1 - Linux
After a few month programming here you have this 6 in 1, we say that it is the counterpart in Linux of the "All in one", though it seems.
In you program have included 6 applications essential for the day-to-day management of Optimus, partitions with the new LG-ICS configuration or the former LG-GB.
Backup/restore of the whole system, and also of the SDs, both internal and external, and stores them in ZIP format.
The program includes:
Uncompress KDZ
Unpacking AP
Backup
Restore
Flash ROM (NVflash)
Rooted
Three languages, Spanish, English and German, I hope that it will soon translate into French, Italian and Portuguese
Click to expand...
Click to collapse
An example of use:
You have a ROM format KDZ and does not the Windows program rather than failing, because well, you copy the kdz within the kdz_folder folder, run the Optimus_Toolkit 6 in 1 and choose option 1- UnPack KDZ.
After a few seconds you have the AP and CP files to Flash with Smartflash. Oh, that doesn't want to boot windows?, no problem, use option 2.- UnPack AP, and then option 4.-Flash ROM for flashing by NVflash ROM KDZ just unpack.
But before Flash want do a backup of the system, as with the 3.- Backup/Restore option, this is in Optitool 2, backup/restore DATA, SYSTEM, etc.
Click to expand...
Click to collapse
The operation is very intuitive, just follow the instructions on screen.
The program does many things, and others will in the future.
I hope that you go reporting if you detect a fault.
Changelog
V-1.1.1
- Support for German language, thanks to Cupacabra - in this version you can change language from the main menu
V-1.1.0
- Support for any language. I have included a language file that you can go adding translations to other languages - error correction. -Added you fixing of current route to run on MAC (by drag0njoe) - the only language menu exits the first runs, the language selected is memorised.
V-1.0.2 R
- UnPack KDZ - now is can copy more than one KDZ within kdz_folder/, the program will create a menu with the KDZ that is inside the folder. - Added limits so that an opcionque can not be pressed does not exist. - Automatically adapts to options with one or two figures.
- Flash ROM - remodelling of the Flash ROM menu and correction of minor errors
V-1.0.2
- Menu flasher - Two new options, [5] Flash RECOVERs and [9] Flash KERNELs. - Alternative kernels copied them to kernel folder / and the recoverys to the recovery folder. - The program will detect the kernels and recoverys withi
V-1.0.1
- Correction on menu flashing, by drag0njoe
- Added flashing Kernel, by drag0njoe
V-1.0 stable
- Fixed bug when unpacking AP
- Fixed bug when unpacking KDZ
- Fixed bug in detection of ROM
- English version, corrected spelling errors.
- Revamped graphic look.
Click to expand...
Click to collapse
CREDITS
• [email protected] introduced the 'LGExtract.exe'. the encrypyted/compressed kdz can be extracted/decrypted to AP.bin/CP.fls by LGExtract.exe
• AP.bin extractor (win32/linux)
• xonar_ made BIN/FLS extractor
and release source
• (original Java version by xonar_)
• (win32 C port by navossoc)
• [TOOL] LGExtract 0.2.1 by navossoc
Click to expand...
Click to collapse
DOWNLOAD
Optimus_Toolkit_6-in-1_V-1.1.1.tar.gz - 25.64 MB
Nice bro,
It's good to have another alternative toolkit for linux users.
New version corrected, improved and stable
Thanks for your work and collection, as a regular linux user it's very useful for me.
I have some recommendations which are might be improve the linux users experience.
I suggest you to use some kind of compression which is takes care about the extended *nix attributes, like the executable bit. For example, the 7zip and the tar.gz will be perfect.
But if you feel better, that's no problem using the proprietary rar format, in this case I have to execute these commands:
Code:
chmod +x scripts/*.sh
chmod +x tools/7za
chmod +x tools/adb_linux
chmod +x tools/adb_mac
chmod +x tools/cabextract
chmod +x tools/extract
chmod +x tools/nvflash
Or, if you think you can implement such a thing like these into your menu.
Not a big problem, just an idea how to make your work more user friendly.
The other, which is also just a minor thing, in the tools/flash_en.sh I found that in the Opti nvflash command line there is a tools/fastboot.bin, which is not corrected to the fastbootICS.bin file, so the nvflash of course does not work with.
Lastly, please consider about integrate the recovery from pengus (CWM non-touch) and tonyp (CWM touch and TWRP soon), and to implement the kernel flashing only (ex. for the kernel testers). I attached my version of your flash_en.sh with Flash ROM option 8 (because I am successfully stucked on boot with a new kernel ).
Thank you for your work!
excellent useful tool!
drag0njoe said:
Thanks for your work and collection, as a regular linux user it's very useful for me.
I have some recommendations which are might be improve the linux users experience.
I suggest you to use some kind of compression which is takes care about the extended *nix attributes, like the executable bit. For example, the 7zip and the tar.gz will be perfect.
But if you feel better, that's no problem using the proprietary rar format, in this case I have to execute these commands:
Code:
chmod +x scripts/*.sh
chmod +x tools/7za
chmod +x tools/adb_linux
chmod +x tools/adb_mac
chmod +x tools/cabextract
chmod +x tools/extract
chmod +x tools/nvflash
Or, if you think you can implement such a thing like these into your menu.
Not a big problem, just an idea how to make your work more user friendly.
The other, which is also just a minor thing, in the tools/flash_en.sh I found that in the Opti nvflash command line there is a tools/fastboot.bin, which is not corrected to the fastbootICS.bin file, so the nvflash of course does not work with.
Lastly, please consider about integrate the recovery from pengus (CWM non-touch) and tonyp (CWM touch and TWRP soon), and to implement the kernel flashing only (ex. for the kernel testers). I attached my version of your flash_en.sh with Flash ROM option 8 (because I am successfully stucked on boot with a new kernel ).
Thank you for your work!
Click to expand...
Click to collapse
I will take into account the compression, I will use the native tar.gz.
On line 101 of your flash_en.sh it refers to tools/recovery_ics-20121230.img
That recovery is that?
I'm hoping to TWRP, is a recovery which I like very much, I tried to adapt it to ICS based on modifications made by Stefan in the CWM, but I only got a tremendous brick ), is that something different from CWM works
If you think of any suggestions, they will be well received.
Stefan Gündhör said:
excellent useful tool!
Click to expand...
Click to collapse
Blessed are the eyes that you read
Homero2 said:
I will take into account the compression, I will use the native tar.gz.
Click to expand...
Click to collapse
Thank you! Maybe the newer Linux users also like it.
Homero2 said:
On line 101 of your flash_en.sh it refers to tools/recovery_ics-20121230.img
That recovery is that?
Click to expand...
Click to collapse
Yes, this is the latest recovery from pengus77, I am using his ROM, so I think this one is better for me.
Homero2 said:
I'm hoping to TWRP, is a recovery which I like very much, I tried to adapt it to ICS based on modifications made by Stefan in the CWM, but I only got a tremendous brick ), is that something different from CWM works
If you think of any suggestions, they will be well received.
Click to expand...
Click to collapse
I tried it too, the result was useless, so I really understand you
Maybe sooner or later somebody has some time to make it for the ICS layout too.
Thank you again for your excellent work, it is really useful for me!
NEW V-1.0.2
- Menu flasher - Two new options, [5] Flash RECOVERs and [9] Flash KERNELs. - Alternative kernels copied them to kernel folder / and the recoverys to the recovery folder. - The program will detect the kernels and recoverys withi
Can't get it working.
Tried running it on a mac but it ends with an End of process after selecting a language:
Escoja una opción/Type an option: [1-2,X]2/Users/ruslanmirsalihov/Desktop/Toolkit_ICS-Root_Stock-v-1.0_by_Homero/root: line 18: tools/en.sh: No such file or directory
logout
On ubuntu it says it was unable to determine my phone.
Any help?
If the "unable to determine my phone" means that when you start the flashing process you get "Nvflash started" "USB device not found" in Ubuntu, I think the problem is that you using wrong cable, or you not plug the phone into the USB while both of the volume keys pressed. Please provide exact error message and the exact menu option you used in order to get your problem solved.
About the mac you need to start Terminal from Utilities and start the script from here.
Or, alternatively, I attached a fixed menu which is working with double-click, just download and replace it your menu file with the attached one (there is a new function which doing the same thing, cd'ing into the script directory, so I just made nearly nothing, but working in linux and mac, and should working in cygwin too.)
But note that, in mac you cannot use the flashing options because of AFAIK there is no nvflash for mac. But you can use the others, such as the rooting and the back up with ADB is working.
This function (fixpath). Should we put it in the script, or just on the menu?
New version 1.1.0, with support for multiple languages, the languages are included in a separate script file.
The program memorizes the selected language, and the language menu will not appear any more
New version, with new options and I think and hope that all errors are corrected.
THanks
At last playing with my android P990 without boot Windows thanks !!!
Does this work with the P880 (Optimus 4X) as well, or is it specific to the P990?
nevermind.......
Phew, search how to nvflash!!!
Sent from my LG-E610 using xda premium
SuperSkill said:
Phew, search how to nvflash!!!
Sent from my LG-E610 using xda premium
Click to expand...
Click to collapse
Newbie here trying to flash my o2x however I am not able to enter APX mode I guess. I've removed the battery and I hold down the volume up/down and plug into USB but nothing appears.. it just says no USB devices were found? Anyone else have this issue, not sure what I am missing here but pretty hard to do anything if device is not recognized. thanks.
archish said:
Newbie here trying to flash my o2x however I am not able to enter APX mode I guess. I've removed the battery and I hold down the volume up/down and plug into USB but nothing appears.. it just says no USB devices were found? Anyone else have this issue, not sure what I am missing here but pretty hard to do anything if device is not recognized. thanks.
Click to expand...
Click to collapse
Try the all in one tool kit by spyrosk
It has the menu for installing the drivers which you need
Install the apx drivers
Sent from my LG-P990 using xda premium