Hello everyone,
Long time reader for time poster. I have this device that is stumping me, and I was hoping with your help I can get to the bottom of its issue.
i am not going to describe everything that I had done as that would take pages and pages, but there is one aspect that I feel might be the crux of the problem so I will start with that and see if it leads us anywhere.
Basically this device was working, sat in a drawer for a while, the battery dried up, and since it wasn't able to boot into android, it always gets stuck at the htc logo screen.
I have tried flashing it using the sd card method, with the newest corresponding zip that I could find, it started doing its thing, then at some point restarted, got stuck again, and I ended up with an unknown radio and dsp (looking at the infos in download/recovery modes)
I don't know the history of the device, but i don't believe usb debugging or oem unlocking were turned on. and obviously I can't check or modify them as I can't get into the device. and it is currently locked and S ON.
Currently, I can boot into recovery/download no problem:
- I can easily detect and interact with the phone through fastboot, but not through adb.
- clearing cache and factory resetting go through fine, no errors, but again after restarting the device it gets stuck at the htc logo.
- if I try to flash through the SD card, it starts normally, then restarts and gets stuck at the htc logo.
- if I try to flash anything through fastboot, I get an error telling me the device is still locked, which it is.
- if I try unlocking using fastboot (following the official htc method), once again it starts normally, but then restarts and gets stuck at the htc logo again.
Correct me if I am wrong, but it feels to me like this is a software issue, that for the hell of me I can't seem to be able to get around.
I tried to keep the post simple, so if any additional information is needed, or tests you'd want me to run please don't hesitate to ask.
Thank you for your help, much appreciated!
Hello again, just a little bump. As I am stuck and any ideas would help.
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.
Hey all.
i tried to flash the 2.22.23.02 radio.
after doing so, the phone loads the Rogers screen, stays there for some time, and then reboots, loading the rogers screen again. this continues indefinitely.
i can no longer access the recovery screen (power+home) or the fastboot screen (power+back).
i have searched for a possible solution, to no avail.
is the phone bricked ? is there any way out of this ?
any help would be greatly appreciated.
- Yaniv.
Have you tried removing battery and hold home button when inserting it again?
yes, i have removed the battery and tried booting into either fastboot or recovery. No luck. as before, it only shows the rogers screen.
i suspect the radio installation was compromised. the battery may have been removed part way through the installation, or the radio file itself may have been corrupt. is there any way to recover from that ?
- Yaniv.
same here, i bricked my phone today when trying to flash 2.22.23.02 The boot-logo has stuck and I can't do anything.
Anyone got a solution? I tried almost everything I found on the internet. I just can't access recovery/fastboot mode.
Everytime i try to connect my phone with USB it says < waiting for device > although it's properly connected.
b4b4j4g4 said:
same here, i bricked my phone today when trying to flash 2.22.23.02 The boot-logo has stuck and I can't do anything.
Anyone got a solution? I tried almost everything I found on the internet. I just can't access recovery/fastboot mode.
Everytime i try to connect my phone with USB it says < waiting for device > although it's properly connected.
Click to expand...
Click to collapse
apparently keep inserting your usb cable and it should pick up. linux ubuntu with adb tools quicker apparently too.
what steps did yo take to get it to wait for devices.
if you stilll have power light light then you should be able to push recovery at some point, but keep trying for 15 mins or so
Hi there. I would appreciate your help here. I am a rookie with android software as I own an HTC Magic almost 3 weeks from now. My phone has the above characteristics:
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0009 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Dec 8 2009, 17:38:48
The software I had was Android 1.5 and it was rooted with RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver ROM. I was watching on Youtube some videos about CyanogenMod 6 at HTC phones and I decided to try to put this software to my phone via ROM Manager. The result is a major disaster (or not?). Specifically, from my phone I opened ROM Manager, download rom, CyanogenMod nightlies , CM6 XXXXXXXX (can’t remember which one) EBI1 Kernel… So I had successfully downloaded it and followed the instructions while installing. After installation completed it automatically rebooted and started loop again and again. All it gets to is the "HTC MAGIC" screen and then reboots every 5 seconds. At the begging I thought that this is the installation process. 30 minutes later I had a doubt for this. I pulled out the battery cause pressing the Power on/off button nothing happened. I tried everything… nothing at all. I pressed the Power on/off button again it continued looping. After I pulled out and inserted the battery I pressed the Home and Power on/off button (Android recovery) it still continued looping. Removed again the battery and inserting again while pressing Back and Power on/off button (fastboot ) it still continued looping. I pressed Home and Back buttons and tapped Power on/off button… the same issue (continued looping). Down volume and Power on/off button… nothing. Up volume and Power on/off button… nada. Pulled out the battery for 30 minutes and tried again… nothing again. Tried again and again with the USB connected and disconnected… nothing. Still looping. I tried to install the previous Rom I had via PC but I couldn’t cause USB was connecting and disconnecting because of the rapid (5 second) boot loop. The only button which seems to work is the trackball which freezes everything with the blue led on and a black screen between the loops. I pressed all the buttons together wishing something to happen… unfortunately nothing happened. I backup my SD card and tried with an older backup I had… nothing… boot loop remains. I am despaired and tired (almost 18 hours online searching some help or solution). The only thing I want is to make fastboot work and install my old ROM via my PC… nothing else.
Please, please, please…. HELP ME!!!
well this is a pain. Your fastboot is also locked. You should read instructions and learn a bit before just flashing whatever you please. CM6 requires old radio and a different SPL. The one you're using isn't compatible, hence the reboots. You also can't get into recovery because your radio and recovery are also not compatible. I'm assuming that rom manager did that? I'm not sure, all you new people are just running that thing and flashing away without any knowledge behind it.
I don't think you're bricked but I'm not 100% sure what to do since I've kept my bootloader unlocked to run fastboot commands (which would easily solve this situation). My suggestion is to get an RUU for your phone, update and then reroot it. Maybe someone else has a better solution but right now you don't have the right recovery and fastboot is locked. At the moment, I can't think of a better solution.
edit: ugh it's late and im sleepy! i just reread what you said, you can't get into fastboot either? If not you're probably bricked
yup, I totally agree: I remember the first time I flashed a rom over the stock version which was installed. I read every sticky thread, the whole wiki page and lots of xda threads before giving flashing a try. It's just too risky to mess up an expensive phone. Just look at all the "bricked my phone, please help" threads, that alone should make one think twice (and read, read, read) before flashing...
I hope someone can still help you. But not getting into fastboot anymore?! :-(
Sorry and good luck,
V.
Sent from my HTC Magic using Tapatalk
Thanks gyes for your replies. Still I can't find a solution. The only thing I can barelly see before it boots again by pressing Back button and On/Off button is ClockworkMod Recovery v2.5.0.1.
As about the mistakes I admit that this is my fault but also I have to say that before I root my HTC I couldn't download anything from ROM Manager. After I had succesfully rooted my phone and downloaded the ROM update from my phone there was no mention about radio issues or conflicts in the installtion proccess. Even though it is my fault and I admit it. I don't mind if I loose my data (I made an SD buck up). I just want to find a way to stop this stuppid loop, make a USB connection with my PC and install my previous ROM even if I have to screw out my phone.
as I'm not able to help you myself (I'm just a user not a developer) I can only recommend checking the "bricked phone" threads for solutions. I think I saw an "how to unbrick phone" thread somewhere. Never read it though. Probably there are many others who messed up their phone somehow and lots of solutions in all those threads. Just use the search feature and look for brick threads, solutions, help, etc. Maybe you'll find something.
Sry that I can't offer more,
Greetz,
V.
It's ok my friend... Thanx 4 replying
i don't know if it's related but a guy had a bad flash and had a blue trackball toom, which you mention in first post, here is his thread on what he did to fix his phone http://forum.xda-developers.com/showthread.php?t=649689&highlight=unbrick
Nope... Nothing helpfull unfortunately! Thanx anyway
A new clue is that I left my HTC magic to boot loop while the usb cable was connected with my PC dinging in and out while rebooting and after 10 minutes it stoped rebooting (it happened one's more yesterday). No button combination is responding (the trackball also) even if I keep pressing them over a minute continuesly. Also no led is lighting even if it is on USB connection. I ashume that if I remove and putt back the battery it will start again the boot loop as it happened yesterday. So I will leave it as it is and try later to restart...
Nothing... Started boot loop again
Today I gave my Magic to HTC Service. It was confirmed that the electronic circuit was "dead" and it had to be replaced. If I'm lucky maybe I wont pay a dime. It depends if the software I had on was Android compadible or not. If not then... better not think about it!
Solved!
Please buy hyelton a beer or a damn new phone. He's a hero.
This worked: http://forum.xda-developers.com/showthread.php?t=2432476&highlight=decrypt
Hey guys, but of an emergency here...
I'm stuck at the LG logo after flashing the Pacman ROM with the latest unofficial CWM, and it seems to have failed at Formatting system. All four touch buttons on the bottom were blue, as if they had been pressed and highlighted. No response from anything.
Reboot. Then it got stuck on the LG logo. I can't access CWM anymore, holding power + vol down does nothing, I just go back to the logo. I'm running a D802.
This was a pretty standard flash for me, I have done this many times, so I was confident in it, but now have no way back into a phone I desperately need within hours.
Process went as follows;
Full wipe, format, initialize install, it failed/crashed/whatever, rebooted, now stuck on logo, unable to access CWM, and obviously unable to access ROM.
USB Debugging was on, but as the ROM doesn't exist anymore, not sure how much help that'll be.
I'll gladly go back to either CWM or TWRP, as well as stock ROM or whatever. I can sort all that out later, right now just need things back in running order.
Edit1: I can't even turn it off. It simply boots up again, so now also worried of damaging display or battery.
Edit2: It's not showing after entering "adb devices". List is empty.
ANY help appreciated.
I'm running Windows 8, and no, I will not be able to reinstall to W7 or Ubuntu.
Thank you
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911