Database Users

HELP! Bricked and completely no display on screen, three lights on

I wanted to install DJ sd's 2.1.1 update, so I entered fastboot and installed clockwork recovery and amss.mbn of 2.1 and rebooted. Now nothing is coming on my screen and I cant boot or enter fastboot or recovery. Please help. Heres my screenshot
C:\STREAK>fastboot.exe -i 0x413c flash recovery recovery.img
sending 'recovery' (6144 KB)... OKAY
writing 'recovery'... OKAY
C:\STREAK>fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (6974 KB)... OKAY
writing 'amss'... OKAY
C:\STREAK>fastboot -i 0x413c reboot
rebooting...
please please please help me.... my dell streak is gone.

Hi there, could your battery be empty? plug it in the wall and try charging it back up. if battery is OK then try take the battery out and leave it for 10mins and put it back in then boot up the streak again but ensure the back cover is on properly.

no battery is not empty, 3 home,menu,n cancel lights are on, but no display, and computer is showing qualcomm cdma technologies msm device connected, but no drivers
please help
can I use adb? how to configure n all, its not detecting my dell streak

bhaveshdj said:
no battery is not empty, 3 home,menu,n cancel lights are on, but no display, and computer is showing qualcomm cdma technologies msm device connected, but no drivers
please help
can I use adb? how to configure n all, its not detecting my dell streak
Click to expand...
Click to collapse
I am having the same problem sadly, let me know if you get it working. I will do the same.

You don't say what version you are upgrading from...
Can you still get into clockwork or fastboot?
bhaveshdj said:
I wanted to install DJ sd's 2.1.1 update, so I entered fastboot and installed clockwork recovery and amss.mbn of 2.1 and rebooted. Now nothing is coming on my screen and I cant boot or enter fastboot or recovery. Please help. Heres my screenshot
C:\STREAK>fastboot.exe -i 0x413c flash recovery recovery.img
sending 'recovery' (6144 KB)... OKAY
writing 'recovery'... OKAY
C:\STREAK>fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (6974 KB)... OKAY
writing 'amss'... OKAY
C:\STREAK>fastboot -i 0x413c reboot
rebooting...
please please please help me.... my dell streak is gone.
Click to expand...
Click to collapse

no he cant, thats the problem.

Help
I was upgrading from an factory unlocked 1.6 asia. Nothing is coming on my screen at all, no fastboot, recovery or adb. In xp its showing as qualcomm technologies cdma msm. Please help.

if what you posted is all you did, you didn't read the instructions properly.. you can only got to 1.2.1 from 1.6 after going O2 2.1 -> DJ_S 1.1.1 -> DJ_S 1.2.1 + amss 2.2

XsCode said:
if what you posted is all you did, you didn't read the instructions properly.. you can only got to 1.2.1 from 1.6 after going O2 2.1 -> DJ_S 1.1.1 -> DJ_S 1.2.1 + amss 2.2
Click to expand...
Click to collapse
that doesnt help

XsCode said:
if what you posted is all you did, you didn't read the instructions properly.. you can only got to 1.2.1 from 1.6 after going O2 2.1 -> DJ_S 1.1.1 -> DJ_S 1.2.1 + amss 2.2
Click to expand...
Click to collapse
You hit the nail on the head as to why a lot of people have problems

OK... so you guys messed up by not reading instructions properly. If this gets fixed I'm sure it wont happen again. LoL
Now to help you guys out... I'm no expert at this but at least let troubleshoot..
-Were you guys rooted with Clockwork recovery (custom recovery) before you flashed the baseband? Or Stock recovery, unrooted.
-Clarify exactly what happens when you try to get in to either Fastbootmode (camera and power button down). How about when you try to get in to Recovery mode (Volume button(s) and power button).
-Try updating the drivers on your PC to use the Qualcomm drivers that were provided when Stephen came up with Froyo Beta 1 (the very first one)

Neither does that, but at least I gave a probable reason for the problem for future reference..
ryrules1 said:
that doesnt help
Click to expand...
Click to collapse

True, I was having a number of problems before updating to v. 1.2 it took me a while to even get v1.1.1 up and running, then I tired to update to v.1.2. Then the Dell boot screen lag, never saw that logo again after trying to downgrading to o2 v2.1.
Where can I get the driver, can someone upload it?

forum.xda-developers.com/showthread.php?t=776883
Get the pdf for links and good instructions on how to install them.
ryrules1 said:
Where can I get the driver, can someone upload it?
Click to expand...
Click to collapse

i can fix this in theory if you drop into the #dellstreak irc channel on freenode - looks like your streak is dropping to diag mode as its detected a system issue

XsCode said:
forum.xda-developers.com/showthread.php?t=776883
Get the pdf for links and good instructions on how to install them.
Click to expand...
Click to collapse
Ahh, Yea I have tired those driver, while they install fine, they still dont help to boot into fastboot or recovery. I still cant connect my streak via adb or fastboot.

FIXED thanks to DJ Steve. So happy. Running v.1.2 w/ new baseband!!! awesomea and FAST.

good to hear...

