Hi this rom is just a rooted, deodexed and flashable version of the latest OTA from T-Mobile. It is meant to be used as a base for other ROMS or if people just want the latest stock experience without having to got back to locked bootloader. Thanks crazysohc for the system dump!
Downloads:
goo.im/devs/sportsstar89/ruby/stock
# cat emmc
dev: size erasesize name
mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 5ffffc00 00000200 "system"
mmcblk0p30: 13fffe00 00000200 "cache"
mmcblk0p31: 9ffffe00 00000200 "userdata"
mmcblk0p32: 01fba800 00000200 "devlog"
mmcblk0p34: 00040000 00000200 "pdata"
mmcblk0p36: 270000000 00000200 "fat"
mmcblk0p37: 00010000 00000200 "extra"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p21: 02000000 00000200 "adsp"
mmcblk0p19: 007ffc00 00000200 "radio_config"
mmcblk0p25: 00400000 00000200 "modem_st1"
mmcblk0p26: 00400000 00000200 "modem_st2"
mmcblk0p18: 02800000 00000200 "mdm9k"
mmcblk0p20: 007ffa00 00000200 "mdm9k_config"
mmcblk0p27: 00400000 00000200 "mdm_efs1"
mmcblk0p28: 00400000 00000200 "mdm_efs2"
Any differences?Still android 4.0.3with sense3.6?
_Le0.<3! said:
Any differences?Still android 4.0.3with sense3.6?
Click to expand...
Click to collapse
Fixed Wi-Fi calling and isis support just the latest OTA from T-Mobile
getting error which installing (status 6 installation aborted)
^worked fine for me.
Thanks sport! I was waiting for this. I haven't learned how to deodex yet.
Sent from my HTC_Amaze_4G using xda app-developers app
SiL3nTKiLL said:
^worked fine for me.
Click to expand...
Click to collapse
i have downloaded 2 times still installation aborted error
mujju85 said:
i have downloaded 2 times still installation aborted error
Click to expand...
Click to collapse
Used to happen to me, I fixed it by downloading the rom directly to the phone's SD instead of transferring from the pc.
itsbuckyb said:
Used to happen to me, I fixed it by downloading the rom directly to the phone's SD instead of transferring from the pc.
Click to expand...
Click to collapse
Ok I m doing this now let's see file is now downloading
Sent from my Micromax P500(Funbook) using xda premium
mujju85 said:
i have downloaded 2 times still installation aborted error
Click to expand...
Click to collapse
Exact same error here. I downloaded it directly to my phone too. I tried installing from both the external sd and the internal. It says the error is in the file, so I'm not sure what's going on.
MD5 sum does not match
Not sure What's going on. Downloaded it from my pc and now the Md5 sums match, but I am still getting the installation abort error.
Guessing I have to rename it to the usual PH85IMG.zip and place it on my sd card and run it in bootloader correct? Sport Thanks a bunch. Once I install it tomorrow morning I'll report back if wifi calling lag is fixed.
PeterC18st said:
Guessing I have to rename it to the usual PH85IMG.zip and place it on my sd card and run it in bootloader correct? Sport Thanks a bunch. Once I install it tomorrow morning I'll report back if wifi calling lag is fixed.
Click to expand...
Click to collapse
no this is a flash-able ROM, use EXT4 recovery
Getting status 6 installation of abort.
Sent from my HTC_Amaze_4G using xda app-developers app
bry2872 said:
Getting status 6 installation of abort.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
It's strange that some say it works, and some of us get status 6 error.
Sent from my HTC_Amaze_4G using xda app-developers app
I get a status 6 error using 4ext, and have downloaded twice. Once from the phone straight to the sdcard & once from the pc
The upload must have gotten corrupted sorrycabout that
Sent from my Nexus 4 using xda premium
Did they fix the signal and battery issues?
blacksapphire08 said:
Did they fix the signal and battery issues?
Click to expand...
Click to collapse
Signal seems a little bit better but battery is about the same
Sent from my HTC_Amaze_4G using xda app-developers app
Related
Hi, i've had my phone for about 6 months and I'm running out of space on the internal memory. It's not an optimus one, but it looks identical to it. It doesn't have much internal memory to begin with. My question is how to unlock it, or how do I delete the locked stuff that clutters it up when I first get it. Diner dash and the stupid little games take up the space that I need.
the simple answer is you need to root. See here for how to. I've had good luck with z4root. When I got my first P509, I rooted but was scared to flash a recovery and rom for fear of bricking my shiny new phone. The fact is though, the only thing that has ever bricked my phone has been KDZ which is an official LG tool.
Once you root, there are many ways that you can go about removing unnecessary bloat. Probably the most popular way is to use Titanium backup which can be downloaded from the market which allows you to uninstall any application on your phone once you grant TiBackup root access.
You could also use Root Explorer (also on the market) which requires that you know a little bit about the phone system itself but will get the job done, if you know what you're doing. Personally I dislike both methods because I don't 'manage' my phone from my phone, too many things can go wrong. Plus, both Titanium Backup and Root Explorer are paid apps. I prefer to use the ADB, but that requires the use of command line which is a big road block for some people.
Should you choose to go the adb route (which assumes that you have installed the Java Development kit available here and the Android Software Development Kit (or SDK) found here
Once you have installed the Android SDK, you can execute the adb (which is in the platform tools folder) from the command line. And no, there is no GUI version, the ADB is strictly a command line tool. To access and modify contents of your phone you will need to gain root access via adb shell. Oh yeah, and don't forget, you need to enable USB debugging on your phone!!!
Code:
adb shell
su
the prompt should change to a pound sign once you have granted "unknown" root access on your phone. once you've gained root access, execute the following command to gain read and write privileges for the phone's system
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
Once you've done this you can delete things from your phone's system, but be EXTREMELY careful because you can mess your phone up pretty bad if you don't know what you're doing.
first, change directory (the command is literally cd) into /system/app which is where all non removable apps are stored on your phone
Code:
cd /system/app
then you can bring up a list of all the files in the folder with
Code:
ls
then you can delete the unnecessary apps with
Code:
rm -rf
I CANNOT STRESS THIS ENOUGH!!!! Be extremely careful about what you delete in here. it is highly recommended that you use the absolute path to the file you are deleting as to minimize accidental cases of
Code:
rm -rf /*
which will probably brick your phone.
in all reality though you're not going to be able to free up much space by removing the games that come with the phone. Plus it is actually safer to simply flash a custom recovery, do a nandroid backup and then flash a custom ROM. The process is simpler, easy to undo and there is very little risk of breaking the system. Modifying the contents of the stock ROM while it may actually seem less extreme than flashing a custom firmware is far more dangerous, simply because you don't have the added security of a good backup to flash back to in case you mess something up. Not only that, but by rooting your phone and removing stock apps already void your warranty so you may as well go ahead and get your money's worth out of the phone.
Once you have installed a custom ROM, you can always use app2sd which is a feature that allows you to install applications to your SD card instead of your phone's internal memory. I don't personally use it because I keep my phone pretty lean, outside of the Android system and default Google apps, I only have maybe 10 or so apps installed; easysms, facebook, twitter, XBMC remote, my bank's app and of course Angry Birds.
N00b-un-2 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
Click to expand...
Click to collapse
I have this phone and use:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount the system partition
***read up on using android sdk (adb)***
attached are the references I keep for working on my Optimus T:
1. List of /system/app files (says 10L, but 10S is the same)
2. List of files I always remove (change to suit your taste)
PS: Once you take care of removing the crapware, let all the built in apps update through the market, then go back and replace the old versions with the new versions (no need for two versions of the same app, it's a waste of space).
Remove file:
rm {filename}
rm AppPack.apk
Replace old version with new version (or make user app a system app):
cat /data/app/{update filename} > /system/app/{original filename}
cat /data/app/com.google.android.maps-1.apk > /system/app/Maps.apk
**remember to use the EXACT same name as shown in the list (Caps make a difference)
I always factory reset after making the changes to clean up.
Enable root access with adb:
C:\android-sdk\tools\adb devices
C:\android-sdk\tools\adb shell
echo 1 > /data/local/lge_adb.conf
*****MANUALLY REBOOT DEVICE*****
Works with P509 V10s
mar11974 said:
I have this phone and use:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount the system partition
Click to expand...
Click to collapse
Maybe different versions of Optimus handle the file system differently. Also, are you mounting via ADB with the phone in recovery? I don't think I've ever mounted anything except mtdblock1 for /system. Interesting, and to be honest from what I understand about the way the filesystem is supposed to work block 3 should be where /system is, but I've never had any success in gaining r/w privilege by mounting anything but block 1.
mar11974 said:
Enable root access with adb:
C:\android-sdk\tools\adb devices
C:\android-sdk\tools\adb shell
echo 1 > /data/local/lge_adb.conf
*****MANUALLY REBOOT DEVICE*****
Works with P509 V10s
Click to expand...
Click to collapse
I've tried rooting the manual way before always without success. Being a Linux hacker, I'm not afraid of the command line and using a tool like z4root always felt like a cop out. But hey, root is root.
Literally to gain root access you are adding a 1 (an on switch if I'm not mistaken) to the a file called lge_adb.conf? That's crazy!
If all you want to do is root, use gingerbreak. Worked on 2 Optimus T phones. It takes maybe 5 minutes.
After rooting, you can download Titanium backup from the market. It can freeze those unwanted apps. If you suddenly find that you need them, you can defrost the apps.
You should consider using a custom ROM. You can use any Optimus T OR Optimus One ROM. Do not use ROMs for the other flavors of Optimus. If you decide to move your app folder to the SD, you can have an almost unlimited # of apps.
Good Luck
N00b-un-2 said:
I've tried rooting the manual way before always without success. Being a Linux hacker, I'm not afraid of the command line and using a tool like z4root always felt like a cop out. But hey, root is root.
Literally to gain root access you are adding a 1 (an on switch if I'm not mistaken) to the a file called lge_adb.conf? That's crazy!
Click to expand...
Click to collapse
The leaked 2.3.3 thread mentioned the method, checked system.mbn file for V10s and the code is there also. This isn't a "hack", it is built into the rom by the manufacturer.
lge_adb.conf doesn't exist in the rom, so it actually is creating a file lge_adb.conf that contains a 1. The system looks for the file on reboot and sets the root status accordingly.
N00b-un-2 said:
Maybe different versions of Optimus handle the file system differently. Also, are you mounting via ADB with the phone in recovery? I don't think I've ever mounted anything except mtdblock1 for /system. Interesting, and to be honest from what I understand about the way the filesystem is supposed to work block 3 should be where /system is, but I've never had any success in gaining r/w privilege by mounting anything but block 1.
Click to expand...
Click to collapse
You may be right, I have been using mtdblock3 from searches trying to remove the crapware, but it works? When using mtdblock1, if you factory restore your phone (HOME + VOL -) do the removed apps return (changes lost)?
mar11974 said:
You may be right, I have been using mtdblock3 from searches trying to remove the crapware, but it works?
Click to expand...
Click to collapse
If you want to find out what is where on your phone, just run:
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
As far as apps returning once they've been removed I wouldn't imagine so. Once you delete them, they're gone. It's not like the Android system has redundancy built into it. If it did, I would imagine that hacking our phones would be considerably more difficult if every time we rebooted the system returned to stock.
Interesting thought though, because I have a bit of experience installing custom firmware on PSPs before I ever started hacking Android and the similarities between the two are striking, but the PSP firmware is designed with redundancy in mind in order to prevent permanent changes being made to the system like flashing custom firmware, and typically the changes made to the system are stored in volatile memory. I had a PSP-3000, and in order to "hack" it so I could play games from the memory stick, it was like a 5 step process involving a ram disk exploit and any time the system suffered a crash or hard reboot, I would have to repeat the whole process, which was often hit or miss. It would usually take me 2-3 attempts to run the exploit enabling custom firmware. Too bad PSP doesn't have an ADB like tool!
doktornotor said:
If you want to find out what is where on your phone, just run:
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
Click to expand...
Click to collapse
Exactly what mine shows, but mounting mtdblock3 command has always worked for me. WHY???
The only thing I can imagine is that since Android is a variant of Linux, there are both a physical address where data is stored and there also exists a virtual file system. Kind of like how you can access the contents of a mounted disk in Linux at /dev/sdb1 or at /media/your-thumb-drive or /mnt/your-thumb-drive, etc. for example. Perhaps this is not the most apt description of this perceived behavior, but I would venture to guess that I'm not too far off. Maybe the virtual location of the particular block is not necessarily important. It certainly leaves one to wonder
mar11974 said:
Remove file:
rm {filename}
rm AppPack.apk
Replace old version with new version (or make user app a system app):
cat /data/app/{update filename} > /system/app/{original filename}
cat /data/app/com.google.android.maps-1.apk > /system/app/Maps.apk
**remember to use the EXACT same name as shown in the list (Caps make a difference)
I always factory reset after making the changes to clean up.
Click to expand...
Click to collapse
The problem with this on a T-Mobile Optimus T is that all the JUNK games and apps and stuff already in the system apps directory, which is why they cant be uninstalled normally.
You can download SuperManager from the market for FREE and remove them from the system/app directory as well, instead of payign for Root Explorer.
If you factory restore the phone, they all come back.
There's a fairly large list of apps you can delete from the TMo optimus T. the primary ones I recommend are the games and telenav GPS. Dont forget to delete the ODEX file as well if you remove the apk!
Here's a list of all the prinstalled junk I've removed off my Optimus T:
AnalogClockWidget.apk
androidERSEmail.apk
AppPack.apk
BookmarksWidget.apk
Calculator.apk <- Redownload from market for different calc app
CalendarWidget.apk
CarHome.apk
CarHomeLauncher.apk
ClockWeatherWidget.apk
ConnectionManagerWidget.apk
DeskClock.apk
DigitalAlarmWidget.apk
DinerDash.apk
DoodleJump.apk
DriveSmart.apk
DriveSmartHelper.apk
DualClockWidget.apk
Email.apk
Facebook.apk <- Redownload from market for current (removable) app
GenieWidget.apk
Gmail.apk <- Redownload from market for current app
GoogleQuickSearchBox.apk
Maps.apk <- Google Maps, Redownload from market for current app
MemoWidget.apk
MessageWidget.apk
MoviePlayer.apk
Music.apk
PacMan.apk
PhotoWidget.apk
PicoTts.apk
Protips.apk
SelfHelp.apk
SoundRecorder.apk
Street.apk
SwypeTips.apk (left swype, just removed the annoying tips part)
Talk.apk
Telenav.apk
thinkdroid.apk
TtsService.apk
Twitter.apk
VisualizationWallpapers.apk
VisualVoicemail.apk <- Redownload from market for current t-mobile app
VoiceDialer.apk
VoiceSearch.apk
Web2goHome.apk
YouTube.apk <- Redownload from market for current (removable) app
Z4Root is the one I used...all you need to do is go to the market .download 4shared .open it and they should be a link there that would allow you to download the app ..if you want to..now search z4root.apk.the latest version should be on top download it ...turn your phone off after that..back on again. enable debugging..go to the app use what you want there's two option ..you can read no need for me to tell you the two options ..click which one you want. then out runs the process and be alarm if your phone reboots....it needs to ....now if you go back to the app you have a choice of un rooting....if you want..there is a app in the market that will check of you have root access..search ..root checker....oh yea you have a new app called super user....that'd what allows root apps to run.do don't uninstall it ..that goes for z4root to ..also..you can use 4shared to get free apps...just search and there you go..
Sent from my LG-P509 using XDA App
This is more like a general question for every android device rather then for a specific one. My question is simple. Is it possible to extract the recovery.img (the stock one) so that it can be flashed back onto the custom recoveries?
i have the same question.
I have a Coby Kyros MID7127. I can get to Stock Recovery, now how do I save it? I've flashed CMW V4.0.1.5 and it more or less works.. but the buttons don't match and that makes it so i can't boot into recovery on power up.
if i could get the stock recovery.img, i'm hoping i could find someone to help me/teach me/point me in the right direction to modify CWM to work on my device.
thanks!
I also want to know this. Anyone?
From here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Your phone has several devices which hold different parts of the filesystem:
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
Note that the order is different for different phones! Check yours to make sure you use the right device.
In this tutorial, we will deal with "recovery" and "boot". "system" holds everything that gets mounted in your system/ directory, and userdata/ is everything that shows up in data/ (this is all the apps you've installed, your preferences, etc).
The recovery and boot partitions are at /dev/mtd/mtd1 and /dev/mtd/mtd2, and before you do anything else you should back these up:
Code:
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
(Note added by lxrose: These commands don't work if your phone is not rooted and the permissions are not set.)
The other thing you should do is put your favorite update.zip file into the root directory of your sd card so that if you screw up your boot partition you can boot into recovery mode and re-apply the update. You probably want one of the pre-rooted recovery images found elsewhere on the forums.
There is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1 unbeknownst to you. Watch out.
yes
Servus...
I just rootet my new HTC Desire X by just following 3 Steps
1. Unlock the Bootloader using HTCDev website
2. Build a custom recovery image using the clockwork image builder, use the touch version (buggy but it works)
(signed recovery image can be found in "RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed.exe" or just make a backup)
builder.clockworkmod.com
flash the recovery image using adb / fastboot
(fastboot flash recovery recovery.img)
3. install Superuser-3.1.3-arm-signed.zip using the custom recovery image (cwm_su doesn't work)
androidsu.com/superuser/
REBOOT.... DONE
(couldn't put this thread where it belongs, there is no place for the HTC Desire X yet)
For all other users, you can download RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed.exe (note that this board adds a space into the filename between 1 and 0) from one of these mirrors:
- http://www.filefactory.com/file/crmx22opr0r
- hotfile.com/dl/174799524/42af8df/RU...5U_1.09.45.201_release_284072_signed.exe.html
have you tested it?
Can't do backup or find the .exe file?
Merowynger said:
Servus...
2. Build a custom recovery image using the clockwork image builder, use the touch version (buggy but it works)
(signed recovery image can be found in "RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed.exe" or just make a backup)
Click to expand...
Click to collapse
^
^
i don't know how to make a backup and i don't know how to find the .exe file^... sorry im noob...
EDIT: LOL, just found out there's another post here from witch you can download it ^^
@MaartenXDA please paste that link here.
You can extract from RUU_PROTO_......_284072_signed.exe by starting the installation and then extract rom.zip from the windows temp directory (its about 370MB)
Unzip rom.zip and take recovery_signed.img (there will be some unzipping errors, but recovery_signed.img is clean).
Then put recovery_signed.img into builder.clockworkmod.com, wait for it to build and download recovery.img.
Has anyone else done it successfully?
For all of you that just want to do the last steps, here is my build of recovery.img.
flash the recovery image using adb / fastboot
(fastboot flash recovery recovery.img)
3. install Superuser-3.1.3-arm-signed.zip using the custom recovery image (cwm_su doesn't work)
Click to expand...
Click to collapse
Cheers,
Jliax said:
For all of you that just want to do the last steps, here is my build of recovery.img.
Cheers,
Click to expand...
Click to collapse
LOLOLOL thnx, i just downloaded that whole RUU_PROTO thing, and it just finished, but now that you just uploaded the recovery.img that whas all for nothing... but thanks
PS: I'm just 12 and live in Holland so i apoligise for my english
---------- Post added at 04:51 PM ---------- Previous post was at 04:41 PM ----------
It worked!!!! Thanks man you're the best :dddddddddddddddddddddd
i highly recommend this for everyone!
I rooted mine successfully yesterday
Many thanks to Merowynger !!!!
Just a summary of _all_ steps to root your HTC Desire X, because it was a little bit of work to figure out all the steps:
1) Unlock the Bootloader using the HTCDev website: http://htcdev.com/bootloader (choose other supported devices in the drop-down list)
2) Download recovery.img two posts above this one) http://forum.xda-developers.com/showpost.php?p=32789024&postcount=6
3) Download Superuser-3.1.3-arm-signed.zip from http://androidsu.com/superuser/
4) Put recovery.img in C:\Android\ (just like in the unlocking guide)
5) Put Superuser-3.1.3-arm-signed.zip on the root of your sdcard (/sdcard/)
6) Start with vol.down and power to get into the bootloader
7) Choose fastboot
8) Start the command line again and goto C:\Android\ where adb.exe etc reside (just like in the unlocking guide)
9) Now type into the command line:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
10) on your phone choose bootloader
11) choose recovery
12) Now choose install zip from sdcard in the clockworkmod menu, locate the Superuser-3.1.3-arm-signed.zip and choose install.
13) Reboot
@ MaartenXDA congrats
Merowynger said:
Servus...
I just rootet my new HTC Desire X by just following 3 Steps
.....
Click to expand...
Click to collapse
Did you get the clockworkmod ROM manager working yet? I would like to make a full backup since it does not work with the current recovery.img. And the ROM manager app is complaining that clockworkmod recovery is not installed
Finally a thread for the desire x :good:
Jliax said:
Did you get the clockworkmod ROM manager working yet? I would like to make a full backup since it does not work with the current recovery.img. And the ROM manager app is complaining that clockworkmod recovery is not installed
Click to expand...
Click to collapse
hmm looks like you need S-OFF the device too.
Jliax said:
I rooted mine successfully yesterday
Many thanks to Merowynger !!!!
Just a summary of _all_ steps to root your HTC Desire X, because it was a little bit of work to figure out all the steps:
1) Unlock the Bootloader using the HTCDev website: http://htcdev.com/bootloader (choose other supported devices in the drop-down list)
2) Download recovery.img two posts above this one) http://forum.xda-developers.com/showpost.php?p=32789024&postcount=6
2) Download Superuser-3.1.3-arm-signed.zip from http://androidsu.com/superuser/
3) Put recovery.img and Superuser-3.1.3-arm-signed.zip on the root of your sdcard (/sdcard/)
4) Start with vol.down and power to get into the bootloader
5) Choose fastboot
6) Start the command line again and goto C:\Android where adb.exe etc reside (just like in the unlocking guide)
7) Now type into the command line:
8) on your phone choose bootloader
9) choose recovery
10) Now choose install zip from sdcard in the clockworkmod menu, locate the Superuser-3.1.3-arm-signed.zip and choose install.
11) Reboot
@ MaartenXDA congrats
Click to expand...
Click to collapse
Hey guys, can somebody confirm its working? Thank you!
tsx777 said:
Finally a thread for the desire x :good:
Click to expand...
Click to collapse
There are already a couple of threads for the HTC Desire X, including one of mine: http://forum.xda-developers.com/showthread.php?t=1936685(With all the specs of the phone) And if you just search for "HTC Desire X", you'll get a couple threads, also with a guide to root the Desire X, wich i mentioned in my thread too
---------- Post added at 04:25 PM ---------- Previous post was at 04:19 PM ----------
feretti said:
Hey guys, can somebody confirm its working? Thank you!
Click to expand...
Click to collapse
Yes, it works, it's quite easy actually, like i said before, it works, and the risk of bricking your phone is extremely small
MaartenXDA said:
There are already a couple of threads for the HTC Desire X, including one of mine: http://forum.xda-developers.com/showthread.php?t=1936685(With all the specs of the phone) And if you just search for "HTC Desire X", you'll get a couple threads, also with a guide to root the Desire X, wich i mentioned in my thread too
Click to expand...
Click to collapse
Yeah, but i'm still waiting for an own Desire X Forum. Some devices like the S3 mini have one - and they aren't even on the market yet.
not writable
Guys your method works. Phone looks rooted, but I cant access to as RW.
Second, that recovery.img doesnt work properly... Fix permissions etc doesnt work, screen size doesnt fit..
Sorry, but I cant declare that using above root tools doesnt help enough.
T
can someone make a system dump :fingers-crossed: thx
Ah well, i just saw my thread was moved to HTC Desire X forum, altough i can't find it when searching for it, when i find it, i will post the link.
EDIT: here it is: http://forum.xda-developers.com/forumdisplay.php?f=1846
Sent from my HTC Desire X using xda premium
x3reme85 said:
can someone make a system dump :fingers-crossed: thx
Click to expand...
Click to collapse
Isn't the RUU mentioned in this thread enough? Otherwise how can we do that?
Need a few people to see if the recovery works. If some can confirm it works, then I have a toolkit ready!
Also, can someone adb and type this in. Then upload the file?
cat proc/emmc > emmc.txt
hasoon2000 said:
Need a few people to see if the recovery works. If some can confirm it works, then I have a toolkit ready!
Also, can someone adb and type this in. Then upload the file?
cat proc/emmc > emmc.txt
Click to expand...
Click to collapse
[email protected]:/ $ cat proc/emmc
cat proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 3bdffe00 00000200 "system"
mmcblk0p27: 0ffffe00 00000200 "cache"
mmcblk0p26: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p31: 46800000 00000200 "fat"
mmcblk0p29: 00011c00 00000200 "extra"
Send me the toolkit and I will test it.
And do let me know if you need anything else.
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
x3reme85 said:
can someone make a system dump :fingers-crossed: thx
Click to expand...
Click to collapse
MaartenXDA created the system dump, this thread contains the download link: http://forum.xda-developers.com/showthread.php?t=1940575
---------- Post added at 10:17 PM ---------- Previous post was at 09:50 PM ----------
For anyone that is interested: While starting clockworkmod recovery it says:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I choose 'backup' or 'create image zip' it says:
Code:
Backing up boot image...
Backing up recovery image...
Backing up system...
Can't mount /system!
HTC Droid DNA System Dump
This is the system dump from the new HTC DNA
from Verizon Wireless.
Download:
HTC Droid DNA System Dump for Verizon Wireless
MD5: ae8b615957b8b66e88eacc1f0c094b57
Thanks:
b16
I can make a base in the morning. Just need the mount points of the phone.
Sent From My HTC Amaze 4G via Someone's Room
Downloading now. I need the mount points to make a base. Can you run this command via adb?
adb shell
cat proc/emmc
Great. Your system dump is corrupted. Did an MD5 check and it matches.
hasoon2000 said:
Great. Your system dump is corrupted. Did an MD5 check and it matches.
Click to expand...
Click to collapse
heres a deodexed version of a different system dump: http://d-h.st/F4v
script hasnt been verified for flashing at all, but might give you something to poke around with (read dont flash it)
i dont have the phone yet, so havent been able to see if there were any issues with apks and jars that were deodexed
Interesting.. the boot animation is in: system\customize\resource\hTC_bootup.zip
JaeKar99 said:
Interesting.. the boot animation is in: system\customize\resource\hTC_bootup.zip
Click to expand...
Click to collapse
you can always change the bootani path in /system/customize/CID/default.xml
but wont work w/o a data wipe though (usually changed in roms)
nitsuj17 said:
you can always change the bootani path in /system/customize/CID/default.xml
but wont work w/o a data wipe though (usually changed in roms)
Click to expand...
Click to collapse
Thanks for the pointer. I seem to be inching closer to actually getting my hands dirty playing with some ROM guts.
hasoon2000 said:
Great. Your system dump is corrupted. Did an MD5 check and it matches.
Click to expand...
Click to collapse
Appears to be fine on my end.. is the zip corrupt or the data within? If its the zip I will reupload.
Sent from my Galaxy Nexus using xda app-developers app
the zip seems to be the issue.
mcluvn said:
the zip seems to be the issue.
Click to expand...
Click to collapse
Mcluvn you got one too or no?
Sent from my Galaxy Nexus using Tapatalk HD
not yet but it's coming soon
hasoon2000 said:
Great. Your system dump is corrupted. Did an MD5 check and it matches.
Click to expand...
Click to collapse
mcluvn said:
not yet but it's coming soon
Click to expand...
Click to collapse
Re-Uploaded ZIP and Updated the OP with new MD5. Let me know if you still experience issues with the archive.
hasoon2000 said:
Great. Your system dump is corrupted. Did an MD5 check and it matches.
Click to expand...
Click to collapse
pretty sure it has something to do with the bootloader it encrypts the zip
hasoon2000 said:
Downloading now. I need the mount points to make a base. Can you run this command via adb?
adb shell
cat proc/emmc
Click to expand...
Click to collapse
Code:
mmcblk0p21: "misc"
mmcblk0p20: "recovery"
mmcblk0p19: "boot"
mmcblk0p32: "system"
mmcblk0p28: "local"
mmcblk0p33: "cache"
mmcblk0p34: "userdata"
mmcblk0p24: "devlog"
mmcblk0p26: "pdata"
mmcblk0p29: "extra"
mmcblk0p16: "radio"
mmcblk0p17: "adsp"
mmcblk0p15: "dsps"
mmcblk0p18: "radio_config"
mmcblk0p22: "modem_st1"
mmcblk0p23: "modem_st2"
mmcblk0p30: "cdma_record"
mmcblk0p31: "reserve"
incase still needed the info
is this flashable? if not can anyone point me to a base flashable ROM that i can begin modding
Dri94 said:
is this flashable? if not can anyone point me to a base flashable ROM that i can begin modding
Click to expand...
Click to collapse
I don't believe it is flashable (OP can chime in). There is currently only two options for you if this isn't flashable:
Install the Stock/Rooted/Deodexed ROM in this forum.
Go to Fastboot, "fastboot oem lock" and the use the RUU to return to stock (RUU program is sticky on this forum).
If anyone can correct me on this, please feel free.
WorldOfJohnboy said:
I don't believe it is flashable (OP can chime in). There is currently only two options for you if this isn't flashable:
Install the Stock/Rooted/Deodexed ROM in this forum.
Go to Fastboot, "fastboot oem lock" and the use the RUU to return to stock (RUU program is sticky on this forum).
If anyone can correct me on this, please feel free.
Click to expand...
Click to collapse
I dont want to return to stock I want to get a base flashable Rom so I can mood out and debloat
____________________________________________________
"I used to do drugs. I still do, but I used to, too."
Dri94 said:
I dont want to return to stock I want to get a base flashable Rom so I can mood out and debloat
____________________________________________________
"I used to do drugs. I still do, but I used to, too."
Click to expand...
Click to collapse
Then your best bet is to flash the only ROM currently available if you don't want to return to stock. It's deodexed so you can mod all you want.
I just flashed the RUU and am starting from scratch... I did something to mess up some widgets, etc. so I wanted to start over.
WorldOfJohnboy said:
Then your best bet is to flash the only ROM currently available if you don't want to return to stock. It's deodexed so you can mod all you want.
I just flashed the RUU and am starting from scratch... I did something to mess up some widgets, etc. so I wanted to start over.
Click to expand...
Click to collapse
Are you able to Unlock after you Re-lock to RUU?
As the title suggests How To Extract Stock Recovery.img From an android device ?
Nishchay1 said:
As the title suggests How To Extract Stock Recovery.img From an android device ?
Click to expand...
Click to collapse
well its quite easy but it can get complicate if you have bml partition
if you have MTD partition then conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
but if your file partition is BML in that case you have a problem.
What model is your cell phone ?
dvucino said:
well its quite easy but it can get complicate if you have bml partition
if you have MTD partition then conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
but if your file partition is BML in that case you have a problem.
What model is your cell phone ?
Click to expand...
Click to collapse
I have a Karbonn A21 . And i dont know what partition do i have . Is there any way to know it ?
i typed cat/proc/mtd but it is showing sh: cat/proc/mtd: not found
Hi,
you need to put a SPACE character between cat and /proc/mtd...
So the correct command is
cat /proc/mtd
Regards
TheSSJ said:
Hi,
you need to put a SPACE character between cat and /proc/mtd...
So the correct command is
cat /proc/mtd
Regards
Click to expand...
Click to collapse
My hcl me u1 tab shows dev : size erasesize name
Means what?i have rooted my tab and i also want to make recovery for my tab.can you help me?
Sent from my GT-I5800 using Tapatalk 2
pratikmore said:
My hcl me u1 tab shows dev : size erasesize name
Means what?i have rooted my tab and i also want to make recovery for my tab.can you help me?
Sent from my GT-I5800 using Tapatalk 2
Click to expand...
Click to collapse
My Device also showing the same " dev : size erasesize name "
Which is the recovery partition ?
OK, that is very interesting!
There´s another possibility to make a backup:
you need SP Flash tool: chinamobiles.org/attachment.php?attachmentid=23720&d=1354147322
and MTK droid tools: http://chinamobiles.org/downloads.php?do=file&id=733
Open MTK droid tools, connect booted phone in Android and click on "blocks map". Switch to full screen mode and make a shortcut copy of all the shown datas. Best: Print that page, you´ll need it later.
Close MTK droid tools again.
Open Flash_tool.exe.
Go to read back and remove all entries if there are any.
Click an "add".
Double-click on entry. Change name "ROM_0" to first entry of you printed list, i.e. "PRELOADER".
click "save"
in next window let "HEX" and enter start adress and length of the list in HEX format (starts always with 0x...)
i.e. PRELOADER start adress 0x0, length 0x40000.
repeat "add" with all entries like DSP_BL, MBR, EBR1, PMT... in my example 19 entries.
Take care that all adresses and lenghts are correct!
at least push "read back"
SP Flash tool will create a backup.
It shows unknown rom structure,backup not possible,not showing anything when click to block info.plz help me...
Sent from my GT-I5800 using Tapatalk 2
In terminal emulator it shows
(1) + stopped (signal) system/bin/romdump
When i used romdump,it means???
Sent from my GT-I5800 using Tapatalk 2
I'm trying to make a backup of stock firmware on the UG007. When I run the ROM structure commands in adb shell, this is what I get
Code:
[email protected]:/ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 20000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 175000000 00004000 "user"
What partitions do I need and what is the extension that I need to use for each in this format?
example:
Code:
[email protected]:/ # dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 0.817 secs (20535148 bytes/sec)
See above post of duvcno
Sent from my GT-I5800 using Tapatalk 2
I am able to get the recovery.img but what other partitions do I need in order to backup the stock firmware?
Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2
loociddreemr said:
I am able to get the recovery.img but what other partitions do I need in order to backup the stock firmware?
Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2
Click to expand...
Click to collapse
Friend,first make the cwm recovery with recovery builder using recovery.img,just google recovery builder.then with new cwm you can take a backup.
Sent from my GT-I5800 using Tapatalk 2
There are others with soft bricked devices. I was trying to create a flashable file for others to use. Will the CWM backup be useful for others? What would be the most useful format for ROM development?
Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2
You can convert any file format in .Zip by online or with some software,just take a backup of your stock rom with cwm.Your phone is based on Allwiner a10 or A13/rockchip based?
Sent from my GT-I5800 using Tapatalk 2
Yes, it's a mini-PC based on a Rockchip RK3066 A9
Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2
loociddreemr said:
Yes, it's a mini-PC based on a Rockchip RK3066 A9
Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2
Click to expand...
Click to collapse
Just visit here :-
http://forum.xda-developers.com/showthread.php?t=1734181
Also :- http://forum.xda-developers.com/showthread.php?t=1987393
Sent from my GT-I5800 using Tapatalk 2
Hey guys, sorry to bother you. Wonder if you guys can help:
I was trying to back up the rom (UG007). I tried connecting to a laptop but it was not detected, not even as a unknown USB device. I connected the UG007 with a USB extender cable (I guess it is called the B type-the big one) with a Male-Male gender changer at one end to the large USB port of a laptop. Also used the mini/micro usb to connect power and HDMI to the TV. I had the "connect to pc" checked and USB debugging on.
Am I doing anything wrong?
Thanks in advance.
install usb driver
Sent from my GT-I5800 using Tapatalk 2
pratikmore said:
install usb driver
Sent from my GT-I5800 using Tapatalk 2
Click to expand...
Click to collapse
Hi Pratikmore, thanks for your suggestion. I can only install the usb driver once the computer has detected the device.
Anyway, made it work. The trick is to connect your device with usb (both micro or the regular usb port work) and only then check the "connect to PC". After that the computer detects the new hardware and then install the usb driver.
Now I have to figure out how to backup the ROM in a relatively non-technical method. Any help?
Thanks