I have a friend who got a MyTouch 3G off of craigslist. It works great, but he saw what I did with my G1 and wanted to root it and all of that business. Well as simple as everyone seems to make it, I still had issues getting it rooted, but I think I got it done. I noticed it already had the Engineering SPL already loaded on it when he got it. I managed to get Amon_RA's 1.2.3 Recovery on it and flash CM4.2.7.1.
Here is the problem, His phone isn't recognized by ADB. I can boot into fastboot and it will recognize the phone, but I tried to update it to Amon_RA's 1.5 recovery through fastboot and it said "NOT ALLOWED". I know I have ADB and Fastboot setup properly because it works fine for my G1. What could be the issue keeping his phone from working.
Thanks in advance.
ccunningham83 said:
I have a friend who got a MyTouch 3G off of craigslist. It works great, but he saw what I did with my G1 and wanted to root it and all of that business. Well as simple as everyone seems to make it, I still had issues getting it rooted, but I think I got it done. I noticed it already had the Engineering SPL already loaded on it when he got it. I managed to get Amon_RA's 1.2.3 Recovery on it and flash CM4.2.7.1.
Here is the problem, His phone isn't recognized by ADB. I can boot into fastboot and it will recognize the phone, but I tried to update it to Amon_RA's 1.5 recovery through fastboot and it said "NOT ALLOWED". I know I have ADB and Fastboot setup properly because it works fine for my G1. What could be the issue keeping his phone from working.
Thanks in advance.
Click to expand...
Click to collapse
what spl does it exactly have?
Does adb work on your phone from that same pc?
Do you have all your drivers correctly installed?
He has:
The Engineering SPL 1.33.0006
PVT32B board
Radio 2.22.19.26I
When I plug in the phone it doesn't ask for new drivers and I even tried to update them manually with the newest SDK.
My phone works fine from the same computer. Fastboot recognizes both of our phones, ADB only recognizes my phone. When I try to flash a new recovery on his phone via fastboot, it says not allowed.
My phone is:
Engineering SPL 1.33.2005
PVT 32B
CPLD-4
Radio 2.2219.26I
might help
http://forum.xda-developers.com/showthread.php?t=595150
sitimber said:
might help
http://forum.xda-developers.com/showthread.php?t=595150
Click to expand...
Click to collapse
I tried that. Re-installing and updating ADB didn't work. Everything that works for my G1 doesn't seem to work for my friends MT3G. I also have a friend who has a stock Hero from sprint and his phone isn't recognized by ADB either.
Fastboot will recognize his device, but it won't allow me to flash his phone.
Related
Hey XDA
Im having a little problem with my Magic.
I would like to flash a new ROM, but i cant get into the recovery menu.
Here is what i do:
I have installed the latest version of SDK on my computer.
I then connect my Magic with the cable, and when Vista comes up with the note saying that want to install the software i tell it to use the drivers that are in the SDK/usb_driver/x86 folder.
I then turn off the phone, and press and hold back button + power button until the phone shows the "3 androids on skateboard" menu.
Then on my computer in the cmd prompt i write: fastboot boot recovery.img, and the the cmd prompt says: <waiting for device> and the nothing else happens, the recovery image dosn't show up on the phone either.
I have checked with adb devices that my phone is connected.
Are there anyone that can help me with this problem because its beginning to annoy me alot, i would like to root my phone and flash another ROM.
So any help would be much appreciated.
Per
Just to check, you made sure you have a spl that's rootable?
http://forum.xda-developers.com/showthread.php?t=529019
And fallowed this before fastboot.
First, setting up your PC (I'm going to assume you're using windows for this) to work with Android in a debugging enviroment.
1. Get the latest Android SDK from here (http://developer.android.com/sdk/1.5_r2/index.html) and unzip it into a convienent directory (most people use C:\Android\, so I suggest you do the same). The result should be something along the lines of C:\Android\android-sdk-windows-1.5_r2\.
2. Set up your phone to work with debugging drivers. The method of doing so can be found here (http://developer.android.com/guide/...ing/device.html) in the "Setting up a Device for Development" section, steps 2 and 3. To test that it works properly, open up a command prompt and navigate to the tools directory (C:\Android\android-sdk-windows-1.5_r2\tools). Type into the prompt:
Code:
adb devices
If it returns your device and serial number, then you're all set.
3. Lastly, grab fastboot.exe from here (http://www.htc.com/www/support/android/adp.html) and place it in the tools directory of the sdk.
Next up, rooting.
Clinton
Thx for the answer, but there is a problem with one of the links you posted, the last one of them (http://developer.android.com/guide/...ing/device.html). it dosn't work.
But you also write something about the SPL, i dont know if i have the right SPL, how can I see if its the right one i have? I've tried reading the link about the SPL, but my problem is that i cant even get into the recovery menu, so i cant flash a new SPL either, or am i wrong?
Please help me
Per
To check your SPL just boot up fastboot (back + power) then just look at the top and see what it says. Then check on the first link I posted and see if your SPL is rootable or not.
Don't know why the last link didn't post proper Here it is.
Clinton
perevers said:
Hey XDA
Im having a little problem with my Magic.
I would like to flash a new ROM, but i cant get into the recovery menu.
Here is what i do:
I have installed the latest version of SDK on my computer.
I then connect my Magic with the cable, and when Vista comes up with the note saying that want to install the software i tell it to use the drivers that are in the SDK/usb_driver/x86 folder.
I then turn off the phone, and press and hold back button + power button until the phone shows the "3 androids on skateboard" menu.
Then on my computer in the cmd prompt i write: fastboot boot recovery.img, and the the cmd prompt says: <waiting for device> and the nothing else happens, the recovery image dosn't show up on the phone either.
I have checked with adb devices that my phone is connected.
Are there anyone that can help me with this problem because its beginning to annoy me alot, i would like to root my phone and flash another ROM.
So any help would be much appreciated.
Per
Click to expand...
Click to collapse
Sound like you're not using the right Recovery .img
Check here to start with: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
ClintonH said:
To check your SPL just boot up fastboot (back + power) then just look at the top and see what it says. Then check on the first link I posted and see if your SPL is rootable or not.
Don't know why the last link didn't post proper Here it is.
Clinton
Click to expand...
Click to collapse
I have the: SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
If what im reading at the first link is correct, my SPL cant be root'et, or im not reading the first link correctly?
And if i need a new SPL, how do i flash that one? and what SPL should i choose? and last, how can i then get my SPL back to how it is now if i need to get the phone to repair?
Per
antonram said:
Sound like you're not using the right Recovery .img
Check here to start with: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
Click to expand...
Click to collapse
I am using the right recovery image, i also tried the one you linked, that didn't work either
Per
perevers said:
I have the: SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
If what im reading at the first link is correct, my SPL cant be root'et, or im not reading the first link correctly?
Per
Click to expand...
Click to collapse
Afraid your not going to be able to root right now. It's in the works though so it might be soon.
Clinton
ClintonH said:
Afraid your not going to be able to root right now. It's in the works though so it might be soon.
Clinton
Click to expand...
Click to collapse
Damn, thats a load of ..... (sorry).
I have just got my phone back from the repair shop because the camera restarted the phone everytime i tried to use it. Before i sent it to repair i had no problem rooting it or getting in the recovery menu.
But can you tell what the problem is? is it because the recovery image dosn't work with my SPl and the recovery image guys need to "crack" my SPL first or what?
Per
perevers said:
Damn, thats a load of ..... (sorry).
I have just got my phone back from the repair shop because the camera restarted the phone everytime i tried to use it. Before i sent it to repair i had no problem rooting it or getting in the recovery menu.
But can you tell what the problem is? is it because the recovery image dosn't work with my SPl and the recovery image guys need to "crack" my SPL first or what?
Per
Click to expand...
Click to collapse
Here you go read This on the SPL. By the way which phone do you have? Is it a Rogers Magic? Just good to know what's not rootable, you should post your phone details in that thread if it's something not listed on the first page.
Clinton
ClintonH said:
Here you go read This on the SPL. By the way which phone do you have? Is it a Rogers Magic? Just good to know what's not rootable, you should post your phone details in that thread if it's something not listed on the first page.
Clinton
Click to expand...
Click to collapse
Its a HTC branded magic, dont know if its a rogers. But im from Denmark, and bought it in Denmark. dont know if that helps.
Thx for the help, will read the thread.
Btw. can you tell where i can see how far they are in "cracking" this SPL?
Per
hello everyone,
im having some trouble with my 32b vodafone magic. im hoping someone might be able to help me with.
i tried to update the rom to the jachero, but i didnt update the SPL first. now when i turn on the phone it just goes to the hero/htc splashscreen and keeps looping that. the phone wont load up fully.
i did some searches and found out that i could use the adb program in the android sdk, however when i load it nothing is showing in the devices list. i think this is because usb debugging is not enabled?
i can get into fastboot OK and cyans 1.4 recovery as well.
would it be possible for me to go into the console and type a command in there that would enable usb debugging? if so what do i need to type and how do i get the keyboard to appear in cyans recovery console in the first place? - (i have the usb drivers already installed on windows from the sdk)
other then that i was thinking i could just buy a micro sd card reader and copy the spl onto it that way and then update? and then update the ROM.
ive tried restore/wipe but that doesn't work for me either, i still keep getting stuck on the splash screen.
any help would be very much appreciated.
thanks a mill,
luke
hi again,
i thought id give some more info that might be of use, hopefully.
my current spl is 1.33.0004 and the radio is 2.22.19.26I
i tried using fastboot but everytime i try to flash a file onto the device i get remote: signature verify fail
thanks,
luke
hiyas, just a quick update, i went and got an sd card reader and updated the spl and then put the rom on it and its flying now.
Hello, i updated my magic with the wrong ROM and now nothing works except FASTBOOT (vol down + power). everything else just freezes to the red vodafone screen. What can i do from here?
Here's the info:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0010
CPLD-12
RADIO-3.22.20.17
Please please with anything on top help?
ok
let's make things interesting. mods feel free to sticky this...
i really need a solution this weekend. i'll send three bottles of the best local beer to whoever solves my problem.
go!
Do you have a Nandroid backup of your original ROM? If so - see here
http://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
If not, I'm sure a quick search will show someone has posted a full backup somewhere on here.
Sorry...didn't notice before that you have the Perfect SPL. I suggest looking here instead -
http://forum.xda-developers.com/showthread.php?t=547133
alexdroid said:
Hello, i updated my magic with the wrong ROM and now nothing works except FASTBOOT (vol down + power). everything else just freezes to the red vodafone screen. What can i do from here?
Here's the info:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0010
CPLD-12
RADIO-3.22.20.17
Please please with anything on top help?
Click to expand...
Click to collapse
Have done the same ..as you
I used adb get recovery to work again from fastboot
keepitnang said:
Sorry...didn't notice before that you have the Perfect SPL. I suggest looking here instead -
http://forum.xda-developers.com/showthread.php?t=547133
Click to expand...
Click to collapse
tried that, fastboot gives me the "remote: not allow" error.
alexdroid said:
tried that, fastboot gives me the "remote: not allow" error.
Click to expand...
Click to collapse
Yeah...that's because your phone has the Perfect SPL - it won't allow a fastboot connection. The article I linked to shows you how to change the SPL and enable this. Having said that, have you tried stian230's suggestion concerning connecting via adb to restore a recovery image?
Have a look at Amon_RA's thread for his excellent recovery image. This shows how to push the image to your phone and boot to it -
http://forum.xda-developers.com/showthread.php?t=530492
keepitnang said:
... have you tried stian230's suggestion concerning connecting via adb to restore a recovery image?
Have a look at Amon_RA's thread for his excellent recovery image. This shows how to push the image to your phone and boot to it -
http://forum.xda-developers.com/showthread.php?t=530492
Click to expand...
Click to collapse
adb does not recognize my phone (all the drivers are ok, fastboot can see it). all the guides dealing with this said to make sure i have USB debugging enabled, but i can't access my phone to do this.
changing the spl seems to permanently void the warranty (not sure about this)...
K...sorry...this is where my n00bness runs me into a brick wall. The only way I know of to recover in this instance based on what you have said is to go ahead and flash a 'friendlier' SPL. Perhaps someone infinitely cleverer than I knows of another method though?
alexdroid said:
adb does not recognize my phone (all the drivers are ok, fastboot can see it). all the guides dealing with this said to make sure i have USB debugging enabled, but i can't access my phone to do this.
changing the spl seems to permanently void the warranty (not sure about this)...
Click to expand...
Click to collapse
ADB will find your phone if you try a little while.
I promise
Just take it easy do not stress.
Try the phone off. or try recovery even if you do not get in recovery adb believe that it is the in recovery .
certainly sounds a bit strange but I did it that way
i just can't get adb to recognize my device. i tired on xp and 7, unistalled and reinstalled usb drivers and nothing.
all the guides mention tunring on USB debugging, but i can't get into android to do that. all i have is the damn fastboot. is there any other way to turn on usb debugging?
edit: apparently, adb isn't supposed to work in recovery mode. and since i can't use fastboot, because of my SPL, i'm locked out. any other ideas?
does not sound good. but I had the same problem a week ago. I had flashed a ROM and used the wrong port 32A. phone had a "semibriked" I only had access to fastboot and hboot.
I also have perfect spl. But after many attempts the adb found my phone.
I had an empty sdcard with only recovery-RA-sapphire-v1.5.2H.img on it.
is there any other method to change spl, or make fastboot work? the goldcard thing looks crazy hard...
Hope someone here can help. I have the HTC MAGIC 32A hboot 1.76.0010, cpld-12, radio-6.35.16.19 and tried flashing the ROM with ROM MANAGER, and everything was going good, phone rebooted, status bar was moving, then it stopped, now I can only get to the ROGERS screen. I am able to get into fast boot, but nothing else, I tried the factory reset, and still nothing. ABD wont recognize the phone, but the computer recognizes android 1.0 but I dont think I have it set up right, as I have aworking MAGIC, and I cant get the abd to recognize that phone either. Can someone point me to a walk through on restoring this phone, or give me some pointers? I dont recall the actual ROM I tried flashing but will try and get that if needed as well phone goes into clockwork recovery but only for a few moments .
Run this in fastboot mode
Code:
fastboot getvar version-main
fastboot getvar cid
specs:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
what i have done:
http://forum.xda-developers.com/showthread.php?t=605239 (the upgrade part)
with the files from *urgh* cant find the link again.. *search in history*
edit; cant find the url, f***, anyway, the filenames was "update-hboot-1.76.2007-signed.zip", "NewRadio.img"
what i want to do:
get a new ROM on the phone, with 2.0+ with sense
i can't flash recovery with fastboot, however, i can boot into 1 with fastboot boot /path/to/img in CMD.
however, that does not seem to work, i suspect it has something to do with the errors im getting on fastboot.
the errors are:
SD Checking...
Loading... [SAPPDIAG.zip]
No image!
Loading... [SAPPDIAG3.nbh]
No image or wrong image!
Loading... [SAPPDIAG2.nbh]
No image or wrong image!
Loading... [SAPPDIAG.nbh]
No image or wrong image!
Loading... [SAPPIMG.zip]
No image!
i have no idea what happend =3 im such a noob on this.. =(
would be very happy if someone could help me ASAP, as i don't have any other mobile at the moment.
oh and, i can't boot into the ROM i've tried to "install" with carz recovery img, the rom "Magic13" that i got from here, somewhere..
actually, i would be very happy if i could just get it back to its original shape, hardrest and all that doesnt seem to work either..
1. These errors are not in fastboot, but in hboot-mode...
SD Checking...
Loading... [SAPPDIAG.zip]
No image!
and blah-blah-blah
2. Your phone is not bricked
3. To get right combo hboot/radio with S-OFF and abiltiy to install custom roms you must do this: http://forum.xda-developers.com/showpost.php?p=5526163&postcount=1
5[Strogino] said:
1. These errors are not in fastboot, but in hboot-mode...
SD Checking...
Loading... [SAPPDIAG.zip]
No image!
and blah-blah-blah
2. Your phone is not bricked
3. To get right combo hboot/radio with S-OFF and abiltiy to install custom roms you must do this: http://forum.xda-developers.com/showpost.php?p=5526163&postcount=1
Click to expand...
Click to collapse
i can't do the RUU because i can't boot my phone, its stuck on splash screen, so the program cant find the phone.
sorry, i should have mentioned that too.
comoba said:
i can't do the RUU because i can't boot my phone, its stuck on splash screen, so the program cant find the phone.
sorry, i should have mentioned that too.
Click to expand...
Click to collapse
1. Remove battery, wait 5-10 seconds, place it back
2. Turn phone on by pressing and holding Back + Power (phone should load into fastboot)
3. Connect to PC, if connected successfully - text 'fastboot' will change to 'fastboot usb'
4. Run RUU
that doesnt seem to help, it (the program) still gives usb connection error 170, but i can access it from fastboot in cmd.
=/
comoba said:
that doesnt seem to help, it (the program) still gives usb connection error 170, but i can access it from fastboot in cmd.
=/
Click to expand...
Click to collapse
Error 170 links to USB connection error.
Make sure that you've installed Android SDK Tools (with drivers package), HTC Sync (with drivers / or drivers only).
In Android SDK Tools there are two utilities: /platform-tools/adb.exe and /tools/fastboot.exe
You can check connection with PC when executing:
adb devices (in normal-mode)
fastboot devices (in fastboot-mode)
If any utility returned serial number - so you don't have any problems with usb connection and can try install RUU
5[Strogino] said:
Error 170 links to USB connection error.
Make sure that you've installed Android SDK Tools (with drivers package), HTC Sync (with drivers / or drivers only).
In Android SDK Tools there are two utilities: /platform-tools/adb.exe and /tools/fastboot.exe
You can check connection with PC when executing:
adb devices (in normal-mode)
fastboot devices (in fastboot-mode)
If any utility returned serial number - so you don't have any problems with usb connection and can try install RUU
Click to expand...
Click to collapse
the only thing im missing on that list is htc sync, so ill download it and try again, i have adb and fastboot, but im not sure that adb can connect to the phone in fastboot ( since i can't boot to ROM )
e; adb and htc sync cant find the devices, as suspected, probably due the fact that i can't boot the device other then with "fastboot boot <recovery img>" in fastboot-usbmode.
and the program still can't find the phone after installing htc sync (same error).
comoba said:
the only thing im missing on that list is htc sync, so ill download it and try again, i have adb and fastboot, but im not sure that adb can connect to the phone in fastboot ( since i can't boot to ROM )
e; adb and htc sync cant find the devices, as suspected, probably due the fact that i can't boot the device other then with "fastboot boot <recovery img>" in fastboot-usbmode.
and the program still can't find the phone after installing htc sync (same error).
Click to expand...
Click to collapse
Yeah. Adb works only in normal-mode, but fastboot.exe works in fastboot-mode.
So...
Load into fastboot-mode
Run command
Code:
fastboot devices
Does it return serial number?
5[Strogino] said:
Yeah. Adb works only in normal-mode, but fastboot.exe works in fastboot-mode.
So...
Load into fastboot-mode
Run command
Code:
fastboot devices
Does it return serial number?
Click to expand...
Click to collapse
yes it returns "HT95PKF03141 fastboot", but what do i do with that?
Your computer can see phone, but you have to change usb-cable or usb-port.
Sent from my A7-040 using Tapatalk
5[Strogino] said:
Your computer can see phone, but you have to change usb-cable or usb-port.
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
oh ok... that makes sense, i think, because i've been using a unorignal cable since my original cable is borrowed out.
who knew a cable could make such a hassle.
comoba said:
oh ok... that makes sense, i think, because i've been using a unorignal cable since my original cable is borrowed out.
Click to expand...
Click to collapse
actually, same error with original cable...
maybe it's the OS? im using win7 64bit.. hmm, ill try find a computer with a 32bit OS.
Edit; got a hold of a winXP computer, it seems to work.
what's a good ROM for atleast 1.6 or higher with HTC Sense?
comoba said:
Edit; got a hold of a winXP computer, it seems to work.
what's a good ROM for atleast 1.6 or higher with HTC Sense?
Click to expand...
Click to collapse
Congratulations)
If you are on 1.76.2007 / 6.35.XX.XX so you can try this:
http://forum.xda-developers.com/showthread.php?t=1025330 (Android 2.3.3 with Sense)
or with Android 2.1 but more native (stable, fast and smooth)
http://forum.xda-developers.com/showthread.php?t=778083
http://forum.xda-developers.com/showthread.php?t=822531
a few questions about the guide posted, since i haven't done anything yet other then the RUU so i could atleast use the phone...
do i really need a goldcard? i've read the guide, and it doesnt seems to do anything but edit my sdcard, which seems weird since it works to the phone already and it seems i already have root, because 'adb shell' gives me #, and i downloaded superuser, which doesn't seem to be any issue, but i still have S-On, so i'm a bit confused about that.
where do i get the SPL & HBoot? the links seems to be missing in the guide.
i guess i should flash new SPL and HBoot before saying this, but the error in hboot still exists after RUU.
thanks for all the help =)
comoba said:
a few questions about the guide posted, since i haven't done anything yet other then the RUU so i could atleast use the phone...
do i really need a goldcard?
Click to expand...
Click to collapse
Every time if you want flash official ROM that is not for your country/operator you need goldcard. In general, phone has own CID (example HTC__037 - Indonesia), ROM has list of compatible CIDs. While flashing ROM is checking list with phone's CID. If they are not equal - you will get error. Goldcard emulates cid 11111111 which is always in ROM CID list.
comoba said:
but i still have S-On, so i'm a bit confused about that.
Click to expand...
Click to collapse
Yeah, to do S-OFF you must flash engineering bootloader. Hboot which compatible to radio 6.35.XX.XX is hboot 1.76.2007
comoba said:
where do i get the SPL & HBoot? the links seems to be missing in the guide.
i guess i should flash new SPL and HBoot before saying this, but the error in hboot still exists after RUU.
thanks for all the help =)
Click to expand...
Click to collapse
SPL and HBoot and Bootloader are same things (in general, when people write manuals)
And yes, you need flash HBoot 1.76.2007 - you will get more abilities (like fastboot commands)
HBoot 1.76.2007 ENG S-OFF here: Download Flash via custom recovery