I used fastboot mode from PC and my streak. accidentally i use command
fastboot erase recovery
fastboot erase boot
for the first command, it's well done. but for the second command, error message occured then my streak turned off suddenly. I pressed the power button, and any combination button but nothing happen. then i plugged the usb to my phone and pc, but nothing happen. it wont charge at all. it's totally bricked. may someone help me how to fix it?
You should have read the disclaimers posted on the Wiki as well as in various threads here about using fastboot commands Hell, you could have simply searched for fastboot and found plenty of threads about the Streak and fastboot. Instead, you plunged ahead and destroyed your Streak.
Your only options now are to either purchase a Streak with a broken screen off ebay for its motherboard, or to pay someone to have the Streak resurrected using a JTAG setup. While it's more costly to purchase a second Streak than to have the Streak you own JTAGged, the benefit is in being able to use the Streak as a phone. Streaks resurrected with a JTAG setup lose phone capability.
Related
my Streak5 becomes a brick, after i try use fastboot -w, current sutiation is: can't power on with press power button, and no fastboot press power+crmera, no recovery press power+volUp+VolDown, and no device found once connect to Windows PC and press volUp. someone can help to recover it?
From the Dell Streak entry on the XDA Wiki:
WARNING ABOUT FASTBOOT: Do not attempt to use fastboot erase or fastboot -w on the Streak. The fastboot program on the streak has issues and attempting to erase partitions with it may result in it hanging. If it hangs the Streak will not be able to start up and is likely not rescuable by any manner (including QDL Tool). Use factory reset via recovery mode instead.
Click to expand...
Click to collapse
I wish I had more encouraging news for you, but I'm afraid you need to get a hold of Dell.
You didn't do any research before you tried to flash your Streak so now you pretty much have an unrecoverable brick. You may have some luck with JTAG but it's a 50/50 chance you won't be able to use SIM with it by what I have read in the forums. You can forget about warranty after what you've done to it. SO this is what happens when you flash without having read enough
download streakflash from streakdoid.com that will unbrick it but with base 2.2 drives so you cant go back to 1.6 after you use it, only 2.1 and up. so run streakflash then flash 2.1 or 2.2 recovery and intall update.pkg
Why did you bump a 3 month old thread? more importantly qdl tool will not work here by itself anyway.
You must dissemble the device to fix this specific issue.
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Using the guide from atrix4ghacks.com Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the message
SVF:405;1:2
Failed to boot 0x1000
1- RSD
2-Fastboot
3-NVflash
4- BP HW Bypass RSD
5-BP HW Bypass QC DLOAD
6-BP HW Bypass & Boot AP
7-BP HW Bypass BP only
8- BP SW Bypass RSD
9- Andriod recovery
10- Boot Andriod (no BP)
11- Device UID
12- Console
13- Early USB
14- BP tools
I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS. When I tried to execute the command via Command prompt. I keep getting unknown command errors (yes, directories within the command are good).
Did I just kill my phone?
I have found a few posts here related to this, though I havent found what seems to be a solid answer to a "fix" for this. I would highly appreciate if someone could try to help me with this.
Sorry, I have broken a noob rule (was pretty late when I watched the video), I thank you all in advanced for any help
STOP!!! YOU HAVEN"T KILLED YOUR PHONE JUST YET!
BUT IF YOU SBF YOU WILL!!!
Go into fastboot and repeat all of the unlock commands, reboot and your phone should boot fine after that.
Ok, I will give that a shot!
Hopefully this will work. THANK YOU!
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Grumbles said:
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Click to expand...
Click to collapse
Ugh... from what I heard the battery won't charge while in fastboot mode. You need a standalone charger or a different battery.
So, it doesn't let you get into fastboot at all, huh?
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Grumbles said:
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Click to expand...
Click to collapse
The factory cable would allow you to use the phone without the battery, but it might take more money and time to make then you think.
From what I understand, RSD threw you an error when you were flashing bootloader unlock.
Anyway, you need to find a way to charge your battery and they do the fastboot unlock commands.
If that doesn't work you need to reflash the pudding SBF, (make sure you install the drivers Windows x64 version here prior to flashing and that your phone is recognized in RSDlited)
Get the correct pudding file from here: http://forum.xda-developers.com/showthread.php?t=1136261
Use instructions here (start at step 1) : http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Note that after pudding is flashed successfully and you do the unlock commands, you will get a failed to boot error (seems like what you have now). You need to redo the unlock commands in fastboot and it will fix the problem.
Good luck.!
Alright!
Got the cable completed and works!
So, battery situation is handled, now to follow your steps
THANK YOU! I will report back and let you know.
Ok,
Clearly I am doing something wrong here.....
I followed the instructions using the newest Pudding_preroot.sbf file, and the RSD software sees the device (as a SE flash not a NS if that matters) and will start the flashing process.
Everything works to plan until the phone does its reboot(99$ executed), gives the fail to boot message again. Then wants to start back up in RSD mode.... The RSD application on the otherhand, it seems like its trying to switch the phone to"BP passthrough mode" I do not see that exact option, and after it failed while rebooting to RSD. I tried to move it to fastboot, BP HW Bypass RSD, and finally BP SW bypass RSD... All with the same failure on the RSD screen:
"Failed Flashing Process. Phone (0000): Error switching to BP Pass through mode (0x70BE); phone connected"
I have a funny feeling that this part is obvious, for that I am sorry for my ignorance.
I am pretty sure this thing is toast...
After getting nowhere after step 12, and multiple attempts to install the pudding_preroot file. I did some searching around and found multiple atrix users that would get the same issues. From the flash showing up as SE rather than NE, to the constant failing during the flash via RSD lite, with the same failure errors.
I noticed a "NV flash" option, and found this link that could establish a recovery USB driver to the phone. Do you think this maybe my next best route?
http://forum.xda-developers.com/showthread.php?t=1123429
My factory cable is good, so that option IS open..... Though I am starting to think this is toast.
We cannot use NVFlash unless we get the SBK (signature file). Currently, we do not have it. Motorola does, so plead to them
OK, well now it decided to only mount itself as a unknown APX device... Not sure the whats or whys there. Nothing has changed since the last failures?
Hey man, I think RSD shows the flashing process as failed since it can't fully reboot the phone.
Go into fastboot mode and try doing the unlock commands. (try this twice if ita fails after the first time).
In the worst case scenario if unlocking fails no matter what, you can flash a complete 2.3.4 rom via SBF and that should get you back up and running.
Let us know how it goes.
Remember, if you can get into RSD or fastboot - the phone isn't bricked yet!
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Oh, and it'll run ICS
...or at least boot it! (can't yet post links)
youtube.com/watch?v=dUmuQULyrAk
You can Fastboot the device and only botched the system image correct? Well, in theory all you need to do is boot ClockworkMod Recovery through Fastboot and restore a dump someone has already done. I think their is one in the Dev Forum already.
ThisIsDave said:
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Click to expand...
Click to collapse
Thanks for the info, saved me at least 3 or 4 times after soft bricking my Q. One thing that I found to help is while the device is bricked type in command prompt: adb reboot-bootloader ... this will generate a waiting for device tag then once you see that unplug the Nexus Q and plug it in, within one second as soon as you see a hint of blue on the mute button put your palm over it and it typically boots right into fastboot mode. If not just unplug and repete until it goes.
FYI: Also if you try to launch clockwork from an apk and instal a rom you will almost most definitely soft brick it (tried to sideload AOSP JB ROM and some others with no luck).
Hi guys, I was going through tutorial [HOWTO MAY16]UNLOCK BOOTLOADER, FLASH RECOVERY, INSTALL ROM Atrix 4G Bell/int'l + ATT in the ATRIX 4G GENERAL section and I got to the step 16 OK. Now my phone boots up with the word unlocked. My question is now do I need to go through the "Proper Recovery" steps too? Or is that section only for people that messed up something? If I need to do that how do I do it? Do I need to put my phone into fastboot mode somehow again? I tried to type in those commands fastboot devices, fastboot erase recovery and fastboot flash recovery recovery-atrix5.img but it said <waiting for device> I only had my phone connected to pc with a usb cable. What do I do now?
Here is the link to tutorial http://forum.xda-developers.com/showthread.php?t=1302423
Thanks
Yes, you need to do the "recovery" part too.
Yes, you need to be in fastboot mode, that's why all the commands have "fastboot" in them.
OK but how exactly do I get into the fastboot mode? And when do I connect the usb cable?
ravilov said:
Yes, you need to do the "recovery" part too.
Yes, you need to be in fastboot mode, that's why all the commands have "fastboot" in them.
Click to expand...
Click to collapse
LOL. You must be coming from dummy/feature phones where connecting the USB cable at a specific time in the process mattered.
Reboot phone, hold Vol(-), make sure you have "fastboot" on the screen, confirm with Vol(+). Plug the cord at any given time. (You can leave it plugged in too, it doesn't matter.)
And use search next time, this has been covered countless times.
Great, I'm a total newbe and scared sh$&less that Im gonna brick my phone Anyway one more question if you don't mind. When I try to flash to new kernel or CMx software does it matter what phone (Bell/Att or version of OS) I have? Is it always the same procedure for all phones?
ravilov said:
LOL. You must be coming from dummy/feature phones where connecting the USB cable at a specific time in the process mattered.
Reboot phone, hold Vol(-), make sure you have "fastboot" on the screen, confirm with Vol(+). Plug the cord at any given time. (You can leave it plugged in too, it doesn't matter.)
And use search next time, this has been covered countless times.
Click to expand...
Click to collapse
Always the same. The ROMs are even interchangeable. It only ever matters for unlocking the BL, which you've done already.
Nothing can go wrong if you just pay attention and do exactly as the procedure/guide/tutorial tells you to.
Hello,
Looing for help de-bricking a Hisense A5. Here is the situation.
I successfully rooted from firmware 06.09.06.00. However, stupidly I let Magisk Manager attempt to update via its "recovery partition" method, which resulted in the device going into a boot loop.
Previous flashes have succeeded both with the QFIL method and EDL mode (via adb), as well as with a MicroSD card and TF Mode. However, this time, neither the TF Mode flash is working, nor can I put the device in EDL mode.
Naturally, since it's boot-looping, no adb comms are possible, but I can get the device to boot into Fastboot, where it displays "FASTBOOT" on the screen. Unfortunately, though, none of the fastboot binaries I have found accepts the `reboot-edl` command. I did try manually editing the binary to replace instances of `reboot-bootloader` with `reboot-edl`. With that hacked up binary, issuing `fastboot reboot-edl` no longer errors out, but the device simply reboots and falls back into the boot-loop.
As a last resort, I bought an EDL cable, specifically the one here: Xiaomi Deep Flash Cable 9008 Mode Bootloader Lock Recovery.
Since the device automatically tries to boot when supplying power, I have simply held the button on the EDL cable while plugging into the phone. Variously, long-pressing the button or quickly releasing after plugging in both procude no visibly different effect. The phone simply boot-loops.
Have I overlooked something silly?
Do you have any ideas why I am failing to get the device into EDL mode?
Any help de-bricking my new, fancy phone would be much appreciated.
Cheers,
Hi,
While I am not familiar with your device or with the QFIL method, I was able to recover from a similar-sounding predicament. If the QFIL method is normally implemented when the device is powered down, you may be able to power the device down briefly or have a brief moment during the loop to start the flash process, which should return things to normal.
Dave
Thanks. Was your device also Qualcomm?
AFAIK, flashing this one requires putting the device in EDL mode, and every method I've traid has failed.
Hi again,
Sorry for the mix-up. I was perhaps a bit too hopeful about the QFIL method. Believingly, someone familiar with your system can respond.
Dave
You can try this ways.
https://blog.csdn.net/wang_chaodong/article/details/114366691
and this way
fastboot reboot emergency
@justcopy123 Beautiful. That worked.
For posterity, to enter EDL (QDL) mode, you have to manually jump some JTAG pins on the back of the device.:
1. Remove SIM/microSD card tray. If you forget this step, it will be easy to accidentally break the tray when removing the back cover.
2. Remove back (white) plastic cover;
This is actually somewhat challenging. It just requires force, however. The cover has a small lip and seam with the black screen frame. I used a small flathead screwdriver to carefully (but forcefully!) prise it apart.
3. Attach device to computer with USB cable. This should will power it on.
4. Attach a jumper to the JTAG pins on the rear of device:
[Hisense A5] How to Enter Hardware EDL mode
Hisense A6, A6L, A5 ... can not unlock bootloader you can enter A5 hardware edlmode teardown your phone jump this point with clip(?) and connect usb cable if can not enter you need take off power cable ( right bottom corner) and retry...
forum.xda-developers.com
5. If device is bootlooping, you will need to keep the pins jumped until the beginning of a new boot cycle.