Need help flashing radio - Nexus One Q&A, Help & Troubleshooting

I flashed to EPE54B via fastboot and in cmd, both sending and writing said "OKAY". The bar on the top right of the phone also completed so I tried to reboot my phone into recovery so that I could flash the new cyanogenmod. Unfortunately, my phone has been stuck on the "X" boot screen (non-animated one with the lock) for an hour now. I have not restarted, removed the battery, unplugged the usb cable, or anything. Also, my computer popped up saying it could not find the drivers for "Qualcomm CDMA Technologies MSM".
Is my phone possibly bricked? Thank you.

iheartn1 said:
I flashed to EPE54B via fastboot and in cmd, both sending and writing said "OKAY". The bar on the top right of the phone also completed so I tried to reboot my phone into recovery so that I could flash the new cyanogenmod. Unfortunately, my phone has been stuck on the "X" boot screen (non-animated one with the lock) for an hour now. I have not restarted, removed the battery, unplugged the usb cable, or anything. Also, my computer popped up saying it could not find the drivers for "Qualcomm CDMA Technologies MSM".
Is my phone possibly bricked? Thank you.
Click to expand...
Click to collapse
no....
reset it (volume down and power button)
restore to your latest nandroid to make sure everything still works right...
now when you try your next flash do a wipe (factory default) first and then try flashing your radio and new rom if you have on
ive had trouble in the past with cyanogen's roms doing the boot loop on the "X screen" in the past so you are not alone... but your most likely error is doing a wipe after your nandroid... then install the new rom... see if that works

Related

Did I just brick my Hero? Help!

Some basic info about my phone-
HBOOT 1.47.0000
Radio 2.42.01.04.23
Carrier- iWireless (Kroger, Sprint subsidary)
S-ON
Alright, so I was just using my phone as normal. Running CM7.2 and ClockWorkMod Recovery. I turned off my phone, everything was fine. When I went to turn it on again, it showed the green HTC logo, as per normal, then it suddenly rebooted. There, it showed the green HTC logo again, and it'll just stay there. So I tried to boot into recovery (pulled the battery, put it back in, held the red end call button + volume down, got into hboot, then pressed home to go to recovery).
The thing is- it did the same thing. Reboot before it gets to recovery, and then stuck at the HTC Logo. I tried using the Sprint RUU, didn't work- it told me to download the right RUU for this phone, and gives me an error 131. I used the flashable RUU found in this thread (found here), in conjunction with this tutorial (found here). It gave me an error that looked like this when I ran "fastboot flash zip *flashable RUU zip path*"
Code:
FAILED (remote: 42 custom id check fail)
I believe it has something to do with the fact that it is NOT a Sprint branded phone. It doesn't even have a Google logo on the back.
Since it's not S-OFF, I can't flash a recovery via fastboot. I'm stuck. Help?
*TO CLARIFY*
I can't get into Recovery, or the actual system. I also can't access adb. The only part I can access is the bootloader and fastboot.
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
laie1472 said:
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
About 75% if I remember correctly. Only light usage. And I just turned it off in school, we were taking a test. Nothing abnormal about turning it off. And yes, several times. Tried flashing recovery/system/boot in every way possible, using that command and not using that command. I noticed something else- it seems like the NAND memory is completely wiped. There is NOTHING on the phone, other than the bootloader.
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
laie1472 said:
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes, I tried flashing multiple times. As I said, it fails with a CID check failure. And it doesn't seem that there's anything on the NAND anymore, as it doesn't even get to the boot logo, and recovery will just restart the phone.
My PC recognizes my phone, only in fastboot. And just normal bootloader info- model number, baseband, etc.

Stuck in boot loop (after upgrade to 5.1)

Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Revolution_09 said:
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Click to expand...
Click to collapse
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
alray said:
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
Click to expand...
Click to collapse
Thank you! Everything else went smoothly and I've flashed 5.1 now.

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk

How do I unbrick my unrooted HTC 626G?

(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
dulfried said:
(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
Click to expand...
Click to collapse
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
brokenbrain939 said:
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
Click to expand...
Click to collapse
Thanks a lot, I'm finally able to communicate with my phone via PC now. Booting still doesn't work but now I can at least format the storage and hopefully flash the factory ROM.

[FIXED] Fastboot? Recovery bootlooping, but never getting there

Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus

Categories

Resources