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!
Related
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
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?
Current state of phone:
bootloader = relocked tampered
S-ON
Hboot = 2.09.0000
radio = 1.12.11.1210
Phone has no OS/Rom all I have access to is bootloader and recovery TWRP
Unable to flash a rom in TWRP
Had freshly rooted replacement evo LTE (as of yesterday)
-unlocked HTCdev method
-installed superuser and gained root access
today, tried to install a custom sense based rom (located here: http://forum.xda-developers.com/showthread.php?t=1712618 )
Aroma install was unable to set up permissions and install failed and dropped me into a boot loop
tried installing several other sense roms and CM10 with no success before realizing that TWRP was not able to mount several aspects such as Cache and other import parts.
unable to fix
have since:
-relocked bootloader
-attempted to run RUU.exe files with no success
-attempted to gain s-off to use viperRUU and got the error message "FAILED (remote: 43 mail version check fail)"
I am at a loss... could someone please help, if you need me to check anything please just let me know what you need and how to get it.
Since you are S-ON you have to fastboot flash the boot.img/kernel and then the rom
Try MeanBean it is S-ON friendly it has a kernel installer
BTW you will have to unlock again
bigdaddy619 said:
Since you are S-ON you have to fastboot flash the boot.img/kernel and then the rom
Try MeanBean it is S-ON friendly it has a kernel installer
BTW you will have to unlock again
Click to expand...
Click to collapse
where can i find the files you are referring too? Sorry it has been a long several hours, thankyou for your help
Try MeanBean first at least it will get you back up and running
http://forum.xda-developers.com/showthread.php?t=2048229
1. put it on your sdcard
2. boot into twrp
3. click install and find the zip and swipe to install
bigdaddy619 said:
Try MeanBean first at least it will get you back up and running
http://forum.xda-developers.com/showthread.php?t=2048229
1. put it on your sdcard
2. boot into twrp
3. click install and find the zip and swipe to install
Click to expand...
Click to collapse
I cant do that.... i have tried several roms and TWRP is not mounting the things I need to flash... im going to try reflashing the recovery img and let you know here in a moment.... thanks for your help!!! ill be back in just a moment
After reflashing twrp type
fastboot erase cache
Also make sure you unlock your bootloader again
bigdaddy619 said:
After reflashing twrp type
fastboot erase cache
Also make sure you unlock your bootloader again
Click to expand...
Click to collapse
check check and check
unlocked, erased cache, reflashed twrp, and tried to install rom
I get the following in the TWRP logs:
E:Unable to mount /sdcard
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /sd-ext
unable to flash anything through recovery
idk what to do
shootin4aces said:
check check and check
unlocked, erased cache, reflashed twrp, and tried to install rom
I get the following in the TWRP logs:
E:Unable to mount /sdcard
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /sd-ext
unable to flash anything through recovery
idk what to do
Click to expand...
Click to collapse
Have you tried to sideload a rom thru twrp?
You may have to format your sdcards and start fresh (if you take this route backup the important stuff to your PC first)
bigdaddy619 said:
Have you tried to sideload a rom thru twrp?
You may have to format your sdcards and start fresh (if you take this route backup the important stuff to your PC first)
Click to expand...
Click to collapse
Im honestly not sure which route to take, what would you suggest as a sure proof method to resolve the issue, backing up everything now from sd card and then I have no data to lose.
I have never sideloaded really before, what exactly do I need to do
again, thanks so much for your help
bigdaddy619 said:
Have you tried to sideload a rom thru twrp?
You may have to format your sdcards and start fresh (if you take this route backup the important stuff to your PC first)
Click to expand...
Click to collapse
and since i cant mount anything really, how will I be able to sideload? nothing will mount through TWRP
shootin4aces said:
Im honestly not sure which route to take, what would you suggest as a sure proof method to resolve the issue, backing up everything now from sd card and then I have no data to lose.
I have never sideloaded really before, what exactly do I need to do
again, thanks so much for your help
Click to expand...
Click to collapse
If it's not a huge deal I would just format both sdcards and start fresh.
To sideload
Go into twrp
1. Select Advance
2. Select ADB Sideload
3. Check the boxes to wipe chache/dalvik cache and swipe to begin
4. Re-name the rom zip something easy to type haha and put it in your android-sdk/platform-tools folder(or wherever you have your ADB and Fastboot located)
5. Open a cmd window from that folder and type adb sideload filename.zip
Once it's done sideloading it will flash the zip
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
shootin4aces said:
and since i cant mount anything really, how will I be able to sideload? nothing will mount through TWRP
Click to expand...
Click to collapse
Does it mount when you connect to your PC? Both sdcards?
---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------
Also what version of twrp are you using? I would suggest 2.4.1.0
get it here
http://techerrata.com/browse/twrp2/jewel
in bootloader, choose “FASTBOOT”, hit the Power button, then plug-in your microUSB cable from your phone to computer.
type "fastboot flash recovery openrecovery-twrp-2.x.x.x-jewel.img" without the quotes and press enter (Replace the x's with the version you choose exp. 2.3.3.0)
Copy and paste is the easiest way to do this that way there are no typo's
Now type "fastboot erase cache" without the quotes and press enter
bigdaddy619 said:
If it's not a huge deal I would just format both sdcards and start fresh.
To sideload
Go into twrp
1. Select Advance
2. Select ADB Sideload
3. Check the boxes to wipe chache/dalvik cache and swipe to begin
4. Re-name the rom zip something easy to type haha and put it in your android-sdk/platform-tools folder(or wherever you have your ADB and Fastboot located)
5. Open a cmd window from that folder and type adb sideload filename.zip
Once it's done sideloading it will flash the zip
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Does it mount when you connect to your PC? Both sdcards?
Click to expand...
Click to collapse
when i mount Via usb it says it needs to format disk I:
when i select to format it opens up a format removable disk window that says capacity 9.93 GB.... should i tell it to reformat? or how should I go about it? I only see 1 item i can reformat
bigdaddy619 said:
If it's not a huge deal I would just format both sdcards and start fresh.
To sideload
Go into twrp
1. Select Advance
2. Select ADB Sideload
3. Check the boxes to wipe chache/dalvik cache and swipe to begin
4. Re-name the rom zip something easy to type haha and put it in your android-sdk/platform-tools folder(or wherever you have your ADB and Fastboot located)
5. Open a cmd window from that folder and type adb sideload filename.zip
Once it's done sideloading it will flash the zip
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Does it mount when you connect to your PC? Both sdcards?
---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------
Also what version of twrp are you using? I would suggest 2.4.1.0
get it here
http://techerrata.com/browse/twrp2/jewel
in bootloader, choose “FASTBOOT”, hit the Power button, then plug-in your microUSB cable from your phone to computer.
type "fastboot flash recovery openrecovery-twrp-2.x.x.x-jewel.img" without the quotes and press enter (Replace the x's with the version you choose exp. 2.3.3.0)
Copy and paste is the easiest way to do this that way there are no typo's
Now type "fastboot erase cache" without the quotes and press enter
Click to expand...
Click to collapse
I have TWRP 2.6.0.0
That is you Internal sdcard which is probably where the problem lies
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
shootin4aces said:
I have TWRP 2.6.0.0
Click to expand...
Click to collapse
Try going back to 2.4.1.0 and see what happens before you try formatting
bigdaddy619 said:
That is you Internal sdcard which is probably where the problem lies
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Try going back to 2.4.1.0 and see what happens before you try formatting
Click to expand...
Click to collapse
still unable to mount after going back to that version...gonna have to reformat... on the computer should I reformat as FAT32? and should I use the default allocation size of 8192 bytes?
shootin4aces said:
still unable to mount after going back to that version...gonna have to reformat... on the computer should I reformat as FAT32? and should I use the default allocation size of 8192 bytes?
Click to expand...
Click to collapse
It's been a while since I formatted my sdcards so I don't really remember so use your best judgement I'm pretty sure I just clicked format and didn't change anything
bigdaddy619 said:
It's been a while since I formatted my sdcards so I don't really remember so use your best judgement I'm pretty sure I just clicked format and didn't change anything
Click to expand...
Click to collapse
here goes nothing
Good luck
bigdaddy619 said:
It's been a while since I formatted my sdcards so I don't really remember so use your best judgement I'm pretty sure I just clicked format and didn't change anything
Click to expand...
Click to collapse
reformatted and sideloaded a rom... started to flash the zip afterwards but then said E:unable to mount /data
that was the only one this time though
shootin4aces said:
reformatted and sideloaded a rom... started to flash the zip afterwards but then said E:unable to mount /data
that was the only one this time though
Click to expand...
Click to collapse
Copy it to your phone from your PC and flash normally in twrp
Solution
Turns out that the CWM Recovery Backup was very helpful for the kitchen and it worked, now I can make a custom ROM for MT6572 mbk72_wet_jb3 Devices, I will soon post a tutorial of how I did all of it, as soon as I finish a Custom ROM.
I hope this can make someone happy soon. :victory:
History:
Hi everyone, I have some questions about the creation of an update.zip with a customized SYSTEM from the stock ROM of my device.
My problem is that everything work as it should be, I can do an update.zip to flash only boot.img and it works and an update.zip to delete packages or add packages and it also works.
But when I want to format my system partition to write all the files from my kitchen, it does not boot at all, I can´t even do a logcat... I´ve tried to do an update.zip without any modifications and still nothing.
Any suggestions??
This is the last thing that I want to do before doing a tutorial on how to Root, Flash Recovery, and install Custom Roms on Mediatek 6572 Device: mbk72_wet_jb3
Update: I´ve tried to just copy the system files without the updater-script do a format, and do the format manually before running the update, and it goes into bootloop but I can see the logcat saying it´s missing a lot of libraries, but all of them are actually there in the system/lib folder, and I looked at the permissions and where all correct..
Click to expand...
Click to collapse
may i know type n vendor of your phone ??
SuperAnt said:
Solution
Turns out that the CWM Recovery Backup was very helpful for the kitchen and it worked, now I can make a custom ROM for MT6572 mbk72_wet_jb3 Devices, I will soon post a tutorial of how I did all of it, as soon as I finish a Custom ROM.
I hope this can make someone happy soon. :victory:
History:
Click to expand...
Click to collapse
Hey my friend I am looking to customize my ROM for:
Model Number: Android
Android Version: 4.2.2
Baseband Version: MOLY.WR8.W1315.MD.WG.MP.V4.P5, 2013/09/04
Kernel Version: 3.4.5
Build Number: ALPS.JB3.MP.V1.6
But having problems getting the ROM from the device:
doing: cat /proc/emmc
- gives me
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 0001ba00 00145000 "android"
emmc_p5: 00160a00 000c0000 "cache"
emmc_p6: 00220a00 00100800 "usrdata"
emmc_p7: 00321200 0040c600 "fat"
and doing: cat /proc/mtd
- produces
dev: size erasesize name
- no mounts
Have you any ideas?
SuperAnt said:
Solution
Turns out that the CWM Recovery Backup was very helpful for the kitchen and it worked, now I can make a custom ROM for MT6572 mbk72_wet_jb3 Devices, I will soon post a tutorial of how I did all of it, as soon as I finish a Custom ROM.
I hope this can make someone happy soon. :victory:
History:
Click to expand...
Click to collapse
Hello,
Gr8 stuff , did You manage to finish this tutorial , will make me verry happy.
While playing around with custom roms and android kitchen to better understand Android , i am stuck at stock system recovery on a Korean clone device. (mtk6572 device)
I can flash the device , and i have no /system partition , just enough to boot and load recovery. (preloader.bin , uboot.bin , boot.img and recovery.img backed up from stock and flashed)
I need to flash the system.img and load android on the device , but i do not have the system.img file i just have the /system folder extracted from it before it died and trying to create a .zip file and flash it using the stock recovery.
When trying to apply any update i always get
Install /sdcard
Installation aborted
or
install /sdcard
Error: Invalid OTA package, missing scatter
Installation aborted.
I tried all different stuff i though about , adding scatter file, extracting/editing the zip files (updater-script/update-script) replace the update-binaries with the ones for my phone , the problem is all the attempt results are the Installation aborted , with no errors or hints on what is going on , and read the posts about recovery.log (http://forum.xda-developers.com/showthread.php?t=633246) but logs are not generated in this stock recovery and no options to show them or send them to /sdcard.
I am using the kitchen provided by dsixda.
P.S: thanks alot for this kitchen it just makes life alooooot easier and u can actually learn the process with great information's.
The second error i get ( Invalid OTA ...) makes me thing the update-binaries are correct and its being executed , so i used the kitchen to add the scatter file for my device , sign the package and upload it , but then the wierd thing is i get the first error again , confusing cz i do not know where and how to trace my problem , tried to understand how the updater-script is made and try to display some info in it just to see if its executed but no luck , just the installation aborted message!!!
Can any one point me on to a tutorial explaining what exactly happens when you are in system recovery , and try to apply update from sdcard and choose the update?
Is there any difference between how these updates are executed in different devices/roms/android versions ?
Sorry for making this post to long ( i feel i am sending an email lol) , just needed to be clear and give as many info as i got to help solve this issue.
Thanks in advance.
Mike
---------- Post added at 08:58 PM ---------- Previous post was at 08:44 PM ----------
chronograff said:
Hey my friend I am looking to customize my ROM for:
Model Number: Android
Android Version: 4.2.2
Baseband Version: MOLY.WR8.W1315.MD.WG.MP.V4.P5, 2013/09/04
Kernel Version: 3.4.5
Build Number: ALPS.JB3.MP.V1.6
But having problems getting the ROM from the device:
doing: cat /proc/emmc
- gives me
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 0001ba00 00145000 "android"
emmc_p5: 00160a00 000c0000 "cache"
emmc_p6: 00220a00 00100800 "usrdata"
emmc_p7: 00321200 0040c600 "fat"
and doing: cat /proc/mtd
- produces
dev: size erasesize name
- no mounts
Have you any ideas?
Click to expand...
Click to collapse
Hi ,
did you tried mtkdroid tools?
below is copied from a link , but you know new users cannot post urls.
1. Connect your phone and run downloaded MTKDroidTools.exe. After few seconds your phone info should be displayed.
2. Go to "Root, Backup, Recovery" tab. Backup button is now disabled. Click the "Root" button on the bottom to get root access to your phone.
3. You will receive a pop-up message requesting your approval for root access. You may also receive a confirmation on phone screen. The pop-up message may differ if your phone is not already rooted.
4. Now, the Backup button and other disabled buttons should be enabled.
5. You may select "Backup userdata and cache" if you want to backup your user data and settings. Click Backup button. The process will start. You can select "Yes" for "Packing backup?" question during process if you want to compress backup into a zip file.
6. When the backup is complete, go to your MTKDroidTools folder and open backups. You will find the compressed backup zip file and uncompressed files there. You can use SP Flash tool to restore your ROM when needed.
SuperAnt said:
Solution
Turns out that the CWM Recovery Backup was very helpful for the kitchen and it worked, now I can make a custom ROM for MT6572 mbk72_wet_jb3 Devices, I will soon post a tutorial of how I did all of it, as soon as I finish a Custom ROM.
I hope this can make someone happy soon. :victory:
History:
Click to expand...
Click to collapse
im waiting for that thx
I see that I´ve got some more people interested in this, I will then finish the tutorial, right now I don´t have the device because it´s been used on my job, I needed to modify all the apps so I had to do all of this to modify everything that I could without breaking the phone, with the kitchen I was able to remove all the bloat software and also change the initial software like the launcher, phone app, gallery, etc to custom ones.
As soon as I get more devices I will finish the tutorial, because I will have more to unlock and change the apps.
Greetings!
SuperAnt said:
I see that I´ve got some more people interested in this, I will then finish the tutorial, right now I don´t have the device because it´s been used on my job, I needed to modify all the apps so I had to do all of this to modify everything that I could without breaking the phone, with the kitchen I was able to remove all the bloat software and also change the initial software like the launcher, phone app, gallery, etc to custom ones.
As soon as I get more devices I will finish the tutorial, because I will have more to unlock and change the apps.
Greetings!
Click to expand...
Click to collapse
so bro ???
Can anyone help me with the rom for this phone?
https://www.china-devices.com/topic/10252-identify-correct-rom-for-mt6572-clone-iphone-6s/
NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I have created this flashable zip myself and tried this on QMobile Z8 only. It's similar to Wiko Ridge 4G and Blu Life One (2015) in hardware specifications.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing.
NOTE-2:
This flashable zip flashes SYSTEM and BOOT partitions only. If you face ROM abnormal behavior like signals issue, charging problem, device heat up etc. you may flash other partitions as explained here.
Read here more about partitions.
REQUIREMENTS
To flash zip, CUSTOM RECOVERY must be installed. If you don't have one, get here.
If your device is bricked and doesn't boot, try flashing factory firmware as explained here. Even if Download Mode isn't accessible, get official support for your device and pray for it.
STEPS
Download QMobile Z8 Stock ROM Lollipop 5.0.2 Rooted flashable unsigned zip and place it on SD Card or Internal Memory (if you don't going to wipe it).
Reboot into Recovery.
Install ROM zip.
Wipe DALVIK-CACHE, CACHE & DATA.
Reboot. Ignore "No OS Installed" warning (if it comes).
Enjoy!
Thanks for Your Post
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
sadiq1 said:
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
Click to expand...
Click to collapse
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
sadiq1 said:
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
Click to expand...
Click to collapse
dd is a command on UNIX-like operating systems including Linux and Android to copy / dump data. https://www.computerhope.com/unix/dd.htm
Put both img files on internal sd card. Boot in recovery and run these commands from built-in terminal or adb shell:
Code:
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
Make sure "/dev/block/mmcblk0p23" and "/dev/block/mmcblk0p24" are correct partitions to flash or you may overwrite wrong partitions.
Don't forget to make a backup before making experiments.
mirfatif said:
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
Click to expand...
Click to collapse
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
x.ak**** said:
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
Click to expand...
Click to collapse
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
mirfatif said:
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
Click to expand...
Click to collapse
Exactly that's why I prefer them and recommend them.
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------
mirfAtif
where can i write this command
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
I have TWRP this is a GUI program , where can i write command there?
---------- Post added at 06:35 PM ---------- Previous post was at 05:44 PM ----------
I found the terminal to write the command
Let me know where should i keep the files after unzip them
---------- Post added at 06:46 PM ---------- Previous post was at 06:35 PM ----------
Sorry mirfatif
You told me every thing in ur first post , i didnt read it properly,
Thanks ,
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
sadiq1 said:
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
Click to expand...
Click to collapse
Execute these commands:
Code:
ls -l /dev/block/bootdevice/by-name/boot
ls -l /dev/block/bootdevice/by-name/system
sadiq1 said:
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
Click to expand...
Click to collapse
Flash QMobile factory firmware, not Wiko's. If that doesn't fix, there must be hardware problem.
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
sadiq1 said:
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
Click to expand...
Click to collapse
You must be flashing wrong partition. Or try changing different dd binary e.g. from latest busybox version.
Or if you can loop mount system.img with ext4 filesystem, simple copy files to /system partition along with file permissions.
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
sadiq1 said:
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
Click to expand...
Click to collapse
Then other firmware partitions from Wiko must be incompatible with QMobile ROM. Simple is to use a flasher which flashes all partitions. But replace the recovery image with custom recovery like TWRP. After that you may flash this rooted ROM if needed.
yar mujhe app se bat kerni he 03343210716/03028484502
I downloaded some firemware for qmobile , using QFile application
every thing was ready when i click on download there was error "download fail:sahara failvalue canot be null"
sadiq1 said:
yar mujhe app se bat kerni he 03343210716/03028484502
Click to expand...
Click to collapse
English please, it's international forum.
PM me for personal assistance.
mirfatif said:
English please, it's international forum.
PM me for personal assistance.
Click to expand...
Click to collapse
He's saying he wants to have a word with you and he has given his number.
x.ak**** said:
He's saying he wants to have a word with you and he has given his number.
Click to expand...
Click to collapse
I know I'm Urdu speaking :laugh:
Just asking to follow the rules.