[Guide] Installing recovery.img from terminal Emulator - AT&T, Rogers HTC One X, Telstra One XL

Please read and re-read the entire post before attempting!
Disclaimer
Recognize that you do this at your own risk. I am not responsible for your phone becoming useless; walls that you put holes in out of anger; or anything else that may result from your inability to follow simple directions. Remember, you are writing to your phones partition system. Writing to the wrong partition will... NOT be good! You have been warned. Common sense prevails!
(Please note: your phone must be rooted for this process to work)​
If the following steps are followed exactly you WILL have success.
1. Download the recovery you wish to write to your phone, rename it recovery.img (Not required. That being said, however, it will keep things simple, and allow you to simply copy and paste the necessary commands below), and place it on the ROOT of your sdcard.
2. Open Terminal Emulator and type:
Code:
su
(this will give you root access).
3. Once you gain root access type the following, EXACTLY:
Code:
cat /proc/emmc
Your Terminal will list all of your partitions, with corresponding names. Doing so will ensure that you write your recovery.img to the correct partition.
Here is the output you should get back:
cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p32: 0616a000 00000200 "reserve"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
mmcblk0p32: 0616a000 00000200 "reserve"
[note that there is a space between cat and the /]
Then type the following:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Click to expand...
Click to collapse
Make sure that the mmcblk (recovery) above matches the output of cat /proc/emmc!!!!!
4. If all goes well, you will not get any errors (To ease your minds, I did this step-by-step as listed above, moments before writing this up; with success! - and it only took about 15 seconds!). Next, from Terminal Emulator type:
Code:
reboot recovery
5. Your phone will now reboot into your new recovery!
6. Enjoy!
Click to expand...
Click to collapse
This is so easy to do that I personally don't find much need for the apps that do everything for you. But that's just me; to each his/her own.
Additional Resources​
Terminal Emulator Commands
Guide: Using The terminal Emulator
Linux Commands On Android
Just as a side note:
If you look at the source code for Recovery Tools on GitHub, you will see that the app is actually performing these same commands behind the scenes; to accommodate a broad range of devices and additional options. It is more user friendly for those not comfortable with executing from the command line. I just wanted to point out that, as far as nuts and bolts are concerned, it is essentially the same.

Reserved for expansion
Sent from my One X using XDA Premium 4 mobile app

And one more.
Sent from my One X using XDA Premium 4 mobile app

Why not just use
Su
Flash_image recovery /path/to/recovery.IMG
It just seems easier to me.
Sent from my One X using xda app-developers app

magnetboard said:
Why not just use
Su
Flash_image recovery /path/to/recovery.IMG
It just seems easier to me.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Flash_Image is just a script that does the same thing. I could make a text document with the commands in it (both the dd and the reboot recovery commands), place it in /system/bin... Set the permissions to executable... Name it 123 (or whatever) and just run 123 from the terminal emulator to flash the recovery.
But to answer your original question, I was honestly trying to teach people basic terminal emulator command line work. Sure, I could have provided a script like flash_image, or my own, but what would anyone really learn?
Sent from my One X using XDA Premium 4 mobile app

Agreed. The point of this thread is to educate, the script just bypasses the learning component of doing it manually.
Sent from my Evita

I understand the point of learning, I've learned a lot from other devs and users in general. I just put it out there because not everyone can remember commands or remember to do this over and over again. I didn't mean to step on toes, and I'm sorry if I did. But, not everyone wants to learn. Some just want to do it as easily as they can which usually has a lesser chance of something going wrong.
Sent from my One X using xda app-developers app

magnetboard said:
I understand the point of learning, I've learned a lot from other devs and users in general. I just put it out there because not everyone can remember commands or remember to do this over and over again. I didn't mean to step on toes, and I'm sorry if I did. But, not everyone wants to learn. Some just want to do it as easily as they can which usually has a lesser chance of something going wrong.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I didn't take it personally at all. Post two and three were place marked for expansion. I had planned on showing the flash_image way, as well as show "how" to write a script of your own for the purposes of pushing a recovery manually through terminal emulator.
I appreciate your thoughts.
Sent from my One X using XDA Premium 4 mobile app

Pretty cool guide BJ. I got rid of the automatic app I had and I refer to this and type the commands. I know I took it for the educational value and appreciate what is going on "behind the scenes" . Not everybody is built that way though.
I compare it with working on cars. I still help people change spark plugs and serpentine belts (which I consider basic maintenance.)
But it is cool knowing the commands and understanding the "why" behind it.

Related

T-Mobile (US) MyTouch system folder

