Hello guys.
Once again I need your help.
Following my last thread:
http://forum.xda-developers.com/showthread.php?t=847320
(AKA "Help! no SD recognition, USB link doesn't work and no signal!")
After taking martijn_bakker's and ianmufc's advice regarding how to issue the correct command from fastboot:
- My phone regained sd functionality.
- My phone had proper signal again.
- BUT I still have USB issues, AND more:
I am currently running Cyanogenmod 6.1.1 for HTC Desire, and I have the following issues:
- When I try to go back to the stock Froyo, or anything that resembles it really (LeeDroid for example), my signal goes bananas: When I try to call anyone, it rings the person, then "ends" the call, only to bring it back again after a few seconds and then disconnect again.
I've also tried different radios (including the one LeeDroid recommended) to no avail.
So basically I cannot make calls with the original ROM.
- USB: When I connect my phone to my PC it charges it, BUT my PC doesn't recognize it, and I cannot transfer files between the SD card and the PC, or sync etc.
- I've got no Bluetooth! (Not sure if this is a Cyanogenmod issue or not though)
- Phone turns off when released from electricity charging (Doesn't happen with PC USB charging though).
The thing is I really didn't mind the original Froyo 2.2 ROM, infact I like it very much. I really like the HTC Sense features and the weather+clock widget with the animations.
The only reason I ever rooted my phone was to get apps2sd on it, so I don't keep running out of space when installing new apps. But I never even got that to work...
My question to you guys is how can I fix my current problems and have a properly working HTC Desire with a stock/custom Froyo ROM (that can make phone calls ) with apps2sd on it?
Thanks in advance!
Liran
First how have you been getting stock on your phone? Have you tried the ruu? If you are zip flashing have you wiped everything? Go to recovery wipe data/factory reset, wipe cache, advanced then wipe dalvik cache, back button, mounts then wipe everything except sd-card. Make sure you wipe sdext. Then try to flash.
Sent from my HTC Desire using Tapatalk
Well as you still don't have usb-connectivity, it sounds like you need to continue on the usb-brick fix. You have issued the command, which let you use the sd-card again. Now you just need to write a new misc partition as described here:
http://forum.xda-developers.com/showthread.php?t=691639
Doing this should make your phone work like it used to, as this is the only thing that is not fixable by flashing another rom if you need some help on it, i might be able to help, but in short terms, you need to flash a misc image, which have the right values, as the one on your phone have been changed in some way. The image is provided in the thread.
edit: and for god's sake do not try to run a ruu, as flashing the misc image might require root, and you may not be able to regain root without usb-connectivity. Also an ruu does not overwrite the misc partition, so it won't help your problem.
edit2: also you should try flashing a new radio that is known to work like 5.09.05.30_2 just to make sure this isn't also causing problems. It should be possible from a zip file using recovery.
_Dennis_ said:
First how have you been getting stock on your phone? Have you tried the ruu? If you are zip flashing have you wiped everything? Go to recovery wipe data/factory reset, wipe cache, advanced then wipe dalvik cache, back button, mounts then wipe everything except sd-card. Make sure you wipe sdext. Then try to flash.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
TBH I don't exactly know what RUU is. I've heard it before but I'm not sure exactly what it means.
When I said I flashed the stock Froyo I meant this: Official_FroYo_2.10.405.2
and I also tried LeeDrOiD_v2.2f_A2SD.
Regarding the wipes I've done everything you wrote above to no avail.
mortenmhp said:
Well as you still don't have usb-connectivity, it sounds like you need to continue on the usb-brick fix. You have issued the command, which let you use the sd-card again. Now you just need to write a new misc partition as described here:
http://forum.xda-developers.com/showthread.php?t=691639
Doing this should make your phone work like it used to, as this is the only thing that is not fixable by flashing another rom if you need some help on it, i might be able to help, but in short terms, you need to flash a misc image, which have the right values, as the one on your phone have been changed in some way. The image is provided in the thread.
edit: and for god's sake do not try to run a ruu, as flashing the misc image might require root, and you may not be able to regain root without usb-connectivity. Also an ruu does not overwrite the misc partition, so it won't help your problem.
Click to expand...
Click to collapse
Thanks mate I will try that.
One thing I forgot to mention though - My phone is S-ON.
I'm not sure if it used to be S-OFF or not though.
Does that make any difference or does it not matter?
Hum. I appologize I never had a USB brick (knock in wood) so I assumed his problem would be in the rom possibly something he did while fixing the USB brick.
Sent from my HTC Desire using Tapatalk
It does make a difference yes, but you doesn't need s-off for this. It would just make it a whole lot easier. But just get your CID like described in the thread and change the misc image to this. Then flash it like described
edit:
dennis: np something else is wrong as well, but fixing the usb is very urgent, and the other problem should be fixable by running a ruu or simply flashing a new radio+rom afterwards.
mortenmhp said:
It does make a difference yes, but you doesn't need s-off for this. It would just make it a whole lot easier. But just get your CID like described in the thread and change the misc image to this. Then flash it like described
Click to expand...
Click to collapse
Will do!
I'll update when I'm done
liranh said:
Will do!
I'll update when I'm done
Click to expand...
Click to collapse
A bit stuck... Here is what I've done:
1. Got the CID.
2. Got a hex editor. wrote the new CID instead of the one in the img file. Saved it.
3. I put the new img file and flash_image.zip in the /data on my sd card.
I Put the card in my phone, started my phone, opened Terminal Emulator and typed in "/data/flash_image misc /data/mtd0.img" (without the quotes of course). the phone said: "/data/flash_image: not found".
What am I doing wrong?
Well you should not have a /data folder on your sd card it is a partition on the phone. In order to put it there, save the 2 files in the root of the sd-card and issue those commands in a terminal emulator:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
As written in the thread, you might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image) but try to do it without those
Then you should be able to run the command you specified in the previous post
Edit: and the reason you got the error before was of course, that your files was in /sdcard/data and not in /data
liranh said:
A bit stuck... Here is what I've done:
1. Got the CID.
2. Got a hex editor. wrote the new CID instead of the one in the img file. Saved it.
3. I put the new img file and flash_image.zip in the /data on my sd card.
I Put the card in my phone, started my phone, opened Terminal Emulator and typed in "/data/flash_image misc /data/mtd0.img" (without the quotes of course). the phone said: "/data/flash_image: not found".
What am I doing wrong?
Click to expand...
Click to collapse
Actually, should it not be like this:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Reboot.
Masdroid: Yes exactly apart from that he apparently didn't have the files on the sdcard root
MasDroid said:
Actually, should it not be like this:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Reboot.
Click to expand...
Click to collapse
mortenmhp said:
Well you should not have a /data folder on your sd card it is a partition on the phone. In order to put it there, save the 2 files in the root of the sd-card and issue those commands in a terminal emulator:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
As written in the thread, you might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image) but try to do it without those
Then you should be able to run the command you specified in the previous post
Edit: and the reason you got the error before was of course, that your files was in /sdcard/data and not in /data
Click to expand...
Click to collapse
Using a file manager on my phone, I put both files on the root of my SD card.
I then issued the following commands using Terminal Emulator:
su
(granted)
cat /sdcard/flash_image > /data/flash_image
Phone says: /sdcard/flash_image: No such file or directory
I should mention that I took out the card and connected it to my PC again to confirm the files have actually gone onto the root of the SD card (and they have), put the SD card back in my phone, issued the same commands in Terminal Emulator and got the same message...
Any ideas?
Sounds strange, just to make sure. You have unzipped the flash_image, so that it is not the flash_image.zip you have on you sd-card.
Also run "ls /sdcard" in terminal emulator to see a list of the files in the root and check, that it's there, and do not have a file extension. If it's there and the name is "flash_image" then it should work.
mortenmhp said:
Sounds strange, just to make sure. You have unzipped the flash_image, so that it is not the flash_image.zip you have on you sd-card.
Also run "ls /sdcard" in terminal emulator to see a list of the files in the root and check, that it's there, and do not have a file extension. If it's there and the name is "flash_image" then it should work.
Click to expand...
Click to collapse
Mate you are spot on with your first sentence. Give me a minute
Haha nice one thought i could've made the same mistake
mortenmhp said:
Haha nice one thought i could've made the same mistake
Click to expand...
Click to collapse
Yeah cause you know how when you put files on your phone to flash them you usually keep them in their zip format - that's what tricked me...
Haha yea let us know if you get it sorted
mortenmhp said:
Haha nice one thought i could've made the same mistake
Click to expand...
Click to collapse
Well spotted
mortenmhp and MasDroid thank you both so much!
Everything is working perfectly now!
I thought I would never get my phone to work properly again!
If any of you is ever in London - drinks are on me!
Related
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.
do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?
A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.
Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.
GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.
I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?
i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?
Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.
ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.
hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now
watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.
ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!
I have followed a few different guides regarding this and RUU will not find my phone. I have ran the program about 10 times and it just wont seem to find it. Also, it takes about 15 minutes for the program to tell me it can not find my phone. I have no idea why it takes so log to NOT find anything, LOL. is there another way to restore it or am i out of luck?
PS. I have rooted with unrevoked3. I need to return my phone so i need to completely stock.
EVOvillain said:
I have followed a few different guides regarding this and RUU will not find my phone. I have ran the program about 10 times and it just wont seem to find it. Also, it takes about 15 minutes for the program to tell me it can not find my phone. I have no idea why it takes so log to NOT find anything, LOL. is there another way to restore it or am i out of luck?
PS. I have rooted with unrevoked3. I need to return my phone so i need to completely stock.
Click to expand...
Click to collapse
In order to get back to Stock you need do this first http://forum.xda-developers.com/showthread.php?t=701835 Step 2 and 3.
(Be sure you mark usb debugging) After finish it, turn off the phone press volume down and power to Bootloader screen
wait until load hboot, then in fastboot plug the usb and press power botton and will change to fastboot USB, Then run the RUU. http://shipped-roms.com/shipped/Supersonic/
Good Luck!!
Ps: I got same issue when i began root and unroot but after practice is a piece of cake.
thanks a lot m8. ill give it a shot. hopefully it works because i need to turn my phone in soon.
EDIT: how and where do I enter this code? sorry, im a noob.
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
EVOvillain said:
thanks a lot m8. ill give it a shot. hopefully it works because i need to turn my phone in soon.
EDIT: how and where do I enter this code? sorry, im a noob.
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Click to expand...
Click to collapse
First you need put in you sd card the flash-image and mtd-eng.img .Be sure you mark usb debugging . Then you need use the adb shell. I recommend download evo-recovery http://link.geekfor.me/evorecovery decompress and put in you c: drive then open Command Prompt - and type first
cd c:\evo-recovery
will show up c:\evo-recovery next to this type adb-windows shell
will show up a # sign (if you got $ you unrooted)
after # singn type : (line by line)
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Put the PC36IMG in you Sd card and follow the intruction to step 3
Good luck!!
I did what you say but my phone does not recognize the PC36IMG file.
did you make sure the PC36IMG file DOES NOT have .zip on the end...the name of the file should be just PC36IMG.
If it is named PC36IMG.zip and you hide file extensions on your computer, the file is actually named PC36IMG.zip.zip
EVOvillain said:
I did what you say but my phone does not recognize the PC36IMG file.
Click to expand...
Click to collapse
When you did step 2 and type line by line , last line doesnt give you error?
If you continue with same issue with PC36IMG.ZIP, and because you got unrevoked3 , try flash first 147.651.1 stock root.zip here:http://www.mediafire.com/?n2zrnymmdmn Then try again step 2 and 3 in the top of this thread. That's work for me when i tested before unrevoked3
Good Luck
cocobongo77 said:
In order to get back to Stock you need do this first http://forum.xda-developers.com/showthread.php?t=701835 Step 2 and 3.
(Be sure you mark usb debugging) After finish it, turn off the phone press volume down and power to Bootloader screen
wait until load hboot, then in fastboot plug the usb and press power botton and will change to fastboot USB, Then run the RUU. http://shipped-roms.com/shipped/Supersonic/
Good Luck!!
Ps: I got same issue when i began root and unroot but after practice is a piece of cake.
Click to expand...
Click to collapse
Thanks nice piece of info to have just in case
EVOvillain said:
I did what you say but my phone does not recognize the PC36IMG file.
Click to expand...
Click to collapse
yea thats not a problem at all you probably just have the file named PC36IMG.zip.zip. remove one ".zip", your computer is probably just hiding the extension.
If anyone is advanced enough to root their phone and flash ROMS< kernels, etc, then they should be advanced enough to go to Folder Options and uncheck Hide File Extensions on their computer....
Pretty easy did it 6 times for lots of people u can find the latest ru build pc36img on xda just look for it then get unrevoked forever son from there site when u get that flash it turns s on then get and place the latest ruu build on SD card go into boot loader and let it do its thing bingo stock pm me man if you need more help. Don't forget to delete the unrevoked file from SD card or the pc36img when your done.
Ps don't try those auto programs they can be a hassle.
EVOvillain said:
I have followed a few different guides regarding this and RUU will not find my phone. I have ran the program about 10 times and it just wont seem to find it. Also, it takes about 15 minutes for the program to tell me it can not find my phone. I have no idea why it takes so log to NOT find anything, LOL. is there another way to restore it or am i out of luck?
PS. I have rooted with unrevoked3. I need to return my phone so i need to completely stock.
Click to expand...
Click to collapse
HERE you go man get unrevoked forever son from there site and download this Ruu the one at the bottom is the latest build.
http://shipped-roms.com/index.php?category=android&model=Supersonic
hope this helps.
Fastest and easiest trouble free way man done it alot.
Easiest way to Unroot:
http://forum.xda-developers.com/showthread.php?t=829045
Scroll down a little.
Hello all,
I've had a DZ for nearly 2 weeks now, and have been holding off on installing roms, overclocking etc until there were clear, reversible guidlines available.
A few days ago I was being curious and ended up doing this the UBERROOT guide.
Essentially I temprooted using Visionary then executed the gfree script on my PC:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
This went well, and when I got to the bootloader I could see indeed that my S was OFF.
However, before I go any further I want to know how to reverse what I've done. This is mentioned at the bottom of the UBERROOT guide:
'run gfree, which will create a new backup of partition 7 in its unlocked state.
this will disable wp on the emmc, as well as remove the brq filter from the kernel.
at this point, you can dd if=/wherever/your/partition7-relock.img of=/dev/block/mmcblk0p7
sync; reboot'
I found the backup, although it was a .bin file not .img
I entered in the command above, but my phone rebooted before I could enter the 'sync' command. My S is still off, it would seem.
So my question to you fine people, having typed all this is:
How can I use the gfree backup to return my phone back to stock?
nofixio said:
How can I use the gfree backup to return my phone back to stock?
Click to expand...
Click to collapse
You can use the "dd" command to copy back the image of that original partition, as you mention.
However, the latest version of gfree now includes some new options to un-do that stuff, e.g. you can switch S-ON back on and change your SID via options. See the Wiki on this - http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF
nofixio said:
Hello all,
I've had a DZ for nearly 2 weeks now, and have been holding off on installing roms, overclocking etc until there were clear, reversible guidlines available.
A few days ago I was being curious and ended up doing this the UBERROOT guide.
Essentially I temprooted using Visionary then executed the gfree script on my PC:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
This went well, and when I got to the bootloader I could see indeed that my S was OFF.
However, before I go any further I want to know how to reverse what I've done. This is mentioned at the bottom of the UBERROOT guide:
'run gfree, which will create a new backup of partition 7 in its unlocked state.
this will disable wp on the emmc, as well as remove the brq filter from the kernel.
at this point, you can dd if=/wherever/your/partition7-relock.img of=/dev/block/mmcblk0p7
sync; reboot'
I found the backup, although it was a .bin file not .img
I entered in the command above, but my phone rebooted before I could enter the 'sync' command. My S is still off, it would seem.
So my question to you fine people, having typed all this is:
How can I use the gfree backup to return my phone back to stock?
Click to expand...
Click to collapse
When you run gfree, it creates a bin file in your sd card. That bin file you shall rename it to "whatever".img, to be more specific rename it to partiiton7-relock.img.
Now once you did this, just run gfree again:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
Once done the above, just download terminal emulator and from there run:
su
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
exit
And reebot the phone, Now you can go and see you are S-ON.
This method above works without a problem as myself have tried several times, however as steviewevie mentioned, the new version of gfree does this easier.
buzmay said:
When you run gfree, it creates a bin file in your sd card. That bin file you shall rename it to "whatever".img, to be more specific rename it to partiiton7-relock.img.
Now once you did this, just run gfree again:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
Once done the above, just download terminal emulator and from there run:
su
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
exit
And reebot the phone, Now you can go and see you are S-ON.
This method above works without a problem as myself have tried several times, however as steviewevie mentioned, the new version of gfree does this easier.
Click to expand...
Click to collapse
How to get that file (partition7-relock.img)? Because I formated the card after g-free method and I runned the official Ruu, so now I have that stupid S-Off, I need it S-On...
Niiceg said:
How to get that file (partition7-relock.img)? Because I formated the card after g-free method and I runned the official Ruu, so now I have that stupid S-Off, I need it S-On...
Click to expand...
Click to collapse
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
steviewevie said:
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
Click to expand...
Click to collapse
I don't find anything more than this guide:
Turning S-On
If you are returning your Vision to stock, you will want to flash your stock ROM and Recovery image before starting this, as root permissions and S-Off are required for both of those processes.
Remove Gfree (turn back S-On):
When you first ran Gfree, it automatically backed up your stock partition 7 (with S-On) and placed it on your microSD card as a file named part7-(something).bin and you will need to rename this file to: partition7-relock.img
Open up your ADB command prompt on your computer (with your phone plugged in) and type the following exactly as shown:
Code:
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
reboot bootloader
Your phone will reboot into bootloader. Look at the first line. The end should now say "S-On".
steviewevie said:
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
Click to expand...
Click to collapse
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Update: On fattire's thread they said they took down v3 because people were having problems with it and are now advising using v2 and the old restore method.
joemm said:
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Click to expand...
Click to collapse
Where to get that file if i already formated the card?!
Niiceg said:
Where to get that file if i already formated the card?!
Click to expand...
Click to collapse
There is no where to get the file if you erased/formatted your sdcard without saving it somewhere else, the instructons on gfree tell you to do this:
"gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer."
So if you didnt do this I really dont know what you can do. I have my part7backup but I dont know if its specific to my device or if anyone can use it.
joemm said:
There is no where to get the file if you erased/formatted your sdcard without saving it somewhere else, the instructons on gfree tell you to do this:
"gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer."
So if you didnt do this I really dont know what you can do. I have my part7backup but I dont know if its specific to my device or if anyone can use it.
Click to expand...
Click to collapse
Well, What device you have? Z or G2? I think that it's not specific, because all phones are the same ;D
Niiceg said:
I don't find anything more than this guide:
Turning S-On
Click to expand...
Click to collapse
Look at http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF
Scroll down to the bit that shows you the usage message for gfree and check out the "-s" option
joemm said:
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Update: On fattire's thread they said they took down v3 because people were having problems with it and are now advising using v2 and the old restore method.
Click to expand...
Click to collapse
The latest gfree 0.03 had problems, yes, so they went back to 0.02 in the Wiki. But as my previous post shows, you can still un-do things with gfree 0.02.
The only reason to use the backup of partition 7 that I can think of is if you don't know what your original CID was to reset to, or if you want to SIM Lock your phone again (there doesn't seem to be an undo option for the SIM Unlock).
steviewevie said:
The latest gfree 0.03 had problems, yes, so they went back to 0.02 in the Wiki. But as my previous post shows, you can still un-do things with gfree 0.02.
The only reason to use the backup of partition 7 that I can think of is if you don't know what your original CID was to reset to, or if you want to SIM Lock your phone again (there doesn't seem to be an undo option for the SIM Unlock).
Click to expand...
Click to collapse
Ok, I see the option for sec-flag on/off but does that also restore the sim lock?
Sent from my T-Mobile G2 using XDA App
joemm said:
Ok, I see the option for sec-flag on/off but does that also restore the sim lock?
Click to expand...
Click to collapse
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
steviewevie said:
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
Click to expand...
Click to collapse
I wasn't sure myself, thanks.
Sent from my T-Mobile G2 using XDA App
steviewevie said:
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
Click to expand...
Click to collapse
Okey, can you tell how to do everything? Because I don't know anything with that gfree... And there is no instruction... Please, help me get the S-On
I have PM'd the author of gfree about an option for SIM re-lock, because that would be useful. I guess you will still need some sort of carrier string which it needs re-locking to though ? Would be handy if perhaps gfree told you what that was before you unlocked it.
Im in the same boat as niiceg, I cannot find my backup and have had no luck in my searchs. Any Idea's what I can do from here?
Thanks in advance..
ps I'm guess my next step is to re root and do
su
cd /data/local
chmod 777 gfree
./gfree -s on
sync
???
bildo said:
Im in the same boat as niiceg, I cannot find my backup and have had no luck in my searchs. Any Idea's what I can do from here?
Thanks in advance..
ps I'm guess my next step is to re root and do
su
cd /data/local
chmod 777 gfree
./gfree -s on
sync
Click to expand...
Click to collapse
Yes, you just need to run "gfree -s on" as root to go from radio S-OFF to S-ON, no need to find/restore that backup.
HTC Desire USB Bricked Without Root
Hey guys, got a really tricky one for you here...
Some people may have seen a thread I posted the other day about problems that had arisen with my HTC Desire, well I have managed to find out that these problems are being caused by a USB Brick.
As of now I have managed to restore SD Functions however my phone will still not connect to the computer, and the phone won't recieve a network signal from Orange.
I read through this tutorial here and also this one here. My problem is, all the requirements of the fix, my device does not meet. My phone is not rooted, it is running the latest software and has the latest HBoot.
I also found this that looked very promising, however when I tried to log into my Google account on my phone, everytime it said it couldn't make a connection, I left it for a few hours and the same thing, I can't help but think this is due to the USB brick?
I just really need some help, is there anything I can do to restore USB functionality? The phone is being sent to HTC tomorrow, however I can cancel at any point. Please, I know there are so many amazing people on XDA that can help me. Thankyou
*UPDATE* - After using the Fastboot code to enable the SD Card, my Sim Card is now working. I have been able to log into my G-Mail account and download the terminal emulator which is an apparent fix in one of the posts I linked above, however this doesn't work. Please can someone help me
hy did you try to reinstal the software ???? the original os or an upgrade??
en_mih said:
hy did you try to reinstal the software ???? the original os or an upgrade??
Click to expand...
Click to collapse
I have done a factory reset, re-installed the PB99IMG and also flashed an RRU. All the problems persist
Really need help with this guys! E-Mail - [email protected]
jaaystott said:
Really need help with this guys! E-Mail - [email protected]
Click to expand...
Click to collapse
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
leinad said:
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
Click to expand...
Click to collapse
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
HQRaja said:
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
Click to expand...
Click to collapse
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
jaaystott said:
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
Click to expand...
Click to collapse
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
leinad said:
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
Click to expand...
Click to collapse
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
jaaystott said:
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
Click to expand...
Click to collapse
:-( (10 characters)
leinad said:
:-( (10 characters)
Click to expand...
Click to collapse
I really appreciate the help you gave me mate, even if I asn't able to fix my device, thankyou for the time.
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
moley10 said:
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
Click to expand...
Click to collapse
I found a way around this, as I was having the same problem. Try This ->
cat /sdcard/rageagainstthecage-arm5.bin > data/data/rageagainstthecage-arm5.bin
Do that for the two other commands that follow that, then follow the instructions as given, that should work.
HQRaja said:
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
Click to expand...
Click to collapse
Link to your blog? =)
ok, so i did that, no longer got errors.. seemed to work but after reboot still the same, doesnt connect to my pc, and device manager it is still being shown as 'qualcomm cdma technologies msm' in other devices!
is the purpose of those commands to moved the files to certain directory? i can get temp root with visionary to perhaps just move the files in root explorer?
thanks for all the help. its much appreciated!
Hello,
I've got a similar problem but this solutions doesn't work for me, because I cannot create a CID.
Any ideas?
Thanks in advance
hi,
i managed to create files etc and still am stuck with the same problem... searched hi and low for days,
hopefully someone will be able to find us a solution..
You mean creating the mtd from that site? Thats because you need to type the Build Number not the kernel version.
Hi guys,
I got a problem:
I rooted my Desire PVT4 with unrevoked and AmonRa-Recovery under Linux Mint Live CD. Everything went fine.
Next, I wanted to prepare for flashing a new rom. I did a Titanium Backup and downloaded Rom Manager. I proceeded to do a nand-backup, which it did, I guess. After that, however, my desire didn't recognize my sd card anymore.
Connecting to Windows 7 didn't work either. (It did work before)
So I went and bought a new sd card. I formatted it and put it in my device. Still, no sd card detected.
Along with the new sd card, I got an adapter, so I can now stick the sd card directly into my computer.
Surprise: I could now see both sd cards in Windows. Still, I formatted both after backing up the files on it.
The Desire wasn't able to boot anymore, though. So I went into recovery mode and partitioned the card manually with AmonRa recovery 2.0.1. This did work.
I can boot the Desire now, but it still won't detect the sd card.
Mounting it with AmonRa doesn't work either.
I read, that the problem might be caused by using RomManager on a PVT4 device.
Installing the HTC drivers didn't help and I can't install the google USB drivers. When I try to do so it says that there were no drivers found in the specified directory (""C:\android-sdk-windows\google-usb_driver")
In the device manager it shows 3 "Qualcomm CDMA Technologies MSM" (bought it in Germany, so shouldn't it read "GSM"?). All of them are marked with a yellow question mark. Upon trying to update the drivers I selected "Install software from a list or source" and specified ""C:\android-sdk-windows\google-usb_driver". I clicked "proceed" but Windows tells me that it couldn't find the drivers. Tried that on Win7 and on my WinXP laptop.
I desperately need help. I'm no pro. Actually I am a complete noob I searched on google but I couldn't find any solution so far.
Since I can't access my sd card (except partitioning in AmonRa, that did work somehow) I can't access any .zip on my sd card.
e. Additional information:
Upon trying to mount in Amonra recovery it says:
""Can't mount /sdcard"
Same, when trying to flash a .zip from sd.
hboot version is 0.93 I think.
I tried the following:
Just fixed it... i think the problem erupted because i have AmonRA recovery and used Rom manager (Clockwork mod recovery based) .. there were several reports
that this may cause a usb brick. ... any way... i searched for how to unbrick it.. and used a clone cd from modaco ((Tinycore.img)) which is linux based to boot from it (with phone connected to fastboot usb) .. and
entered the following commands :
Quote
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
and it enabled the sdcard... i checked the sdcard workability from the recovery (i hadn't format it yet) then thought : WTH, why not to try and restart the phone to see if it will log in normally .. and it did (naturally
because the sdcard block was the thing that prevented it from booting from the very start)...
Click to expand...
Click to collapse
Except that I used Linux Mint Live CD.
All I got was:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write/protected, mounting read-only
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: /dev/sr0 already mounted or /mnt/cdrom busy
mount: according to mtab, /dev/sr0 is already mounted on /mnt/cdrom
cd /mnt/cdrom/root
bash: cd: /mnt/cdrom/root: No such file or directory
Must I use TinyCore? I read somewhere that it only works for Hboot 0.8 and lower? What exactly is TinyCore anyways?
I almost know nothing about linux
No one?
Now I can't even get a signal anymore. I could cry...
Have you tried this procedure?
http://forum.xda-developers.com/showthread.php?t=691639
It worked for me when i bricked (pvt1 s-off). The problem seems to lie in the misc partition, which you have patch with the edited img file...
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
e. Also, my PC does not recognize the desire when pluggin into USB.
Eiskrem-Kaiser said:
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
Click to expand...
Click to collapse
You type that into cmd prompt window on your PC.
There are some instructions on SD card fix in this thread:
http://forum.xda-developers.com/showthread.php?t=691639
It happened to me when I partitioned the SD card in windows. Could you chech if your partitions on your SD are both set as primary and also uncheck "Take ownership of filesystem" (or something like that) when you are using the HD utility in linux.
Basically what happened was that the partitions were logical in stead of primary. Banged my had in the wall for two days before I figured this out. Hope it helps.
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Eiskrem-Kaiser said:
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Click to expand...
Click to collapse
I guess it means that sdcard can't be mounted...anyway, have you done the hexeditor thing already?
I just put the two files on the sd card and rebooted in fastmode. However, I'm not sure about my rom version. Where can I find out which one I have?
e. I just typed "cat /sdcard/flash_image > /data/flash_image" in ConnectBot, but it says "cannot create /data/flash_image: permission denied"
e.. When I type in "su" first, it still says "/sdcard/flash_image: No such file or directory"
Eiskrem-Kaiser said:
Where can I find out which one I have?
Click to expand...
Click to collapse
Oh sorry, i didn't read that...well i remember i was confused about that too at this point...too bad i can't remember how i found out.
Anyway, i found another solution on modaco:
"2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
3. Put THIS (attached) update.zip on your sdcard.
4. Reboot into recovery.
5. Apply sdcard:update.zip.
6. This will automatically fix your MISC partition with the correct CID. Reboot, and your done!"
Try this and tell me if it works in the while
I just booted into fastmode again and typed "fastboot oem enableqxdm 0" into the command prompt.
Now the Desire detects the sd card again :thumbsup:
Now I will try to use the cat command again.
e. I just did the thing with the "update.zip". Rebooting now.
e. I got my sd card back and a phone signal. That's great so far. Now what?
Still, when typing
"cat /sdcard/flash_image > /data/flash_image"
I get
"/sdcard/flash_image: No such file or directory"
I guess you're done if it worked...are you able to connect normally to your pc now? You should be :s
Also, those commands are meant to be used in a terminal emulator, not on your pc, i hope you didn't misread...anyway if you used the modaco tip you shouldn't need that anymore.
When you're done remember to copy your misc folder to a safe place, it will be enough to replace it via root explorer or similar if someday you'll brick again...
Nope, can't get it to connect to my PC quite yet. But I hope I will get that to work after rebooting the phone and/or windows or installing the htc drivers again.
I can not thank you enough right now. I was going crazy about this. Just bought my desire recently, upgrading from the Legend, with the little spare money I had. It would have been bad, if it was broken now.
So: THANK YOU VERY MUCH.
Also, someone tried to call me yesterday, while my phone signal didn't work. Now everytime I start the Phone, it shows me my missed call.
My girlfriend has a similar problem with a message I sent her. Everytime she boots her phone, she gets that message (fortunately it's "I love you" ).
So, I guess, it has something to do with the SIM?
Hmm, if you can't connect it might mean that the usb isn't fully restored...could you turn off the phone, plug it to pc, turn it back on and see if drivers get installed properly? Just to make sure...
I am stupid.
Hold on, it might work now. I had to switch to "local" in ConnectBot. Thought the app would remember that, but it didn't
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Eiskrem-Kaiser said:
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Click to expand...
Click to collapse
Sorry, i'm not sure i got ya. How would you run connectbot while you're in saftboot mode?? Because that's what i did, to make it clearer:
1. Downloaded image file "mtd0.img" and "flash_image" (from here http://forum.xda-developers.com/showthread.php?t=691639) and put them on sdcard (ofc i edited mtd0.img with my CID using some free hex editor before)
2. Installed Android Terminal Emulator app (from market), but connectbot should be the same.
3. Opened emulator, typed "su" command, accepted to give root permissions
executed this commands:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/misc.img > /data/misc.img
chmod 755 /data/flash_image
/data/flash_image misc /data/misc.img
4. Rebooted phone, connected to pc.
5. Success
Is this exactly what you did?
Yes. I typed exactly that. I just wanted to type it in again, but now it tells me again, that there is no such file or directory on /sdcard. But I can see the file with Astro being on the sdcard.
e. Maybe I used the wrong rom version number?
e.. Someone suggested to run in fastboot mode and type "fastboot oem eraseconfig". What exactly would this do? Which config would be erased?
What exactly is fastboot?
Eiskrem-Kaiser said:
Maybe I used the wrong rom version number?
What exactly is fastboot?
Click to expand...
Click to collapse
You just need the CID, not the rom version for this...
Anyway, please note that when i write misc.img i mean mtd0.img, that's what you typed right? Sorry if i confused you.
I guess there's no need to mess further with fasboot, i didn't need it, except for mounting sdcard.
If this still fails, you can always move mtd0.img and flash_image to /data manually via root explorer app, then go on from the chmod command.