Related
Hello XDA-Developers. Long time lurker, first time poster. After watching the "Noob" video, I feel compelled to apologize in advance for needing to call on your greater experience and knowledge.
The specs (If there's anything left out that you might need, let me know. If I can get to it, I'll post it):
Model: Samsung/Google Nexus S GT-i9020A
Bootloader Ver: I9020XXKA3
Baseband Ver: I9020UCKD1
Carrier: Bootloader says ATT, my actual carrier is Telus.
ROM: Cyanogenmod 7.1 RC1 Experimental
Kernel: Netarchy's Nexus S CFS 1.3.6 Stable
CWM Ver: 3.0.2.4
The problem:
I've been running CM7 for the last couple of months (since I got the phone). I woke my phone, opened the Market, and it suddenly went into a boot loop; not from the beginning Google logo though, just the Nexus S boot screen, and very laggy. I let it try to boot for a while, and did a battery pull when it was (to my apparently idiotic mind) obviously not going to. Put the battery back in and it just sat there on the Google logo for a good half hour.
Here's where things get a little curious. I pulled the battery again, and PWR+VOL UP to get to the bootloader. Load up CWM, and lo and behold, I can't mount the internal SD or the DATA partition. Thus, I can't restore, can't flash anything new, and I've got a phone good for a whole lot of nothing.
What I've done so far:
I've spent the last 9 (yes, nine.) hours searching the internet with increasingly more vague and unrelated search terms. The best solution I've found so far: "Take out the SD card, pull everything off of it and format it. Put it back in to the phone, and presto!" A caveat that you all know: The Nexus S has no removable SD card.
One of the first things I tried, having only fastboot at my disposal, has turned out to be the worst thing I could have possibly done. I tried locking then unlocking the bootloader again, to wipe everything and start from an empty phone. Well, the boot loader won't unlock again. Fastboot sees my Nexus S, fastboot oem unlock yields the familiar "Unlock Bootloader?" screen, and when I select Yes.... Nothing happens. The phone stops responding, the command prompt sits there with "c:\fastboot-path>fastboot oem unlock ..."
Now, the solution to this, according to some, is to wait long enough and do a battery pull to finish unlocking the bootloader. This has yielded no results. Further research indicates that the internal storage may have some kind of hardware problem, a known issue with the Nexus S. Being forced to look at sending the phone in for repairs, I've become a little desperate. I need to removed the CWM somehow. I've got the stock recovery.img, but I'm stuck with a locked bootloader. I did a lot of research into using ODIN to recover the phone back to stock, but I can't get the phone into Download Mode. Using the VOL UP+DOWN then plugging it into USB throws me directly into the screen asking me to unlock my bootloader... except there's no way to say yes or no.
At this point, I'm seriously panicking. This is my only phone, and I'm really quite broke. I can't afford to pay for repairs if they find the phone is out of their ridiculously strict warranty. I can't afford to be without a way to get a hold of me when I'm not standing next to my fiancée or staring at my GMail inbox... Quite literally, my job depends on this phone.
Help me XDA-Developers... You're my only hope.
Update: Odin seems to detect the phone even though it doesn't say download mode, BUT the part of the recovery that writes data fails, and it just hangs. I can't restore using that either, I guess.
Update 2: Forgot to mention, the "Download Mode" screen looks like the unlock bootloader prompt (the green title and the first three paragraphs), and under that it has "USB Control Init//USB Control Init End". When I run Odin, the words "Verify Image (IPBL) ... Success" appear in read above the USB Control Init message. It's at this point it hangs and does nothing for over an hour. After a battery pull, the message "Complete(Write) operation failed." comes up in Odin.
Is there anything I can do here?
sorry im just heading to bed so this is more of a reminder for me to post tomorrow but
what does it say when you try and mount the sd in clockwork? have to tried taking a logcat?
don't panic.
CWM Mount /sdcard returns the error "Error mounting /sdcard!". The same goes for /system and /data.
As far as a logcat goes, fastboot sees the Nexus S, but the ADB shell does not. Sits at "waiting for device" indefinitely if I try at the bootloader. If I try in CWM Recovery, it returns the error: "/shbin/sh: exec: line 1: logcat: not found".
Something must have happened to my /boot partition as well. Doesn't hang at the Google logo anymore, just dumps me back into the bootloader, with a message at the top saying "FASTBOOT MODE - NO BOOT OR RECOVERY IMG". Given that the CWM recovery is still there, I have no idea what's going on with that one.
I am not sure but I think that you are not in the Download Mode. You should see big "Download mode" text on your screen. And you can't boot your phone because you wiped it already with the unlock command therefore the message - no boot no recovery. ADB doesn't work in bootloader.
Question - when you boot into bootloader does it says locked or unlocked? I think that your NAND memory is corrupted, flashing with ODIN could help but you need to see the "Download mode" text in order to flash with ODIN.
My bootloader is currently locked, which is turning out to be a real headache. I can't get the "fastboot oem unlock" command to complete. As I type this, I let the command run for ~15250 seconds (yes, 15 thousand) and did a battery pull, given no indication that it had completed.
Does your Download mode look like this? If yes, that is right. Have you also checked that your Device is recognized from Windows and that the drivers for the download mode are installed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@brainmaster: The drivers seem to be installed properly. "fastboot devices" shows the proper serial. My "Download Mode" does NOT look like that. I'll post a picture as soon as I can. The best way to describe the screen I get when doing the "VOL UP+DOWN" button combination while plugging in the USB is the top half of the screen is the first three paragraphs of the "Unlock Bootloader?" prompt, and the bottom half is the bottom part of the bootloader screen.
It's the only method (other than a 301K resistor on a micro-USB) that I've found to get the Nexus S into download mode. Is there another way?
As an aside, are there different drivers for Download Mode? My phone shows up as "Android 1.0" when using fastboot or the screen that's supposedly "Download Mode", and from when I first rooted the phone, I know it shows up as "Nexus S" when plugged in and actually booted into a ROM. I've applied the Samsung ADB interface drivers to those, and the fastboot works. Obviously I can't check the ADB shell right now.
That is the thing - you are not in the Download mode. If you wore then you will see "Samsung CDMA Modem Device" installed (that is for mine although its GSM device).
And the Download mode should look like that photo with two additional text lines.
I think that its bricked, sorry.
You could pull out battery and let it so for at least 5 minutes, and then try the Download mode - you are doing it right: Vol Down + Vol Up (When the Phone is off) and then plug the USB Cable in the PC.
Thanks for the replies, brainmaster.
Is there a way of completely bricking the phone at this point? I'm trying to figure out a way that the phone will appear to still be under warranty. The only issue is the CWM: if I could get rid of that somehow, then I'd be golden to send this sucker in for repairs.
Only problem is my bootloader's locked.
Don't take 100% for sure, but I think that you already wiped the CWM, since there is no boot image then there is also no recovery.
I still have access to CWM Recovery :|
Have you tried:
fastboot erase recovery
Yes, but the fastboot returns the error that the bootloader is locked and that I should run fastboot oem unlock to run the erase.
Well, all my troubleshooting efforts failed, even the 301k resistor jig. I sent the phone in for repairs on Friday, August 5th. As of today, I learned it's with Samsung's technician right now, and nobody's called about a voided warranty, so here's hoping.
Figured I wouldn't leave the thread at a dead end, in case anyone stumbled onto this from google/xda search:
Samsung sent the repair ticket back to the Telus store with the repair code "REPLACE", so they just gave me a new handset. I have no idea why they just said replace but I have my Nexus back, and that's all that's important.
So are you gonna re-root your Nexus, LOL? Or too much of a headache?
Hah, I rooted and stuck CM7 on it within two hours of knowing the new one I got wasn't busted. Stock just doesn't cut it, potential headaches or not.
Serious Nexus S is serious.
litanyoffail said:
Hah, I rooted and stuck CM7 on it within two hours of knowing the new one I got wasn't busted. Stock just doesn't cut it, potential headaches or not.
Serious Nexus S is serious.
Click to expand...
Click to collapse
LOL!! Yeah, I'm new to the Nexus from HTC Evo 4g and I was on the fence whether to root or not, but I'm gonna take the plunge!! Very unlikely to brick a device except in the most unfortunate of circumstances!
The last week I have been struggling to unbrick my i9023 Nexus S. Without any luck... Let's start at the beginning, how I bricked my Nexus S. If you don't think this is relevant you can skip it.
Stay with me because it's going to be a long thread...
How I bricked my Nexus S
I was running a CM9 Nightly (from around 10 March) until a week ago, together with the matrix CFS 18.0 kernel. I had a problem with rebooting. Every time I rebooted, it would take 2 or 3 tries before it actually started. First it would just reboot again, or even freeze. So after almost a month I was kinda tired of that problem, so I decided to flash a new CM9 Nightly, the one from 7 April. I flashed the Nightly like I always do, wipe cache/dalvik, and I also flashed the new matrix CFS 18.5 kernel, + the latest gapps and the reloadedICS mod. It was working fine. I rebooted a couple of times more into recovery because I wasn't happy with the reloadedICS mod. Everything was still working fine.
The battery was draining very quickly though. I was watching TV for an hour and when I decided to go to bed the battery was already dead. So I put it in the charger because I wanted to check my facebook before I went to bed. It booted fine, but when I started loading facebook in the browser, my phone freezed. I wasn't really alarmed because, well, let's face it, that's the risk with nightlies. So I pulled out the battery, something I have done a lot of times since I started rooting/flashing. After that: dead. No reaction. No charging icon when it was plugged in the charger. No vibration when I pressed the power button, nothing. A brick...
What I've tried
Although it is uncommon, I wasn't the first to brick a Nexus S. Apparently it had something to do with updating to ICS 4.0.4, on which the april 7 nightly was based on I guess.
Luckily there was AdamOutler's Unbrickable Resurrector. After some setbacks I managed to get the Resurrector working. And against all odds I "unbricked" my Nexus S on the first try! Well, I got it into download mode (home and search button). The only problem was that I still didn't have a screen. The home and search button were lit up, but the screen was still black... And according to most people, it isn't supposed to be black...
Ignoring that fact, I downloaded fastboot and tried to flash bootloader.img, as instructed. It didn't work because my bootloader wasn't unlocked, something that struck me as very weird because it definitely was unlocked before the brick. So I tried to unlock the bootloader. But for that, you need a screen... With a lot of luck I managed to unlock the bootloader. Don't ask me how, but after a few tries I succeeded.
I was making progress. And I was happy about that . So I tried to flash the bootloader again. But it still didn't work. "Write failed". After some internet research I found out wat the problem was. It had something to do with the bootloader and radio being a different version. I used the command "fastboot getvar all" and it told me the following:
- Bootloader version: i9020XXKA3
- Radio version: i9020XXXXX
Apparently the radio version isn't supposed to be XXXXX, and that's why I couldn't flash bootloader.img or radio.img. Also, this is the reason that I couldn't boot my device in the first place.
Obviously I wasn't the only person with this problem. I found a guy that had the same problem as me. He used the command "fastboot boot recovery3101.img", using an older version of CWM recovery. If you used that command, your phone would always boot into recovery, so that you can flash a new OTA.
So I downloaded that older version of CWM, and I tried the same command. And it worked! The home and search button were off and the menu and back button were on! But, still no screen. And the guy that used the same command did have a screen...
I had no clue on what to do next, so I pressed the power button, in the hope that I could boot my device directly into recovery after that. I pressed the power button, the backlight of the soft keys went out... and that was my poor Nexus S' last breath of life...
I tried the resurrector tool after that... "failed to write"...
So, am I really f***ed?
I just can't comprehend that my Nexus S could be dead forever... The hardware is fine, it's just the software that keeps it from booting up! The idea of that is crazy... Certainly with a Nexus S for christ's sake!
So, what am I to do? I kinda gave up hope...
UPDATE: SITUATION ATM
1) With AdamOutler's Unbrickable Resurrector I can get into download mode. Sometimes it doesn't work but when I pull out the battery it works again.
Now I can flash every partition with fastboot, except for;
- the bootloader (which is XXKA3)
- the radio (which is XXXXX)
The probable cause for this is the fact that "secure: on", according to "fastboot getvar all". This is very weird because no one on the internet has a Nexus S with "secure: on". It is some security for i.a. HTC devices.
When flashing the bootloader or radio, I get the following error:
sending 'bootloader/radio' <file size>...
OKAY [time]
writing 'bootloader/radio'...
FAILED <remote: Write Fail>
finished. total time: time
Click to expand...
Click to collapse
Using "fastboot -w update image-******.zip":
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
After that the flash goes fine. When it reboots, my phone is dead again. This is because the radio didn't change with this zip. If there would be a radio in that zip, it would not have worked anyway.
The radio is booted first in android, and because of this I can't do anything (the XXXXX version is wrong). This is probably also why the recovery doesn't work properly (see below). And the "secure: on" prevents me from flashing another radio.
2) With "fastboot boot recovery.img" I can get in the recovery mode. ADB "shell" works, and so does "push" and "pull". The screen is black, though. Even with a very strong flashlight I still can't see anything. I can only see 2 or 3 lines (it is different with each recovery). When I press the volume buttons to scroll, I see no changes at all on my screen.
What I have tried in recovery:
- Installing an OTA zip. I can ADB "push" an OTA zip. I have checked that with ADB "shell". Since I can't see anything I have to guide myself using pictures from CWM menus. But nothing happens. There is no sign that the install worked. The only sign that I'm actually in recovery is that the menu and back softkey are lit up, and that when I press the power button without pressing the volume buttons first, my phone powers off (this is because "reboot system now" is on top of the list in recovery, I guess).
- ADB pushing anything on /sdcard. When I turn off my phone after that and resurrect it again, the file is gone. This could be because my memory is dead. But isn't this because the resurrector removes it? Anyway, when I push a file with ADB, it definitely is on my sdcard. Only after rebooting and resurrecting it isn't...
NOTE: Rebooting/booting in whatever mode doesn't work. The only two things I can do are listed above. The moment I plug out my device, I have to use the resurrector again. Because of this there it makes no sense to flash a recovery, since I can't boot anyway. The only way I can get into recovery is by using "fastboot boot recovery.img".
NOTE 2: Recovery.log shows some errors. I will post the whole log soon...
Possible solutions?
A) How can I flash a different radio, despite of "secure: on"?
B) Can we change "secure: on" to "secure: off"? For HTC users this is as normal as "fastboot oem unlock", but there is no one on the internet that has a Nexus S with "secure: on".
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
polobunny said:
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
Click to expand...
Click to collapse
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Androyed said:
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Click to expand...
Click to collapse
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
polobunny said:
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
Click to expand...
Click to collapse
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Androyed said:
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Click to expand...
Click to collapse
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
polobunny said:
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
Click to expand...
Click to collapse
I have used other batteries (luckily I have friends with a Nexus S), but that doesn't change anything.
The big question is, how can I get into download mode again? The resurrector worked at first, but when I flashed CWM to the boot partition and rebooted after that, I can't get any signs of life out of my Nexus S. Resurrector doesn't work anymore, nothing...
The weird thing is, the moment I used the "fastboot boot recovery.img" command, windows stopped recognising the device. But according to the soft keys, it did go from download mode into recovery mode. I still didn't see anything, but I guess that's because the SLCD bug.
I guess I should not have had rebooted when I was finally in recovery...
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
polobunny said:
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
Click to expand...
Click to collapse
Nope, no problem at all.
The only way I could get some life out of it, was by using the resurrector tool. But now even that isn't possible anymore...
Is it actually possible to really perma-brick a Nexus S? Or are people just saying that because they lack the knowledge to unbrick it. I'm pretty sure it can't be a hardware problem. It is the software that is preventing it to boot up. That's what a brick is, right?
WOW, GOOD NEWS!
After a few (totally random) tries, I managed to resurrect my phone again! I am now in the download mode. From here I can use fastboot boot recovery.img. I still don't have a screen though...
When I get into recovery (without screen), what should I do then? Because previous time, windows stopped recognizing my phone... Should I push an OTA to my Nexus S BEFORE I use fastboot boot recovery.img? And if so, how? And if I do so, how on earth am I going to manage to install that zip without a screen? There are a lot of files on my sd card... An option would be to wipe them all, if that's possible. Another option would be to give it something starting with a 1 or an A so that it comes up on top of the list.
The problem is that I can't flash anything because of that i9020XXXXX radio version.... Is there any way I can flash another radio? Just flashing with fastboot doesn't work because of that XXXXX version...
Got it into recovery again! Windows recognized USB mass storage for a second, but not anymore.
Using a flashlight I can see that there is SOMETHING on the screen, but when I press the volume buttons to scroll nothing changes...
Another breakthrough! I installed ADB drivers, and now I got ADB working!
Can you control CWM recovery from the computer, using ADB? Because now all I have to do is flash an OTA, but I can't see anything, not even with a flashlight...
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
wmdunn said:
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
Click to expand...
Click to collapse
I'm not really good at the technical stuff either. I'm like this dog:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I can learn quickly. I know how to push a file to the SD Card using ADB. I also now how to wipe all user data using fastboot. Combining that, I have a SD Card with only 1 file: the OTA I want to flash. That should make thinks a lot easier since I can't see a damn on my screen.
My problem wouldn't even that bad, if it weren't three problems combined. Normally when people unbrick their phone with the resurrector, they can flash a bootloader.img. But I can't, because of that i9020XXXXX baseband version. I tried to flash another radio.img but that doesn't work either. To top this off, my screen doesn't work. Even with a flashlight I only see that there's SOMETHING on the screen, but I don't see any changes when I press the volume buttons for example.
The problem with not seeing anything is that I don't know if what I did, worked. I can't confirm anything. Maybe when I flash the OTA it says: update failed. But I can't see that so how would I know?
That's why I was hoping for a way to not only push files to the SD Card using ADB and wipe all user data using fastboot, but also for a way to install zip from SD Card using ADB/fastboot.
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Harbb said:
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Click to expand...
Click to collapse
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
[Q] i9023 very freaking bricked, lost all hope...
Pls help i am also facing same problem i have given NS to service center they said they will be changing its mother board is there any thing can b done.
Androyed said:
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
Click to expand...
Click to collapse
Try installing factory images from fastboot, You dont need the screen for that just get it to download mode.
http://forum.xda-developers.com/showthread.php?t=1572307
in cmd it says waiting for device and nothing happened its blank
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Does QHSUSB_DLOAD appear in device manager?
I looked up d device manager could not find anything like this. Anywhere specific I need to look at ?
sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Your description is confusing to me. Your thread title says it is softbricked but then you say that you put the phone in debug mode? Does your rom boot fully?
Are you trying to toolkit from the Rom, bootloader or fastboot?
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
I had an issue with softbricking my phone. A good last resort is to flash the RUU (thats what i was told to do and it worked like a charm). It will totally reset your phone to factory settings...and you will need to re-lock your bootloader (just use the All-In-One Toolkit) but besides that, you will once again have a working phone and can just re-root it. If you need the RUU file I can supply the link to it with a little bit of searching. Good Luck!
sadrulez said:
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
Click to expand...
Click to collapse
Everyone's so ready to have a guy run a RUU. Even if he did that it he still would be stuck.
If the toolkit isn't working then you have done something wrong.
Check in device manager and look if you see a category that says "android usb devices"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it's not there you don't have the driver installed correctly. If it is there, double check that you have developer options enabled. In the develop options menu check for something that say enable android debugging.
While you phone is booted normally, plug it into your computer. Can you see something in the notification area that says something about debugging mode?
If you got all that done is the toolkit still not working?
I recommend using a Windows 7 PC to install HTC Sync, then copying the folder to your computer. Then install the drivers manually through device manager, selecting the previous folder that you copied. The drivers should detect your phone then.
@dc211 I can't believe your still using XP lol
Sent from my HTC One S using Tapatalk 2
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
sadrulez said:
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
Click to expand...
Click to collapse
Try holding volume down and power. Out should boot into the bootloader.
Sent from my HTC One S using Tapatalk 2
I already tried that. Holding vol button down + power button restarts the phone in CWM recovery mode
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
sadrulez said:
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
Click to expand...
Click to collapse
Run an RUU, whichever suits your CID /bootloader version.
Sent from my HTC One S using Tapatalk 2
After doing a ton of reading and searching, I still have no idea what my phone is doing. It seems bricked…but only sometimes/partially?
To begin with, I am using ViperXL 3.2.8, elementalX kernel, TWRP 2.5.000 and have been happily using it that way for the summer.
Today I was using facebook to accept a friend request and it suddenly force closed on me. “ oh well” I thought, it’s always been buggy and slow. Hit ok on the msg, then put my phone down. After about a minute, Google play services force closed. Then others began closing, cascading to the point of things like “android core” force closing. My phone then crashed and restarted (its done THAT part before, somewhat often too. Very annoying). I cannot remember exactly, but I think that it then restarted, took foreverrrr to come up, then unlocked the phone and everything started force closing again, faster than I could hit “OK”. Crashed again, restarted…this time got stuck on the Viper boot logo. Let it do that for a while, then restarted by holding power button. Came up, same thing happened. Next I went into TWRP to clear cache and dalvik. When I tried, it fails with the message “cannot mount /cache” about 3 times. Then I went to reboot it, come up and says something like “it doesn’t look like your phone is rooted, would you like to install SuperSU?” whether I click yes or no doesn’t matter, TWRP hangs for a little while and then the phone shuts off.
At this point, I'm mildly panicking, so do some searching. I noticed that “android.process.acore” closed a lot, and it came up that facebook could be an issue. After several tries, got booted up far enough to attempt uninstalling the app. It completed, but the phone then instantly crashed. Checking afterwards, it’s still there. Also, when I do get to into android (about 70% of the time it hangs at the boot animation) and try to access developer tools to enable USB debugging, settings instantly force closes. Same with venom tweaks when I try to change CPU voltage (I'm under-clocked and under-volted, trying to get better battery life..this thing is a total hog for some reason). Oh, and when I get booted up for long enough it’ll come up saying that “internal storage is corrupted and may have to be formatted”.
It gets weirder. Thinking that perhaps TWRP is somehow corrupted, I attempted to flash a different version (2.6 first, then 2.3.3.1). “fastboot flash recovery TWRP.img” completes just fine, no errors. But when I go to recovery, 2.5.0.0 is still there! How it that possible? Also, “fastboot erase cache” completes fine too, regardless of what TWRP says. But I'm not convinced it’s doing anything at this point. Another odd thing, the phone will not successfully reboot with either “fastboot reboot-recovery” or selecting it in the bootloader menu. It shuts off, then the charge light comes on (to indicate booting) but then goes off again before anything comes on screen.
One more thing: when I tried "fastboot oem lock" it fails with "status read failed (too many links)".
I apologize if this is disjointed, I’ve tried a lot of things in a short time and they kind blend together a little.
TL;DR:
Every process on the phone force closes on boot
TWRP cannot mount /cache
TWRP cannot be updated, even though fastboot succeeds
My phone is posessed!
HELP!
Thanks in advance, at this point I'm ready to try anything, if only to get it so I can give it to AT&T and get a different one!
If you put your phone into bootloader does it stay there happily? You could try an RUU, but it's risky at this point if the phone is so unstable.
Sent from my Evita
timmaaa said:
If you put your phone into bootloader does it stay there happily? You could try an RUU, but it's risky at this point if the phone is so unstable.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply! It does stay in bootloader quite nicely, that's about the only thing it does at this point. Is it safe to flash an RUU being S-off, unlocked and CID 11111111? I was actually planning on trying that next. Also would the proper one be named "RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105"?
Thanks!
Yeah you're s-off so you'll be fine. Click the link in my signature, you'll find links to RUU threads in there.
Sent from my Evita
timmaaa said:
Yeah you're s-off so you'll be fine. Click the link in my signature, you'll find links to RUU threads in there.
Sent from my Evita
Click to expand...
Click to collapse
Great, thanks! I'll report back any results I get...hopefully those results wont be a steaming pile of slag
Flash the RUU and run it like that for a couple of days to see if the problems persist.
The initial problems could well have been because you were using TWRP 2.5, it's full of bugs. After running stock, and if it's fine, when you're gonna flash custom ROMs again make sure you use TWRP 2.6, it's in perfect working order.
Sent from my Evita
timmaaa said:
Flash the RUU and run it like that for a couple of days to see if the problems persist.
The initial problems could well have been because you were using TWRP 2.5, it's full of bugs. After running stock, and if it's fine, when you're gonna flash custom ROMs again make sure you use TWRP 2.6, it's in perfect working order.
Sent from my Evita
Click to expand...
Click to collapse
New problem: When I go to RUU, it gets to the part where it reboots my phone back into bootloader and fails. the phone shuts off and then the charge light comes on, so good so far, then it goes out (like it tries to boot) but then come back on and nothing happens. After a minute or 3 the RUU errors out since it can no longer see the phone. The same thing happens if I try to tell it to reboot bootloader from the bootloader...this is weird.
Also, I cannot relock my phone! All I get is:
Code:
fastboot oem lock ->
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.955s
Side note, the output from "fastboot getvar version-main" is blank. My phone somehow seems to have every glitch known to man right now!
I can get USB debugging enabled! Well, only because it has always seemed to toggle every other time I hook my phone to the computer...but still, I can get to adb commands now. However, I'm not really sure that got me anywhere at this point
Put your phone into bootloader/fastboot manually and then run the RUU. Don't worry about relocking.
Sent from my Evita
timmaaa said:
Put your phone into bootloader/fastboot manually and then run the RUU. Don't worry about relocking.
Sent from my Evita
Click to expand...
Click to collapse
That's what I've tried doing, the RUU decides to reboot it from being in bootloader back to bootloader for some reason, and that's where it gets hung up.
I'm beginning to think there is something seriously wrong with my cache, bc after I get my phone to boot the only really reoccurring stopped process is android.process.acore, which according to Google has something to do with programs and how they access cache?
Thanks for the help thus far!
Try the fastboot command:
fastboot erase cache
Try that a few times, then try RUU again.
Sent from my Evita
timmaaa said:
Try the fastboot command:
fastboot erase cache
Try that a few times, then try RUU again.
Sent from my Evita
Click to expand...
Click to collapse
Will do. So a few minutes ago I got to 10% with the RUU, this time run with the phone booted and in USB debug mode. Got to the HTC logo on a black background, it sent the RUU..then went into "waiting for bootloader" while my phone non-booted, as usual.
While I was doing some research, I left the phone at the bootup animation for like 10 min, and it finally booted with a message about a UUID (might have been UDID, not sure) mismatch. Don't know if any of this means anything, but it's certainly very odd.
Forgot this earlier, but sometimes it will boot for a while and go to a black screen, with the backlight still on.
Thanks again!
So, I've been trying things, and I have discovered that I am completely unable to make any file system changes whatsoever. Oh sure, I can mount the sd card in TWRP and delete/move things. But after a reboot, it acts like I never touched it, and it's right back to how it was before. Same with flashing a recovery. I've even tried getting it to boot and using adb to shell in and delete files that way, but still no change.
I'm running out of things to try....I almost want to take it in to AT&T and see if I can at least pay them to do something about it...heck, at this point I'd pay for a refurb phone!
Anyone has any ideas, let me know
to Flash an RUU if the ruu installer is giving you errors:
1)extract rom.zip from ruu.exe; google it, basically you open the ruu installer and search your temporary(Appdata in windows) files for rom.zip
2)fastboot oem rebootRUU
3)fastboot flash zip rom.zip (with atleast 70% battery as it takes a while)
charge the phone from any custom recovery if you cant boot it up to charge it(preferably twrp as it turns screen off to charge quicker)
That doesn't accomplish the same result as running an RUU at all, it's just like flashing a ROM.
Sent from my Evita
Vcek said:
to Flash an RUU if the ruu installer is giving you errors:
1)extract rom.zip from ruu.exe; google it, basically you open the ruu installer and search your temporary(Appdata in windows) files for rom.zip
2)fastboot oem rebootRUU
3)fastboot flash zip rom.zip (with atleast 70% battery as it takes a while)
charge the phone from any custom recovery if you cant boot it up to charge it(preferably twrp as it turns screen off to charge quicker)
Click to expand...
Click to collapse
Thanks for the reply! I just tried that, and when I run "fastboot oem rebootRUU" it does the same thing as before: shuts off, the charge light comes on, then goes of for 2-3 seconds, then comes back on and the screen is off and it stays that way. However, I then ran "fastboot flash zip rom.zip" and while it said "waiting for device" got it back into fastboot mode. Then this:
Code:
< waiting for device >
sending 'zip' (576544 KB)...
OKAY [ 26.127s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 26.169s
no this must be run from RUU mode, try unlocking your bootloader first(then relocking it)
timmaaa said:
That doesn't accomplish the same result as running an RUU at all, it's just like flashing a ROM.
Sent from my Evita
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i am talking about this kind of rom.zip
Yeah I know that, but that only updates the ROM partition to stock which isn't what we're aiming for. We're trying to do a complete return to stock, all partitions, which that method won't accomplish.
Sent from my Evita
the ruu installer does nothing more than flashing the rom.zip which contains all the partitions(21 partitions including hboot,sbl's,radio,touch,data,system,boot,recovery).
Ask around, I think you'll find that method doesn't do the whole job.
Sent from my Evita
It seems that the issue here is that my phone cannot get into RUU mode, since it cannot complete a reboot when sent a software command. As I said before, when I execute "fastboot oem rebootRUU", it shuts off but then won't come back on. Same with "fastboot reboot", "fastboot reboot-bootloader", and any adb reboot command. This issue also occurs when rebooting from the actual boot loader menu, as well as recovery. However, in TWRP, if I hit "reboot recovery", it won't come back up. But if I hit "reboot bootloader" (or system, I believe), it will in fact come back up.
Thanks for the replies! If I can only get to RUU mode I think we can fix this
Hello,
I'd like to say I was told about this site, and I hope someone can help. I find the forum very difficult to navigate.
I have a moto G 2015 that I tried to root, but I fear that I made some mistake or downloaded a bad rom or something because I can only access the root loader, or w/e it's called. The new rom or recovery image or w/e (yes i'm sorry i don't know all the terms) never loaded, and even the backup (which installed successfully) won't load.
Can I factory reset my phone with the original android rom? I really like this phone and it's just a brick now. I'm using my old phone which i don't like as much. I hope someone can help.
You'll have to flash the stock firmware using fastboot, here is the guide. Refer first 2-3 posts by lost101 for the instructions.
Also, the guide has a link for the firmware index where you can download the latest firmware for your particular model (mine is XT1550, for example).
You should already have ADB and fastboot set-up on your PC as you have tried to root. Assuming that you're using Windows, Extract the firmware into the folder where adb.exe and fastboot.exe are located.
Now, boot the phone into bootloader mode by pressing and holding power+volume down button for about 7-10 seconds. You can release the keys once you see an Android robot lying on its back. The screen should read 'fastboot mode'. Connect the phone to your PC, the screen should now day 'USB connected'. Now open a command prompt from the location where you placed the firmware files. You're now ready to flash the stock firmware.
Follow the guide linked above for the required commands. Make sure to do the recovery flash first, factory reset, then reboot to bootloader again to continue rest of the procedure.
BTW, what was the backup you mentioned that restored successfully? Can you describe it more?
Broadcasted from Zeta Reticuli
Let me provide some images I took with my other phone. It might help.
OK I have osprey xt1540 and i used something called Team Win Recovery Project v2.8.7.0. I can still get into the TWRP thing, and there's a bunch of options i'm sure you're aware of. The backup of my phone that I made doesn't seem to work. It will load say that it loaded properly. Maybe I can provide some photos to show you what I've done.
The backup was simply a backup of my phone before attempting to flash it the first time. It was meant as a way to recover the phone I think..
edit: OK so I'm not allowed to post pictures because I have fewer than 10 posts. That's going to make it harder to get help.
edit 2: BTW In the list for stock firmware I'm not sure which one to take. I found the version of my phone, but it seems newer than any of those listed. 24.71.2 where the newest there is 24.65.33 ?
I found a more recent firmware, but it still doesn't exactly match my phone (I think?) I'll post them
My phone: 24.72.2.osprey_retca.retca.en.ca
Most recent found: MotoG3_XT1540_OSPREY_RETCA_5.1.1_LPI23.72-16.3_cid14_subsidy-DEFAULT_CFC.xml.zip
And I found it from this thread: https://forum.xda-developers.com/showthread.php?t=2537119
Also I wonder if my phone will work if I can just relock the bootloader somehow. I get stuck on that screen that warns about the bootloader unlocked (white screen with motorola warning.) I can get on that screen, the bootloader, and then the team win recovery thing. I hope this helps
First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.
KrisM22 said:
First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.
Click to expand...
Click to collapse
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.
mobile.frank said:
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.
Click to expand...
Click to collapse
I would need to see a copy of your terminal output.
Try what you were doing again in TWRP, this time after the error, use the third button on nav bar (right to the home button, 4 horizontal lines) to switch to terminal output window; then press and hold down power+volume down to take a screenshot and then upload it here, it might help us understand the situation better.
And if you are aiming for a stock firmware install, probably 'XT1540_OSPREY_RETCA_6.0_MPI24.65-33.1-2-2_cid14' is what you want. Got from the firmware index thread here.
BTW, you can try some threads on the off-topic section to increase your post count.
Broadcasted from Zeta Reticuli
KrisM22 said:
I would need to see a copy of your terminal output.
Click to expand...
Click to collapse
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything.) I imagine i have to update the TWRP from this screen, but the instructions in the links you sent me don't correspond with the files that I downloaded. If I type in what I downloaded it doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the program and screen and instructions. The codes there don't work because the filenames are different:
This is an example trying to use the recovery img which tbh I'm not even sure what image that is.
I attempted to root my motorola a long time ago, that's why i can't remember how i managed to do any of it. I think I deleted all the links to the instructions I was using.
mobile.frank said:
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything)
This is the program and screen and instructions. The codes there don't work because the filenames are different:
Click to expand...
Click to collapse
fastboot devices shows the devices that are in fastboot mode (same as bootloader mode in our case) connected to the PC. So, connect the phone via USB and try running that command, it'll show up your device's serial no. and 'fastboot' written on the right side.
Now, rename your recovery image to twrp.img. Or you n modify the command itself. Make sure that the recovery is in the same folder as these 4 files. For example, if your recovery is named twrp-3.1.0.0-osprey.img, then type in-
Code:
fastboot flash recovery twrp-3.1.0.0-osprey.img
after you get a [DONE], scroll down and select recovery in phone.
If you already have a twrp version installed now, then copy the new twrp.img file to your sdcard. In TWRP>Install>install image. Select the file, select recovery in next step and swipe to flash.
Broadcasted from Zeta Reticuli
from the lying down android in the first picture, it shows you have stock recovery.
KrisM22 said:
from the lying down android in the first picture, it shows you have stock recovery.
Click to expand...
Click to collapse
That's the bootloader screen, not recovery.
Sent from my MotoG3 using Tapatalk
OK I managed to update the TWRP and am trying to restore the phone backup from the SD card. I made the backup before making any changes when I tried to root my phone.
I don't know if anything works because every time the phone reboots I get the "Warning bootloader unlocked" screen; so maybe it even worked when i tried to root it, but is just always stuck on this screen. I only get that screen, or the bootloader screen if I go to it.
OK so I tried to follow these directions with the factory image for my phone, and it didn't work. I get a nice motorola boot screen, and then nothing:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#
I strongly suggest you look at this:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
That will also tell you how to get rid of the nasty bootloader screen.
Also make sure you WIPE dalvik/art,data,system,cache before you restore. Anything.