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?
***Root method for .621 update***
THIS IS FOR USERS WITH THE .621 UPDATE ONLY. IF YOU HAVE NOT UPDATED DO NOT USE THIS METHOD.
*****DO NOT USE WINDOWS*****DO NOT USE RSDLITE*****
Instructs are made by Skelente
1.) Download the latest Ubuntu iso for your system. Most processors these days are 64 bit, but if you're running on an older computer or do not know if you have a 32 or 64 bit processor I'd recommend doing 32 bit just to be safe (64 bit processors can run both 32 and 64 bit distributions, but 32 bit systems cannot run 64 bit distributions.) Side note: you can download other distributions, but if you do you will not be able to create the persistent drive using the USB method. It should also be noted that some older systems cannot boot from USB, most newer systems (post 2000/2001 IIRC) can boot from USB, however you should consult Google to verify for your system.
2.) Burn the iso:
2.a If you have a cd burner and blank disc, this is the easiest method but, again, you will not have a persistent drive you will just have a Live CD. Use an iso burner to burn to cd, then skip to step 3a.
2.b If you do not have a burner, a blank disc (or don't feel like wasting a DVD disc) but have a free USB drive (with at least 2 GB of memory, bit overkill but it has to be big enough to hold the iso + changes + the persistent "drive") then I recommend downloading either unetbootin or universal USB installer. Go to either web site and follow their instructions. If you use Ubuntu, you'll have the option of creating a persistent drive, which is basically a fake-partition that allows you to save files to when you reboot Linux after running this Live USB. I would recommend using a persistent size of at least 200 mb so we can save the SBF file and sbf_flash. If you created a persistent drive go to step 4. If you opted out of this, skip to step 4.
3.a So you have a Live CD now. If you have a spare flash drive, load up the 604 SBF and sbf_flash. Either way, you'll need to proceed to booting into linux, go to step 4.
3.b Once the respective application has finished, copy the SBF and sbf_flash file to the persistent drive listed in windows.
4. Now we need to boot from your Live image. Restart your computer. When your computer is booting up it should give you two options, "Enter BIOS" and "Select Boot Order" or similar. For my Lenovo Laptop, I can hit F12 to change the boot order, and from there I can select my USB port and it'll boot from there. If you do not see a boot order option, you will need to go into your bios and change the boot order manually. Again, you will need consult Google for this as the menu selections vary by system. It really isn't that hard to figure out if you go through the menus, but I strongly, strongly, strongly recommend and encourage you to google your motherboard's manual to verify what you need to change if you don't know what you are doing. You are responsible for any changes you make on your system. Your BIOS is crucial for your system to function properly. Once you have found where to change your boot order, select the respective drive (USB, or your CD/DVD drive). These will be listed by the manufacture name (so SamsungXXXX for a Samsung drive or PNYXXXX if you're using a PNY usb stick.)
5. When Ubuntu boots up, it'll give you an option to run "Live" from the CD/USB. Select this option. Installing to your hard drive could mess up your current OS install, and I'm not going to get into partitioning here. Once you've gotten into Ubuntu, select "Dash Home" in the upper left hand corner, and then type terminal in the search box. Click terminal, then open it up.
6. Now you'll need to get to where ever you have the SBF and sbf_flash stored through the terminal. If you chose to use the boot cd, and did not have an available flash drive, you will need to download the SBF from here, as well as sbf_flash and then extract them to the same folder. The default is "Downloads" and I recommend just extracting them to that directory for simplicity.
6.a If you had to download the SBF/sbf_flash, getting there through terminal is rather easy. All you'll need to do is type these commands into the terminal:
cd Downloads
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
6.b If you already copied the required files to a USB drive, we need to get there through terminal. Type these commands:
cd /
cd /media/
ls (This command will list all the drives connected to your system, cdrom, usb, etc. If you used the Universal USB installer it will list the USB drive as "PENDRIVE", I'm not sure what the default is for Unetbootin but you should be able to figure it out and if you just used a spare device it could be completely random.)
cd drivename (obvioiusly this will vary based on the USB method, for me its "cd PENDRIVE"
If your files were just on the main drive, you don't need to do anything else but the following commands. If you put them in another folder, you will need to do "cd foldername" without the quotes obviously. When you're in the directory with both the SBF and sbf_flash you will need to do these commands (again, ignoring the '-'):
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
7.) After sbf_flash is done, you'll need to restart your computer. Its recommended you remove your boot media (cd or usb drive) so that Windows can boot normally. If you changed the boot order in bios you will need to change it back to what it was before, otherwise whenever you have a CD/USB stick plugged in your computer will automatically try to boot from it, and get pissy if it can't boot from the media.
8.) Once you're back in windows you'll need to run the zergrushv4 root method. From there you can do whatever you want. You still cannot SBF to previous versions (602 or 605) and you cannot run Froyo roms.
Downloads:
sbf_flash
SBF File & root tools
*HELP*
If you flashed with RSD Lite and have no data here is your options...
Flash stock .621 sbf and...
Switch devices on your account to reactivate the data
or
Call verizon to have them reporvision your data...
Once you are on the milestone system you can flash a custom rom.
You must SBF in Linux using sbf_flash, otherwise .604's radio will flash over .621's and your phone will no longer be able to take or place phone calls.
Edit: It may just be data, instead of phone capabilities. But still, flashing in Linux is much easier than having to spend time with Verizon's incompetent phone operators.
Sent from my Transformer TF101 using Tapatalk
If you SBF'd using RSD Lite, you flashed the 605 baseband over the 621. I didn't think this would mess up texts/phone calls but just your data connection, but correct me if I'm wrong I'm just going from memory (I had a dx2, just been watching the threads.) This was a big problem for the people over at rootz and they had a few different tactics on how to solve it. Some were able to call VZW and ask the tech support to "re-provision their data" although that was with mixed results (it depended who ya got on the phone, some people had no luck and other people had their data start back up no problems.) You would need to sbf back to 621 and call from a separate phone, however. Another user (skreelink) theorized that it was merely the AUTH code that was being messed up, and suggested that (for those with a secondary smart phone) you just go onto VZW.com, switch out phones for your number, wait 15 minutes, then go back to the website and switch back to your DX. I'm not sure if anyone has had any success with the latter but I know the former worked for a handful of people (with others getting tech support who had no idea what they were talking about.) If you call and don't get someone knowledgeable, I'd just cross your fingers and call back another time and hope you get someone different.
link not working
anyone have updated link that works to download this?
yea i learned about the radio the hard way, but i found a quick fix... maybe...
If you flashed with windows and now cant get data if you have a old smartphone that is compatible with you plan just go online and switch devices and then switch them back. Saves from having to call verizon But some people may not have a extra
I am probably one of those people who will also need to use this alternative root method but I have a question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned off my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
bamx2 said:
I am probably one of those people who will also need to use this alternative root method but I have question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started the downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned of my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
Click to expand...
Click to collapse
If you disabled the download you are still on .605.
Turn your phone on, quickly root it with Pete's Motorola Root Tools, install Titanium Backup and freeze the "2.3.3 Updater" application.
Afterwards, reboot your phone and you should be golden.
Sent from my DROIDX using Tapatalk
nfazzdar - Thanks for the reply . I did a factory reset and that got rid of the yellow triangle. I then rooted as you suggested and installed TiBu . I really is too bad that M and V are pullin this cr#p .
I am going to update the post and host the files. There is also some extra stuff i will put up for download.
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Good to know. I think that I will also install OTA Rootkeeper as well.
deboyz1014 said:
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Click to expand...
Click to collapse
using linux mint and have a ?
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
BRANDENDEUCE said:
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
Click to expand...
Click to collapse
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
landonotis said:
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
Click to expand...
Click to collapse
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
infazzdar said:
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
When exactly do we need to input the code? I am assuming this is in terminal on linux?
BRANDENDEUCE said:
When exactly do we need to input the code? I am assuming this is in terminal on linux?
Click to expand...
Click to collapse
Sorry for not specifying, but you assume correctly.
Sent from my Transformer TF101 using Tapatalk
What roms can we use now?
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
BRANDENDEUCE said:
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
Click to expand...
Click to collapse
I believe this thread will be of help to you. =D
http://rootzwiki.com/index.php?/topic/21337-[ROMS]-Multi-ROM-Thread---Blur-Based-ROMs-for-those-on-.621/.604!
Sent from my DROIDX using Tapatalk 2 Beta-5
This worked great.
Any cwm kernels are we able to use?
Just wondering if we can flash custom kernels since we can do roms? If so any help would be appreciated.
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.
Hi....this is my first time in my life i buy device with android software so I need help,I don't know any thing about android and i want root my phone.
other thing why cant use all my phone storage or that problem will fix after root my phone .............so help me guyz plz
Root
BMG50 said:
Hi....this is my first time in my life i buy device with android software so I need help,I don't know any thing about android and i want root my phone.
other thing why cant use all my phone storage or that problem will fix after root my phone .............so help me guyz plz
Click to expand...
Click to collapse
I've just helped a friend root their HTC Sensation XL, it was a painful job because we found a few methods and they didn't work!!! :crying:
BUTTT, this guide really helped: Damn just found out the because I'm a new member on here, I can't paste URLs, that is annoying!!!Type in on Google, "How to root the HTC sensation XL", and it should be the first result on a website called "theunlockr"
First you need to unlock the bootloader, there is a link on the above linked page to a HTC dev site where you can do that, then you need to download the three files/folders in sections II, PUT THESE ON YOUR DESKTOP! Don't unZIP the SuperSU folder. When you unZIP the fastboot folder, put all the files onto the desktop.
On section III, Everything should be straightforward up to the point of number 7, (for number 5, the root of the SD card means straight onto it, not into any folders), make sure you do number 6! At this point, you will have your device on (on Android) and plugged into your computer, then type the command in number 7 (adb reboot bootloader), then using the volume keys to scroll, and the power button to select, select fastboot, then carry on to step 8, then step 9 taking care to put the correct file name into the command, then step 10, boot into your recovery.
Section IV is pretty straight forward, GOOD LUCK!!!
With your phone storage (I don't know the figures - haven't used the device directly), but some of it will be used up by the Android OS. Your remaining space will more than likely be split up into internal storage which is used like an SD card, and the App/data section which stores the apps and the data surprisingly! Haha!!
Any problems, reply and I'll try to get back to you as soon as I can!!
Good luck,
Twiglets100
Don't forget to hit the thanks button please if I helped you!
first thank you so much for helping
and i think i need ur help again in step 9 plz explain this step to me.and I've get ( error : cannot load ' recovery.Img' ) when i tryed to do step 9 like website
BMG50 said:
first thank you so much for helping
and i think i need ur help again in step 9 plz explain this step to me.and I've get ( error : cannot load ' recovery.Img' ) when i tryed to do step 9 like website
Click to expand...
Click to collapse
Don't worry, me and my friend ran into that problem too! Firstly, your recovery .img needs to be in the same folder as the fastboot.exe, and make sure you type into the command the EXACT filename of the .img. The filename may also be case-sensitive, bare that in mind!
E.g. On your desktop, you may have the unZIPped folder with fastboot.exe in, your recovery .img should be moved into this folder.
Then type the command: Fastboot flash recovery filename.img
And press enter, this then may take up to a few minutes.
Good luck!
Twiglets100
Don't forget to hit the thanks button please if I helped you!
Hi,
i have a samsung gt S5300 Poket Smartphone. I use Ubuntu on my PCs for a long time, and because of this i want to root my device, install a terminal and have the full (or nearly full) terminal opportunities which i have on Ubuntu PC, if i type sudo su. Now i am new at android and give attention to it.
Now i googled a time, and found a topic http://forum.xda-developers.com/showthread.php?t=2365697, where it is rcommended to download a zip-file from mediafire. Now i am thinking about how secure it is to install a zip-file from mediafire (relating to viruses etc. that may be included).
It would be nice if you could give me some information. Thank you.