Info & Fixes: Vibrate 5 Times and Green light flash - EVO 4G General

Alright guys, I know this is actually not an issue with newer evo's but need to confirm some stuff about it so lets start giving you reasons why this happens:
I have only seen this effect Hardware Revision 0001 Evo 4G's that used Unrevoked as an S-off method.
Symptoms?
Won't turn on (Vibrate 5 times + green light)
Asking for Qualcomm MSM drivers when plugged into the computer ( see fix for won't turn on below)
Random S-on
SD card refuses to mount
Unusable in ADB
If you RUU it starts rebooting constantly giving the vibrate 5 times + green light
Fixes?
Wont turn on = Plug into your computer and turn it on
S-on = none
SDCard refusing to mount = run fastboot oem enableqxdm 0 from the Fastboot USB mode while it's connected to your computer.
Unusable in ADB: Use this script with terminal emulator [should fix] here You need to run either script manager or terminal emulator as su and move all the files to the root of your sdcard. Then run sh /sdcard/sdcard.sh.
RUU = None (sorry, I learned there is nothing you can do about this.
Causes: It seems to be consistent with only release day (or close to) evo's that are doing something while flashing, backing up, wiping, or doing something with a custom rom being added or removed from the device. It is possible that it could be a NAND failure and it would actually explain why it requires qualcomm drivers when you plug it in as it's in a forced download mode.
What can you do about it?
Only thing you can do is RUU and take it back to sprint to show them. This is the device's way of bricking itself WITHOUT turning into a paperweight.
Just figured I would post this thread so people who want information on it can find it and fix it. In the past 2 days, I've helped 2 people fix the SDcards and no ADB. Unfortunately unable to get them back S-off or to remove the vibrate and green flash.

Related

Wrong SPL zip file. Now what? [SOLVED]

[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.
If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P
I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!
A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P
The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.
I never use my HTC cable, I use a standard mini USB cable.
P
OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.
Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P
You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!
Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P
I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.
Try doing what modaco suggested and see where that ends up.
modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.
The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?
That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P
'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.
Does the bootloader still show the old version?
P

Read BEFORE flashing!!

Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.

Bricked DHD after ARHD, Sense3.0 and CRT-ScreenON/OFF

Hey there
i debranded, rooted, downgraded and flashed Android Revoltion HD 5.1.7 on my DHD.
Everything worked fine.
Then I flashed some Sense 3 Addons (in the right order)
And everything worked fine.
THEN I flashed the CRT Addon (which was really cool :-D)
And everthing worked fine.
Well, 2 days later, I wanted to shut down my DHD over the night.
It didnt worked well, cant describe it anymore, but I had to push the POWER button more then twice to finally shut it down.
And on the next morning: the DHD only booted to the HTC Logo.
Bootloader was still there BUT the recovery couldnt be loaded.
SO, after that I used the PD98IMG and flashed it over.
But it didnt worked.
And today, the DHD doesnt even turns on.
My plan was, to connect it to the PC and flash a 1.32. via RUU.
But now, its pretty much dead.
It doesnt even lights up, when its plugged in to charge
Is there anything I could do or try?
Hi,
When you remove & reinsert your battery & plug into your PC do you get an Orange charging LED? Don't try to turn your handset on just yet.
Just tried it, and: yes, orange LED is on
/edit:
Well... that means what?
Is there a chance for hope?
or is it bricked, regardless of that
There is always hope.
While plugged in and with the Orange light showing open a cmd window and navigate to your SDK/platform-tools folder
now run
Code:
adb devices
you should get a readout of your HTC device
now run,
Code:
adb reboot recovery
You should now boot into recovery.
Perform a full wipe, system, data, cache, and dalvik cache. Then reflash ARHD again, and reboot once complete.
You will lose all un-backedup data, but your SDcard data is safe.
Damn..
When I type adb devices, it wont find the DHD..
Its definately plugged into your PC & the Orange LED is on?
Yes.
But i have to say, i had similiar problems in the past:
i couldnt use those "one click tools" for S-Off and stuff.
Have you tried to access the bootloader? Vol Down + Power.
Sure.
But that doesnt work. The DHD doesnt do anything...
Instead of the orange LED when plugged in (but only if i not tried to boot)
Btw.:
after unplugging it from the pc: the orange LED stays on. it wont go off..
i tried it on another pc,
adb devices gives out the list,
but my DHD is not listed
How many HTC devices do you have plugged in? The information it returns should look similar to
Code:
<Your SDK\platform-tools path>adb devices
List of devices attached
HT0[B]xxxxxxxx[/B]6 recovery
I have no other HTC devices plugged in.
and in my case, it looks like:
Code:
<Your SDK\platform-tools path>adb devices
List of devices attached
its just empty -.-
it DID worked on my pc - it was listed and i could 'communicate' over usb
but now, its not listed..
Keep trying, once you get a positive return
run
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Preferably recovery first.
is it still possible that it works, even if it doesnt at the moment?
ok, i'm gonna try it then
hope dies last..
try reinstall HTC Sync.
Yep just keep trying. Android is a bit unpredictable this way.
Also, just to make sure you have no other factors involved, take out the Sim card and the SD card. Just to make sure no other factors are involved.
thx for the help mates, but i dont think this gonna work.
tried it several times now, and on 3 different pc's.
it just wont work.
i called my provider yesterday and gonna send it in tomorrow
hope it wont take to long AND it wont cost to much (if the find out that its my fault ; )
If PD98IMG.zip cannot restore your phone (did it even load? It should in every case), nothing can. You have to send it to HTC. I would suggest to try PD98IMG.zip again.
Sorry - Testing -
jkoljo said:
If PD98IMG.zip cannot restore your phone (did it even load? It should in every case), nothing can. You have to send it to HTC. I would suggest to try PD98IMG.zip again.
Click to expand...
Click to collapse
At first still could access bootloader and flashed the PD98IMG
But it didnt work.
And now: i cant access bootloader anymore - dhd doesnt boot.
so yeah, i got to send it in

[GUIDE] Recover Moto Maxx from HARD BRICK

WHAT IS HARD-BRICK?​
The Hard-Brick, translated means device NULL, without function neither one! This happens a lot for forced updating: AS ANDROID 4.4.4 FOR 5xx ....
Most of the time, the cell phone stays in BOOTLOOP (infinite loop), another case as hard brick gets on the black screen with LED access.
Then you ask me?
Wagner, I Brickei my device, how to recover?
YES! There is always a way to recover. More remembering that each device has a way of doing, some are easier and others more complicated. We just need to find the right files.
So let's go!​
MOTOROLA DRIVER
Drivers required for device recognition on PC.
If you have already installed, you do not have to install again.
Download
HAND-BRICK.exe
It will install the drives, recover the cell phone and recover the fastboot.
Download
STEP BY STEP​
1- Turn off the phone and enter the fastboot mode:
Yes, I know the phone is off!
Plus the device is in operation and we need the phone to be turned off and enter the Fastboot mode.
HOW DO I DO THAT? I discovered two ways!
- Fast and easy mode:
OPEN THE PHONE AND DISCONNES THE BATTERY, IT WILL PLACE THE FATBOOT MODE.
IF YOU MAKE ERRORS IN COMMANDS, YOU CAN GET THE FASTEST ANSWER.
- Time-consuming and need patience:
PLUG THE PHONE TO CHARGE "INTO THE SOCKET", THE LED GOES ON, WAITES THE LED OFF.
If the LED does not turn on?
SAFETY THE POWER BUTTON ON + THE DOWN VOLUME, FOR 2 SECONDS OR ACCOUNT UP TO 30!
THEN PLACE INTO THE OUTLET, AND OBSERVE THAT THE LED WILL TURN ON! And wait until the LED turns OFF.
Why did I say I had to be patient?
Well, you're going to do this straight, each made the commands go wrong.
And it will only work again if the phone restarts. Many times the LEDs do not light up among other things like not recognizing on the PC.
HOW DO I KNOW THAT IT WORKS?
When using the unbrick, it will show you a path:
EXP:
C: / USERS / NAME / DESKTOP / MOTO MAXX / PORTUGUESE [BR] / 2 - REVIVER FB / UNBRICK - 5.1> .QBOOT BLANK - FLASH
AND THEN HE SHOWS THE RECOGNIZED FILES.
When of FAILED?
(BLANK-FLASH: **********):
THE FILES WILL BE DEMANDED TO BE RECOGNIZED, THEN IN THIS CASE THE COMMANDS WILL NOT WORK! AND AI FOLLOW THE STEPS AGAIN THE LED!
OK! now that the phone is off and ready to use the unbrick.
Remember, every time you use the unbrick and appear errors, you will have to repeat the STEP to turn on the LED!
2 - Connect the device to the PC, and check that the device is being recognized as QUSB-BULK.
Search the device manager for your PC.
And look in the part (Ports (COM and LPT)) and see if you recognize the device!
3- Install the MOTOROLA + Qualcomm USB drives.
In the Device Manager will shows that the device is being recognized as QUALCOMM.
4- Choose the Unbrick option and execute the files "GO" and wait ends up to 100%
NOTE THAT: THE PHONE WILL BECOME LIFE, AND SHOW THE BOOTLOADER WITHOUT ANDROID!
If it looks like FAIL - You have to repeat STEP 1 to turn on the LED, done that, Test other files
Contains GPT.BIN files from Android 4.4.4 to the latest version 6.0.1!
CASE NOTHING WORKS USE THIS FILE "download"
1 - REMOVE THE ARCHIVE
2- EXECUTE THE FILE WITH THE NAME "GO.bat"
3- NOTHING EVEN? ENTER WITHIN THE "DATE" FOLDER AND EXECUTE THE "01 GO.bat"
4 - NOTHING EVEN? EXECUTE THE FILE "02 GO.cmd"
ONE OF THOSE FILES MUST WORK, BECAUSE THERE IS ONLY THIS FILE!
Now go to the Fastboot option and execute the files "GO"
Contains GPT.BIN files from Android 4.4.4 to the latest version 6.0.1!
THE NEW VERSION IS MARKED WITH RED!
6. Ready! the cell phone will restart with Android 5.0.2, but this one with ERROR does not connect in the WIFI!
To correct this error, turn off the phone
Enter Fastboot mode
Choose a ROM STOCK "here" and install.
If you want a customized ROM First:
Download the new version of TWRP "here"
Choose a CUSTOM ROM "here"
And the GApps according to Android Chosen "here"
READY! YOU CAN BE HAPPY AND INSTALL ANY ROM THAT YOU WANT.
REMEMBER THAT THE ROM Stock 4.4.4 CAN NOT BE UPDATED OVER.
Hope this helps!
do not forget to leave your LIKE and SHARE, leave your comment than you found.
Hi Wagner! The "HAND-BRICK.exe" download link isn't working. Could you provide a new download link, please? Thanks in advance!!!

Issues with Recovery Mode, Bootlooping, Flashing, EDL, and ADB Commands

Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?

Categories

Resources