Related
Hello All,
I've tried my hardest to search all over the forums but I still can't figure this out. I'm highlighting all I've tried to eliminate all that junk.
I have a 32A magic and I tried updating the ROM via this post.
I actually installed the radio 6.35.08.29 a little bit lower on the post using recovery mode while it was on my SD.
My device is rooted via theunlockr.com's one click rooting.
I think this was the problem because I was supposed to install the radio 6.35.10.18 because as soon as it was finished installing and rebooting, it keeps rebooting and doesn't even get past the splash screen
Here's where the issues start making me want to pull my hair out.
The good news (from what I'm hearing) is that I can still boot into fastboot and HBoot modes, but I can't get to restore mode at all
I'm getting better with the sdk so I'm understanding fastboot etc now but the main problem I believe is that it won't recognize my device.
I am on windows 7, but yes I've installed the latest drivers and device manager is recognizing it but when I try in cmnd to type adb devices it shows "List of devices attached" and it's emtpy.
I try to type something like adb bugreport and it comes back "error: device not found"
So clearly it doesn't seem to be recognizing the device.
What I was trying to do what push another radio to the device or something but at this point I have no idea what I am to do, especially since I can't get to restore!! Grr!
Any ideas?
p.s.
I thought I'd mention that I think this may be because I didn't (and cannot) select USB debugging from the menu as I can't load the device...
May be bricked... Oh well lol
update
It's only going into fastboot mode when plugged in now.
kob123 said:
It's only going into fastboot mode when plugged in now.
Click to expand...
Click to collapse
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
make sure those files are in your tools folder
Thanks,
The files recovery-RA-hero-v1.5.2, Radio_HTC_PVT_32A_6.35.10.18, as well as hboot-1.76.2007 are all in the tools folder.
For fastboot flash radio:
I keep getting:
sending 'radio' ... okay
writing 'radio' ... INFOsignature checking...
FAILED (remote: signature verify fail)
Same thing happens for flashing hboot and recovery as well...
fastboot erase system -w
fastboot reboot-bootloader
both work fine.
Like I said, thanks HUGE so far, but still not working...
im also having the very same problem i cant even flash the sappimg or anything i dont even get the recovery
sapphier pvt 32b ship s-on h
hboot-1.33.0009 (sapp30000)
cpld-10
radio-3.22.20.17
thats all i get please help
ok i got it check it this is what i did i put the engineering-spl-hboot 1.33.2005on to sdcard and rename to update...
then turn on to recovery holding home n power...
then when the triangle picture pops up press home & end call buttons again just press it no need to hold....
once done updating place sappimg.zip on to sdcard...
power on to hboot ...
phonewill load zip file.....
let it do its thing again after done reboot and you got it!!!!!!
i had a card adapter sou will need on let me know if it helped you out....also i formatted my sdcard before i started because phone had problems mounting card when in recovery
http://forum.xda-developers.com/showthread.php?t=530527
download the update.zip
fastboot boot recovery-RA-sapphire-v1.5.2.img
(make sure you use sapphire unless you have the hero radio and spl installed otherwise the hero recovery is needed if you have the cursorsense radio which effectivly makes the magic a hero)
apply the update.zip
then you should be able to fastboot the prev instructions
just fyi make sure u check your radio on the fastboot screen before using the hero or sapphire recovery - make sure you use the proper one!
update
Hey all my problem was also with the spl as well for some reason. I also loaded the newest rogers update instead which the combination did the trick...
kob123 said:
Hey all my problem was also with the spl as well for some reason. I also loaded the newest rogers update instead which the combination did the trick...
Click to expand...
Click to collapse
yeaaa the spl is what my above tricck woulda fixed but if you loaded the latest rogers update you got no root access for now which kinda sucks
I updated the Radio on my 32a then I went to Fastboot mode to load the hboot image and discovered that i get a (failed : remote not allowed) message everytime I try to flash anything. So I guess I need a goldcard the only problem is I can't boot up to reformat the SD and make a goldcard...
Any idea's??
I'm lost!!
Can someone make a Goldcard for me, on another phone? I don't know what to do,
Thanks in advance...
anyone???
I'll pay for a goldcard if someone sends me one, assuming I can use one made on another phone in my phone. I need a way to get past my Fastboot mode and I can't boot to recovery or get anywhere else... to make a Goldcard
HELP?!?!
i used my memory card that came with my phone to create a gold card and it worked perfectly well just make sure you follow the guide to the letter.
you cant use one from another phone as you have to get the CID from your phone which is unique from phone to phone.
i believe what you should of done was flash the image first then update the radio but just search the forums theres bound to be someone with the same problem or even a google search might help
icow said:
i used my memory card that came with my phone to create a gold card and it worked perfectly well just make sure you follow the guide to the letter.
you cant use one from another phone as you have to get the CID from your phone which is unique from phone to phone.
i believe what you should of done was flash the image first then update the radio but just search the forums theres bound to be someone with the same problem or even a google search might help
Click to expand...
Click to collapse
But I can't use my phone to make a Goldcard because I can't get it booted up to a point where i can use adb shell. Only Fastboot
use a card reader. if you don't have one, go buy one, they are very useful to have lying around...
hi
please please please my phone is completely dead can i use the blue led mode ?? or the gold card to revive it and use fastboot again????
march83 said:
use a card reader. if you don't have one, go buy one, they are very useful to have lying around...
Click to expand...
Click to collapse
How does a card reader help me get the cid number off the phone? Don't i still need to get to adb mode to do that? which means booting the phone up which it won't do...
What's your HBOOT version? I got that while upgrading my RADIO. All I had to do was install an engineering SPL first. Then I was able to flash the new SPL.
you need to post more info. what radio did u upgrade to and whats your spl/hboot? Also, what recovery did u use?
I also noticed you saying something about the blueLED, I thought you could still get into fastboot...
can you still get into fastboot? I'm confused, cause you went from being able to go into fastboot and then now it's completely dead?
current set up
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT - 1.33.0010
CPLD-12
RADIO-6.35.00.29 (was 3.22.20.17 before update)
June 2 2009, 17:28:28
I the current recovery is RA-magic-v1.2.3H and I was trying to upgrade to RA-hero-v1.6.2 and Hboot 1.76.2007.
I got the radio upgraded but when I go to Fastboot to flash the hboot i get the (Failure: remote not allowed) error. So I can't change anything with the current hboot. I'm guessing I need a goldcard since I can't get to recovery mode, but every set of instructions for making a Goldcard requires the phone to be in adb shell mode which i can't get too.
At this point i don't care if i get the new radio on or not I just want it working again. I was running the SuperD 1.9.3 ROM with the Old radio...
The Blue LED issue wasn't me, I dont know who that is or what that was about.. I CAN still get to fastboot
Um, is that an engineering SPL? I believe you need one before doing this.
Did you try flashing the old radio again? Also, how did you upgrade your radio? Did you use Fastboot or Recovery?
If you can't flash anything.. well I dunno what else to do, never seen this problem yet. Maybe someone else with some more knowledge can help you, but try searching. I'm sure you're not the only one who's been through this situation.
Give this a try, I have no idea if it works though.
(Read this off unlockr)
Download the Hero Recovery Image
Put it in your androidsdk/tools folder
in fastboot, type
fastboot boot NameOfRecoveryImage.img
The only way i know how to change the Radio back is to Flash it through fastboot and this is the message i get when flashing anything through fastboot:
FAILED <remote: not allow>
The first time i changed the Radio to the new one I did it through recovery mode
I can't make it in to recovery mode anymore...
help?...
If you flash an engineering SPL you'll be able to continue. Flash 1.33.2010 and then continue from there. That happened to me too.
If you can read:
Prerequisites:
- HTC Magic / Sapphire 32A
- Engineering SPL
----- 1.33.2005
----- 1.33.2009
----- 1.33.2010
----- If you boot into fastboot and have issues with "fastboot:remote not allow", then your SPL won't work. Upgrade to Engineering SPL before continuing.
----- If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
- Working ADB/Fastboot Drivers
- Basic knowledge or modding your phone
Click to expand...
Click to collapse
This is the very top of the topic.
rquattro said:
If you flash an engineering SPL you'll be able to continue. Flash 1.33.2010 and then continue from there. That happened to me too.
If you can read:
This is the very top of the topic.
Click to expand...
Click to collapse
how do I flash it through recovery if I can't boot into recovery?
can your computer detect the device? can ADB detect it? Can you get into fastboot mode (Power+Back)? You could try to flash the engineer SPL (and the old radio) through command prompt:
Do it in this order:
Code:
fastboot flash radio Radio_HTC_PVT_32A_3.22.20.17.img
fastboot flash hboot hboot-1.33.2010.img
fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
fastboot erase system -w
fastboot reboot-bootloader
The files you'll need are all at this topic.
perhaps you missed the part about any fastboot command giving me a
FAILURE <remote: not allow> error
The one thing that gives me hope is that I get about 1-2 seconds of response from adb during boot up before it shuts down and starts the boot process again. If I knew how to run an update.zip from adb shell in one or two commmands maybe i have a chance at loading the old radio or engineering SPL or something. If I try to get to recovery mode it locks up after a second and I can't run the update through the menu...
??
fibofan said:
How does a card reader help me get the cid number off the phone? Don't i still need to get to adb mode to do that? which means booting the phone up which it won't do...
Click to expand...
Click to collapse
If you have fastboot, can't you fastboot boot recovery.img?
It's like a liveCD boot. Or maybe flash the old radio back on.
You did say you have fastboot, right?
HBoot mode?
fibofan said:
perhaps you missed the part about any fastboot command giving me a
FAILURE <remote: not allow> error
The one thing that gives me hope is that I get about 1-2 seconds of response from adb during boot up before it shuts down and starts the boot process again. If I knew how to run an update.zip from adb shell in one or two commmands maybe i have a chance at loading the old radio or engineering SPL or something. If I try to get to recovery mode it locks up after a second and I can't run the update through the menu...
Click to expand...
Click to collapse
Isn't there an HBoot mode that applies whatever is in an update.zip file? You may be able to recover your radio that way.
Windos or Lenox
i have bricked my mytouch the red screen of death VodaFone. i am trying the unbrick method (fastboot boot recover.img)
which some have said it works. would i have a better change of success on windows or lenox. cant
bricked mytouch1.0 with the new software 1.6 from htc gold card the vodafone sap.img because the usa was giving a version on device is older.
i was trying to change radio then spl looked like flash radio just fine went to the reboot then never came back from the vodafone screen.
cant fastboot and cant go to recovery
charging light just fine
Brick
ive came to the concluion that i did everything right it just bricked anyways. i think im going to send it to htc and see how much they will charge me
Hi
A friend gave me his htc magic because he crashed him.
he has already rooted his device
he put 2.1 rom and he decided to put another "fastest" and he crash his device
he told me that radio is bugged and his rom too.
I think with what i read on this forum that it's semi bricked because i can go to the Fastboot with pushing back and Power
When i put him on regulary i get Rogers screen then a Black screen.
What do you think about it ? bricked ? semi bricked ? Recoverable ?
here is a Video who show what happen when i press differents Buttoms
youtube.com/watch?v=MaSAh_8YK2E
Thanks
Need more exact details on which Magic it is. Can you read off the fastboot screen.
it's a 32A magic
The first version without jack 3.5
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0010 (SAPP10000)
CPLD-10
RADIO - 6.35.10.18
jan 14 2010
Hboot
fast boot mode
sim lock
Fastboot
Hboot mode
Reset device
restart to hboot
Reset
Hrm... new radio.
Assuming he already rooted the device, but didn't have a working rom for the radio combination, try one of the "New Radio" roms for 32A and see if it works (Can you get into recovery?)
Like t his 32A Port of OpenEclair for New Radios
http://forum.xda-developers.com/showthread.php?t=640105
If you can't get into recovery you may need to flash the 1.6.2H recovery image from here:
http://forum.xda-developers.com/showthread.php?t=530492
and if you can't flash recovery (due to the SPL being Perfected) and you want to try something from scratch (you may have downgrade the new radio back to 3.xx via this link http://forum.xda-developers.com/showthread.php?t=605239 )
You can try something like Cyanogenmod with this 32A Wiki Guide. (Though I *Think* you'll need to get a Engineering SPL to get rid of any Perfecting)
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32A_Firmware_to_CyanogenMod
ok thanks i'm gonna test =)
but now i have another probleme.
i cannot charge the htc magic don't know why ...
i try to solve that probleme to test to unbrick my phone
my problems seems to be Solve,
my battery is dead so i use my htc diamond battery.
can now test To unbrick the phone
And i had new from the old owner
he say me that
"The fastboot is Dead
Spl isn't good
Recovery is dead
And radio seem to don't work too"
hmm see i can't acces to the recovery mode how can i upgrade my radio ? ..
gluton said:
hmm see i can't acces to the recovery mode how can i upgrade my radio ? ..
Click to expand...
Click to collapse
You'll probably need to downgrade to an Engineering SPL for your phone if you are unable to do fastboot flash radio radio.img from the command line.
(I'd look more for you but I'm currently coding a website for a client).
i tryed to make the first part of http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32A_Firmware_to_CyanogenMod
"if it says 'Remote Not Allow' or similar, your SPL may need to be changed"
They are exactly say that in the commands prompt so i need to flash my Spl i'm actualy trying =)
and i think that i have to make a Gold card to flash my spl
Edit
I tryed to Downgrade my SPL with a tutorial in my language
"http://swissdroid.wordpress.com/2010/02/23/32a-changer-le-spl-ou-le-radio-de-votre-magic/"
And i cannot flash anything they alway say "sending 'xxx' <xxkb>... FAILED (remote: Not allow)
Ans i don't know how i could make a goldcard with a bricked phone.
So What can i do ? ..
The "remote not allowed" means the SPL is perfected. Perfected means that it's "Locked".
You have to make a gold card:
http://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
Once you have a gold card then you download a new SPL and put it onto the card (read instructions from there):
http://forum.xda-developers.com/showthread.php?p=4332591
Engineerings SPL v1.33.2010
Once you have an Engineering (prefered) or non-perfected SPL you'll be able to flash what you need without the 'remote not allowed' message.
But I must warn you, make sure you read the instructions several times before doing anything and verify that its for your exact device.
Thanks for you Help Kbeezie
I've got a probleme
my phone is reconize when i type fastboot devices
but when i write adb devices , it's found nothing so i can't go to the next step : /
Does i need a non bricked magic to make a gold card ?
gluton said:
Thanks for you Help Kbeezie
I've got a probleme
my phone is reconize when i type fastboot devices
but when i write adb devices , it's found nothing so i can't go to the next step : /
Does i need a non bricked magic to make a gold card ?
Click to expand...
Click to collapse
You can't do adb from fastboot, only from the recovery. If you flashed a new SPL (Engineering) You need to then flash the appropriate recovery/radio/hboot, then when you turn off the phone you press and hold down Home + Power to get into Recovery mode, once there then you can do adb, or you can mount the USB and copy over an update.zip or rom file.
Kind of hoping someone with experience on the older Magic/MyTouch (32B) chimes in.
Okay
but i can't flash recovery so
i need flash my Spl and i can't flash normaly my spl 'not allowed"
so i need to make a goldcard and i need use Adb commands so how can i make goldcard ? i don't understand ..
gluton said:
Okay
but i can't flash recovery so
i need flash my Spl and i can't flash normaly my spl 'not allowed"
so i need to make a goldcard and i need use Adb commands so how can i make goldcard ? i don't understand ..
Click to expand...
Click to collapse
The new SPL is placed on the goldcard, then you do volume down + power in order to Hboot, doing so will cause it to update the SPL package. You don't flash an SPL with fastboot command .
yes but i can't make the goldcard for flashing my SPL because i need to make adb commands so what can i do ? ..
I'm sorry i really don't understand :$
It mean that my magic is dead ? ..
How did you write your fastboot info if you cant access fastboot mode? I cant believe that someone could memorize every detail, including the exact list of options.
Its just that that SPL is a perfected one...you could try re-flashing it by using a goldcard via fastboot. Or try running RUU.
gluton said:
It mean that my magic is dead ? ..
Click to expand...
Click to collapse
As long as you can enter fastboot mode, its not bricked.
i have acces to my fastboot mode
But i have probleme with creating the goldcard to flash the SPL.
In the step to create goldcard i need tu use ADb commands to get my CID but i can't use them.
So how could i get my CID ?
And Kbeezie Told me that it's because it's in recovery that we can use those commands.
So how can i make the goldcard ?
That what i don't understand :$
Thanks for the help everyone
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.
My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?
The bootloader was already unlocked when I got the phone.
Thanks for this. I will test it and add it to my guide.
VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?
gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.
Okay, got it.
Too many things floating through the intertubes with similar filenames.
gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.
S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!
I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .
signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.
You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked
to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.