Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
I could really do with some help on this - Kinda paniking cos i'm afraid!
I posted it in the thread on modaco too, so hopefully I can get some help
I am on a 16gb Wifi Euoropean Flyer that needs the RUU RUU_Flyer_HTC_WWE_Wifi_2.27.1114.31_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204727_signed
I have downloaded all the necessary things, checked all the MD5 sums etc etc.
I have successfully gotten to step 14, where i successfully unlocked the bootloader with the HTC dev tools.
Once the gui option came on screen to say whether i wanted to unlock the bootloader, i selected yes, and instantly the device rebooted, but stayed on the white HTC logo screen.
It stayed like this for about 5 mins, before i held the power button down, restarted and got back to the bootloader. (It says unlocked at the top in pink)
I ran the adb command to flash the updated recovery image, (fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.hboot0011.img), and it said 'sending' okay and 'writing'okay but once i selected to go to recovery, the decive just stayed on the white splash screen, and i think it is in a bootloop.
I can successfully get back to the bootloader every time, and it is displayed as fastboot USB in red (i can hear the sound as it is connected to my machine), but when i type adb devices, it says device cannot be found.
I can however relock and then subsequently unlock the bootloader using the HTC dev tools, but still get stuck at this point. (when relocked it does say *security warning* as well as locked)
Please please please can somebody help, this would be much appreciated.
(I'm not sure if it is possible to place a recovery image on the SD card and let the bootloader install it as it does the checks at the start?)
Thanks in advance
You can't communicate via adb in fastboot menu
Get back to fastboot
Try to flash recovery again
Fastboot flash recovery "name of recovery file"
Fastboot and adb are two different things
If it fails again, delete the recovery image and redownload and try again
Sent from my HTC Flyer P510e using xda premium
I tired again, i unlocked the bootloader using HTC dev tools, starting through the process instead of using the same email file.
I think the problem is with the HTC dev unlock, cos when i press yes, it gets stuck on the HTC splash screen. (Just out of interest, what should happen when i select yes to unlock on the flyer?)
Flashed the re-downloaded recovery in fastboot (md5 sums match again), this is what was returned:
sending 'recovery' (4746 KB)...
OKAY [ 0.755s]
writing 'recovery'...
OKAY [ 0.612s]
finished. total time: 1.367s
then selected 'bootloader' on the flyer, then 'recovery' and then it still get stucks on the white splash screen.
I double checked all the mb5 sums of all the files i have flashed in this process, and they are all good.
The flyer will not turn off, it just turns itself back on again and again. The only way to make it stay off is to lock the bootloader again
Any reccomendations?
Thanks
I am not sure why the recovery is not flashing
You may want to OEM lock and revert back to gingerbread
Sent from my HTC Flyer P510e using xda premium
thanks, to do that, do i just run fastboot oem lock?
then run the RUU?
That should do it
Sent from my HTC Flyer P510e using xda premium
Phew! That did it, back to GB for now. Thanks ever so much!
Do you recon it is worth my while to try again? I would like to try HC...
I mean you were able to recover so you got that going for you. I am not sure what was causing your problem though.
Yeah, but its a strange one isnt it?
I've just tried to S-OFF with revolutionary, and it reboots to the bootloader, and then stops, with the cmd window just saying, waiting for fastboot..... - it'll stay like this forever untill i turn the device off.
I remember i had this problem the first time i S-OFFed, but cant quite remembver how i fixed it - could this problem be somehow related to the HC install problem?
Maybe try another USB port or uninstall reinstall drivers
how long did you give the htc screen? it may take a lil while for recovery to start. id maybe give it as long as 5 minutes just to make 100% sure its really stuck.
if you wrote the recovery with the unlocked bootloader,im not sure why it wouldnt have worked,other than a bad imagea not compatible image,or possibly a simple fail to start. ive had this happen with TWRP recovery on other devices,and occasionally with clockwork-when booting to recovery it just sticks at the htc screen.
go for it again. assuming youre using all the correct,newest,and matching files,theres no reason it shouldnt work.
if you have the same trouble next time, while the on the white htc screen,when trying to get to recovery,try typing "adb devices" in your command window. if you get your serial number back, try "adb reboot recovery" and see if it starts that time.
the bootloop after unlocking the HC hboot is because that hboot and boot images are not compatible with the GB /system that is still currently on the phone. i was able to "adb reboot bootloader" during the bootloop rather than holding the power button to get back to fastboot so i could flash the recovery.
the *security warning* when you relocked it is becuase the hboot is confused about the firmware that doesnt match it.
hope that helps IMO its worth trying again- honeycomb makes the tablet alot nicer(for me anyway) than gingerbread.
Yeah I left it for at least 10 minutes, and no activity at all, other than the splash screen.
I might give it a go again, I'll report back as to how it goes!
Sent from my HTC Sensation Z710e using XDA App
send me a pm/email if you want me to take a teamviewer look if you get stuck again.
I have searched and searched and searched.....nothing seems to work.....
I was messing around with my phone (latest update and rooted). I was messing with rom toolbox and was trying to change the theme...
Bottom line, phone is stuck on the M screen (dual core screen)
I tried to do a hard reset but it didnt work... Just goes back to the same screen.
any ideas are greatly appreciated!!!!
Thank you in advance
Is your bootloader unlocked? Do you have CWM installed by any chance?...
Sent from my MB860 using XDA Premium App
nope neither
from what you've said it would appear that you've changed something whilst in rom toolbox and as such it won't boot up.
You say you've got the latest update and I am wondering if this means your bootloader is locked now? When did you update your phone? when you start up the phone are you able to get in recovery? (volume down when starting up).
Anything I could suggest is going to be full of dangers (sbf flash for one).
Barry, the phone was updated a few weeks ago. I believe it was running 2.3.6
Any thing that can be done like sbf i am willing to give a try....and yes i messed up in rom toolbox
Soft Bricked my phone
I did the same to my phone as well. I had updated my phone from neutrino 2.7 to 2.8 through CWM. When I booted up for the first time, it worked fine but when I did a factory reset through neutrino, it booted up and then got stuck on the boot screen.
The phone was unlocked and rooted but for some reason usb is not being recognized in the pc, CWM is not loading up and RSD lite wont recognize phone because it is not running Blur. I tried using various commands on fastboot and adb such as fastboot devices and adb device but I dont get anything back..the device seems to stuck in perpetual bootloop. I can get into fastboot and RSd but it is stuck on starting fastboot protocol suppor..
The one bright spot is that LED comes on when i plug in USB without battery meaning the phone is being charged by USB just not being recognized. I tried installing all the drivers and reinstalling them but I usually get a device error on computer which is a 64 bit Windows 7.
I think I am F#Cked..can somebody help me..
theoretically, since I can get into fastboot cant I just go to recovery and wipe the data and then install a update from the SD card?
I would just need to unlock the bootloader right?
it was running the 4.5.141 update.
I can get RSD to show up on the phone and it does connect to the computer.....
FastBoot does connect to the computer
jpimaging817 said:
theoretically, since I can get into fastboot cant I just go to recovery and wipe the data and then install a update from the SD card?
I would just need to unlock the bootloader right?
it was running the 4.5.141 update.
I can get RSD to show up on the phone and it does connect to the computer.....
FastBoot does connect to the computer
Click to expand...
Click to collapse
why not give it a try? if it does not work, flash the 4.5.141 update via RSD Lite, if you get into bootloop, push clockwork recovery via fastboot, then boot into recovery wipe cache, wipe davlik cache, wipe data/factory reset, then reboot. if you really can't get it to work you can send it to me so I can try fix it, that is if you would trust me. Just pay for return shipping, you can use usps flat rate box with signature confirmation so you'll know i have received it. I have previously helped a guy in Dell Streak Forum and I have lots of positive feedback in XDA Market place, i just love helping other out, flashing ROMs and fixing broken/bricked phones. Just PM me if you are interested.
I have made progress!
I have managed to unlock the bootloader with the following
http://forum.xda-developers.com/showthread.php?t=1182871
I am still stuck on the same M screen still, it just says unlocked now.....
Where do I go from here?
Looks like all I need to do now is find a way to get the rom onto the sd card so that I can flash it with clock work recovery.....
I tried to mount my external 2 gig card and do it that way but it didnt work....
Any other ideas?
As the subject heading says, I am trying to fix a phone for a friend that is stuck in an infinite white screen HTC logo loop boot.
Background: I'm able to pull the battery and then go into the bootloader. I have tried going into the stock recovery to no avail. I have performed the "Image CRC" and "Factory Reset" several times, eventually I was able to get into the device and it worked, but once I restarted it (thinking it was fixed and testing it) it's back to the same state again. I can't get it to communicate with my PC or MAC to do anything with it through ADB. I've been able to get in and completed booted twice now but cannot get in anymore. Both times I hadn't been able to do anything with it except for "Image CRC" and "Factory Reset" because I wasn't near a computer at the time.
I pulled the SD card out so that factor is eliminated
What options are there left? Any suggestions?
No ideas?
I'm gonna download the .19 RUU and try it, as well as the .05 ruu
If its not rooted an still under warranty take it to verizon. If it is rooted,unlocked and s off then try downloading the most recent stock ruu and fastboot flash it.
Sent from my ADR6400L using Tapatalk 2
Sorry, I didn't include that information.
It's not rooted, possibly not under warranty (not sure yet), it's still S-ON.
Part of the problem is the fact I can't get into the recovery either, when I go to do so, it just loop boots again. This phone was never rooted or even attempted to be rooted before I got it so it's not from any causes like that. It's just a simple issue of loop booting and I wanted to try to attempt to root it as well as fix it.
Is it bricked? It occasionally boots in completely but when I went to turn on debugging mode it rebooted again and is now looping again.
At any point were you able to distinguish what software it is running ? .9 or .19. Maybe it tied to download the new software which is .19 and didn't complete. Jast throwing out some ideas.
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1703455
The HTC tool I was referring too
Sent from my ADR6400L using xda premium
Yeah, it's running .19, and I tried flashing the RUU for .19. I tried that tool but it never was able to connect because I can't get it passed the HTC boot and when it recently finally got fully booted and I went to enable USB debugging it rebooted on me and is now still loop booting lol.
I personally have the EVO 3D and have a MAC and PC and have tried having ADB detect the phone and it doesn't. My only guaranteed way to get it from doing anything other than looping is going into the bootloader or HBOOT. If I try the recovery it loops and then normal boot also loops
EDIT: oh and I also have installed a new SD card and formatted it.
any other ideas?
http://forum.xda-developers.com/showthread.php?p=27078714 I linked to another thread with revolutionary hboot drivers, if you need them.
I'm trying to find the stock recovery for you too, maybe you can get that to flash in bootloader
from my ADR6400L using xda premium
http://db.tt/cIqxle9q
Link to stock recovery. Rename to PG05IMG.zip and see if it will flash.
from my ADR6400L using xda premium
It's having a moment of clarity again! lol
I left it alone sitting on the charger for like an hour and went to check it and it was booted up completely. I'm trying to root it with revolutionary but I'm having a driver issue I believe now.
Check the link above with the revolutionary hboot driver download. I had the same issue with it saying "waiting for device.". I installed those drivers, restarted revolutionary and it found it and rooted and s-off with no problem.
Sent from my ADR6400L using xda premium
I spoke too soon, I plugged it into the MAC and it auto-rebooted again and now it's loop booting again.
Here's a few pictures I took when it was working for those few minutes lol.
http://imageshack.us/g/84/imag1246.jpg/
I'm gonna try that stock recovery zip and see if I can let it sit on the charger again (it's a radioshack cig lighter socket adapter with a cig lighter generic charger that matches the .7A from the original instead of charging off USB) to see if it'll go through again
Yeah, same problem. Whenever I plug it into the computer after installing the HTC ADB drivers it just automatically restarts, regardless of which computer (PC or Mac).
It sounds like a physical defect that I'm not going to be able to circumvent.
incarceration said:
Yeah, same problem. Whenever I plug it into the computer after installing the HTC ADB drivers it just automatically restarts, regardless of which computer (PC or Mac).
It sounds like a physical defect that I'm not going to be able to circumvent.
Click to expand...
Click to collapse
That's what i was thinking
Agreed. May not be fixable unfortunately.
sent from above
Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again