Got a dump of the official T-Mobile (US) MyTouch system folder. Not a whole lot of interesting stuff here, the build.prop is different, but otherwise the ROM looks nearly the same as the G1's official 1.5 firmware. The build id is CRB57.
A first attempt at booting a modified recovery thru fastboot failed with the "remote: not allowed" message.
Download here: http://n0rp.chemlab.org/android/mytouchdump.zip
Thanks to markdt098 for grabbing it.
Hey Cy,
This is the one from the test versions. The TMo proprietary stuff that's supposed to set the MyTouch above the G1 isn't on the phones that have been released thus far. So, we'll most likely need to keep our eyes out for a dump that includes those items.
A first attempt at booting a modified recovery thru fastboot failed with the "remote: not allowed" message.
So no go on rooting? I have the phone for a couple of days and really wanted to root. If anyone figures it out Please. PM me.
so did u try both these recovery images?
[Recovery] RAv1.0 : Modded ION recovery!
sangeet.003 said:
so did u try both these recovery images?
[Recovery] RAv1.0 : Modded ION recovery!
Click to expand...
Click to collapse
Yes. They couldn't be booted via "fastboot boot".
I don't actually have the device, though.
So u can alternately get the boot image & other images through "/dev/mtd/mtd*" using "adb pull /dev/mtd/mtd* *.img"
what problem does "fastboot boot" gives?
does it hangs @ the first screen after restart? or the "fastboot boot" itself isn't supported..
thread?
We've already got a thread going on fastboot remote not allow. Should they be merged
nixxofugi said:
We've already got a thread going on fastboot remote not allow. Should they be merged
Click to expand...
Click to collapse
this thread is for getting hands on myTouch 3G system, m telling way 2 get oher stuffs out of the phone like boot & other partitions, not only fastboot thing.
cyanogen said:
Yes. They couldn't be booted via "fastboot boot".
I don't actually have the device, though.
Click to expand...
Click to collapse
I have the devise for a couple of days. You cannot ADB without rooting first. I read about pushing mod recovery through fastboot, I won't do that unless I can revert to original state. Does any one know if you can $fastboot pull system/recovery.img
Mi|enko said:
Hey Cy,
This is the one from the test versions. The TMo proprietary stuff that's supposed to set the MyTouch above the G1 isn't on the phones that have been released thus far. So, we'll most likely need to keep our eyes out for a dump that includes those items.
Click to expand...
Click to collapse
What stuff exactly are you talking about? The Sherpa app is the only thing I can think of that the release myTouch will have that mine does not.
Edit: And exchange support...do you think that will require an OTA update for the myTouch's given out to employees?
try this:
1. Boot the device full till the home screen
2. use cmd & go to "adb shell"
3. then type in "cat /proc/mtd"
u ll see some thing like this:
Code:
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 05a00000 00020000 "system"
mtd4: 01e00000 00020000 "cache"
mtd5: 059c0000 00020000 "userdata"
4. then use, use mtd<dev number> according to <name>.img
Code:
"adb pull /dev/mtd/mtd1 recovery.img"
"adb pull /dev/mtd/mtd2 boot.img"
"adb pull /dev/mtd/mtd3 system.img"
"adb pull /dev/mtd/mtd5 userdata.img"
by doing so u ll backup recovery & then try flashing recovery...
post what u get here.
sangeet.003 said:
try this:
1. Boot the device full till the home screen
2. use cmd & go to "adb shell"
3. then type in "cat /proc/mtd"
u ll see some thing like this:
Code:
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 05a00000 00020000 "system"
mtd4: 01e00000 00020000 "cache"
mtd5: 059c0000 00020000 "userdata"
4. then use, use mtd<dev number> according to <name>.img
Code:
"adb pull /dev/mtd/mtd1 recovery.img"
"adb pull /dev/mtd/mtd2 boot.img"
"adb pull /dev/mtd/mtd3 system.img"
"adb pull /dev/mtd/mtd5 userdata.img"
by doing so u ll backup recovery & then try flashing recovery...
post what u get here.
Click to expand...
Click to collapse
I get a permission denied error when trying that.
markdt098 said:
I get a permission denied error when trying that.
Click to expand...
Click to collapse
for what cat proc? or adb pull ?...
Sorry, should of clarified, adb pull gives me the error, cat proc does not.
have unrestricted access to a mytouch as well, if theres anything you'd like me to do let me know... i have the exact same problems with fastboot as well as the adb shell permission errors
k first let me check the available stuff in the system folder by cyanogen so to know what it has & what it dosent... plz wait for some time... may be later... today
cyanogen said:
Got a dump of the official T-Mobile (US) MyTouch system folder. Not a whole lot of interesting stuff here, the build.prop is different, but otherwise the ROM looks nearly the same as the G1's official 1.5 firmware. The build id is CRB57.
A first attempt at booting a modified recovery thru fastboot failed with the "remote: not allowed" message.
Download here: http://n0rp.chemlab.org/android/mytouchdump.zip
Thanks to markdt098 for grabbing it.
Click to expand...
Click to collapse
Does this mean you will soon be blessing us ION/Magic owners with your modified roms?
Gimpeh said:
Does this mean you will soon be blessing us ION/Magic owners with your modified roms?
Click to expand...
Click to collapse
May be he or me too, i am waiting for it to come to India so rooting it can be done together...
Need donations to get our hands on Magic coz we both have an g1... thats hard to spend on too... m 16... 4 me its tooooo hard.. lol
n may be there will be ION/HERO/Ophone ports to magic too... m Currently Downloading Ophone SDK to Get system out of it...
markdt098 said:
What stuff exactly are you talking about? The Sherpa app is the only thing I can think of that the release myTouch will have that mine does not.
Edit: And exchange support...do you think that will require an OTA update for the myTouch's given out to employees?
Click to expand...
Click to collapse
Probably. Sherpa's supposedly what the MyTouch will have that other android devices won't (at least not at first). Then there's exchange and finally the customization options (for making the device your own). I'm actually curious about that last one the most. Wonder if they worked with a dev to bring theme support or what.
Mi|enko said:
Probably. Sherpa's supposedly what the MyTouch will have that other android devices won't (at least not at first). Then there's exchange and finally the customization options (for making the device your own). I'm actually curious about that last one the most. Wonder if they worked with a dev to bring theme support or what.
Click to expand...
Click to collapse
Not tested but i think we just need the myTouch boot img to get it running with root on other devices...
let me try it with other boot img's...

[System Dump]Motorola Backflip Blur_Version.0.1.1199.MB300.ATT.en.US

