Related
Tutorial -> Howto root your SGS the easy way (without software and still keep all your data and settings)
Because the lack of good tutorials i decided to write my own! (for n00bs)
This method will keep all your data and settings! this means the phone will not be factory resetted.
You won't need the Android SDK tools to go in recovery mode! or use Odin3
Reported to work on all firmwares!* (even simlocked devices and phones with voodoo fix etc) but use at your own risk! (it is pretty safe and foolproof!)
If you wan't to unroot (to avoid waranty problems) you can unroot your phone!
* This method is not working for Froyo 2.2 roms but if you do wan't to root JPH 2.2 click here! (Respect for Chainfire!)
* For people that don't have the 3 button combo i made a small script to boot in to recovery. See tutorial below
!!! Disclaimer: If you brick your phone it's your own problem! But it is fairly safe because you can still reflash your phone with Odin3
Only root your phone if you feel the need to! (like applying the lagfix or for use with certain backup apps)
ROOT includes:
- Superuser 2.3.6.1
- Busybox 1.16.0 (for use with Titanium Backup)
Automated Method!
This method works for phones with and without the 3 button combo!
Rooting works on the following models:
- I9000
- I9000M
- I9000B
- I9000T
- SGH-T959
- I5800
- I5801
Howto (un)root:
1. Download SGS Eclair Easy Rooting.zip
2. Unzip the directory somewhere
3. Open start.bat
4. Follow instructions
Click to expand...
Click to collapse
Manual Method!
Howto (un)root:
1. Download:
- 2.1 update.zip (For - I9000, I9000M, I9000B, I9000T, SGH-T959, I5800, I5801)
- UnRoot update.zip (this will remove your root completely and doesn't leave a trace!)
2. Put update.zip to root of /sdcard (not /sdcard/sd) (not on the physical SD card but the Internal SD card/Phone Memory)
3. Turn off phone
4. Hold down volume up + home button + power (tip: release the power button for half a second when you see the samsung logo)
Note: If you don't have the 3 button combo use the tutorial below (steps 4a - 4g).
5. Phone will reboot into recovery mode
6. Wait until you see the Recovery Screen and then release the buttons
7. With the volume down key go to the option: "apply: /sdcard/update.zip"
8. Press the home button
9. Phone will start updating
10. Phone reboots... and there you go! your phone is (un)rooted!
Click to expand...
Click to collapse
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
4a) Download the easy reboot recovery.zip script and unzip it somewhere
4b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
4c) Connect phone with USB cable to pc
4d) Wait until all the drivers are installed
4e) Start reboot recovery.bat
4f) The phone will now start in recovery
4g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
Click to expand...
Click to collapse
FAQ!
Busybox FAQ
Lot's of people are asking about busybox. busybox is included in the update.zip. But it's not the latest version! See how you can get the correct version.
To update manually to the latest version:
1. Search market for: "Busybox or "Busy box"
2. Install busybox app
3. Update trough app
4. Press update in app
5. Accept Superuser request
6. Busybox is now updated and installed in system/xbin!
If you want to use Titanium Backup (it is recomended to use the busybox that comes with titanium backup)
1. Install Titanium Backup
2. Open Titanium Backup
3. Press the "Problems?" button
4. Press "Yes, do it"
5. Titanium Backup will now download and install the required busybox version
If you want to use a lagfix!
- Both the OneClickLagFix and CFLagFix 1.80 automatically push the correct BusyBox version to your phone
Click to expand...
Click to collapse
General FAQ:
- Help i get a status 7 error message!
This is because of your CSC! flash another CSC and you can root your phone! how? use the search button!
- I can't root because it the update.zip fails to apply in recovery mode and i have android 2.1:
This is because you are using a open CSC or a branded phone. So in order to fix this you need to reflash your firmware with the standard CSC and not a localized one.
http://forum.xda-developers.com/showthread.php?t=787163 Check this thread to change your CSC!
Reported CSC's that have rootprotection (if you have a root protected csc please report it):
- CSC_I9000OLBJG4
- CSC_I9000GVODDJG1
Reported working CSC's (report if yours is working)
- CSC_I9000OXAJM1
- CSC_I9000OXXJM1
- CSC_I9000ODDJG4
- CSC_I9000OJPJG1
- CSC_I9000GVD2JM3
Right now i can't do much about it since i have no rootprotected phone to make a workaround.... so small request lend or sponsor me a root protected phone
- If you are having problems please post your phones firmware and csc version (you can check it by typing *#1234#)
Click to expand...
Click to collapse
Updates!
UPDATES:
24-08-10: Superuser 2.3.4! (update the su binary through the app!)
27-08-10: Added easy reboot recovery script throug ADB for people that don't have the 3 button combo!
29-08-10: Included correct su binary
02-09-10: Added FAQ
09-09-10: Updated Superuser to 2.3.6.1
14-09-10: Added UnRoot update.zip! This will remove the ROOT completely and doesn't leave a trace! (same steps to unroot as to root just use different update.zip) (please delete update.zip after usage)
14-09-10: Updated Busybox to 1.16.0 for use with Titanium Backup
19-09-10: Added automated method! Very easy and usable for every n00b
19-09-10: Added topic to the Vibrant section with automated method!
20-09-10: Added support for I5801
Click to expand...
Click to collapse
Feel free to comment! or BUY me a BEER by clicking here!
I will stick this for now, but will review it's sticky status as comments come in regarding this guide.
EDIT: Note, I make no claim to the correctness of this guide. I expect senior members to verify and comment on it's correctness, and/or propose additions/changes to it's content.
It is the correct method, and works with ALL firmware, not just JG5..
There are two other methods here but this is definitely a working approach for (just about) every firmware.
I know! But those methods are not very clear for beginners (like me)
That's why i came up with this method! It's easy to apply and it won't factory reset your phone!
should be /sdcard and not /sddata
BackfireNL said:
I know! But those methods are not very clear for beginners (like me)
That's why i came up with this method! It's easy to apply and it won't factory reset your phone!
Click to expand...
Click to collapse
I added it here (since the procedure is identical to flashing a custom ROM, there wasn't much to change)
Edit: Sorry dat ik zo langzaam was met reageren op je PM. Maar je hebt het duidelijk wel snel zelf gevonden ;-)
Darkstriker said:
I added it here (since the procedure is identical to flashing a custom ROM, there wasn't much to change)
Edit: Sorry dat ik zo langzaam was met reageren op je PM. Maar je hebt het duidelijk wel snel zelf gevonden ;-)
Click to expand...
Click to collapse
Cool! Your thread is very helpfull! This is just a foolproof tutorial howto root your SGS (for dummies like me)
offtopic: Geeft niet! het is me gelukt! nu nog een grotere SD kaart en ff die "lagfix" erop knallen! Standaard rom is voor de rest prima!
Uhm.. could a mod update the title to [TUT] Howto root your SGS I9000 the easy way (for dummies) (still keep all your data and settings)
This is the method ive alwaas used as its the simplest and i didnt know how to use adb,decent of you to post it up for the new guys-I only got around to learning how to use adb last night and its quite a hassle first time.
sammy555 said:
This is the method ive alwaas used as its the simplest and i didnt know how to use adb,decent of you to post it up for the new guys-I only got around to learning how to use adb last night and its quite a hassle first time.
Click to expand...
Click to collapse
I wish somebody would write a good tutorial for that! (not that i already searched for a good tut.)
I will start trying using adb as soon as i'm going to apply the lag/speedfix!
But first i need a bigger SD card!
That sounds like an interesting topic to add to my FAQ.
I'll try to fit it into the second post ;-)
Darkstriker said:
That sounds like an interesting topic to add to my FAQ.
I'll try to fit it into the second post ;-)
Click to expand...
Click to collapse
That would be pretttty nice! Many beginners would benefit from that!
It makes modding your phone a lot easier!
This is the method I've used and continue to use to root my phone.
Worked a treat on my SGS with stock JF3 firmware.
Thanks!
BackfireNL said:
Tutorial -> Howto root your SGS the easy way (without software and still keep all your data and settings)
Because the lack of good tutorials i decided to write my own! (for n00bs)
This method will keep all your data and settings! this means the phone will not be factory resetted.
You won't need the Android SDK tools to go in recovery mode! or use Odin3
The method is tested on a Dutch SGS with firmware I9000XWJG5 (no simlock)
Reported to work on all firmwares! but use at your own risk! (it is pretty safe and foolproof!)
!!! Disclaimer: If you brick your phone it's your own problem! But it is fairly safe because you can still reflash your phone with Odin3
Only root your phone if you feel the need to! (like applying the lagfix)
Steps:
1. Download: update.zip (got it from samdroid.net)
2. Put update.zip to root of /sdcard (not /sdcard/sd)
3. Remove simcard and SD card (just to be sure)
4. Hold down volume up + home button + power
5. Phone will reboot into recovery mode
6. Wait until you see the Recovery Screen and then release the buttons
7. With the volume down key go to the option: "apply: /sdcard/update.zip"
8. Press the home button
9. Phone will start updating
10. Phone reboots... and there you go! your phone is rooted!
Feel free to comment!
Click to expand...
Click to collapse
Points to raise:
1. You don't have to remove the SIM or SD card
2. You need to put some instruction for the installation of busybox, for example:
adb shell
su
< on the SGS you need to accept the Superuser request >
busybox --install -s /system/xbin
damianarnold said:
Points to raise:
1. You don't have to remove the SIM or SD card
2. You need to put some instruction for the installation of busybox, for example:
adb shell
su
< on the SGS you need to accept the Superuser request >
busybox --install -s /system/xbin
Click to expand...
Click to collapse
Edited point 1.
And about busybox! busybox is already installed when you apply the update.zip!
If you wan't to update busybox or install it you can use the Busybox app from the market! (search busybox or busy box)
Then accept the superuser request!
BackfireNL said:
Edited point 1.
And about busybox! busybox is already installed when you apply the update.zip!
If you wan't to update busybox or install it you can use the Busybox app from the market! (search busybox or busy box)
Then accept the superuser request!
Click to expand...
Click to collapse
Busybox is on the media but it isn't installed, if you don't do a 'proper' install you have to prefix every command with 'busybox' ie. 'busybox cp' to copy. Installing busybox into that directory ensures that all the busybox (standard linux commands) are present making life considerably easier for the various shell scripts that are available for the SGS.
BackfireNL said:
I wish somebody would write a good tutorial for that! (not that i already searched for a good tut.)
I will start trying using adb as soon as i'm going to apply the lag/speedfix!
But first i need a bigger SD card!
Click to expand...
Click to collapse
To be honest its easier to find a video on you tube.
this method is by far the cleanest and simplest way, just the way it should be
Notes:
Click to expand...
Click to collapse
This build is a rework/continuation of MDJ Revolution series
I started this thread, as there was some demand for this to get updated. If m-deejay decides to update his original build, I will discontinue this build
Use this at your own risk. I will not be accountable if this causes you phone to fail, or you lose your data. The backup of your data is your responsibility.
I am a newbie to the android development, so please be patient with fixes and releases; and your help and advice will be appreciated.
Finally: If you cannot donate, then Click Thanks if you appreciate the build, and all works.
Kernel Usage
Click to expand...
Click to collapse
The new thread for the kernel is HERE
ROM Links
Click to expand...
Click to collapse
I have tested an upgrade myself to these releases myself, and have not encountered any problems. But everyones setup is different, the upgrade process may work for you. But would recommend to do a NAND backup before you do. FINALLY, I will not be held responsible if you lose any data.
If you experience any boot loops, then expect at least 2, please report if you do get this, and what was your process, so that I can understand where the problem is happening.
DFT releases have been only included for experimental purposes, I will not guarantee that this works.
The build of this ROM is available here, If anyone wants to have play with this build, then feel free to checkout the repository by running the following command in Linux. This will grab the whole repository onto your machine.
Code:
git clone http://git.gitorious.org/android-leo-revolution/revolution-hd.git
Revolution HD 1.4 Super Light NAND CWM MAGLDR, Click or scan the image
Revolution HD 1.4 Super Light NAND CWM cLK, Click or scan the image
Revolution HD v1.4 Super Light NAND DFT (flashable via MAGLDR) MAGLDR 1.13 required
Revolution HD v1.4 Super Light NAND cLK (flashable via cLK using fastboot) cLK 1.3.1 required, attached in this post
Revolution HD v2.6 NAND CWM MAGLDR, Click or scan the image
Revolution HD v2.6 NAND CWM cLK, Click or scan the image
Revolution HD v2.6 NAND DFT (flashable via MAGLDR) MAGLDR 1.13 required
Revolution HD v2.6 NAND cLK (flashable via cLK using fastboot) cLK 1.3.1 required, attached in this post
Updates
Click to expand...
Click to collapse
Revolution HD 1.4.2 Super Light NAND CWM MAGLDR, Click or scan the image
Revolution HD 1.4.2 Super Light NAND CWM cLK, Click or scan the image
Revolution HD 2.6.2 NAND CWM MAGLDR, Click or scan the image
Revolution HD 2.6.2 NAND CWM cLK, Click or scan the image
Forum Links
Click to expand...
Click to collapse
ClockworkMod HowTo
cLK howto
config.txt Howto
Click to expand...
Click to collapse
This file needs to go onto your FAT32/vfat partition of the SD card
ppp_mode - set PPP or not, valid values 1 or 0 (not for cLK)
gps_zone - zone from pool.ntp.org, values may be uk, us, europe etc... check pool.ntp.org, for all possible values
a2sd_mode - set which a2sd mode you want, possible values, apps, dalvik, data (dalvik is default)
- a2sd - app and app-private
- dalvik - app, app-private and dalvik-cache
- data - app, app-private, dalvik-cache and data
- none - none of the above
example config
Code:
ppp_mode=1
gps_zone=uk
a2sd_mode=data
cLK Howto
Click to expand...
Click to collapse
Download the attached cLK1.3.3_system_300M_arif-ali.zip or cLK1.3.3_system_250M_arif-ali.zip for SL
turn phone on with volume down key, so that it is in SPL
install cLK by double-clicking CustomRUU.exe
To install recovery download the correct one from post #2 of cLK thread (link above)
reboot phone into fastboot by keeping the back key pressed
flash recovery by running "fastboot flash recovery recovery.img"
How To SL1.4.2 & 2.6.2 (CWM - MAGLDR)
Click to expand...
Click to collapse
Make sure you have partitioned the SD card correctly (ext partition, and a vfat partition)
Make sure you have followed the ClockWorkMod Howto to add the recovery to the phone (see links in the thanks/credits section)
Download the link above and put it into the vfat partition, maybe in a folder called ROMS
Boot phone into MAGLDR by holding on the Red button/close call
Select AD Recovery (Option 8)
Select Install zip from sdcard
Select choose zip from sdcard
Select the ROM from the SD
Select Yes to install the zip
reboot the phone and enjoy
How To SL1.4.2 & 2.6.2 (CWM - cLK)
Click to expand...
Click to collapse
Make sure you have partitioned the SD card correctly (ext partition, and a vfat partition)
Download the link above and put it into the vfat partition, maybe in a folder called ROMS
Boot phone into fastboot by pressing the back key
flash the recovery using "fastboot flash recovery recovery.img"
reboot phone into cLK recovery by holding on the Home key
Select Install zip from sdcard
Select choose zip from sdcard
Select the ROM from the SD
Select Yes to install the zip
reboot the phone and enjoy
How To SL1.4 & 2.6 (DFT)
Click to expand...
Click to collapse
MAGLDR 1.13 is now required
Connect phone to computer
Reboot phone and press hold the Red (on/off) button, until you get into the MAGLDR menu
Select USB Flasher
Start the DAF.exe application, and press Next until it tries to flash
press green button (call) button on the phone
This will now flash the phone and reboot
How To SL1.4 & 2.6 (cLK - fastboot)
Click to expand...
Click to collapse
Connect phone to computer
Reboot phone and press hold the back key, until you get into fastboot
Run "fastboot flash boot boot.img"
Run "fastboot flash system system.img"
Run "fastboot flash userdata data.img"
Run "fastboot reboot"
This will reboot phone, enjoy!!!
Howto apps2sd
Click to expand...
Click to collapse
By default app, app-private and dalvik-cache are on the SD card, if you need any other option, then follow the below instructions on what you want
data2sd
Code:
adb shell a2sd datasd
no dalvik on sd
Code:
adb shell a2sd nocache
remove a2sd completely
Code:
adb shell a2sd remove
Howto ROM Manager
Click to expand...
Click to collapse
After booting into the phone, you need to create the following file on your sdcard, and reboot the phone. Hopefully after this, your phone should work.
Code:
/sdcard/clockworkmod/.settings
with the following contents
Code:
{"is_clockworkmod":true,"current_recovery_version":"3.0.1.9","readonly_recovery":false,"recovery_timestamp":1300214577721,"flash_recovery":"flash_image recovery %s ; ","reboot_recovery":"","detected_device":"leo"}
I will attempt to get this added in the next release
Please READ!!!
Click to expand...
Click to collapse
make sure that any app that you do install move it back to the phone, and that will automatically reside on the SD card in the ext2/ext3/ext4 partition
For the Revolution 2.6 you need at least 288 MB in /system, so for EU users you need to flash the CWM build with 300MB /system, you can change the flash.cfg from the ClockworkMod and the change it similar to
Code:
system ya 300M
You can use the attached Recovery_300M.zip instead, which has the files changed, and flash using the attached file.
Known Issues / Bugs
Click to expand...
Click to collapse
At first/second/maybe third boot You will get a message "Process system is not responding".
FIX: press the volume up/down key wait 5 seconds, and it will continue to start
Occasional low volume
To Do List / Work in-progress
Click to expand...
Click to collapse
v2.7 & v1.5
Fix AudioFlinger Issue
re-do init process so that config.txt is read from SD card (only works with MAGLDR)
a2sd mode (apps, dalvik, data) - part 2
Add Stock Theme Option
Thanks/Credits
Click to expand...
Click to collapse
m-deejay (ROM & kernel)
Cotulla (MAGLDR, HSPL)
kholk (Radio)
RaiderX303 (ClockworkMod)
birkoffsjunk (img2cwm)
tkirton (dtapps2sd)
cedesmith (cLK)
letama (ril_wrapper)
#htc-linux and #htc-linux-chat
All ROM users
Screenshots
Screenshots in attachements
Changelog
Common ChangeLog
Code:
[B]v1.4.2 and v2.6.2[/B] (22/03/2011)
* new kernel AA 0.5 (see kernel thread for details)
* support for ROM Manager if using cLK
* Add latest ROM Manager to cLK build
* Update to cLK 1.3.3
* cache moved to mtd cache
* Update gmail, youtube, ES Explorer apks
[B]v1.4.1 and v2.6.1[/B] (11/03/2011)
* fix config.txt default value for a2sd_mode to be dalvik (caused issues if no value in config.txt)
* add config.txt support for cLK (excluding ppp_mode)
[B]v1.4 and v2.6[/B] (6/03/2011)
* fixed bug with upgrade and a2sd
* upgrade kernel to 0.3 (see changelog below for details)
* able to change settings dynamically using config.txt (MAGLDR only)
* gps zone
* ppp/rmnet
* a2sd mode (apps, dalvik, data)
* Add PPP support (to use with cLK)
* fix bugs with PPP
[B]v1.3 and v2.5[/B] (18/02/2011)
* fixed a bug with a2sd+
- now upgrade should work without any problems
- switching between 2.5 and 1.3 shouldn't be a problem now
- if data2sd is enabled, then this won't get ruined
* update kernel so that it contains the latest patches from (http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc)
- merge MDJ kernel with current tree
- kernel-aa-0.2
[B]v1.2 and v2.4[/B] (06/02/2011)
* Fixed root issue
* reverted to dtapps2sd-2.7.5.3-beta04 (credit to tkirton)
- app
- app-private
- dalvik-cache
* added ES Explorer
[B]v1.1 and 2.3 [/B](19/01/11)
* S10.4 OC kernel included
* Loading of the relevant modules correctly
* Add apps2sd+
* Fixed data network issue
[B]v1.0 and 2.2[/B](16/01/11)
* Unsquashed
* Initial Release
Revolution HD
Code:
[B]v2.4.1[/B] (09/02/2011)
* Fixed apps2sd issue
* removed bootanimation.zip
[B]v2.4[/B] (07/02/2011)
* added Talk
Previous Changelogs (MDJ)
Code:
[b]v2.2[/b]
- Squashed apps & framework for more userspace
- Removed some media stuff
[b]v2.1[/b]
- Now for all Leo versions (LEO512 & LEO1024)
- New method (only system.img)
- Newest kernel MDJ S9.1 OC
- Fixed root permissions (Superuser)
- Fixed Market
- Removed some gapps (Talk, Facebook, Twitter, Maps, etc) (you can install it from market)
- Removed some wallpapers
- Removed some themes
- Others fixes/tweaks/changes
[b]v2.0[/b]
- Initial NAND release
[b]v1.0 Super Light[/b]
* Initial Release
* Removed 80% HTC Sense
* Newest kernel MDJ S9.2 OC
I only have mgdlr on a tmous.do I have to partition and do all that stuff.or can I just flash normally.
milkoo said:
I only have mgdlr on a tmous.do I have to partition and do all that stuff.or can I just flash normally.
Click to expand...
Click to collapse
Not at the moment. I will have a go with that later date, keep a look out
where dtapps2sd-2.7.5.2-signed.zip file?
add: ok. i find other thread.
I installed them all but stop blank screen. why?
(sorry for english)
Thanks. I really want that calender fixed.for now if I want to update the kernal I just copy the files with root explorer and reboot?
Sent from my HTC HD2 using XDA App
rambetiko said:
where dtapps2sd-2.7.5.2-signed.zip file?
Click to expand...
Click to collapse
check first post, now attached.
milkoo said:
Thanks. I really want that calender fixed.for now if I want to update the kernal I just copy the files with root explorer and reboot?
Click to expand...
Click to collapse
1. Extract the zip
2. mount the /boot on the phone using adb
3. copy the zImage in boot to /boot
4. copy syste/lib/modules/* to /system/lib/modules/.
5. reboot the phone
It is very likely the following may work, but I don't know your environment to be sure
if /dev/block/mtdblock0 is not your boot then, this will not work. You want to check to make sure
The Link in the first post is not meant for installing using manual process. but for CWM, but if you know what you are doing then you can use it
Code:
adb shell mkdir /data/boot
adb shell mount -t yaffs2 -orw,nosuid,nodev /dev/block/mtdblock0 /data/boot
cd boot
adb push zImage /data/boot/zImage
adb remount
cd ..\system\lib\modules
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push fuse.ko /system/lib/modules/fuse.ko
adb push msm_rmnet.ko /system/lib/modules/msm_rmnet.ko
adb push nls_utf8.ko /system/lib/modules/nls_utf8.ko
echo Cleaning up...
adb shell umount /data/boot
adb shell rmdir /data/boot
That's too confusing.I'm just going to wait for a normal flash.thank you.
Sent from my HTC HD2 using XDA App
Thanks for the work arif-ali, I'm sorry but how do I run the command to xfer the dalvik-cache? sorry if its a stupid question.
Won't boot, bootloop, not a noob
Edit: I didn't try or read enough, my favorite build thank you for your hard work. Make sure SYSTEM PARTION is 400MB from clockwork page
follow instructions and walha sweetest build by to date HD2 devs kick ass
neileisenhauer said:
Won't boot, bootloop, not a noob
Click to expand...
Click to collapse
Me too um almost missing SD android
This is all "greek" to me...I'm going to have to wait for a un-squashed normal NAND version.
I appreciate all the work that you have been doing to keep this alive.
Thanks!
Pictures please
if you may send the pictures in this forum to see if it worked for you. Thank you for working for this.
DAP420 said:
Me too um almost missing SD android
Click to expand...
Click to collapse
1. How big are your system partitions?
for the Revolution HD 2.2 it needs to be ~300MB
2. Have you done a factory/data reset from the CWM menu, before installing via CWM? (make sure you are running 1.2 of ClockWorkMod)
calaisxtyo said:
Thanks for the work arif-ali, I'm sorry but how do I run the command to xfer the dalvik-cache? sorry if its a stupid question.
Click to expand...
Click to collapse
The command is in the first post
search the forums on how to get the adb working on your system
In short
1. download adb for your system
2. make sure adb in your path
3. open a terminal/command prompt
4. run the command in the first post
New release
All,
I am building a release for Super Light, i have it all ready, but I am stuck at one problem at the moment.
After every boot I need to press the volume up/down key once for it to boot.
Something about audioflinger. Anyone have any ideas?
Volume buttom?
Are you talk about auto boot?
I'm not sure I understand the question well.
Check this link half way down the page.
jayceooi.com/2010/12/31/how-to-install-nand-android-on-htc-hd2
Keep up the good work.
Eric Br
I flashed CWM 250M, then installed the lite version 1.1, but it won't boot...
Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.
[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible
Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image
I dont get it
Sent from my Nexus 4 using xda app-developers app
gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake
Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?
Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!
hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.
Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails
Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation
Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk
Model Device: XT1676
Yesterday I unlocked the bootloader, the message "ID: bad key" appeared when the phone was started. I ignored this, I flashed the 64bit twrp and here the problems start - I've tried many roms:
- FireHound v4.5,
- AospExtended v5.4,
- BootleggersROM 2.2,
- dotOS 2.1 and 2.2,
On all roms (except for dotOS 2.1) the same problem appears - the system itself works and starts correctly, but when I flash any version of Open Gapps the phone falls into the bootloop, the exception is dotOS 2.1, it works fine, but there are not many functions has dotOS 2.2, interestingly - when I flash dotOS 2.1, gapps, run the phone and then I do flash update to 2.2, everything works fine, but I would like to use another rom, but all have the same problem, does anyone know how I fix it?
And as for "ID: bad key" - I can not even relock the bootloader and unlock again (I read that helps), because the phone has a bootloader with the NPPS25.137-93-8 stock version, which even can not be downloaded anywhere, and the flash attempt of the older stock is canceled due to the older security patch.
The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
TheFixItMan said:
The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Click to expand...
Click to collapse
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.
Wanted_X2 said:
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.
Click to expand...
Click to collapse
how did you get build.prop by adb? in twrp? what commands? thanks
durc12 said:
how did you get build.prop by adb? in twrp? what commands? thanks
Click to expand...
Click to collapse
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/
Wanted_X2 said:
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/
Click to expand...
Click to collapse
I install the rom, then the gapps, but it says to me that no build.prop is ther with the pull command, I don´t know why
EDIT: finally I did it, but it was neccesary to mount /system in twrp, to check the box in "mount". Thaks for all