Everyone should do it at least once, really. Teaches humility and caution.
I was messing around between ROMs with SafeStrap, testing battery life. Had gone ahead and tested SlimKat while I had it booted, found it acceptable, so I decided to do stock JB next.
It seemed only right and proper to install myfishbear's deodexed ROM over stock, so if it turned out that I was going to use it, I wouldn't need to shuffle it anywhere. And, I imagine, it would have been fine if I had simply installed it over stock.
However, in a moment of brilliance, I wiped the stock slot, installed the deodexed ROM, ignored the "NO O/S MORON" warning, and rebooted. In my defense, I had read somewhere that new versions of SS made a safety check to make sure necessary boot files were intact, and I knew that there were recovery options in case of bricking, so I wasn't especially worried if I screwed something up.
Well, I screwed something up, obviously. If I had to guess, I would say that I wiped the bootloader out?
So now:
Trying to let it boot results in a black screen
Trying to get into AP FastBoot results in a black screen
Recovery is accessible. However...
Trying to flash firmware from an SD card zip aborts itself when verifying the package. Have tried a few Android 4.x packages so far, for variety. To be honest, I didn't really expect this to work in the first place.
Trying to use Fastboot from recovery results in Windows detecting the phone as "Droid4", improperly installed (good ol' yellow triangle), and refuses to let me install it as the Motorola Flash Interface as it should be (won't even give me the option when I try to forcefully install the driver).
What shall I try next?
Septfox said:
Everyone should do it at least once, really. Teaches humility and caution.
I was messing around between ROMs with SafeStrap, testing battery life. Had gone ahead and tested SlimKat while I had it booted, found it acceptable, so I decided to do stock JB next.
It seemed only right and proper to install myfishbear's deodexed ROM over stock, so if it turned out that I was going to use it, I wouldn't need to shuffle it anywhere. And, I imagine, it would have been fine if I had simply installed it over stock.
However, in a moment of brilliance, I wiped the stock slot, installed the deodexed ROM, ignored the "NO O/S MORON" warning, and rebooted. In my defense, I had read somewhere that new versions of SS made a safety check to make sure necessary boot files were intact, and I knew that there were recovery options in case of bricking, so I wasn't especially worried if I screwed something up.
Well, I screwed something up, obviously. If I had to guess, I would say that I wiped the bootloader out?
So now:
Trying to let it boot results in a black screen
Trying to get into AP FastBoot results in a black screen
Recovery is accessible. However...
Trying to flash firmware from an SD card zip aborts itself when verifying the package. Have tried a few Android 4.x packages so far, for variety. To be honest, I didn't really expect this to work in the first place.
Trying to use Fastboot from recovery results in Windows detecting the phone as "Droid4", improperly installed (good ol' yellow triangle), and refuses to let me install it as the Motorola Flash Interface as it should be (won't even give me the option when I try to forcefully install the driver).
What shall I try next?
Click to expand...
Click to collapse
What recovery is accessible?
Sent from my DROIDX using XDA Free mobile app
sd_shadow said:
What recovery is accessible?
Sent from my DROIDX using XDA Free mobile app
Click to expand...
Click to collapse
The second one, Android's recovery.
Septfox said:
The second one, Android's recovery.
Click to expand...
Click to collapse
Stock recovery is worthless for flashing.
Need to use ap fastboot with rsd lite to flash stock firmware
Sent from my DROIDX using XDA Free mobile app
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
http://forum.xda-developers.com/showthread.php?t=2817531
Sent from my DROIDX using XDA Free mobile app
---------- Post added at 01:55 AM ---------- Previous post was at 01:53 AM ----------
Or could just try
Power off, Hold M key, Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap
Sent from my DROIDX using XDA Free mobile app
sd_shadow said:
Stock recovery is worthless for flashing.
Need to use ap fastboot with rsd lite to flash stock firmware
Click to expand...
Click to collapse
I've realized this, yes. If the stock recovery weren't useless, there wouldn't be the need for using fastboot. I was just playing with it, since I couldn't get anything else to work properly.
sd_shadow said:
Or could just try
Power off, Hold M key, Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap
Click to expand...
Click to collapse
The key word being "should"...but I've actually already tried this, after seeing it in a couple of other posts. Booting this way results in the same black screen as booting without holding M.
Right, well. I made a factory-style cable, to avoid killing my battery while I screw around.
I would very much appreciate any further suggestions on how to proceed. Is there any way to get the phone running from stock recovery, or am I completely SOL without AP Fastboot working from the first recovery menu?
Picking up another mainboard is always an option, but I'd really prefer not to if at all possible.
Septfox said:
Right, well. I made a factory-style cable, to avoid killing my battery while I screw around.
I would very much appreciate any further suggestions on how to proceed. Is there any way to get the phone running from stock recovery, or am I completely SOL without AP Fastboot working from the first recovery menu?
Picking up another mainboard is always an option, but I'd really prefer not to if at all possible.
Click to expand...
Click to collapse
power off, press both volume buttons
sd_shadow said:
power off, press both volume buttons
Click to expand...
Click to collapse
That gets me the first menu.
Everything in this menu, aside from Recovery, results in a black screen; even the M-to-BP Tools Safestrap shortcut.
Recovery, of course, gets me to android recovery, which apparently borders on useless. I mean, there's a fastboot option there, but it doesn't seem to work properly.
Septfox said:
That gets me the first menu.
Everything in this menu, aside from Recovery, results in a black screen; even the M-to-BP Tools Safestrap shortcut.
Recovery, of course, gets me to android recovery, which apparently borders on useless. I mean, there's a fastboot option there, but it doesn't seem to work properly.
Click to expand...
Click to collapse
Power off your phone, hold volume down button and press power button, until you see AP Fastboot Flash Mode
sd_shadow said:
Power off your phone, hold volume down button and press power button, until you see AP Fastboot Flash Mode
Click to expand...
Click to collapse
Ok, just so we're on the same page here.
First menu:
{
"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 have no problem getting to this menu. Everything but Recovery in this menu fails to do anything but go to a black screen; including AP Fastboot. Holding M while opening this menu, then selecting BP Tools to try and skip to Safestrap, doesn't work.
Recovery:
Useless, because it can't seem to actually flash packages (I would guess because how borked everything is), and the fastboot option doesn't seem to work properly.
Septfox said:
Ok, just so we're on the same page here.
Click to expand...
Click to collapse
When from power off, hold just volume down, power on, should go straight to ap fastboot
Useless, because it can't seem to actually flash packages (I would guess because how borked everything is), and the fastboot option doesn't seem to work properly.
Click to expand...
Click to collapse
No only update.zip(s) can be installed in stock recovery and only if Stock rom is installed, and only if it is the correct update, can not install updates on same system version, can not downgrade, so if newest system version is installed, there is no update.zip that will work. It's the same for every Motorola Droid for last 4 years.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
updates.zips are named like Blur_Version.6.16.217.XT894.Verizon.en.US.zip
rsd lite fles are like cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
---------- Post added at 06:15 PM ---------- Previous post was at 06:10 PM ----------
could try
Code:
adb reboot-bootloader
sd_shadow said:
When from power off, hold just volume down, power on, should go straight to ap fastboot
No only update.zip(s) can be installed in stock recovery and only if Stock rom is installed, and only if it is the correct update, can not install updates on same system version, can not downgrade, so if newest system version is installed, there is no update.zip that will work. It's the same for every Motorola Droid for last 4 years.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
updates.zips are named like Blur_Version.6.16.217.XT894.Verizon.en.US.zip
rsd lite fles are like cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
Click to expand...
Click to collapse
Ah, I see. That seems...rather short-sighted of Motorola. They knew very well that many of their users would be doing monumentally stupid things - like wiping the phone, for example - being able to debrick it from recovery would be extraordinarily helpful...
Then again, I'm sure that stock recovery on my Ally was just as unhelpful, so eh.
This is my first Droid, my first Motorola ever in fact, so I didn't know.
I'm aware of the naming conventions, I actually did download the RSD lite file for debricking...just couldn't get anywhere to use it. Several updates too, to spam at the package installer; that of course got me absolutely nowhere.
Anyway, I finally got into Fastboot.
What I was trying to do originally was disconnect the battery to power the phone off, then reconnect it and follow your instruction for going straight into Fastboot. This wasn't working; the phone refused to power on until I let go of all buttons. Is there some other way of shutting the phone off? Simply pressing the power button does nothing for me.
I thought we were having a breakdown in communication, since Vol Down+Power is supposed to be for reset. I apologize.
What finally got me in was disconnecting the battery, then holding the button down while "manually" powering on by using the factory-style cable. I now have the AP Fastboot menu; I just have to get Windows to install it properly (currently up, improperly as I understand, as "Mot Single ADB Interface"). I have your Google Docs guide up, so hopefully I can proceed from here without screwing anything else up.
Septfox said:
Ah, I see. That seems...rather short-sighted of Motorola. They knew very well that many of their users would be doing monumentally stupid things - like wiping the phone, for example - being able to debrick it from recovery would be extraordinarily helpful...
Then again, I'm sure that stock recovery on my Ally was just as unhelpful, so eh.
This is my first Droid, my first Motorola ever in fact, so I didn't know.
Click to expand...
Click to collapse
all "Droid"(s) are designed for Verizon, and Verizon does not want their devices rooted, so this would not happen.
I'm aware of the naming conventions, I actually did download the RSD lite file for debricking...just couldn't get anywhere to use it. Several updates too, to spam at the package installer; that of course got me absolutely nowhere.
Anyway, I finally got into Fastboot.
What I was trying to do originally was disconnect the battery to power the phone off, then reconnect it and follow your instruction for going straight into Fastboot. This wasn't working; the phone refused to power on until I let go of all buttons. Is there some other way of shutting the phone off? Simply pressing the power button does nothing for me.
I thought we were having a breakdown in communication, since Vol Down+Power is supposed to be for reset. I apologize.
What finally got me in was disconnecting the battery, then holding the button down while "manually" powering on by using the factory-style cable. I now have the AP Fastboot menu; I just have to get Windows to install it properly (currently up, improperly as I understand, as "Mot Single ADB Interface"). I have your Google Docs guide up, so hopefully I can proceed from here without screwing anything else up.
Click to expand...
Click to collapse
Windows does not like Motorola devices/Drivers, may need to reboot pc and droid 4 a few times
Let me start this post off by saying THANK YOU for sticking around and putting up with me. It has been a trying day, both because of this and offline stuff going on. I'm sorry if any of it bled over into my responses.
Flash was successful, phone is currently doing its thing, and I now know several new things about not only my phone, but Motorola devices in general. As well as what to avoid doing at all cost in the future unless I want more headaches.
sd_shadow said:
all "Droid"(s) are designed for Verizon, and Verizon does not want their devices rooted, so this would not happen.
Click to expand...
Click to collapse
Yes, god forbid people try and get the most out of devices that they paid several hundred dollars and/or are roped into multi-year contracts for.
sd_shadow said:
Windows does not like Motorola devices/Drivers, may need to reboot pc and droid 4 a few times
Click to expand...
Click to collapse
Funny thing about that.
I couldn't get Windows to install the phone "properly". Manually installing it as the Motorola Flash Interface simply made it unusable. After repeatedly rebooting the phone and computer, trying different cables and installation orders and methods, I finally gave up and left it as "Mot Single ADB Interface". RSD lite picked it up, but wouldn't display any information about it; didn't care, told it to flash anyway. The way I figured, it's not like it could hurt the phone much more than it already was.
Lo and behold, it worked. I'm not saying that this is a typical case and leaving it alone will work for everyone, but for anyone looking for an answer in the future: if you can't install it "properly", try flashing it anyway, provided it displays in Device Manager as functioning with no issues.
Final question, before I go off and do something stupid again: how does one flash ROMs into the stock "slot"? Is it a simple matter of installing without wiping the existing partitions?
Though frankly, at this point, I'm almost happy to just leave well enough alone and write that 3gb off as unusable.
Can't remember if all the ROMs can be installed on stock slot.
Cm11 and slimkat can just in safestrap/twrp, select stock slot, factory reset, and install.
Sent from my DROIDX using XDA Free mobile app
Indeed, Slimkat installed with absolutely no issue, and is at this point well on its way to being acceptably tweaked for daily usage. Aside from the rare random hot reboot, anyway.
Thanks again for your help, I can say with certainty that the phone wouldn't be working without it.
Related
OK, so I am not new to flashing ROM's, but I formatted system from recovery (storage and mounts) and was going to flash unleashed 1.1, but somehow I accidentally rebooted phone before flashing anything!
Now the phone only boots into the M dual core logo, and wont go any further. After a battery pull, I attempted to go into recovery by volume up/down and power button simultaneously, and choose recovery, but the phone goes to the exclamation point inside the triangle and wont boot into recovery.
What do I do?
There's a partial fxz that will reflash just the stock system partition. Find that and use it.
Sent from my DROID BIONIC using Tapatalk
I just started looking into the FXZ, and am downloading it right now. I dont see a partial file though. the whole one is huge! searching now....
I've pm'ed you
Sent from my DROID BIONIC using Tapatalk
OK, so this file must be it
http://forum.xda-developers.com/showpost.php?p=17560174&postcount=21
I guess this is relatively simple. Haven't had to use RSD, so will search for a tutorial. Hope this file will download from the coffee shop I am at in the next 30 minutes!
Easy. Pull battery. Put battery back in. Hold vol down button. Press the power button to get the black screen with white letters. Launch rsd pick the file you downloaded select uncompress and flash. Go have a cigarette or quick beer and it will be done.
I have done it way too many times by bricking my phone trying to edit services jar to get 1% battery increments although i may throw in the towel soon on that
Sent from my DROID BIONIC using XDA App
theproj said:
Easy. Pull battery. Put battery back in. Hold vol down button. Press the power button to get the black screen with white letters. Launch rsd pick the file you downloaded select uncompress and flash. Go have a cigarette or quick beer and it will be done.
I have done it way too many times by bricking my phone trying to edit services jar to get 1% battery increments although i may throw in the towel soon on that
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Geez, you were right on time with this. I was starting to stress because I couldnt get RSD to recognize the phone, and I have no idea how to open a command prompt in windows ( i know. Retarded)
THANK YOU (phone just booted up)
Glad to hear. Now root your phone (faq in the dev forum will help) set it all up how you want and make a nandroid backup for the next time you brick your phone.
Sent from my DROID BIONIC using XDA App
theproj said:
Glad to hear. Now root your phone (faq in the dev forum will help) set it all up how you want and make a nandroid backup for the next time you brick your phone.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Actually, was already rooted and had a back up, was gonna update from unleashed 1.0 to 1.1, and pulled a dumb A** mistake. First time since having a rooted D1, and Incredible that I have done this!
I love this forum and all its users!
I had the same problem FINALLY got it working.
Ok I might sound retarded, but I can not get this phone started. I root the one with one of the One-click programs then i went on to remove the bloatware, however I guess I removed the home launcher without installing another one from the market. Now the phone will not pass the screen that comes right after the big M. What do i do? can someone please help?
gkybjk said:
Ok I might sound retarded, but I can not get this phone started. I root the one with one of the One-click programs then i went on to remove the bloatware, however I guess I removed the home launcher without installing another one from the market. Now the phone will not pass the screen that comes right after the big M. What do i do? can someone please help?
Click to expand...
Click to collapse
You're gonna have to use RSD lite again
AP Fastboot Flash Mode (S)
Battery OK to Program
Transfer Mode : USB COnnected
I am stuck at this screen. Wont let me do anything! Anyone knows what I should do? Thanks
I swear I just saw a post last night that stated you could get into recovery by the following method.
pull the battery, put battery back in, hold down the volume up and down buttons while pressing the power button simultaneously. This should take you to the screen with exclamation mark inside triangle.
Next (this is the part where I get uncertain. Darn memory)
press the volume buttons simultaneously and it takes you to factory recovery? or volume down by itself. If you can get to recovery you can wipe cache/dalvik cache and system format under (mounts and storage), then re-flash the rom again.
But I am not certain about that, because I cant find it again, but it wont hurt to try.
If that doesnt work, you may have to do the following, but It would seem like that is extreme fix for just removing your launcher?
someone chime in here.
theproj said:
Easy. Pull battery. Put battery back in. Hold vol down button. Press the power button to get the black screen with white letters. Launch rsd pick the file you downloaded select uncompress and flash. Go have a cigarette or quick beer and it will be done.
I have done it way too many times by bricking my phone trying to edit services jar to get 1% battery increments although i may throw in the towel soon on that
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Thanks
I got it figured it out. I had to install fastboot images and flash them to phone by windows command prompt. Thanks everyone!
Hi,
I have a 1 month old HTC Vivid. It was running it on ICS 4.0.3 and it was rooted. Today, while I was working on it, it suddenly powered off and now it won't do anything. Like it doesn't display anything on the screen, doesn't get powered up and when I connect the charger, I can't even see the orange light. ITS TOTALLY F**KED UP!!!
Please Help!! Thanks!!
Can you boot into H-Boot?
Sent from my HTC PH39100 using XDA
I got the same problem. The phone did not work at all. It only flashed for a few seconds when I pressed the power button. I searched all the websites, but nothing worked. My solution is to send the phone to HTC to have it fix. They have a very good customer service.
With the charger plugged in, does the phone vibrate when the HOME, MENU, BACK, or SEARCH buttons are pressed?
Had a similar problem, for me HTC was the only solution, just say that it happened suddenly and dont mention anything about boot loader or roms.
Have you guys tried project UNBRICK yet? Search that on the forum here, as I can't post links yet.
jul644 said:
Had a similar problem, for me HTC was the only solution, just say that it happened suddenly and dont mention anything about boot loader or roms.
Click to expand...
Click to collapse
This. AT&T replaced my no-power Vivid under the One Year Warranty.
BTJustice said:
With the charger plugged in, does the phone vibrate when the HOME, MENU, BACK, or SEARCH buttons are pressed?
Click to expand...
Click to collapse
mine does. do you know how to fix it.
rhino474 said:
mine does. do you know how to fix it.
Click to expand...
Click to collapse
Yes but it is a pain and takes several tries. I had this problem a few days ago and this was the only way I could get around it.
I HOPE YOU HAVE DATA BACKED UP! That's your responsibility and not mine. If this ruins your phone then tough. I will not be held responsible for a bricked phone...
First off, assuming the bootloader is UNLOCKED, install the ALL IN ONE tool on your computer (it actually runs from a folder and doesn't really install which is good)...
http://forum.xda-developers.com/showthread.php?t=1498003
Open it, then...
Remove any bought protective case (it may mess with the buttons).
Unplug charger.
Remove battery.
Wait 5 minutes.
Reinstall battery.
Plug in USB cable from the computer.
Hold down the VOLUME DOWN button and then the POWER button.
It should boot into the bootloader. On the ALL IN ONE tool, flash recovery to CWM. Once complete, click on "Boot into Recovery".
If the phone does not boot into Recovery, flash recovery to WCX.
If the phone reboots into Recovery, you will want to do a factory reset, wipe cache, go to mounts and format them all. Then mount it as USB and copy/paste a ROM over and flash to that ROM. I like Virtuous Inquisition v4.0.2.1.
Good luck.
BTJustice said:
Yes but it is a pain and takes several tries. I had this problem a few days ago and this was the only way I could get around it.
I HOPE YOU HAVE DATA BACKED UP! That's your responsibility and not mine. If this ruins your phone then tough. I will not be held responsible for a bricked phone...
First off, assuming the bootloader is UNLOCKED, install the ALL IN ONE tool on your computer (it actually runs from a folder and doesn't really install which is good)...
http://forum.xda-developers.com/showthread.php?t=1498003
Open it, then...
Remove any bought protective case (it may mess with the buttons).
Unplug charger.
Remove battery.
Wait 5 minutes.
Reinstall battery.
Plug in USB cable from the computer.
Hold down the VOLUME DOWN button and then the POWER button.
It should boot into the bootloader. On the ALL IN ONE tool, flash recovery to CWM. Once complete, click on "Boot into Recovery".
If the phone does not boot into Recovery, flash recovery to WCX.
If the phone reboots into Recovery, you will want to do a factory reset, wipe cache, go to mounts and format them all. Then mount it as USB and copy/paste a ROM over and flash to that ROM. I like Virtuous Inquisition v4.0.2.1.
Good luck.
Click to expand...
Click to collapse
it didnt work, but thanks for trying.
---------- Post added at 05:17 AM ---------- Previous post was at 05:06 AM ----------
rhino474 said:
it didnt work, but thanks for trying.
Click to expand...
Click to collapse
Never mind, I got it working. Thanks.
rhino474 said:
it didnt work, but thanks for trying.
---------- Post added at 05:17 AM ---------- Previous post was at 05:06 AM ----------
Never mind, I got it working. Thanks.
Click to expand...
Click to collapse
What did you wind up doing to get it to work? Be descriptive.
I too had my vivid bricked but i use Toolkit to solve the issue.:victory:
BTJustice said:
Yes but it is a pain and takes several tries. I had this problem a few days ago and this was the only way I could get around it.
I HOPE YOU HAVE DATA BACKED UP! That's your responsibility and not mine. If this ruins your phone then tough. I will not be held responsible for a bricked phone...
First off, assuming the bootloader is UNLOCKED, install the ALL IN ONE tool on your computer (it actually runs from a folder and doesn't really install which is good)...
http://forum.xda-developers.com/showthread.php?t=1498003
Open it, then...
Remove any bought protective case (it may mess with the buttons).
Unplug charger.
Remove battery.
Wait 5 minutes.
Reinstall battery.
Plug in USB cable from the computer.
Hold down the VOLUME DOWN button and then the POWER button.
It should boot into the bootloader. On the ALL IN ONE tool, flash recovery to CWM. Once complete, click on "Boot into Recovery".
If the phone does not boot into Recovery, flash recovery to WCX.
If the phone reboots into Recovery, you will want to do a factory reset, wipe cache, go to mounts and format them all. Then mount it as USB and copy/paste a ROM over and flash to that ROM. I like Virtuous Inquisition v4.0.2.1.
Good luck.
Click to expand...
Click to collapse
Worked perfect - had to pull the kernel out of the ROM I used and flash it with the tool but it worked perfectly...
Im betting your screen might be toast, happened to my wife's vivid, completely just up and died one day for no reason. I haven't rooted yet and this sort of stuff makes me leary to do it.
Sent from my VTC HIVID using the xda app
http://forum.xda-developers.com/showthread.php?t=1717766
http://forum.xda-developers.com/showthread.php?t=1479060
http://forum.xda-developers.com/showthread.php?t=1531208
http://forum.xda-developers.com/showthread.php?t=1694017
http://forum.xda-developers.com/showthread.php?t=1769616
http://forum.xda-developers.com/showthread.php?t=1652689
http://forum.xda-developers.com/showthread.php?t=1732268
http://forum.xda-developers.com/showthread.php?t=1754534
EDIT: I have stopped looking for these threads. The more I look, the more I find. If the above threads don't convince you that there is a serious issue with the vivid, then adding more of the same problem will no longer help.
I have added this thread to a growing list of similar threads. Please read the other threads and see if your issues seem familiar.
From what I understand... Don't let your battery run out on this phone. Some Vivids kill batteries.
Solution? None yet.
1. Buy a new battery once a couple of months-ish, until someone figures out why some Vivids are eating batteries. YMMV
*OR*
2. You might invest in a external charger and see if that can bring the "Vivid munched" battery back to life. YMMV
I vote to thread merge the above threads if this proves to be the issue.
I think I might have done it, this time. I installed RebelROM on my phone, as I was curious if it would be more battery friendly. I decided that it wasn't, and went to reboot into recovery to reinstall the nandroid I had made earlier in the afternoon. Oops. My only available recovery was CWM, not TWRP. No problem, I thought, I will just reinstall with CWM. Give me a chance to learn the new recovery, I thought. But, CWM wasn't seeing my external SD card, so I went back and forth to move the nandroid I had made to the internal SD, so CWM could see it. I also installed TWRP to the internal SD, as CWM was proving to be a pain. Unfortunately, TWRP wasn't able to access my internal SD, where the nandroid was now stored, so I tried to recover into an older nandroid. Now, though, the phone won't boot at all, past the screen that describes the phone as an Exhibit from T-Mobile. I can't boot back into recovery. I can't access the drives through the USB cord, either. Any suggestions? Skyukillparanormal has disappeared. Ironically, I'm up in his neck of the woods. Any assistance would be appreciated.
Proud2banoob said:
I think I might have done it, this time. I installed RebelROM on my phone, as I was curious if it would be more battery friendly. I decided that it wasn't, and went to reboot into recovery to reinstall the nandroid I had made earlier in the afternoon. Oops. My only available recovery was CWM, not TWRP. No problem, I thought, I will just reinstall with CWM. Give me a chance to learn the new recovery, I thought. But, CWM wasn't seeing my external SD card, so I went back and forth to move the nandroid I had made to the internal SD, so CWM could see it. I also installed TWRP to the internal SD, as CWM was proving to be a pain. Unfortunately, TWRP wasn't able to access my internal SD, where the nandroid was now stored, so I tried to recover into an older nandroid. Now, though, the phone won't boot at all, past the screen that describes the phone as an Exhibit from T-Mobile. I can't boot back into recovery. I can't access the drives through the USB cord, either. Any suggestions? Skyukillparanormal has disappeared. Ironically, I'm up in his neck of the woods. Any assistance would be appreciated.
Click to expand...
Click to collapse
Pull the battery. After replacing, push down the power button and volume up at the same time. Hole them down for a few seconds. CWM should reappear. Either restore your recovery if it was CWM created or reflash the ROM.
ArtfulDodger said:
Pull the battery. After replacing, push down the power button and volume up at the same time. Hole them down for a few seconds. CWM should reappear. Either restore your recovery if it was CWM created or reflash the ROM.
Click to expand...
Click to collapse
Unfortunately, AD, CWM is not reappearing. I had been holding down the power and volume down keys to no avail. Now I know why. It seems, though, that the power/volume up combo has the same (lack of) effect. Am I screwed?
Proud2banoob said:
Unfortunately, AD, CWM is not reappearing. I had been holding down the power and volume down keys to no avail. Now I know why. It seems, though, that the power/volume up combo has the same (lack of) effect. Am I screwed?
Click to expand...
Click to collapse
If that isn't working there are more serious problems. Try 2 or 3 times as it doesn't always work the first time. You can try ODIN but it's for advanced users. If you don't know how to use it probably not the best option. I hope you didn't brick your recovery because in that case that's the only option that will save you.
ArtfulDodger said:
If that isn't working there are more serious problems. Try 2 or 3 times as it doesn't always work the first time. You can try ODIN but it's for advanced users. If you don't know how to use it probably not the best option. I hope you didn't brick your recovery because in that case that's the only option that will save you.
Click to expand...
Click to collapse
I tried multiple times. I was thinking ODIN might be my only option, but I would never do that myself. I will have to do some research to learn if there is someone near where I am now, or where I live. Thanks for your help. I thought we'd lost you to the S2 fora....
Proud2banoob said:
I tried multiple times. I was thinking ODIN might be my only option, but I would never do that myself. I will have to do some research to learn if there is someone near where I am now, or where I live. Thanks for your help. I thought we'd lost you to the S2 fora....
Click to expand...
Click to collapse
Well soon that will be the case but not yet! Anyway here the link to get ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=2012979&d=1370213005
Instructions here:
2. With your phone powered off, go into the Download (or Odin) mode by pressing the volume down and power buttons. When the screen with the exclamation mark appears, select the volume up button. You should now be in download mode.
3. Connect your Galaxy Exhibit to your PC.
3. Open Odin Multi Downloader v4.43.exe on your PC.
4. click on the OPS-Button and navigate to the folder with the extracted files and select Ancora.ops file.
5. Select the options: One Package, Protect OPS. I did not touch the Auto Reboot, Reset Time options.
6.Click on the One Package-Button and select the md5 file in the extracted folder.
7. Click on the Start button. The flashing process took around 5 minutes for me, at which point the phone rebooted into recovery mode to finish the process. I selected reboot the system.
ODIN flashable CWM here: http://forum.xda-developers.com/attachment.php?attachmentid=1962398&d=1368560948
If you do this, keep in mind I can't be responsible for the results. Otherwise then yes, seek assistance from somebody who can help you in person.
ArtfulDodger said:
Well soon that will be the case but not yet! Anyway here the link to get ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=2012979&d=1370213005
Instructions here:
2. With your phone powered off, go into the Download (or Odin) mode by pressing the volume down and power buttons. When the screen with the exclamation mark appears, select the volume up button. You should now be in download mode.
3. Connect your Galaxy Exhibit to your PC.
3. Open Odin Multi Downloader v4.43.exe on your PC.
4. click on the OPS-Button and navigate to the folder with the extracted files and select Ancora.ops file.
5. Select the options: One Package, Protect OPS. I did not touch the Auto Reboot, Reset Time options.
6.Click on the One Package-Button and select the md5 file in the extracted folder.
7. Click on the Start button. The flashing process took around 5 minutes for me, at which point the phone rebooted into recovery mode to finish the process. I selected reboot the system.
ODIN flashable CWM here: http://forum.xda-developers.com/attachment.php?attachmentid=1962398&d=1368560948
If you do this, keep in mind I can't be responsible for the results. Otherwise then yes, seek assistance from somebody who can help you in person.
Click to expand...
Click to collapse
Thank you for the link, but I can already tell that there will be a problem with that solution, as well. I tried over and over to press the power volume down button. I never saw a screen with an exclamation point. I never see anything until I release both buttons, at which point it starts up normally, but like I said, freezes before the rom loads, or before loading any recovery. There seems to be no difference if I hold down the vol up or the vol down button.
Proud2banoob said:
Thank you for the link, but I can already tell that there will be a problem with that solution, as well. I tried over and over to press the power volume down button. I never saw a screen with an exclamation point. I never see anything until I release both buttons, at which point it starts up normally, but like I said, freezes before the rom loads, or before loading any recovery. There seems to be no difference if I hold down the vol up or the vol down button.
Click to expand...
Click to collapse
Just like CWM, it can take a few tries. Yeah I know that gets old but sometimes it's taken me 4 or 5 attempts before I can get the phone into download mode. Don't give up until you're sure there is nothing to be done. It really just sounds like a soft brick to me.
Maybe if all else fails just say the hell with it, and if you can, get the Galaxy Light on HSN ($150). They'll let you pay in installments if you can't/don't want to pay all at once. You won't be able to root it just yet since it's new, but man maybe it's for the best. At least you will not be able to brick that phone! It has JB on it anyway.
ArtfulDodger said:
Just like CWM, it can take a few tries. Yeah I know that gets old but sometimes it's taken me 4 or 5 attempts before I can get the phone into download mode. Don't give up until you're sure there is nothing to be done. It really just sounds like a soft brick to me.
Maybe if all else fails just say the hell with it, and if you can, get the Galaxy Light on HSN ($150). They'll let you pay in installments if you can't/don't want to pay all at once. You won't be able to root it just yet since it's new, but man maybe it's for the best. At least you will not be able to brick that phone! It has JB on it anyway.
Click to expand...
Click to collapse
Soft brick is what I was thinking, too.
Man, that Galaxy Light is perfect! I have been looking for exactly that phone for a while. When did it come out? And paying in installments makes it even better. Plus, I've now learned my lesson. When I do root that phone, I will be more careful about my flashaholic tendencies. If I get it, that is. We'll have to see.
Proud2banoob said:
Soft brick is what I was thinking, too.
Man, that Galaxy Light is perfect! I have been looking for exactly that phone for a while. When did it come out? And paying in installments makes it even better. Plus, I've now learned my lesson. When I do root that phone, I will be more careful about my flashaholic tendencies. If I get it, that is. We'll have to see.
Click to expand...
Click to collapse
Came out in just the past couple of months. The hardware is so much better than the Exhibit. Again keep in mind, there presently is no way to root it and there are no custom ROMs right now. Activity on XDA for this device has been pretty light, only downside to this phone and the main reason I passed on it.
ArtfulDodger said:
Came out in just the past couple of months. The hardware is so much better than the Exhibit. Again keep in mind, there presently is no way to root it and there are no custom ROMs right now. Activity on XDA for this device has been pretty light, only downside to this phone and the main reason I passed on it.
Click to expand...
Click to collapse
I understand about there being no xda activity. That's a consideration. With 8 GB of internal storage _plus_ a removable SD card, though, I can't see bloatware being a problem for a bit. By then, the Slimroms guys will have gotten ahold of it and put together something, I am sure. Can I live with stock jb? Can I even pick this up? Hmmmmmm...... Food for thought.
ArtfulDodger said:
Well soon that will be the case but not yet! Anyway here the link to get ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=2012979&d=1370213005
Instructions here:
2. With your phone powered off, go into the Download (or Odin) mode by pressing the volume down and power buttons. When the screen with the exclamation mark appears, select the volume up button. You should now be in download mode.
3. Connect your Galaxy Exhibit to your PC.
3. Open Odin Multi Downloader v4.43.exe on your PC.
4. click on the OPS-Button and navigate to the folder with the extracted files and select Ancora.ops file.
5. Select the options: One Package, Protect OPS. I did not touch the Auto Reboot, Reset Time options.
6.Click on the One Package-Button and select the md5 file in the extracted folder.
7. Click on the Start button. The flashing process took around 5 minutes for me, at which point the phone rebooted into recovery mode to finish the process. I selected reboot the system.
ODIN flashable CWM here: http://forum.xda-developers.com/attachment.php?attachmentid=1962398&d=1368560948
If you do this, keep in mind I can't be responsible for the results. Otherwise then yes, seek assistance from somebody who can help you in person.
Click to expand...
Click to collapse
sorry, AD. I have one more question. Once I reboot into recovery mode, can I just reflash a nandroid, or do I have to reload the rom and kernel again?
Proud2banoob said:
sorry, AD. I have one more question. Once I reboot into recovery mode, can I just reflash a nandroid, or do I have to reload the rom and kernel again?
Click to expand...
Click to collapse
You should be able to restore the nandroid. Since you have CWM working again, you can always do a full wipe & flash the ROM again if that doesn't work.
ArtfulDodger said:
You should be able to restore the nandroid. Since you have CWM working again, you can always do a full wipe & flash the ROM again if that doesn't work.
Click to expand...
Click to collapse
My thought, exactly. Thanks.
ArtfulDodger said:
You should be able to restore the nandroid. Since you have CWM working again, you can always do a full wipe & flash the ROM again if that doesn't work.
Click to expand...
Click to collapse
I got everything going to the point where I was to select the md5 file. There was no md5 file in the Odin folder I downloaded and extracted. Where should I look for the md5 file to restart the phone? It also seems that ODIN doesn't recognize that the phone is connected. The phone says it's in ODIN mode, but the program isn't showing any indication that the phone is connected. Thanks.
Proud2banoob said:
I got everything going to the point where I was to select the md5 file. There was no md5 file in the Odin folder I downloaded and extracted. Where should I look for the md5 file to restart the phone? It also seems that ODIN doesn't recognize that the phone is connected. The phone says it's in ODIN mode, but the program isn't showing any indication that the phone is connected. Thanks.
Click to expand...
Click to collapse
Wow, then that means you don't have the Samsung drivers installed. This is getting more complicated. You'll have to have the drivers installed for this device. Unfortunately it might be too late because after you get them installed to your PC, you have to connect your phone and it would have to be in a usable state for the drivers to finish installing if I remember correctly.
Anyay you can still try it, here's the drivers you need: http://www.samsung.com/us/support/owners/product/SGH-T679DBBTMB?
it sure is nice being able to reach out and having people give assistance. thanks guys.
ArtfulDodger said:
Wow, then that means you don't have the Samsung drivers installed. This is getting more complicated. You'll have to have the drivers installed for this device. Unfortunately it might be too late because after you get them installed to your PC, you have to connect your phone and it would have to be in a usable state for the drivers to finish installing if I remember correctly.
Anyay you can still try it, here's the drivers you need: http://www.samsung.com/us/support/owners/product/SGH-T679DBBTMB?
Click to expand...
Click to collapse
Actually, all is not lost. The drivers have been located and installed and the phone is now detected. Exactly which boxes are checked on the ODIN panel? You had mentioned that you didn't touch two of them (Protect OPS and Reset Time, I believe), but those were already selected when the program started. Right now, all 4 options are selected. Is the CWM .tar file all you need for the One Package link, or is there something else?
Proud2banoob said:
Actually, all is not lost. The drivers have been located and installed and the phone is now detected. Exactly which boxes are checked on the ODIN panel? You had mentioned that you didn't touch two of them (Protect OPS and Reset Time, I believe), but those were already selected when the program started. Right now, all 4 options are selected. Is the CWM .tar file all you need for the One Package link, or is there something else?
Click to expand...
Click to collapse
No the CWM file is all you need. After you flash that you're done.
Sent from my Samsung Galaxy Exhibit running AOIP.
---------- Post added at 09:07 AM ---------- Previous post was at 09:05 AM ----------
teerout said:
it sure is nice being able to reach out and having people give assistance. thanks guys.
Click to expand...
Click to collapse
That's what the community should be all about. If I need something I'd hope someone would do the same for me and usually they do.
Sent from my Samsung Galaxy Exhibit running AOIP.
ArtfulDodger said:
No the CWM file is all you need. After you flash that you're done.
Sent from my Samsung Galaxy Exhibit running AOIP.
---------- Post added at 09:07 AM ---------- Previous post was at 09:05 AM ----------
That's what the community should be all about. If I need something I'd hope someone would do the same for me and usually they do.
Sent from my Samsung Galaxy Exhibit running AOIP.
Click to expand...
Click to collapse
Error message saying an unnamed file was not found and operation terminated...
edit-never mind. it's fine. it's doing its thing....
It says "pass" and the 5 min timer is done, but the phone has not rebooted. Is there something else I need to do? Auto-reboot is selected, but it doesn't seem to be booting. Thanks.
This is the first issue with an android phone I've had in a while where I have absolutely no idea what I should do next.
The music player was beginning to stutter a LOT on my install of CM11, and I was having issues where if I selected a song to play on my music player, the volume would suddenly spike to THE HIGHEST LEVEL, and I had to adjust the volume down to get it to reset back to normal. So I figured I'd wipe everything clean and re-install CM11. I didn't just wipe /data and /cache, but I also wiped /system because I believe the issues mentioned above came from a Sony Walkman Mod ZIP I flashed. So after formatting all of the partitions, I went to the "Install" button of TWRP (by the way, I am using TWRP 2.8.1.0) to re-install the CM11 ROM. When I tried to open the CM11 ZIP, TWRP gave me an error saying it couldn't open the file to flash it. I tried using adb sideload as well but adb sideload gave me a similar error.
So I figured it was just an issue with TWRP and that I'd have to boot into fastboot and flash a different recovery image that I know works, like shinobisoft's CWM. I power off the phone, hold the volume up button while plugging the phone back in to the USB port and I am greeted with the Download Mode screen as usual. Here's where things start to get unusual: instead of the phone taking about 1-2 seconds and presenting me with a "Fastboot Ready" line of text or something similar to that, the Download Mode screen hangs on [270] udc_start().
What should I do from here? I tried flashing back to the stock KDZ, but Download Mode needs to be working to do that. Also, I can still get into TWRP recovery just fine, and TWRP can still see all of my partitions.
jasonmerc said:
This is the first issue with an android phone I've had in a while where I have absolutely no idea what I should do next.
The music player was beginning to stutter a LOT on my install of CM11, and I was having issues where if I selected a song to play on my music player, the volume would suddenly spike to THE HIGHEST LEVEL, and I had to adjust the volume down to get it to reset back to normal. So I figured I'd wipe everything clean and re-install CM11. I didn't just wipe /data and /cache, but I also wiped /system because I believe the issues mentioned above came from a Sony Walkman Mod ZIP I flashed. So after formatting all of the partitions, I went to the "Install" button of TWRP (by the way, I am using TWRP 2.8.1.0) to re-install the CM11 ROM. When I tried to open the CM11 ZIP, TWRP gave me an error saying it couldn't open the file to flash it. I tried using adb sideload as well but adb sideload gave me a similar error.
So I figured it was just an issue with TWRP and that I'd have to boot into fastboot and flash a different recovery image that I know works, like shinobisoft's CWM. I power off the phone, hold the volume up button while plugging the phone back in to the USB port and I am greeted with the Download Mode screen as usual. Here's where things start to get unusual: instead of the phone taking about 1-2 seconds and presenting me with a "Fastboot Ready" line of text or something similar to that, the Download Mode screen hangs on [270] udc_start().
What should I do from here? I tried flashing back to the stock KDZ, but Download Mode needs to be working to do that. Also, I can still get into TWRP recovery just fine, and TWRP can still see all of my partitions.
Click to expand...
Click to collapse
Check your PM's
shinobisoft said:
Check your PM's
Click to expand...
Click to collapse
I tried your suggestion of holding the power button but that didn't work. And this is the ONE TIME where I did not make any backups. I couldn't because TWRP couldn't read my /data partition since my phone was encrypted, but before this whole thing happened I formatted /data as EXT4 (which I did before without issue), so I don't think it should be encrypted anymore.
jasonmerc said:
I tried your suggestion of holding the power button but that didn't work. And this is the ONE TIME where I did not make any backups. I couldn't because TWRP couldn't read my /data partition since my phone was encrypted, but before this whole thing happened I formatted /data as EXT4 (which I did before without issue), so I don't think it should be encrypted anymore.
Click to expand...
Click to collapse
What I said about the power button was only to help you get out of fastboot mode so you could try to get to fastboot mode again. LOL.
BTW, I always have a least 2 backups on my sdcard.
You're in a bit of a pickle... I need to think about this for a few...
**BUMP***
I went back to TWRP and tried flashing a PurePerformances .zip and it was able to flash just fine. But even with a fresh download of the CM11 ZIP It still doesn't work. Maybe I'll try flashing a different ROM.
jasonmerc said:
**BUMP***
I went back to TWRP and tried flashing a PurePerformances .zip and it was able to flash just fine. But even with a fresh download of the CM11 ZIP It still doesn't work. Maybe I'll try flashing a different ROM.
Click to expand...
Click to collapse
That's really strange. As I stated in my ROM thread, I haven't changed anything with the last build...
Whoa, just noticed the 12/2 build! I was trying to flash the 10/22 this whole time. I'll try flashing 12/2.
I tried the new build with ADB Side load. It was able to load the zip!
But the device could not be found...
Sent from my MB520 using XDA Free mobile app
jasonmerc said:
I tried the new build with ADB Side load. It was able to load the zip!
But the device could not be found...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
So ADB debugging isn't enabled in TWRP 2.8.1.0? Have you tried another recovery? And why sideload? Why not straight flash?
shinobisoft said:
So ADB debugging isn't enabled in TWRP 2.8.1.0? Have you tried another recovery? And why sideload? Why not straight flash?
Click to expand...
Click to collapse
I can't load another recovery on here without going into fastboot. And I am currently in the process of attempting a straight flash. I am going to save the rom on an SD card on another phone then inset it in the L90.
Sent from my MB520 using XDA Free mobile app
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
jasonmerc said:
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
LMFAO. Lesson learned I hope. LOL
shinobisoft said:
LMFAO. Lesson learned I hope. LOL
Click to expand...
Click to collapse
I've never had this happen to me before. What's weird is the cable was able to transmit power to the device, but not data.
Sent from my LG-D415 using XDA Free mobile app
jasonmerc said:
I've never had this happen to me before. What's weird is the cable was able to transmit power to the device, but not data.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Ya got me. I use the same cable for PC communication. My main charger is a hardwire charger so I basically just leave my data cable attached to my PC. In fact, it's the same cable I started modding my P506 with about 2 years ago .
jasonmerc said:
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
Speaking of feeling stupid, is that the fastboot screen? Like, if I have that screen and it says "hold up till download mode" does that mean I can do fastboot commands like that????? Maybe I DID enable fastboot mode????
whodisname said:
Speaking of feeling stupid, is that the fastboot screen? Like, if I have that screen and it says "hold up till download mode" does that mean I can do fastboot commands like that????? Maybe I DID enable fastboot mode????
Click to expand...
Click to collapse
Yes, that is the fastboot screen in the picture and it passed the UDC START. What you have to do is power off the phone, hold volume up while inserting USB cable to phone, and KEEP HOLDING VOLUME UP until you see something like "fastboot: processing commands". Then you will be in fastboot.
Sent from my LG-D415 using XDA Free mobile app
How long you got to hold it? I been holding it for about 3 min and counting'
---------- Post added at 11:42 PM ---------- Previous post was at 11:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2559363
---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------
For your problem
whodisname said:
How long you got to hold it? I been holding it for about 3 min and counting'
---------- Post added at 11:42 PM ---------- Previous post was at 11:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2559363
---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------
For your problem
Click to expand...
Click to collapse
Its only for a few seconds.
Sent from my LG-D415 using Tapatalk
I don't think I got it. It goes into the screen but if I hold down the button it stays the same. I unplugged the coed and plugged it back in (saw something about that here but I can't find it again) fastball devices comes back with nothing. Fastboot OEM unlock gets "waiting for device" as does fastboot reboot and fastboot flash recovery recovery.IMG (I have twrp in my fastboot folder called recovery.IMG) does download mode look like all the rest of the LG phones I have seen with the S/W UPGRADE IN PROGRESS DO NOT TURN OFF TARGET. Just asking because these things are subject to change!
whodisname said:
I don't think I got it. It goes into the screen but if I hold down the button it stays the same. I unplugged the coed and plugged it back in (saw something about that here but I can't find it again) fastball devices comes back with nothing. Fastboot OEM unlock gets "waiting for device" as does fastboot reboot and fastboot flash recovery recovery.IMG (I have twrp in my fastboot folder called recovery.IMG) does download mode look like all the rest of the LG phones I have seen with the S/W UPGRADE IN PROGRESS DO NOT TURN OFF TARGET. Just asking because these things are subject to change!
Click to expand...
Click to collapse
Download mode and fastboot mode are the same. S/W Upgrade mode is totally different. S/W Upgrade mode is what you should have if you DIDN'T zero out your laf partition. If you did zero out your laf partition, then you should have access to fastboot/download mode.
If the fastboot executable isn't recognizing your device, then you must be in S/W Upgrade mode, or fastboot mode on the device had become corrupted somehow.
I remember reading in the Android Original Development section that you used the script to increase your internal data storage. Does that script mess with the laf partition? If so, there's your issue.
Stock n locked DT 1254 6.0.1 latest ota rom. When turning on phone boots until stock rom supposed to work. Then toast pops up Unfortunately system UI has stopped. When you tap ok it goes away for a few seconds then comes back no matter how many times you try it. You can push power to shut down and after vibrate tap ok and tap shutdown and will shut down. You can boot into fastboot but when you go to recovery it seems to be gone. Followed root junky's restore with rsdlight several times with latest software but didn't work. Using windows 10 pc to do this. Any help appreciated...
Found this will study up...
https://forum.xda-developers.com/ge...torola-usb-drivers-rsd-lite-firmware-t3042687
Had to use an updated win7 PC for it to function correctly and restore the turbo. Must be a bug with win10 and rsd or moto drivers even tho it said it worked...
newbe1droidx said:
Stock n locked DT 1254 6.0.1 latest ota rom. When turning on phone boots until stock rom supposed to work. Then toast pops up Unfortunately system UI has stopped. When you tap ok it goes away for a few seconds then comes back no matter how many times you try it. You can push power to shut down and after vibrate tap ok and tap shutdown and will shut down. You can boot into fastboot but when you go to recovery it seems to be gone. Followed root junky's restore with rsdlight several times with latest software but didn't work. Using windows 10 pc to do this. Any help appreciated...
Found this will study up...
https://forum.xda-developers.com/ge...torola-usb-drivers-rsd-lite-firmware-t3042687
Click to expand...
Click to collapse
You get this fixed?
Which bootloader?
using QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip
sd_shadow said:
You get this fixed?
Which bootloader?
using QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
No caing for very senior father and don't have all the time I want, do have 5-5 from root junky but didn't work. Possibly from using win 10. Am restoring a HP win 7 machine now doing updates and etc to try it. Thanks for checking up on me I appreciate all you've done since droid x days. Will keep updating as I can...
newbe1droidx said:
No caing for very senior father and don't have all the time I want, do have 5-5 from root junky but didn't work. Possibly from using win 10. Am restoring a HP win 7 machine now doing updates and etc to try it. Thanks for checking up on me I appreciate all you've done since droid x days. Will keep updating as I can...
Click to expand...
Click to collapse
Windows 10 can be a problem.
Sent from my Moto E (4) using Tapatalk
@sd_shadow Windows 7 machine did the trick, but getting it updated was tricky, had to make sure security essentials was installed and activated. then updates would happen. Used Motorola device mgr and rsdlite 6.2.4 then flashed QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip. So far signing in ok and restoring apps and data from google, see what gets restored. But still no recovery available. Did I miss something?
newbe1droidx said:
@sd_shadow Windows 7 machine did the trick, but getting it updated was tricky, had to make sure security essentials was installed and activated. then updates would happen. Used Motorola device mgr and rsdlite 6.2.4 then flashed QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip. So far signing in ok and restoring apps and data from google, see what gets restored. But still no recovery available. Did I miss something?
Click to expand...
Click to collapse
Why are you trying to get to recovery, it's mostly useless, on a Motorola
just trying to get it back to factory, not my phone for a friend. Thats all
OK found this for stock recovery when you see a dead andy with no command: In the dead andy screen press vol up + power for 4 seconds. if nothing happens try again, is a little tricky. Seems an update changed how you access recovery. Thanks for the help
newbe1droidx said:
just trying to get it back to factory, not my phone for a friend. Thats all
Click to expand...
Click to collapse
Rsd lite didn't wipe the device?
that's default.
Sent from my Moto E (4) using Tapatalk
---------- Post added at 06:52 PM ---------- Previous post was at 06:49 PM ----------
Motorola Firmware with CFC in the name will wipe data as part of the flashing process.
---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------
Did you verify md5 of firmware file?
Yes all confirmed good, on another site they said after an ota the change took place on accessing recovery, this friend always took ota's. Maybe part of 5-5? I don't know
newbe1droidx said:
Yes all confirmed good, on another site they said after an ota the change took place on accessing recovery, this friend always took ota's. Maybe part of 5-5? I don't know
Click to expand...
Click to collapse
What step are you using to get to recovery?
Sent from my Moto E (4) using Tapatalk
Vol down and power, then vol down to recovery, then power and see the dead Andy with no command, then supposed to push down button hold and push power then let up and will be at recovery. Still waiting for apps and data to finish restoring before I try it.
newbe1droidx said:
Vol down and power, then vol down to recovery, then power and see the dead Andy with no command, then supposed to push down button hold and push power then let up and will be at recovery. Still waiting for apps and data to finish restoring before I try it.
Click to expand...
Click to collapse
sounds right, I've sometimes found the button combination at the no command screen a little tricky.
You may need to adjust how long you press the buttons, to get into recovery.
Sent from my XT1254 using Tapatalk
OK thanks very much, I guess using a win7 machine is what made it work for me. All set to use again. Thanks so much!