I was rooting my phone last night and was successful. When trying to load a Cayanogen rom, it wouldn't get past the "Vodafone" splash screen. I noticed I did not have the proper radio installed, so, I installed the radio for Android 1.5 from the website.
Now, it is stuck in the red vodafone splash screen, and won't let me enter fastboot, bootloader, or recovery.
So, am I screwed, or is there a way I can fix this? I honestly searched for a VERY long time, and could not come up with much help.
Thanks. Also, I am using this on AT&T and it is unlocked.
if you can enter fastboot or recovery or anything than its not looking good, have you taken the battery out for a while and tried fastboot again?
I'll try leaving the battery out for a little while and try again. I just let it sit on the splash screen for about 15 minutes with no luck.
Left the battery out for 20 minutes, put it back in, tried to enter bootloader/fastboot/recovery, still with no luck.
Any other suggestions? I literally just bought this phone last week!
Also, since I am on at&t and this is a T-Mobile phone, and it is bricked, is there any way I would be able to send it in for a warranty replacement? I have no receipt of the original purchase, but still have the original packaging.
Related
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
My myTouch won't boot into recovery, fastboot, hboot, nothing. Just shows a splash screen and nothing else happens. I can't get the SDK to recognize that the phone is plugged into USB and load recovery that way, either. I've tried damn near everything I could find on these forums, with still no dice. Someone suggested I reflash the sappimg, but how can I, when I can't even load recovery or fastboot in the first place?
sorry but you've bricked your phone once you can't get into fastboot your phone is good as dead. happened to me as well but I was lucky get a new phone after warranty.
They've already sent out a replacement, but when they get my old one, can they charge me for the replacement if they find out what I did?
they wont be able to tell, unless you tell them. I did the same thing to my G1, and it just stayed at the "Tmobile G1" screen, nothing else. I told them it happened while doing the OTA software update.. no questions asked.
Awesome. I kinda figured that if they couldn't get past the splash screen, there was no way they could tell. Good to know, since I added the extra $2/month for extended warranty, so if I ever brick it again like this I can exchange it again. Ha HA!
Hi guys, something strange happened, got my nexus 3 weeks ago and i right away unlocked bootloader, flashed custom recovery and rooted it, installed a few apps and everything was fine, day before yesterday while sending an email my phone got stuck and rebooted, took awhile and when it did i noticed the cell network being empty, i would press anything on the screen and it would do the same. So i downloaded the stock images and flashed everything according to section D of the topic http://forum.xda-developers.com/show....php?t=2010312 and boot took awhile finally it started and i got the welcome screen, clicked on English USA and again the cell network is empty and phone frooze in the first screen only, it rebooted and it boots up with a black screen and i get the message "process system isn't responding, OK or wait" and press ok or wait whichever and phone reboot or even if i try to press any of the options, its stuck. But bootloader works since i can do fastboot devices or fastboot reboot-bootloader, i can also boot into recovery which is CMW. This is getting frustrating and im confused, can anyone help me out here? Thanks
RMA time. Relock the bootloader and ship her off. If reloading the stock images doesn't fix it, it's likely hardware.
estallings15 said:
RMA time. Relock the bootloader and ship her off. If reloading the stock images doesn't fix it, it's likely hardware.
Click to expand...
Click to collapse
Isn't there anything else i can try before shipping it back or give up?
EDIT:
I pushed CM zip file via adb and it got pushed successfully and i even flashed it via CMW recovery and it even said complete and when i reboot the device its stuck on the Google screen and nothing else happens..
masantula said:
Isn't there anything else i can try before shipping it back or give up?
Click to expand...
Click to collapse
Gong back to all stock software with fresh flashes is the most extreme attempt at a fix, software wise. What else would you do?
Hmmm, true...this sucks, no other option...thanks
Need help, going to try and give as much detail as possible so sorry for the long post. I dropped my phone a few weeks ago and the LCD broke so got a refurb warrenty replacement phone. Att S4 - got it 12/24 and rooted using towelroot on NJ4. Everything was fine until sunday or monday when I realized my Beautiful Widget weather was still stuck in NJ where i had been a few days ago and the last time I'd turned locations on, thinking location was still just GPS like it used to be. read up on all the location info of power saver vs full accuracy, and decided I would just set my widget to my home zip code. Within 24 hours i started experiencing random reboots of the phone, with the occasional boot loop. tried turning the location settings back off and that helped for about a day before starting having reboot / power off issues again.
So last night I decided I would give up and try and do a factory reset. First i wiped the cache from stock recovery. Then the phone wouldn't boot past the att screen at best. So I went back into stock recovery and did a full reset. at this point the phone will no longer get past the Custom Samsung boot animation. I tried using the one-click unbrick tool, but my phone wasn't coming up as a USB option and I haven't been able to find any additional trouble shooting to get that to work.
So next I decided to Odin the stock unrooted firmware, which i believe was NB1. Now i can't get the phone into recovery at all. It is hit or miss if the phone will even get to the custom boot animation, but immediately shuts down from there. I can still get into download mode at times. Wondering if there may be a hardware issue either my battery (which was from my original phone) or the power button on the refurb because there were points last night when i would have to hit/hold the power button 5 or 6 times before the phone would do anything, regardless of what other buttons i was or wasn't holding down. that seemed to improve once the phone cooled down for a while.
I really have no idea what else to do. Based on everything i've read the phone should be working at this point or should be totally bricked. any guidance is greatly appreciated. I would try and just warranty it again and claim they sent a bad phone but of course it boots just enough to show the custom animation, even after i odin'd on stock. HELP!!!
dingbat005 said:
Need help, going to try and give as much detail as possible so sorry for the long post. I dropped my phone a few weeks ago and the LCD broke so got a refurb warrenty replacement phone. Att S4 - got it 12/24 and rooted using towelroot on NJ4. Everything was fine until sunday or monday when I realized my Beautiful Widget weather was still stuck in NJ where i had been a few days ago and the last time I'd turned locations on, thinking location was still just GPS like it used to be. read up on all the location info of power saver vs full accuracy, and decided I would just set my widget to my home zip code. Within 24 hours i started experiencing random reboots of the phone, with the occasional boot loop. tried turning the location settings back off and that helped for about a day before starting having reboot / power off issues again.
So last night I decided I would give up and try and do a factory reset. First i wiped the cache from stock recovery. Then the phone wouldn't boot past the att screen at best. So I went back into stock recovery and did a full reset. at this point the phone will no longer get past the Custom Samsung boot animation. I tried using the one-click unbrick tool, but my phone wasn't coming up as a USB option and I haven't been able to find any additional trouble shooting to get that to work.
So next I decided to Odin the stock unrooted firmware, which i believe was NB1. Now i can't get the phone into recovery at all. It is hit or miss if the phone will even get to the custom boot animation, but immediately shuts down from there. I can still get into download mode at times. Wondering if there may be a hardware issue either my battery (which was from my original phone) or the power button on the refurb because there were points last night when i would have to hit/hold the power button 5 or 6 times before the phone would do anything, regardless of what other buttons i was or wasn't holding down. that seemed to improve once the phone cooled down for a while.
I really have no idea what else to do. Based on everything i've read the phone should be working at this point or should be totally bricked. any guidance is greatly appreciated. I would try and just warranty it again and claim they sent a bad phone but of course it boots just enough to show the custom animation, even after i odin'd on stock. HELP!!!
Click to expand...
Click to collapse
Odin back to NJ4 :/ You can boot into download mode so that means your phone isn't hard bricked. If that doesn't work than I think I'll have another idea. Oh, by the way, what ODIN version are you using? If its 3.09 put the .tar in the AP section and for 3.07 and below its PDA. Also, make sure it's the correct image. Anything below NB1 doesn't work for KitKat users.
Sent from my SGH-I337 using XDA Free mobile app
My phone decided to hide in my pocket one day while I went swimming. Actually I forgot it was there. 30 minutes later I realize it's there and get it out of the water. I turn it off immediately. Take it to a drying station. When I get it back it turned on for a bit, then shut back down and went into a boot loop. So I restarted it into recovery mode and tried to reload the is, but my boot loader is locked.
My main question is,
How can I unlock the boot loader through the recovery menu. Adb won't do anything until that's done. I've tried Google, I've also read through the first couple pages on here.
I forgot to mention, I did send it back in to oneplus to see what they could do, they told me I'd need 5 or 6 new parts due to water damage. I wonder if I never told them it was water damaged, if they'd still come to that conclusion. The phone boots into recovery. I can navigate through the menus.
cfoster16 said:
My phone decided to hide in my pocket one day while I went swimming. Actually I forgot it was there. 30 minutes later I realize it's there and get it out of the water. I turn it off immediately. Take it to a drying station. When I get it back it turned on for a bit, then shut back down and went into a boot loop. So I restarted it into recovery mode and tried to reload the is, but my boot loader is locked.
My main question is,
How can I unlock the boot loader through the recovery menu. Adb won't do anything until that's done. I've tried Google, I've also read through the first couple pages on here.
I forgot to mention, I did send it back in to oneplus to see what they could do, they told me I'd need 5 or 6 new parts due to water damage. I wonder if I never told them it was water damaged, if they'd still come to that conclusion. The phone boots into recovery. I can navigate through the menus.
Click to expand...
Click to collapse
Water damage can easily indicated when opening the device cause there are indicators like stickers that will be changing color to read when they come in contact with extreme moisture or water.
There's nothing you can do until they repaired the parts.
What help do you want now, it's to late imo
Thank you for the reply. I have the phone back un-repaired. It's still in a boot loop and I can still boot o recovery and see it in adb, but it won't transfer the files with the bootloader locked.
The help I'm asking for is, is there a way to unlock the boot loader without an OS being on the phone? if so, how?
cfoster16 said:
Thank you for the reply. I have the phone back un-repaired. It's still in a boot loop and I can still boot o recovery and see it in adb, but it won't transfer the files with the bootloader locked.
The help I'm asking for is, is there a way to unlock the boot loader without an OS being on the phone? if so, how?
Click to expand...
Click to collapse
Not possible. You need to allow oem unlock.
You could try this:
https://www.google.ca/amp/s/forum.x...uide-unbrick-guide-hard-bricked-t3761706/amp/
It should work for almost any state. I haven't had the need to use it yet, but let me know if it works for you.
Cheers! ?