i have the same problem can somebody help me please? no fastboot no recovery

Hi there
Recently, my Streak was bricked. I did wipe via fastboot and get my device bricked.
Fortunately, varriaty period has not expired, so I got new one.
Seems like there are some "leaks" and factrory errors with Dell Streak devices with hw drivers

[Q] Cant Flash Recovery or Restore Bootloader

Hi guys,
I cant for the life of me get my comp to send anything to the phone's bootloader. It just gets stuck on command prompt. Its really frustrating. My drivers are good and everything is in order. Its a new RMA device that I'm trying to root and send the recovery over fastboot but all it does it gets stuck at "sending." Nothing for a long time. I said eff it and tried restoring with a tar file and still nothing!! WTF LARRY?! Would a factory reset and bootloader relock maybe help it? Bootloader is unlocked but just cant seem to get a CWM sent to bootloader or restore it. Please let me know what you guys think. Much preesh.

Try a different USB port on your computer. Preferably one connected directly to your motherboard.
Sent from my Nexus 4

thanks but still nothing.its just stuck on "sending recovery.img." this is ridiculous. when i had the phone connected via mtp i was also having a hard time transferring anything over a MB.

this is what im also getting after unplugging the cable when it's stuck"
sending 'recovery' (7808 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 312.632s

OMG. God Damn USB cable was the problem here. i dont know how USB cables have their on/off days...makes no sense to me.wtf..

[Q] Oem unlock freezes, unseen error

Hello, so i got a asus nexus 7 wifi model, never seen it working. Recovery says booting failed. The one thing that works is fastboot. So i decided to reflash everything. But when i run fastboot oem unlock after about 6mins i get FAILED (remote: () as i understand no error.
I tried 3 drivers, official, naked and from asus nexus toolkit everytime same result. I tried few different pc's diferent usb ports. So maybe someone had a same problem and knows what to try next.
Bootloader version 4.13
full log:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 391.390s
Thx in advance

xz33r0x said:
Hello, so i got a asus nexus 7 wifi model, never seen it working.
Click to expand...
Click to collapse
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.

bftb0 said:
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
Click to expand...
Click to collapse
I didn't pay for it at all yeah have read about apx. Just was wandering is there any other options, or the nand is dead like a brick

[Q] Did I KILL My Nexus 7 2012?

Hi Guys,
I was hoping to upgrade to Paranoid Android today but didn't get so far.
I went into Clockwork Recovery and did a Factory Reset. I then proceeded to wipe the Dalvik Cache and other Cache. Then after that I set it to format the SD Card.
I noticed that while in recovery I couldn't get my SD card to mount in Windows 7. I booted up the Nexus 7 toolkit and chose a sideloading option for the Paranoid Android zips while the Nexus 7 was in CM Mod. I was staring at a frozen screen so I held the power button and down volume for ten seconds.
After a while it got to the point where the Nexus 7 would not boot. It would not show me the Google logo and when plugged in the Battery Recharging graphic did not come on.
After a while I somehow got it to boot up again. I went back into Recovery Mode and tried the sideloading again. I was still looking at a frozen screen so I did the ten second power button reset.
Now it's bricked. There's no Google logo, no option to go into Bootloader or Recovery. There is no graphic indicating that the Nexus 7 is recharging.
It's been hours. I even went so far to open up the back cover, unplug the battery, and then plug it back in. There's nothing.
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
I thought out of everything I did that unplugging and replugging the battery would have reset the system and allowed me back into Recovery Mode.
Not so....
So, I have to ask: Did I kill my Nexus 7?
Is there any way to bring this thing back? I figure I will leave it charging in a 2A Charger overnight. I need some feedback though because I did some research and have seen that a lot of people are had this problem.

ev1lchris said:
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
Click to expand...
Click to collapse
Did you mean ADB drivers? I can't find anything on ADX. I would try uninstalling and reinstalling the drivers and toolkit as a quick step, I'd also consider other toolkits as a possible solution.

I think he meant APX. APX=done. Only solution: take out phone and call ASUS for an RMA number.

I refuse to believe my Nexus 7 is done.

ev1lchris said:
I refuse to believe my Nexus 7 is done.
Click to expand...
Click to collapse
If you haven't already, do a search on APX mode/drivers. You should find that the only way to recover once in APX is if you have made a copy of a file prior to bricking. That file contains a device-specific number that is required to perform the recovery. Additionally, even with that number the process is quite daunting. Good luck should you soldier on.
PS- You should also know that while in APX mode your device is "on" & the battery is discharging to a non-rechargeable state.

Yup, had the same thing happened to my N7 today after it crashed and could not recover to save it. Plugged it on my laptop and it recognized it as an apx device something. I already called asus for rma and I'll be shipping out mine on monday.

There is hope.
Sent from my ZTE V970 using xda app-developers app

First thing I'm going to do once I get my N7 back, make an nvflash blob http://forum.xda-developers.com/showthread.php?t=2455927

I don't think I ever got the chance to flash anything new onto my Nexus 7. I just did a factory reset and formatted the SD card.

It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!

ev1lchris said:
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
Click to expand...
Click to collapse
You returned from APX? This is a first; what did you do? Are you sure you were in APX?

Lucky! curious also on how you manage to get out of apx mode!

thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!

OffcerClancy said:
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Click to expand...
Click to collapse
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
ev1lchris said:
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
Click to expand...
Click to collapse
I think there's a bit of misunderstanding here about APX mode...
To put it simply... APX doesn't necessarily signify hardbrick.
APX is required for nvFlash operations, such as nvFlashing a new bootloader, should the original become erased/corrupted. Indeed, if that where to happen, the Nexus 7 would automatically default to APX mode... and await for somebody to perform such an nvFlash operation.
Currently the only way of performing nvFlash operations on the Nexus 7 is if the user had run the flatline procedure BEFORE damage had occurred to the bootloader. This procedure generates what are called 'wheelie blobs' on a per-device basis, and are unique to each Nexus 7... ie., they are not transferable. They are required to resurrect a dead Nexus 7 with a corrupted, damaged or erased bootloader.
However, you can electively get into APX mode, even with a functional bootloader. Indeed, the latter part of the flatline procedure requires it. How to do this is detailed here.
So, just because your Nexus 7 is in APX mode doesn't necessarily mean it's hardbricked or the bootloader is damaged/corrupted or erased... though, more often than not, that is exactly what it does mean.
Providing you haven't knowingly done anything that might affect the bootloader, pressing and holding the POWER BUTTON for a good 30 seconds or more, might just be sufficient to kick-start a seemingly dead Nexus 7 out of APX mode. I can't guarantee it will work of course... but it's got to be worth a shot.
And it seems to have worked for @ev1lchris.
Rgrds,
Ged.

Sound like by dumb luck he stumbled in and fell assbackwards out of APX mode.

I brick my N7 when flashing 4.3 vía fastboot, ASUS replace the motherboard and its all good now
Enviado desde mi HTC One mediante Tapatalk

After months of use it is non responsive and in APX mode again. However, I have to highly suspect that the battery is playing a role here.
I have a rubber band constantly pressing the power button.
Let you guys know what happens.

I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?

ChiquiNL said:
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
Click to expand...
Click to collapse
If you're still under warranty and you have tried all you can to revive the thing then yes you should call Asus and do a RMA.

Here's an update on my situation...
I installed a battery I bought off of eBay and.... nothing. Still dead.
I'm charging it and I'm going to continue to have the rubber band wrapped around the power button but I think it's pretty much dead.
Such an awesome tablet that I used and depended on every day.
I bought a refurb N7 2013 but I really would have liked to save my N7 and continued using it.

Broken screen, want to turn usb debugging on

Hello,
The screen of my Razr M is shattered into pieces. (so, neither screen, nor digitizer works)
However, pc still detects my phone, thus I managed restore data, but I want to use my phone without screen via pc.
I have this tool downloaded: http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=200837165
Droid @ Screen can not detect my device. My razr is not listed when I enter adb devices command, so I guess, that USB DEBUGGING must be turned off. I can not figure out how to do it.
p.s Currently my device runs on android 4.4.2 rooted.

Lejolasho said:
Hello,
The screen of my Razr M is shattered into pieces. (so, neither screen, nor digitizer works)
However, pc still detects my phone, thus I managed restore data, but I want to use my phone without screen via pc.
I have this tool downloaded: http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=200837165
Droid @ Screen can not detect my device. My razr is not listed when I enter adb devices command, so I guess, that USB DEBUGGING must be turned off. I can not figure out how to do it.
p.s Currently my device runs on android 4.4.2 rooted.
Click to expand...
Click to collapse
This thread has some good information on this... http://forum.xda-developers.com/showthread.php?t=1725858
Basically, you have to have a custom recovery installed and then edit the init.d file to allow USB Debugging.

xKroniK13x said:
This thread has some good information on this... http://forum.xda-developers.com/showthread.php?t=1725858
Basically, you have to have a custom recovery installed and then edit the init.d file to allow USB Debugging.
Click to expand...
Click to collapse
Thanks for the reply. I have already read a similar thread. I want to follow http://forum.xda-developers.com/showpost.php?p=49098574&postcount=11 this instructions and now am trying install a custom recovery.
At the moment my phone is in fastboot mode and is there any way to find out if bootloader is unlocked or not? which recovery do u recommend for 4.4.2?

could not flash custom recovery, which requires unlocked bootloader.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>fastboot flash recovery D:\TWRP2710-RAZR_M-KITKAT.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (8866 KB)...
OKAY [ 0.684s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.954s
Click to expand...
Click to collapse
what can I do?

You can turn it on the phone and try running the motopocalypse exploit from your computer, but I think it requires USB debugging. May be worth a shot though
Sent from my RAZR M (CM Nightlies) from Tapatalk Pro.

xKroniK13x said:
You can turn it on the phone and try running the motopocalypse exploit from your computer, but I think it requires USB debugging. May be worth a shot though
Sent from my RAZR M (CM Nightlies) from Tapatalk Pro.
Click to expand...
Click to collapse
thanks, but I it did not work.