I pulled the system directory of my backflip. This does not include the boot.img or recovery.img. It is strictly the /system/
http://www.androidspin.com/downloads.php?dir=public/motorola-backflip/&file=moto.backflip.Blur_Version.0.1.1199.MB300.ATT.en.US.zip <== Thanks Androidspin for hosting!
Motorola has now posted the source for the backflip. Hopefully this info helps us get this phone opened up from at&t's crippling efforts. Thanks to nokternl at modmymoto for finding this!
https://opensource.motorola.com/sf/frs/do/viewRelease/projects.backflip/frs.backflip_mb300_at_t_usa.rel12_1199
Code:
system version: Blur_Version.0.1.1199.MB300.ATT.en.US
Model number: MB300
Hardware Version SJUG5763AA
Firmware version:1.5
Basband version: 76xxv-63805027-sdcbalum
Kernal version: 2.6.27 [email protected] #1
Build number: R6380CP1_029.00.02
If someone can help with pulling the boot.img I imagine it would be helpful
adb shell "cat /proc/mtd"
Code:
dev: size erasesize name
mtd0: 00300000 00020000 "boot"
mtd1: 08ac0000 00020000 "system"
mtd2: 0df80000 00020000 "userdata"
mtd3: 00040000 00020000 "misc"
mtd4: 00500000 00020000 "recovery"
mtd5: 06000000 00020000 "cache"
mtd6: 00080000 00020000 "splash"
BACKFLIP ADB GUIDE http://forum.xda-developers.com/showthread.php?t=643866
BACKFLIP SYSTEM DUMP http://forum.xda-developers.com/showthread.php?t=642684
BACKFLIP SOURCE CODE http://forum.xda-developers.com/showthread.php?t=645369
moosefist said:
I pulled the system directory of my backflip. This does not include the boot.img or recovery.img. It is strictly the /system/
http://www.bigandfree.com/12130771
The system version is Blur_Version.0.1.1199.MB300.ATT.en.US
The Build number is R6380CP1_029.00.02
If someone can help with pulling the boot.img I imagine it would be helpful
adb shell "cat /proc/mtd"
Code:
dev: size erasesize name
mtd0: 00300000 00020000 "boot"
mtd1: 08ac0000 00020000 "system"
mtd2: 0df80000 00020000 "userdata"
mtd3: 00040000 00020000 "misc"
mtd4: 00500000 00020000 "recovery"
mtd5: 06000000 00020000 "cache"
mtd6: 00080000 00020000 "splash"
Click to expand...
Click to collapse
I put this down in the HTC Dream:G1 forum I hope you don't mind. I quoted it all from here and mentioned you in the OP, is that alright??
G1BRICKED said:
I put this down in the HTC Dream:G1 forum I hope you don't mind. I quoted it all from here and mentioned you in the OP, is that alright??
Click to expand...
Click to collapse
I debated whether to put it there myself, since that is the most active board. I don't mind at all that its double posted.
There could be some useful stuff in here for some people... if for some reason you hate a google search widget you could change to yahoo . There is a clock mode in this build. There are also a bunch of AT&T specific apps: All-sports GPS, ATT Maps, ATT Music, ATT Navigator, ATT Radio, ATT Wifi hotspots (free wifi), Mobile Banking App, Manage Sim Card, Mobile Video, MobiTV, MusicID, Quickoffice, ATT where, YPmobile. Some of these apps are nice like Mobile Banking for instance, but some are bull**** like att's Where they put on here, its a subscription based version!
I take it this does not have that new Moto Blur Connect music player? http://www.androidcentral.com/motorola-cliq-xt-getting-updated-connected-media-player
How did you use adb with the phone? do you have the USB drivers for the phone? I'm trying to do this same thing for with the new sony xperia10, but adb doesnt find the phone and I dont have the drivers for the Sony. any help would be appreciated. thanks.
An idea I have is for you to post that in the XDA/General/Q&A section where you can get more views. And also post it in the XDA/Dream/Q&A and say you're working on a [DUMP] but don't know how to do it.
It would be great if we could get a moderator to open a section for the Motorola Backflip now that XDA is hosting to hacks for other phones besides HTC.
nutcake852 said:
It would be great if we could get a moderator to open a section for the Motorola Backflip now that XDA is hosting to hacks for other phones besides HTC.
Click to expand...
Click to collapse
I second this, but owning a non-htc makes me biased i guess
largo79 said:
How did you use adb with the phone? do you have the USB drivers for the phone? I'm trying to do this same thing for with the new sony xperia10, but adb doesnt find the phone and I dont have the drivers for the Sony. any help would be appreciated. thanks.
Click to expand...
Click to collapse
Moto has drivers released. If you want, post what kinda OS you are using and i will try to find the developer drivers for you phone. Have you checked the option to enable USB debug mode also?
(I know this is off topic, and most likely in the wrong area, but this is the only thread I can find about the Backflip.)
I love XDA; it's the best website out here on the wonderful world wide internet for information for HTC Phones...
But I would LOVE to see one of you VERY talented individuals attack this phone. Because even though we are stuck in the Stone Age with 1.5; I think someone here could get this bad boy up and running with a very good and clean custom firmware.
And I will pledge to donate to anyone that takes this on.
At least lets get it so we can have root access (if that is not universal; I don't know much about Android, yet) so we can install un-signed packages.
I look forward to seeing what this community can do.
Requesting permission to copy the OP to a thread on Alldroid with a link back here as credit.
I dont know if this will help or not but i found a file on my backflip called block_dump. If anyone is interested in this it is found here: (Root/proc/sys/vm)in this folder the first file is called block_dump. I have found a bunch of files that say block in them.
moosefist said:
I pulled the system directory of my backflip. This does not include the boot.img or recovery.img. It is strictly the /system/
http://www.bigandfree.com/12130771
Motorola has now posted the source for the backflip. Hopefully this info helps us get this phone opened up from at&t's crippling efforts. Thanks to nokternl at modmymoto for finding this!
https://opensource.motorola.com/sf/frs/do/viewRelease/projects.backflip/frs.backflip_mb300_at_t_usa.rel12_1199
Code:
system version: Blur_Version.0.1.1199.MB300.ATT.en.US
Model number: MB300
Hardware Version SJUG5763AA
Firmware version:1.5
Basband version: 76xxv-63805027-sdcbalum
Kernal version: 2.6.27 [email protected] #1
Build number: R6380CP1_029.00.02
If someone can help with pulling the boot.img I imagine it would be helpful
adb shell "cat /proc/mtd"
Code:
dev: size erasesize name
mtd0: 00300000 00020000 "boot"
mtd1: 08ac0000 00020000 "system"
mtd2: 0df80000 00020000 "userdata"
mtd3: 00040000 00020000 "misc"
mtd4: 00500000 00020000 "recovery"
mtd5: 06000000 00020000 "cache"
mtd6: 00080000 00020000 "splash"
BACKFLIP ADB GUIDE http://forum.xda-developers.com/showthread.php?t=643866
BACKFLIP SYSTEM DUMP http://forum.xda-developers.com/showthread.php?t=642684
BACKFLIP SOURCE CODE http://forum.xda-developers.com/showthread.php?t=645369
1. DOWNLOAD USB DRIVERS[/U][/B]
Motorola ADB Driver 32bit
Motorola ADB Driver 64bit​
2. INSTALL THE SDK
-Download latest SDK http://developer.android.com/sdk/index.html
-Extract Archive to C:\SDK\ (or C:\Android, or whatever you want)​
3. Enable debugging on your phone (thanks naplesbill)
-Goto Settings > Applications > Development > and Check the USB debugging option​
4. Optional, but recommended
-Setup Enviroment Variables:
On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path AFTER A SEMICOLON (;C:\SDK\tools\) .​-Setup Droid Explorer:
Goto Droid Explorer Downloads and snatch the latest version, then install. (mine showed an error during install i believe due to the lack of HTC drivers. If you installed motorola's drivers it should still be in your start menu and work fine)​
If for some reason you can't figure it out, install the drivers then try this installation guide: ADB For Dummies Guide
ADB APK Install instructions
BACKFLIP SYSTEM DUMP http://forum.xda-developers.com/showthread.php?t=642684
BACKFLIP SOURCE CODE http://forum.xda-developers.com/showthread.php?t=645369
Click to expand...
Click to collapse
This is the [DUMP] and ADB Setup.
Have fun.
The download link for the dump is dead, at least for me. Anybody have a mirror?
InGeNeTiCs said:
The download link for the dump is dead, at least for me. Anybody have a mirror?
Click to expand...
Click to collapse
If someone can tell me how to do a system dump, my wife is picking up the phone on Friday and I can post one then.
Also this seems to be a system dump as well:
http://www.androidspin.com/download...lip.Blur_Version.0.1.1199.MB300.ATT.en.US.zip
And you can get to the forum linking it at http://forum.androidspin.com/showthread.php?t=2020
godzirra said:
If someone can tell me how to do a system dump, my wife is picking up the phone on Friday and I can post one then.
Also this seems to be a system dump as well:
http://www.androidspin.com/download...lip.Blur_Version.0.1.1199.MB300.ATT.en.US.zip
And you can get to the forum linking it at http://forum.androidspin.com/showthread.php?t=2020
Click to expand...
Click to collapse
Mucho Gusto, I wanted to check this out! Thanks again.
Backflip music
tbaker077 said:
I take it this does not have that new Moto Blur Connect music player?
Click to expand...
Click to collapse
Unfortunately it's saddled with the AT&T Music suite. the music player itself isn't bad, but it has all the crapware att is famous for. I work for a att dealer and the word according to motorola is that the backflip will be running 2.1 by mid june. will this help to get rid of the crapware?
Four days converted from a jailbroken iPhone 3g jailbroken 3.1.2 and overwhelmed but very intrigued. Android is going to be fun!
From very reliable sources, the At&t Backflip will update in June... it would be great to get to the root before that. let me know if there is any info I can help with. I am new to Android, but this is much more fun than blackra1n!
HAHA port it to the Droid!

Changing bootloader: dead Defy

Hey guys.
I executed dd if=/dev/zero of=/dev/block/mmcblk1p1
I've read in droid-developers.org that mbmloader is locked so I thought dd was going to give me write errors. I was wrong, and dd wrote zeros in the mbmloader partition. Now, phone is completely dead and I'll have to get a new one.
But I think that if it's possible to change mbmloader code with zeros, why can't we replace it with a new unsigned bootloader using dd? I couldn't find many real explanations why bootloader can't be replaced besides "it's locked and forget about it", so dd may be a way to replace it. We gonna need the opinion of someone with more knowledge about low-level programming and Defy's hardware.
Bye... And never type this in your Defy if you like it.
I executed dd if=/dev/zero of=/dev/block/mmcblk1p1
Click to expand...
Click to collapse
Sorry, I simply cracked up at that line.
LOL
I have to try this trick:
https://www.droid-developers.org/wiki/How_to_load_mbmloader_from_SD_card
Can someone please dump mmcblk1p1, it can be done with the reverse command:
dd if=/dev/block/mmcblk1p1 of=/mnt/sdcard/mbmloaderdump.img
Yaffs explorer can also dump it if you're afraid to run dd.
Thanks in advance!
If you managed to do
dd if=/dev/zero of=/dev/block/mmcblk1p1
shouldn't you also be able to
dd if=/dev/block/mmcblk1p1 of=~/bootloader.img ?
and if someone can do that and send you the image, shouldn't you also be able to repair your phone?
And why would you try anything like that anyway?? Especially without making a backup first?
I don't have my phone atm, i'm waiting for it to be returned from warranty. So i can't do any tests right now.
Edit: apparently you just found out yourself what I said
Thanks for your answer!
The problem is to recover the image if the phone doesn't even turn on.
As it's stated here, maybe there's a way to load it from SD Card:
https://www.droid-developers.org/wiki/How_to_load_mbmloader_from_SD_card
But for trying that I'd need that someone posts a dump of mmcblk1p1
File uploaded.
Thank you very much for the effort, but it didn't work.
Besides putting the file in root of sdcard, it seems that some code should be put on the phone to make it look on the sdcard for the mbmloader. Since the phone doesn't turn on, i can't put this code.
danimagrin said:
Thank you very much for the effort, but it didn't work.
Besides putting the file in root of sdcard, it seems that some code should be put on the phone to make it look on the sdcard for the mbmloader. Since the phone doesn't turn on, i can't put this code.
Click to expand...
Click to collapse
when you plug in the phone to a linux pc, do you see a USB device?
It seems that it's possible to replace the mbmloader with an unsigned bootloader. In fact, they've tried it on milestone, but failed.
(http://and-developers.com/custom_recovery:alternative_methods)
Either you have to find a existent one or write a new one.
As to the former, we can't find an unsigned bootloader unless moto unlock it.
To do the latter one, you have to get all the information about the phone, another almost impossible thing.
here is the milestone boot chain, similer to defy.
http://and-developers.com/boot:boot_chain
Code:
# cat /proc/mtd
Code:
dev: size erasesize name
mtd0: 00180000 00020000 "pds"
mtd1: 00060000 00020000 "cid"
mtd2: 000a0000 00020000 "logo"
mtd3: 00060000 00020000 "misc"
mtd4: 00380000 00020000 "boot"
mtd5: 00480000 00020000 "recovery"
mtd6: 008e0000 00020000 "cdrom"
mtd7: 0b260000 00020000 "system"
mtd8: 082a0000 00020000 "cache"
mtd9: 0ab20000 00020000 "userdata"
mtd10: 00200000 00020000 "kpanic"
Can't see mbm =)
Maybe you loaded mtd-hack?
Damn... Good guy with dead bootloader. I remember last time we could actually flash just the bootloader at will with phone Motorola E398 using ramloader or the famous flashbackup3.0. The E398 is really immortality. Hope this Defy can reach that height to justify its name.
Sent from my awesome Moto Defy Gingerbread 2.3.3 - XDA Premium

[WIP] Partitions - memory address listing

Okay everyone. Let's get this all straightened out.
We need a concise listing of what memory address corresponds to what partition.
This is a fantastic idea:
dhkr234 said:
Probably would be a good idea to add a wiki for this device..
Click to expand...
Click to collapse
...and we'll work up to that. Documentation is my big thing with the device, and what i've been working on more then anything else as far as development goes.
So let's get all the partition information together, and get it set for a reference thread in the dev section. Then we'll graduate up to a wiki that includes this and all the other necessary info.
Here's what I posted in the CWM thread, I just copied it over to get this thread started. I don't have a lot of time in front of the pc right now, but as I get it i'll move people's finding up into the first post and sort it all out.
Thanks in advance for everyone who wants to contribute to this, we need whatever we don't have, verification that what we do have is right, and corrections to anything that's wrong.
----------------------------------------------
Here's what we got so far:
/dev/block/mmcblk0p27 /devlog ext4
/dev/block/mmcblk0p24 /cache ext4
/dev/block/mmcblk0p23 /data ext4
/dev/block/mmcblk0p22 /system ext4
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat
/dev/block/mmcblk0p14 - Boot Splash Screen
/dev/block/mmcblk0p12 - hboot
----------------------------------------------
I'd like to thank dhkr234 and Etn40ff for their contributions thus far.
dhkr234 said:
Just an FYI: With the UNofficial recovery, we could NOT flash Undeadk9's images (at least not the older ones, haven't tried the newer ones). The unofficial recovery would not mount the /system partition via the updater-script. Issuing an "adb shell mount /system" would mount the system partition for us and allow the install to proceed normally.
---------- Post added at 02:42 PM ---------- Previous post was at 02:28 PM ----------
Ah, I think I see where the issue is.....
From CM's updater-script:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
From Undeadk9's updater-script:
Code:
mount("ext3", "EMMC", "system", "/system");
delete_recursive("/system");
Undeadk9's updater-script *assumes* that the /system partition is formatted, ext3, and clean.
I would say that the CM approach is better. Formatting the bastard ensures that the filesystem is perfect.
Click to expand...
Click to collapse
Here are some, but not all:
Blue6IX said:
/dev/block/mmcblk0p22 /system ext4
/dev/block/mmcblk0p23 /data ext4
/dev/block/mmcblk0p24 /cache ext4
/dev/block/mmcblk0p27 /devlog ext4
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat
doubleshot mount points specifically, i've been using them for a lot of adb stuff.
Just thought i'd throw it out as a handy reference.
Click to expand...
Click to collapse
And:
Etn40ff said:
which is the partition containing the splash?
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Self answer: mmcblk0p14
Click to expand...
Click to collapse
Don't forget:
nbetcher said:
mmcblk0p31: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077fde00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p27: 01400000 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p25: 00400000 00000200 "modem_st1"
mmcblk0p26: 00400000 00000200 "modem_st2"
Other partitions are accessed only by the radio, hboot, and other low-level subsystems.
Click to expand...
Click to collapse
In this post:
thrice43 said:
I'm down to try the dd command, but I'll still need a copy of the 1.44.0006 hboot. If anybody has the 1.44.0006 hboot, can you please open a terminal and run
dd if=/dev/block/mmcblk0p12 of=/data/local/tmp/hboot.img
mv /data/local/tmp/hboot.img /sdcard/
Click to expand...
Click to collapse
Then send me the file on you sdcard?
Etn40ff said:
I messed up a little with strings (1) and file (1). Apparently hboot is stored in /dev/block/mmcblk0p12. If you feel really adventurous you can try to flash a new hboot via dd as you suggested.
I am not 100% sure it will help you: revolutionary hboot (1.44.1107) contains some reference to emapiWlanMac even if it gives an error if you try to use the command.
---------- Post added at 03:29 PM ---------- Previous post was at 02:36 PM ----------
question: where have you got 1.44.0006 ???
I just compared 1.44.0007 (the original hboot) with 1.44.1107 (revolutionary's). They are almost identical: I guess they simply hexedited the significant bits to unlock it (they also changed version number and added the "-Revolutionary-" signature) so none of them will help you change your mac address.
Hboot 1.45.0013 (the latest hboot) is a significantly different beast and might have the desired features but I would not flash it since it will lock your phone again.
Click to expand...
Click to collapse
I know that HTC's engineering bootloader enables the use of more "fastboot oem xxx" commands, and many of them are missing with revolutionary's bootlaoder
Click to expand...
Click to collapse
Also, check this thread in general for some more info on mount points:
http://forum.xda-developers.com/showthread.php?t=1318237
I'm pretty sure there was another post or two describing what some of the as yet unmentioned mount points corresponded to, but I can't remember where they were randomly in threads right now.
We also know that screwing up partition 19 is "harmless":
cf. http://forum.xda-developers.com/showthread.php?p=19078122#post19078122
Etn40ff said:
We also know that screwing up partition 19 is "harmless":
cf. http://forum.xda-developers.com/showthread.php?p=19078122#post19078122
Click to expand...
Click to collapse
run adb shell mount
Have you collected enough info to make the older roms installable on the new official cwm? Switching the version of cwm when I want to try a new rom is a bit of a pain. I like having ROM manager working.
I just found out how to install the older roms with new recovery but I how it can be made automatic.
OMG where was this info a few days ago
Good info to have lol
Jaytex24 said:
Was fooling around with the old data2ext mod I used on my old mt3gs since cm7 is available. Long story short, after installing the .zip and hitting reboot = insta hard brick, as in totally dead (although there is, or was a flickering red light under the trackpad). Win some, lose some amirite. Oh well thats what insurance is for, yay 130.00 deductible from asurion.
I realize it doesnt make much sense to use data2ext, but with a 32g sdcard i figured I could leave all the apps on the internal so I wouldnt have to worry about sacrificing some apps that come with a widget. Plus android is all about fooling around with technology, trial and error I suppose. Oh, I guess I suck, 637 installed apps on my slide
Click to expand...
Click to collapse
Jaytex24 said:
Nope, adb doesn't list the phone as being recognized, all buttons unresponsive. Textbook hard brick, would have similar results by plugging in the USB cable to my flipflops. As long as the device has some life to it I can normally weasel my way out of a brick with adb, but this time its totally dead. I've been lucky tho between my xoom and especially with my mt3gs, guess it was bound to happen eventually, play with fire expect to get burned. I'm sure it has to do with the command line from the original mod altering the /dev/blck of an older device, I didn't make adjustments so that it would write to the correct /block location. So I guess I sent the partition somewhere close to Neptune in relation to the mt4gs build lol
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Techlvr said:
Have you collected enough info to make the older roms installable on the new official cwm? Switching the version of cwm when I want to try a new rom is a bit of a pain. I like having ROM manager working.
I just found out how to install the older roms with new recovery but I how it can be made automatic.
Click to expand...
Click to collapse
That's trivial. The problem is a less-than-stellar updater-script used in the "older roms". What they did is they mounted the /system partition as ext3 and then wiped the data from them. What CM does differently is it FORMATS the /system partition as ext4 and then mounts it. It is trivial to fix the updater-script of the older "roms" so that they actually work.
The application of this information goes well beyond simply flashing a ROM, and it was actually a bootsplash issue that finally convinced me this info needed it's own thread.
Directly interacting with any partition needs to be done using it's memory address, not just a generic mount point.
But yes, it will help people having issues with flashing ROMs too.
Hopefully I can get some time soon to map out a few more, otherwise I also hope that others will post up info to contribute as they find them out.
Sooner or later we'll have all the memory addresses mapped out, and what they correspond to.
This brutal gig at work is over for me on friday morning/afternoon, so hopefully i'll get a few days off to recover and sit around working on stuff like this.
Blue6IX said:
The application of this information goes well beyond simply flashing a ROM, and it was actually a bootsplash issue that finally convinced me this info needed it's own thread.
Directly interacting with any partition needs to be done using it's memory address, not just a generic mount point.
Click to expand...
Click to collapse
All partitions on the device have a unique device file within /dev/block/ -- use of the memory address is highly inadvisable since it creates the potential to mess up your math and affect prior or later partitions on the device (aka, you could brick it). All interaction should be via the specific device file for that partition.
Just remember that the actual addresses are stored within the partition table and each partition is strictly isolated and protected by the kernel.
'fdisk -l /dev/block/mmcblk0' will output the full list of partitions, but note that HTC has applied their particular brand of insanity and partially broken the partition table. You will note at the top of the output it says "Warning: deleting partitions after 60". Basically, look at the START block for each partition. While the start block INCREASES, the partitions are real. When you see the start block suddenly DECREASE, that partition (and all after it) are duplicates of ones that came earlier -- just ignore them.
Also, 'cat /proc/partitions' will give out the proper list, but won't give you the start addresses.
You can find all of the NAMED partitions listed in /proc/emmc.
Determination of other names may require disassembly of the bootloader since they are NOT provided to the kernel.
Sooner or later we'll have all the memory addresses mapped out, and what they correspond to.
Click to expand...
Click to collapse
The memory addresses ARE mapped out. All we need is to know what they correspond to.
Edit: http://forum.xda-developers.com/showpost.php?p=16896745&postcount=3
Edit2: Do NOT confuse device files with mount points. They are NOT equivalent. If you've done any C programming, you may know what a POINTER is. When dealing with storage devices and memory, a device file is basically a pointer to a memory address as specified within the device's partition table.
So for example, if the partition table says "partition 3 starting address is 0x12345678, length is 0x1000", then /dev/block/mmcblk0p2 (because they count from 0) is a pointer to 0x12345678 and has a length of 0x1000. So address 0x0 of /dev/block/mmcblk0p2 ***IS*** address 0x12345678 of /dev/block/mmcblk0. Further, the kernel prevents you from writing outside the range of 0x0->0x0FFF, otherwise you may endanger the contents of partition 4.
Just wanted to say thanks for that helpful posting. I know that's what the thanks button prints, but I wanted to go ahead and type it too.

[4.4.2][HBOOT2.22] New partition layout with 4.4.2 OTA

Update
Watch out! Beginning with the 05/01 nightly the CM11 nightly builds are safe to flash no matter which partition layout you have. Other ROMs may not be independent from the partition layout yet and therefore still need to be modified before flashing. Read your ROM's FAQ or ask the devs for more information on that particular issue.
Introduction - What is this good for?
If you have been on a Stock ROM and got a Stock OTA update to 4.4.2 then it's very likely that you've got a "new partition layout".
This has the effect, that pretty all of the currently available ROMs flying around can't be one-click-flashed via recovery. (Technical background: The install scripts in the usual ROM zips contain instructions that refer to the old partition layout. With the "new layout" the scripts won't work anymore and flashing will fail.)
If you tried already and your phone isn't booting anymore ... Don't panic! As long as you get into fastboot mode, it is highly unlikely that your phone is bricked. And if you're able to flash and boot a recovery you're pretty safe.
Read on to find out how to deal with this.
What do you need?
You need adb and fastboot on your computer and you should basically know how to work with these tools. If you have a Windows computer you need the fastboot and adb drivers to be installed. Just use Google or refer to other sections of this forum on how to do that.
So first let's find out, if you're on the "new partition layout"
As far as I know for now the "new partition layout" comes with HBOOT 2.22. So boot into bootloader and check this out.
If you're not on 2.22 then you still could check the following thing. With 2.22 you definitely should continue.
Boot to your recovery and run the following adb command on your computer:
Code:
adb shell cat /proc/emmc
Compare your output to this:
Code:
$ adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"
Please check very carefully, especially the lines ending with "system", "data", "cache", "boot" and "recovery"!!!
If your output looks the same then you have the "new partition layout". Then you will need a modified recovery that respects the "new partition layout".
Just use one of these (thanks to @kyasu):
TWRP 2.7.0.5: http://forum.xda-developers.com/showpost.php?p=51612358&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/showpost.php?p=51740162&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
Flash it via fastboot:
Code:
fastboot flash recovery twrp-2.7.0.5-m4kk.img
If you even can't boot into recovery you have to flash one of these anyway.
Flash a ROM that has been modified to respect the new partition layout
As already said, almost all ROMs currently available don't match your partitions. The updater-scripts within have to be modified.
So let's collect all ROMs or zips that has been modified already and are therefore ready to flash (from the recovery as usual, as long it's one of the aforementioned).
Don't forget to flash boot.img via fastboot if you're S-ON.
Stock ROMs or nandroid backups:
Stock 4.4.2 (3.10.401.4) odexed or Stock 4.4.2 (3.10.631.5) deodexed can be found here:
http://forum.xda-developers.com/showthread.php?p=51779967 (infos about both ROMs in the first post of the thread)
Stock 4.4.2 (3.10.111.4) odexed nandroid backup from a German T-Mobile device:
https://drive.google.com/file/d/0ByRc8IR1ZBiveTludUt1ZUp4QUk/edit?usp=sharing (MD5: 0a1f21529328c7581f366954eeeba46a)
(should work on non-German devices, too)
Customized ROMs:
CM11 nightly 0403: https://drive.google.com/file/d/0ByRc8IR1ZBivZmpjWmt2YXhfT28/edit?usp=sharing (MD5: 3bc8d4694f1ee80992665138b252431f)
CM11 nightly 0412: https://drive.google.com/file/d/0ByRc8IR1ZBivZ2R0Q01fZHpxd1E/edit?usp=sharing (MD5: f502e43aa9cea3dab5a6b05f68953333)
great work, this should clarify things for people. i imagine users with the modified partition will not be able to flash cm11 nightlies until the roms are modified also ?
I currently s-off, hboot 2.19 & twrp 2.6.3. so ....flashing one of these (TWRP 2.7.0.5: http://forum.xda-developers.com/show...8&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/show...2&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
recoveries will up modify my partition layout ??
cheers
Braddison said:
so ....flashing one of these (TWRP 2.7.0.5: http://forum.xda-developers.com/show...8&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/show...2&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
recoveries will up modify my partition layout ??
Click to expand...
Click to collapse
No, they don't. They're just modified to match the new partition layout (if you have it already).
OK,thanks.
Seems to me,that the way forward (only speculating) devs will produce Roms that will work with the new modified partition layout as its the latest firmware, meaning that pre hboot 2.22 will become obsolete and user will need to upgrade there hboot? surely there must be a simpler way than the route of supercid and flashing an ruu ?
forgive me if my question is wrong, just been off xda for the last few weeks n trying to catch up.
cheers
hi
I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.
BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says
*deamon started succesfull*
error device
Just dont know what to do..
PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...
EdiBese said:
I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.
BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says
*deamon started succesfull*
error device
Just dont know what to do..
PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...
Click to expand...
Click to collapse
I had a similar problem, I just used a OTG (On The Go) cable, with a flash drive.
Braddison said:
OK,thanks.
Seems to me,that the way forward (only speculating) devs will produce Roms that will work with the new modified partition layout as its the latest firmware, meaning that pre hboot 2.22 will become obsolete and user will need to upgrade there hboot?
Click to expand...
Click to collapse
I'm not sure if the new partition layout will become the standard among the devs. Most of the users here switched to custom ROMs way before the OTA with HBOOT 2.22 was released. They all depend on ROMs made for the classic partition layout.
Since upgrading HBOOT isn't that easy (as you mentioned this needs performing a RUU or having S-OFF which is generally not necessary or recommended) it would be the best to stick with the old partition layout as long as possible.
EdiBese said:
I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.
BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says
*deamon started succesfull*
error device
Just dont know what to do..
PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...
Click to expand...
Click to collapse
Did you check the output of cat /proc/emmc as I mentioned above? Do that with the recovery that seems to work well (2.6.0.0 in your case). That's the only way to be absolutely sure about your partitions. Perhaps checking HBOOT version only is not sufficient.
hi
morschesholz said:
I'm not sure if the new partition layout will become the standard among the devs. Most of the users here switched to custom ROMs way before the OTA with HBOOT 2.22 was released. They all depend on ROMs made for the classic partition layout.
Since upgrading HBOOT isn't that easy (as you mentioned this needs performing a RUU or having S-OFF which is generally not necessary or recommended) it would be the best to stick with the old partition layout as long as possible.
Did you check the output of cat /proc/emmc as I mentioned above? Do that with the recovery that seems to work well (2.6.0.0 in your case). That's the only way to be absolutely sure about your partitions. Perhaps checking HBOOT version only is not sufficient.
Click to expand...
Click to collapse
no i didnt check
but i cant flash cm 11 with 2,6.3
it says symllink failed
error in binary counter or something like that
---------- Post added at 11:10 AM ---------- Previous post was at 10:59 AM ----------
I checked it out bro, it seems to be the same
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_con
mmcblk0p23: 00400000 00000200 "modem_st1
mmcblk0p24: 00400000 00000200 "modem_st2
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"
Does your adb really only say: error device?
Usually the output is a little more verbose.
Are you on Windows or on Linux or Mac? On Linux or Mac you could try starting adb with sudo:
Code:
sudo adb kill-server
sudo adb devices
Then your device should be listed (a line containing the id of your device and the word "recovery").
hi
The problem is now.
When i flash 2.7.05, my phone cant be recognized when i am in TRWP mode. And this means i cant push the rom on the device iam stuck here.
I just see something bro look..
i have 2.6.0.0 now and pushed cm on the phone, but now i see i had cm on the /sdcard
But when i flash 2.7.0.5 i cant find cm on the sd card any more? ican find nothing on the sdcard
Just flash 2.7.0.5 again (be sure that it's the modified one from the first post here, it's name should be twrp-2.7.0.5-m4kk.img).
Then run
Code:
sudo adb kill-server
sudo adb devices
and tell us the exact output.
hi
C:\Android>adb devices
adb server is out of date.
* daemon started successfu
List of devices attached
If i try to push
C:\Android>adb push cm-11-20140411-NIGHTLY-m4.zip sdcard/
error: device not found
And in TWRP 2.6 it show 1620 MB Internal Storage, but in 2.7.05 it says 11308 MB, something is wrong..
I cant type in sudo, it doesnt work
---------- Post added at 11:47 AM ---------- Previous post was at 11:27 AM ----------
I downloadede the twrp of your post... flashed again.. same problem
I just cant get this rom on the phone!
Man, you have to use the modified 2.7.0.5 since it matches your new partition layout. That's why 2.7.0.5 is showing you the correct amount of free space: 11308 MB. That's the free space on your userdata partition (which is now at mmcblk0p37). 2.6.0.0 is made for the old layout and expects userdata to be at mmcblk0p35. As you can see from your emmc output, mmcblk0p35 is now /system on your device. That's why 2.6.0.0 is showing you only 1620 MB free space. That's the free space on the system partition.
So stay with 2.7.0.5!!!
The problem you have is that adb is not working. First of all, you can't adb push anything if your device is not recognized. That's what adb devices is doing: listing all recognized devices. So if adb devices shows nothing, nothing is recognized. It's that simple.
But as you can see adb devices tells you "adb server is out of date". Googling that error will give you lots of tips on how to deal with that problem: uninstalling HTC Sync should help.
Then you should be sure to have the latest adb and fastboot versions. You can download a current package here: http://forum.xda-developers.com/showthread.php?t=2317790
Then you first should do this again:
Code:
adb kill-server
adb devices
If - and really only if !!! - your output is something like that:
Code:
[[email protected] ~] adb devices
List of devices attached
HTxxxxxxxxxx recovery
then you're safe to continue.
But before flashing anything to the phone you should wipe all partitions. Go to Wipe > Advanced Wipe, select everything except USB OTG and Internal Storage and then swipe to wipe. After that you can adb push a cm.zip (a modified one) to your sdcard and install it. Finally flash boot.img via fastboot and you're done.
morschesholz said:
Man, you have to use the modified 2.7.0.5 since it matches your new partition layout. That's why 2.7.0.5 is showing you the correct amount of free space: 11308 MB. That's the free space on your userdata partition (which is now at mmcblk0p37). 2.6.0.0 is made for the old layout and expects userdata to be at mmcblk0p35. As you can see from your emmc output, mmcblk0p35 is now /system on your device. That's why 2.6.0.0 is showing you only 1620 MB free space. That's the free space on the system partition.
So stay with 2.7.0.5!!!
The problem you have is that adb is not working. First of all, you can't adb push anything if your device is not recognized. That's what adb devices is doing: listing all recognized devices. So if adb devices shows nothing, nothing is recognized. It's that simple.
But as you can see adb devices tells you "adb server is out of date". Googling that error will give you lots of tips on how to deal with that problem: uninstalling HTC Sync should help.
Then you should be sure to have the latest adb and fastboot versions. You can download a current package here: http://forum.xda-developers.com/showthread.php?t=2317790
Then you first should do this again:
Code:
adb kill-server
adb devices
If - and really only if !!! - your output is something like that:
Code:
[[email protected] ~] adb devices
List of devices attached
HTxxxxxxxxxx recovery
then you're safe to continue.
But before flashing anything to the phone you should wipe all partitions. Go to Wipe > Advanced Wipe, select everything except USB OTG and Internal Storage and then swipe to wipe. After that you can adb push a cm.zip (a modified one) to your sdcard and install it. Finally flash boot.img via fastboot and you're done.
Click to expand...
Click to collapse
Friend, i am on 2.7.0.5 the whole time. I know that my phone is not reognized but i dont know why, because on 2.6.3 it is recognized!
I'm sorry but that's all I can tell you. Do you have HTC Sync installed? Then I advise to uninstall it and use original adb and fastboot executable from the thread I linked to.
morschesholz said:
I'm sorry but that's all I can tell you. Do you have HTC Sync installed? Then I advise to uninstall it and use original adb and fastboot executable from the thread I linked to.
Click to expand...
Click to collapse
Yes HTC sync is installed, i just did everything what you said
But my phone is not recognized, dunno why
Just to be sure: Do you have restarted your computer after uninstalling all the HTC Software?
morschesholz said:
Just to be sure: Do you have restarted your computer after uninstalling all the HTC Software?
Click to expand...
Click to collapse
DId.. the same..
What i dont understand is, under 2.6. my phone i recognized and i can push files, i tried it out an hour ago.. but with 2.7.0.5 it isnt, means there is no problem with the software and drivers on the computer..
What about fastboot? Boot into fastboot mode and check if fastboot devices lists your phone.
hi
morschesholz said:
What about fastboot? Boot into fastboot mode and check if fastboot devices lists your phone.
Click to expand...
Click to collapse
Yes it does
C:\Android>fastboot devices
HT37NWA00458 fastboot

Categories

Resources