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?
Related
This basically (for right now) the stock kernel image with some tweaks to init.
-unsecure boot.img-(perma- rooted adb shell)
-adb remount(mount /system r/w)
-init.d support added in for init scripts(survive after reboot)
-ext4 filesystem mount tweaks-/system/data/cache(faster I/O)
(Actually have a full ext2 version for,****s and giggles, but it boots into the encryption error screen, so cant release that. May have a fix though)
-mem and cache tweaks coming soon
still working on the actual kernel, will release that next, still have lots of work to do
boot.img MD5- fca41dba8f4699b67fd461a1632b65cf
MAKE BACKUP FIRST
You will not have issues if you wipe data, chances are youll be fine if you dont, but if anything starts acting up just wipe data, then install boot.img
This is the actual boot.img and for now has to be flashed with adb with these EXACT commands--
Code:
adb push boot.img /sdcard/
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
reboot
#Thanks Diamondback and friends for offsets
This is not the ideal way to flash this, but i can not get the blob file to staging partition to actually write the image. Im pretty sure its an issue with the signature of the blob file, so if someone wants to pack this into a blob id be glad test it and then update the OP.
My primes been using this boot.img for a few days, along with one other. Flash at your own risk.
NOT COMPATIBLE WITH CM-9
di11igaf said:
This basically (for right now) the stock kernel image with some tweaks to init.
-unsecure boot.img-(perma- rooted adb shell)
-adb remount(mount /system r/w)
-init.d support added in for init scripts(survive after reboot)
-ext4 filesystem mount tweaks-/system/data/cache(faster I/O)
(Actually have a full ext2 version for,****s and giggles, but it boots into the encryption error screen, so cant release that. May have a fix though)
-mem and cache tweaks coming soon
still working on the actual kernel, will release that next, still have lots of work to do
boot.img MD5- fca41dba8f4699b67fd461a1632b65cf
MAKE BACKUP FIRST
You will not have issues if you wipe data, chances are youll be fine if you dont, but if anything starts acting up just wipe data, then install boot.img
This is the actual boot.img and for now has to be flashed with adb with these EXACT commands--
Code:
adb push boot.img /sdcard/
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
reboot
#Thanks Diamondback and friends for offsets
This is not the ideal way to flash this, but i can not get the blob file to staging partition to actually write the image. Im pretty sure its an issue with the signature of the blob file, so if someone wants to pack this into a blob id be glad test it and then update the OP.
My primes been using this boot.img for a few days, along with one other. Flash at your own risk.
Click to expand...
Click to collapse
Great! I'm not the only one who as this problem. For what ever reason I too cannot get the blob to write.
I've tried running the blobpack -s to sign the blob but after trying to write it to the staging partition its a no go.....
EDIT: how are you working on the kernel if it has not been released yet?? JW, not trying to say your not but it would be cool if someone found a way to edit a compiled kernel.
MasterZen88 said:
Great! I'm not the only one who as this problem. For what ever reason I too cannot get the blob to write.
I've tried running the blobpack -s to sign the blob but after trying to write it to the staging partition its a no go.....
EDIT: how are you working on the kernel if it has not been released yet?? JW, not trying to say your not but it would be cool if someone found a way to edit a compiled kernel.
Click to expand...
Click to collapse
ICS kernel source is on the global download site.
Doktaphex said:
ICS kernel source is on the global download site.
Click to expand...
Click to collapse
Correct but thats an older source code V9.4.2.7 right?
MasterZen88 said:
Correct but thats an older source code V9.4.2.7 right?
Click to expand...
Click to collapse
True, I don't know how much they have changed since then. Surely they need to be releasing new source pretty quickly to be in compliance with the license. I don't know enough about that side of things though.
prime has a BLOBSIGN signature in the first 28 bytes of the blob files for prime.
you just need to copy those 28bytes from an existing blob file that works.
this is of course only working on a unlocked prime. then the BLOBSIGN signature is not checked, so anything can be pasted in front of it.
Rayman will update the packblob to include the signature later on.
MasterZen88 said:
Great! I'm not the only one who as this problem. For what ever reason I too cannot get the blob to write.
I've tried running the blobpack -s to sign the blob but after trying to write it to the staging partition its a no go.....
EDIT: how are you working on the kernel if it has not been released yet?? JW, not trying to say your not but it would be cool if someone found a way to edit a compiled kernel.
Click to expand...
Click to collapse
I'm confused. I thought after our PMs you had it flashing just fine?
Sent from my Galaxy Nexus using Tapatalk
jermaine151 said:
I'm confused. I thought after our PMs you had it flashing just fine?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yes it flashed but later I realize non of my settings/changes took effect.
When I stated it work, I had took the stock kernel/initramfs from asus blob, extracted, made no changes at all, recompile like we talked about in our PM's then flashed it. It work but then after I made changes, recompiled. Non of my changes took effect.
Again Jermaine you have been a BIG help. and can only hope one day I can return the favor!!!
jermaine151 said:
I'm confused. I thought after our PMs you had it flashing just fine?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
MasterZen88 said:
Yes it flashed but later I realize non of my settings/changes took effect.
When I stated it work, I had took the stock kernel/initramfs from asus blob, extracted, made no changes at all, recompile like we talked about in our PM's then flashed it. It work but then after I made changes, recompiled. Non of my changes took effect.
Again Jermaine you have been a BIG help. and can only hope one day I can return the favor!!!
Click to expand...
Click to collapse
Flashing blobs does NOT always work. No idea why yet. Directly dd'ing the boot.img to the right place works BETTER than flashing a blob in some cases...
Asus really screwed up with this Unlocker thing....
MasterZen88 said:
Yes it flashed but later I realize non of my settings/changes took effect.
When I stated it work, I had took the stock kernel/initramfs from asus blob, extracted, made no changes at all, recompile like we talked about in our PM's then flashed it. It work but then after I made changes, recompiled. Non of my changes took effect.
Again Jermaine you have been a BIG help. and can only hope one day I can return the favor!!!
Click to expand...
Click to collapse
No problem. I'm surprised it didn't work for you after you made changes.
Diamondback said:
Flashing blobs does NOT always work. No idea why yet. Directly dd'ing the boot.img to the right place works BETTER than flashing a blob in some cases...
Asus really screwed up with this Unlocker thing....
Click to expand...
Click to collapse
Flashing them to staging seems to work perfectly for me. That's how I made my insecure boot.blob and flashed it. It doesn't matter whether you're on unofficial CWM or Official since if you start your updater-script with unmounting staging, it doesn't hurt anything if staging wasn't mounted. Then you can either dd the blob to mmcblk0p4 or you can directly flash it via:
Code:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
I have not found an occasion where this didn't work. You need to make sure that you don't add any --cmdline parameters when you mkbootimg or you will get a bootloop. Staging is definitely the safest way to flash to any partitions on the Prime.
MasterZen88 said:
Correct but thats an older source code V9.4.2.7 right?
Click to expand...
Click to collapse
The kernel versions seem to be the same with the latest .15 build as the previous one. I wonder if they just recompiled the same source and that's why the host name changed to Mercury.
EDIT: I'm going to pack this kernel into a flashable blob and attach it here.
jermaine151 said:
No problem. I'm surprised it didn't work for you after you made changes.
Flashing them to staging seems to work perfectly for me. That's how I made my insecure boot.blob and flashed it. It doesn't matter whether you're on unofficial CWM or Official since if you start your updater-script with unmounting staging, it doesn't hurt anything if staging wasn't mounted. Then you can either dd the blob to mmcblk0p4 or you can directly flash it via:
Code:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
I have not found an occasion where this didn't work. You need to make sure that you don't add any --cmdline parameters when you mkbootimg or you will get a bootloop. Staging is definitely the safest way to flash to any partitions on the Prime.
Click to expand...
Click to collapse
Hmm.. not sure whats going on but I did use this command
Code:
mkbootimg --kernel boot.img-kernel.gz --ramdisk newramdisk.cpio.gz -o newboot.img
To recompile the boot.img then used the new blobtoolsv2 to repack the blob
Code:
blobpack -s kernelblob blob.LNX newboot.img
I know staging is unmounted because I'm using your updater-script
jermaine151 said:
Flashing them to staging seems to work perfectly for me. That's how I made my insecure boot.blob and flashed it. It doesn't matter whether you're on unofficial CWM or Official since if you start your updater-script with unmounting staging, it doesn't hurt anything if staging wasn't mounted. Then you can either dd the blob to mmcblk0p4 or you can directly flash it via:
Code:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
I have not found an occasion where this didn't work. You need to make sure that you don't add any --cmdline parameters when you mkbootimg or you will get a bootloop. Staging is definitely the safest way to flash to any partitions on the Prime.
Click to expand...
Click to collapse
if you copy the blob, while p4 is mounted to staging in cwm, you will have a problem when you reboot, as the filesystem umount, and that cause a small change to the mounted filesystem, to indicate it is umounted normally. and the p4 partition becomes invalid.
so it can easily become a problem if p4 is mounted.
at least thats how i experienced the problem when seen initially.
Dexter_nlb said:
if you copy the blob, while p4 is mounted to staging in cwm, you will have a problem when you reboot, as the filesystem umount, and that cause a small change to the mounted filesystem, to indicate it is umounted normally. and the p4 partition becomes invalid.
so it can easily become a problem if p4 is mounted.
at least thats how i experienced the problem when seen initially.
Click to expand...
Click to collapse
That's why I said to always add an unmount("/staging"); to the top of your script. The attached flashable zip works perfectly on the official CWM; staging is not mounted by default, but I told the script to unmount it anyway in case someone with the unofficial CWM tries to flash it. If it's already unmounted, the script just continues.
Anyone may use this as a template for consistently flashing a kernel to staging.
MasterZen88 said:
Hmm.. not sure whats going on but I did use this command
Code:
mkbootimg --kernel boot.img-kernel.gz --ramdisk newramdisk.cpio.gz -o newboot.img
To recompile the boot.img then used the new blobtoolsv2 to repack the blob
Code:
blobpack -s kernelblob blob.LNX newboot.img
I know staging is unmounted because I'm using your updater-script
Click to expand...
Click to collapse
Hmm... That all looks good. What happens after you attempt to flash this and what changes did you make to the ramdisk?
EDIT: Hey, I just re-read your PM. It sounds like you're editing the wrong file in the ramdisk. To make an insecure boot image, you should be editing init.rc, NOT init.cardhu.rc.
Here's a great guide to follow. It's the same procedure for the Prime as the original Transformer:
http://forum.xda-developers.com/showthread.php?t=1193737
jermaine151 said:
Hmm... That all looks good. What happens after you attempt to flash this and what changes did you make to the ramdisk?
EDIT: Hey, I just re-read your PM. It sounds like you're editing the wrong file in the ramdisk. To make an insecure boot image, you should be editing init.rc, NOT init.cardhu.rc.
Here's a great guide to follow. It's the same procedure for the Prime as the original Transformer:
http://forum.xda-developers.com/showthread.php?t=1193737
Click to expand...
Click to collapse
Okay that makes sense. One f my changes was to default.prop for insecure boot.img
Code:
ro.secure=0
This did not show after I flashed. But I will try again in a couple hour's once my workload calms down... SysAdmin life is not easy...lol
MasterZen88 said:
Okay that makes sense. One f my changes was to default.prop for insecure boot.img
Code:
ro.secure=0
This did not show after I flashed. But I will try again in a couple hour's once my workload calms down... SysAdmin life is not easy...lol
Click to expand...
Click to collapse
LOL! I meant to say default.prop and not init.rc. I totally understand. I used to be a SysSdmin too. Now I moved more towards the networking side of things. Much more calm.
jermaine151 said:
LOL! I meant to say default.prop and not init.rc. I totally understand. I used to be a SysSdmin too. Now I moved more towards the networking side of things. Much more calm.
Click to expand...
Click to collapse
Would love to be on that side of the tracks. I'm banging my head against the wall right now trying to figure out how to implement Microsoft System Center Service Manager 2010 and on top of that one of our Citrix Broker boxes went down last night... Not a funny day at all. But I'll keep this thread about Android...for now....
No, unfortunately flashing a blob does not always do the same as dd'ing boot.img directly. We recently had a case were someone lost root access. the only way to recover was to directly dd a boot.img.
Flashing the SAME boot.img via blob did not work (nor did any other blob we tested)
So blob flashing obviously has some quirks....
Diamondback said:
No, unfortunately flashing a blob does not always do the same as dd'ing boot.img directly. We recently had a case were someone lost root access. the only way to recover was to directly dd a boot.img.
Flashing the SAME boot.img via blob did not work (nor did any other blob we tested)
So blob flashing obviously has some quirks....
Click to expand...
Click to collapse
I just haven't see that issue flashing any of my blobs and CM9 is using the same method and it's working. Who knows.
jermaine151 said:
I just haven't see that issue flashing any of my blobs and CM9 is using the same method and it's working. Who knows.
Click to expand...
Click to collapse
We only had it one time too, but one time is enough to scare me further
This whole blob stuff just is crap
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!
I only started android kernel dev less than a week ago, but I have managed to successfully modify and update the kernel for my HP touchpad without too many issues.
My issue now is I'm trying to update the kernel on my HTC One XL (AT&T One X), and reading through guides like (h ttp://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images), I need to make a copy of the boot image. However I can't find the boot image!?!?!
The following folder does not exist:
/dev/mtd
or
/proc/mtd
Am I missing something? I'm sure this is a total noob problem, but can't find a solution anywhere.
In my TWRP backup folder I have a 'boot.emmc.win' file, can I extract the boot img from this?
Any help would be great!!
DACcer said:
I only started android kernel dev less than a week ago, but I have managed to successfully modify and update the kernel for my HP touchpad without too many issues.
My issue now is I'm trying to update the kernel on my HTC One XL (AT&T One X), and reading through guides like (h ttp://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images), I need to make a copy of the boot image. However I can't find the boot image!?!?!
The following folder does not exist:
/dev/mtd
or
/proc/mtd
Am I missing something? I'm sure this is a total noob problem, but can't find a solution anywhere.
In my TWRP backup folder I have a 'boot.emmc.win' file, can I extract the boot img from this?
Any help would be great!!
Click to expand...
Click to collapse
It uses emmc now. To check your partitions you can use: adb shell cat /proc/emmc
blazingwolf said:
It uses emmc now. To check your partitions you can use: adb shell cat /proc/emmc
Click to expand...
Click to collapse
:victory: that works!!!
However, now that I can see mounts, how can I copy the required image? For instance the output is:
#cat /proc/mtd
dev: size erasesize name
mmcblk0p23: 000....0 000....000 "misc"
mmcblk0p22: 00500000 00020000 "recovery"
mmcblk0p21: 00280000 00020000 "boot"
etc.
cat /dev/emmc/mmcblk0p21 gives me a file not found error.
There is a '21' folder under /dev/emmc? Assume this is the image??
Something along the lines of this should work: dd if=/dev/block/mmcblk0p21 of=/sdcard/boot.img bs=4096
Make sure the info is correct for your device.
blazingwolf said:
Something along the lines of this should work: dd if=/dev/block/mmcblk0p21 of=/sdcard/boot.img bs=4096
Make sure the info is correct for your device.
Click to expand...
Click to collapse
Ahhhh, the dd command :highfive:
Cheers blazingwolf! Just tried it then, and worked perfectly. Didn't set the block size, but assuming that's okay
What is this?
These are pre-rooted Stock ROM Base's for Developer to use to create modified stock ROMs or for the average Joe to restore their device's to working order if they are stuck in a bootloop. You must have an unlocked bootloader and a working Custom Recovery to use this.
Downloads:
T-Mobile / Retail US - 139.11.6 - Odex ***Tested, will not go past the boot logo.
Instructions:
Put the .zip on your internal storage.
Boot up to your Custom Recovery of choice (example: Clockworkmod Recovery).
Make a complete backup of your device using the Custom Recovery, and store that backup on a computer or alternative storage.
Wipe data using the Custom Recovery.
Mount system using the Custom Recovery.
Format system using the Custom Recovery.
Install the .zip from your internal storage using the Custom Recovery.
Reboot and enjoy! (If it asks to disable recovery install, tell it not to.)
Thanks:
My testers.
The Firmware Team.
mhous33 for the base script/binary for the RAZR M DST ROM.
I'll try to get some more bases up since we now have the means to install them and have them working correctly.
Amazing!
Thanks alot man. Never hurts to have an extra backup on my Google Drive or something should the worst happen.
Flashing in 15 minutes or so, when it's done downloading.
THANK YOU for this!
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
It's not booting, so I can't retrieve the file you need. Adb won't detect the device
Gonna have to restore my backup.
[edit] actually ADB is seeing it once I go to recovery... how do I retrieve the file you need?
figured it out, here is the file you requested: https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Extracted using adb while phone was in recovery, after flashing your file. Have to restore now =P
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
scorpion667 said:
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
Click to expand...
Click to collapse
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
mattlgroff said:
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
It did that for me on the first rom, I don't know if Matt put something in the build prop to differentiate it from the stock rom
Sent on my Moto X
scorpion667 said:
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
Click to expand...
Click to collapse
Sounds like its not flashing to system at all
Shame the log isn't saying what is wrong with the ROM zip. Heck its not even showing it attempting to install the zip at all!
No sense.
Sent from my SGH-M919 using Tapatalk 2
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
If Superuser.zip flashes its the ROM.zip as the issue.
Sent from my SGH-M919 using Tapatalk 2
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Once an OTA update comes out for any Moto X variant we'll have a much better idea of the META-INF folder as a whole. In the meantime everyone feel free to keep playing with it to try to get it to work right. Making small updater-script changes to re-upload the entire ROM.zip is a huge pain. Soon enough we'll have the Dev Edition and more Developers will be joining us to get everything squared away.
Thanks testers!
What is the filesystem it (Moto X)?
Jovistyle said:
What is the filesystem it (Moto X)?
Click to expand...
Click to collapse
Code:
# mount point fstype device [device2] [length=]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem
/customize ext4 /dev/block/platform/msm_sdcc.1/by-name/customize
These,
seems pretty solid my co-worker tried it an seems great now
BLKWIDOW said:
seems pretty solid my co-worker tried it an seems great now
Click to expand...
Click to collapse
Wait, so it works now?
Sent from my XT1058 using Tapatalk 2
Is it deodex? No biggy if its not. Download link? Fantastic, getting flashing widthdrawls, shaking and i can't sleep at night
Sent on my Moto X
AKA "For the love of all that's good and holy, how do I stop this?"
I've deleted the FOTA folder, and when I get the notification (about 30 times a day), I long press for App Info, but the Show Notifications checkbox is checked and greyed out so I can't uncheck it.
I tried downloading Disable Service from the Play Store, but it reports that SystemUpdateService is disabled, yet I'm still getting this notification.
Clearly, this is quite frustrating. Thanks for any help.
How did you disable it? I have seen people say TI didn't stop it, and the hidden menu didn't do it. Those peeps had to do both.
Freezing system update in titanium worked for me or flash another rom similar to stock
wwevoxnj said:
Freezing system update in titanium worked for me or flash another rom similar to stock
Click to expand...
Click to collapse
This is how i stopped it right here...
Just delete system update.
Did you try disabling ota in the hidden Verizon menu? Dial ##3328873 + send + 000000, uncheck ota, then delete fota files in cache again and rename LGDMSClient.apk and the same for the .odex file to .bak. Renaming seems what's working for most people instead of freezing.
Reboot
That should take care of it for you.
Deleted - already covered
Kris Nelson said:
Did you try disabling ota in the hidden Verizon menu? Dial ##3328873 + send + 000000, uncheck ota, then delete fota files in cache again and rename LGDMSClient.apk and the same for the .odex file to .bak. Renaming seems what's working for most people instead of freezing.
Reboot
That should take care of it for you.
Click to expand...
Click to collapse
The file rename worked for me. I took all the steps above and even downloaded the exposed module AppOps to no avail
GTiceman said:
The file rename worked for me. I took all the steps above and even downloaded the exposed module AppOps to no avail
Click to expand...
Click to collapse
Where can I find the files I need to edit. I see cache.. but where is that located?
AB_ said:
Where can I find the files I need to edit. I see cache.. but where is that located?
Click to expand...
Click to collapse
system, app
Kris Nelson said:
Did you try disabling ota in the hidden Verizon menu? Dial ##3328873 + send + 000000, uncheck ota, then delete fota files in cache again and rename LGDMSClient.apk and the same for the .odex file to .bak. Renaming seems what's working for most people instead of freezing.
Reboot
That should take care of it for you.
Click to expand...
Click to collapse
Dang! I was looking for that info last week after I received my G3. I finally just took the OTA from 10B to 11C. Yeah, I can flash back but geez that would have been easier.
Thanks! (I did hit the Thanks Button)
What is that app called that I need to rename?edit: found it
Total noob here but know enough to be dangerous. I'm rooted and unlocked and was able to turn off OTAs this way. Question I have is whether there are simple and straightforward instructions on downloading and installing the lastest KDZ updates available. I did download 11C (and decompressed with LG Firmware Extract for Win) but I'm lost as to the proper steps to take from here to make sure I don't brick my precious Any resources would be much appreciated!
Darkmatter661 said:
Total noob here but know enough to be dangerous. I'm rooted and unlocked and was able to turn off OTAs this way. Question I have is whether there are simple and straightforward instructions on downloading and installing the lastest KDZ updates available. I did download 11C (and decompressed with LG Firmware Extract for Win) but I'm lost as to the proper steps to take from here to make sure I don't brick my precious Any resources would be much appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
bweN diorD said:
http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
Click to expand...
Click to collapse
Thank you. I had already scrutinized this thread quite a bit, it actually directed me here and got me to the where I'm at now. However, where do I get the boot.img,modem.img,system.img files - they were not included in the KDZ. All I see in there are a bunch of bin files...
Darkmatter661 said:
Thank you. I had already scrutinized this thread quite a bit, it actually directed me here and got me to the where I'm at now. However, where do I get the boot.img,modem.img,system.img files - they were not included in the KDZ. All I see in there are a bunch of bin files...
Click to expand...
Click to collapse
The IMG files are not in the update zip. They are somewhere in that ota incoming thread. I can post the links later if you can't find them. I'm hosting the system. IMG and have the modem.img, not sure if I have the boot, probably.
Sent from my G3, with mods made possible by team Codefire.
Darkmatter661 said:
Thank you. I had already scrutinized this thread quite a bit, it actually directed me here and got me to the where I'm at now. However, where do I get the boot.img,modem.img,system.img files - they were not included in the KDZ. All I see in there are a bunch of bin files...
Click to expand...
Click to collapse
here are the files. i actually dont have the boot. probably because i never flashed it, didnt see the point. if you are going to move on to a custom rom, there is no point in flashing the system either.
http://www.mediafire.com/download/k33b3gj47xzjyk0/modem-11c.img
http://www.mediafire.com/download/q36hb82dx4eo2cw/system.img
bweN diorD said:
here are the files. i actually dont have the boot. probably because i never flashed it, didnt see the point. if you are going to move on to a custom rom, there is no point in flashing the system either.
http://www.mediafire.com/download/k33b3gj47xzjyk0/modem-11c.img
http://www.mediafire.com/download/q36hb82dx4eo2cw/system.img
Click to expand...
Click to collapse
Thanks! So I'm on 10B now, going to 11C. I get that I need to place the Flash2 zips on the phone, which I've done. I also get that I will place modem-11c.img and system.img in the same folder, then in TWRP, flash the zips. Is that it? I presume that I no longer really need teh KDZ I downloaded since that's basically in these files you're providing. Thanks again!
Darkmatter661 said:
Thanks! So I'm on 10B now, going to 11C. I get that I need to place the Flash2 zips on the phone, which I've done. I also get that I will place modem-11c.img and system.img in the same folder, then in TWRP, flash the zips. Is that it? I presume that I no longer really need teh KDZ I downloaded since that's basically in these files you're providing. Thanks again!
Click to expand...
Click to collapse
sounds close. also you need to remove the -11c from the modem file name.
bweN diorD said:
sounds close. also you need to remove the -11c from the modem file name.
Click to expand...
Click to collapse
That's correct.