"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.
just_guy said:
"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.
Click to expand...
Click to collapse
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk
xKroniK13x said:
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
I know its been a long time but um here is a belated thank you! I did in fact solve the issue thanks to xda and you, so truly thank you
Related
So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday
So to answer the first question, yes I followed the stickied guide up top, and yes, it successfully flashed the bootloader, wiped all data, and flashed stock ROM all to success. It appears my case is unique. I was told that it could be the battery connection, so I've done no fewer than half a dozen times of taking the back off, resetting the battery connection, and closing back up. It does not appear to be the battery.
I am stuck on the fastboot screen, the one where the android is lying down and blue squares project from an body. It shows me the controls I can make with the volume switches and the selection choice of 'Start'... but I cannot do anything. Before I went to flash I could move through the selection with Vol Up ONLY, but now I cannot even do that. Here's all the mode says:
Code:
FASTBOOT MODE
product name - grouper
variant - grouper
hw version - er3
bootloader version - 4.23
baseband version - n/a
serial number - ###############
signing - not defined yet
LOCK STATE - UNLOCKED
I've pretty spent the past twenty four hours on google searching through all the threads I've seen. They are either all dead, or most of them found the sticky fixed their problem. Has anyone heard of it coming to this?! All I can do is access fastbook VIA a DOS prompt and do fastboot commands, and if I disconnect the tablet from my PC, it'll remain in this mode with the screen on until the battery dies. Charging appears to charge the tablet, but again, no controls work. And yes, the buttons were set properly when I closed my tablet.
Anyone?
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
...Awesome... said:
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
Click to expand...
Click to collapse
I'm just trying to boot up! I don't know what happened, but I haven't been able to use it for school all week!
I cannot boot into the OS. Any time I plug this device in it sends me to the fastboot screen with no controls.
OK I just flashed CWMR 6.0.4.3 and it did not fix the problem.
Any other ideas?
I just repeated all the steps again to see if any of them failed before, they have not worked. So recap:
Stuck in fastboot mode
Android will not boot
Loose battery connection is not the problem
I am able to access fastboot on my computer
I have followed everything from the sticky (wipe everything, flash bootloader, flash image)
I have flashed a new recovery
I am still stuck in fastboot
I cannot control options in fastboot with the volume and power buttons
I can only access fastboot by charging my tablet
The only way the tablet will power down is when it completely depletes it's battery
As far as I can tell, nothing was wrong with the tablet when it was functioning
This happened when I went to charge my tablet, presumably when the battery ran flat running android
If I charge too long the tablet gets fairly hot.
That's about all the information I can provide. Is there anything else I can try? Please, I need a tablet for school and I cannot afford a new one!
My phone is seriously screwed as of right now. The other day I learned there was finally a way to root the XT907 version 98.30.1 and so that's immediately did exactly that. Successfully rooted my phone and decided why not go further and flash a custom ROM to it. Attempted to unlock the bootloader was under the belief that it had done so successfully and attempted to flash a recovery twrp to be exact. Now my phone is stuck in AP Fastboot and i cant do anything with it. I can't turn it off, I can't change the menu to reset it, nothing. I'm fairly new to this so i'm probably missing something but I have taken apart the phone and disconnected the battery cable and left it over night, nothing happened still stuck on the same page. I have tried RSDLite, didn't work. I don't know what else to do. This is all my phone says
AP Fastboot Flash Mode (S)
10.9B(*) 9sha-1e9f557, 2013-09-26 13:20:55)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Fail
then its just usb connection and disconnection. The only thing i know that i can do is replace the mother board and im tempted to do just that but im hoping someone on here can help.
Rsdlite will fix you right up. If it didn't work the first time you probably did something wrong
Sent from my XT907 using Tapatalk
Yep
thewraith420 said:
Rsdlite will fix you right up. If it didn't work the first time you probably did something wrong
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Your probably right at first it didnt do anything but i had just left it plugged into the comp for awhile and came back and it was fixed thankfully. more than likely it was the rsd so thank you
hold volume up and power as soon as it turns of press volume up and down and power and then scoll down to reboot and there you go quick fix after just reinstall the stock file and it will fix the loop
good luck
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
scbikep2 said:
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
Click to expand...
Click to collapse
A clear explanation of the problem alone with everything that you have tried will do for reporting hardware/software issues and also help others help you.
Sent from my Nexus 5 using Tapatalk
last night i got the notification to say that i was able to update to 7.0 and i was so excited that i kinda forgot about xposed and stuff and now
the phone is completely useless it wont turn on it just does nothing, when its charging the white light flashes but still nothing Please help
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
echo92 said:
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
Click to expand...
Click to collapse
nope not seeing it
Hmm, so you're not getting anything showing up in Device Manager (like in this thread https://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943 )?
I am not familiar with the procedure of how to unbrick a device like this, vache has uploaded a blank flash file (https://forum.xda-developers.com/showpost.php?p=70701015&postcount=1975), I hope someone else can guide you on the procedure to unbrick your phone if you need such a file.
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
thankyou it worked perfectly
The same here after update!
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
alemangioni said:
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
Click to expand...
Click to collapse
If fastboot still works, perhaps try this fastboot Nougat image, see if that'll flash? https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
It requires you booting into bootloader (so power down your device, wait 5 seconds then hold the volume down and power button, should then boot into bootloader), so it might flash a working recovery and system onto your device.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
I believe there are two possible reasons...
Either 2-3 minutes forces a fully hard reset.
Or
If you have a really really flat battery sometimes as it charges and then boots up it gets stuck in repeated reboot since effort to boot drains more than it can charge in that time, so holding power button holds boot sequence long enough for battery to gain enough charge to allow boot to work..
Both are just my opinions so might be completely wrong
I think it's Option no1, because in my case the battery was nearly full charged.
Nevertheless... One guy happy to have helped, the other guy happy to have reanimated his phone:laugh: