Database Users

Unbricking mytouch/g1 ( soft bricks only but no harm trying )

I found a site with someone who bricked their phone but found a loop hole. I have never bricked my phone and hoping i never will but for those who have bricked their phone here are some steps to try to unbrick it! HOPE IT HELPS! SEND FEED BACK!!
So you can’t access bootloader or recovery and the only thing that works is the blue led trick when pressing trackball + power button??
Try the procedure below.
Step 1: Turned Phone off by taking out the battery.
Step 2: Prepared SD card
Put SD card in card reader and formatted it as FAT32, copied the DREAIMG.nbh onto it.
Or try Sapphimg.nbh
Step 3: Put SD card back in phone
Step 4: Hold Vol down + Power + track ball together and put battery to start phone
Step 5: Run update
IF THAT DIDNT WORK!
TRY THIS!
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.
The G1 screen will hang there for a good minute or two, but be paticiant, it will boot. Now you have a choice. Try to hack your phone again, because you're in the correct state to have another go, or, you can stick with the official Android. Now if you choose to stick with the official Android, here's what you do.
Step 1: Upgrading to Android 1.0 RC33
Download the file signed-PLAT-RC33-from-RC30.zip
Rename the file to update.zip and copy it to your SD card
Reboot your phone into recovery mode. Power off the phone first and then hold down the Home key while powering it back on.
The recovery mode is finished loading when you see the ! mark inside the triangle. Press Alt + L to display the list of options.
Press Alt + S to flash the file update.zip.
Wait for the update to apply. Your phone may reboot during this process so be patient.
Press Home + Back if prompted to reboot your phone.
Step 2: Upgrading to Android 1.5 CRB43
Download the file signed-kila-ota-148830.de6a94ca.zip
Repeat the steps from above to flash the update file.
Step 3: Upgrade to Android 1.5 CRC1
Download the file signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
Repeat the steps from above to flash the update file.
Step 4: Upgrade to Android 1.6 DRC83
Download the file signed-kila-DRC83-from-CRC1.c41b93c1.zip
Repeat the steps from above to flash the update file.
PM FOR THE DIRECT WEBSITES!

sad cause this will get locked soon.

domuhhnic said:
sad cause this will get locked soon.
Click to expand...
Click to collapse
why? all we need is someone who can confirm this is true on xda and it will be stickied EVERYWHERE

LOCKED?
domuhhnic said:
sad cause this will get locked soon.
Click to expand...
Click to collapse
Why will this get locked??

Yuppie
oshizzle1991 said:
why? all we need is someone who can confirm this is true on xda and it will be stickied EVERYWHERE
Click to expand...
Click to collapse
Exactly .. but i dont know anyone with a bricked phone so i cant ask them if it works.. if it gets locked (whatever that means) i'll repost it!

id be interested to see if this works... although its assuming you have a dream/g1 .. did you post this in the g1 section?

POST?
digitaljeff said:
id be interested to see if this works... although its assuming you have a dream/g1 .. did you post this in the g1 section?
Click to expand...
Click to collapse
Yes, I have a HTC MAJIC/MYTOUCH .. nope i have not posted it there but i will now

i tried to update radio and now :
So you can’t access bootloader or recovery and the only thing that works is the blue led trick when pressing trackball + power button??
Try all of this methods , but no result..
phone just shows htc magic when i turn it on usually, and nothing!
what can i do?

...
Im still looking of ways to unbrick phones

Possible hint!
Has anyone tried using adb .. Reflashing the recovery img??

...another hint..
kemimarie said:
Has anyone tried using adb .. Reflashing the recovery img??
Click to expand...
Click to collapse
run fastboot boot recovery-image.img or whatever you named your recovery image. It'll display "waiting for device..." message just keep pluging it in, unplugging, popping the battery and eventually your device will respond and boot into recovery.
Someone bricked and i did it... twice trying to flash the eng 2010 SPL. It worked the third time and my device is up and running again with an engineering SPL.
if your device is stuck on the first splash but displays in red "Fastboot USB" message in the upper left corner of the screen, DO NOT power it down. run the above mentioned command and reflash.

deleted... double post.

Found another hint
ch3w said:
confirmed...
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
Click to expand...
Click to collapse
try that on your g1/mytouch!

kemimarie said:
try that on your g1/mytouch!
Click to expand...
Click to collapse
this method worked on my second bricked magic, still trying it on the first one but... no luck yet. i had the same problem with both of them tho

kemimarie said:
run fastboot boot recovery-image.img or whatever you named your recovery image. It'll display "waiting for device..." message just keep pluging it in, unplugging, popping the battery and eventually your device will respond and boot into recovery.
Someone bricked and i did it... twice trying to flash the eng 2010 SPL. It worked the third time and my device is up and running again with an engineering SPL.
if your device is stuck on the first splash but displays in red "Fastboot USB" message in the upper left corner of the screen, DO NOT power it down. run the above mentioned command and reflash.
Click to expand...
Click to collapse
fastboot boot recovery?
boot.img and recovery.img are two totally different things.
The recovery (amon_ra is preferred)
The boot.img is where the kernel, ramdisk, etc resides.
you must've meant fastboot flash boot boot.img
or
fastboot flash recovery recovery.img
but not both.

ch3w said:
this method worked on my second bricked magic, still trying it on the first one but... no luck yet. i had the same problem with both of them tho
Click to expand...
Click to collapse
YAAYY!! Im glad to hear you say you had some success!

Binary100100 said:
fastboot boot recovery?
boot.img and recovery.img are two totally different things.
The recovery (amon_ra is preferred)
The boot.img is where the kernel, ramdisk, etc resides.
you must've meant fastboot flash boot boot.img
or
fastboot flash recovery recovery.img
but not both.
Click to expand...
Click to collapse
I just copied and pasted from a website.. THEY did that and it worked for them lol

bricked Mytouch3g
Bricked mytouch3g -- brandnew phone. Just tried to flash cyanogen test3 and everything went fine but then I rebooted and all I have is vodafone boot screen, nothing else works but the blue led which will not load any img. adp doesn't work it never detects a phone no matter what you do. It was the first flash too. Crazy how HTC didn't make a built in hard reset like you have on windows mobile phones. You wonder if they want people to crash there phones so they have to replace them ect etc.

Hello.
My phone has the same problem.
Anything that is needed done. But no no avail.
My phone is brick.
Help help help

Mod edit: not dev related, moved to general

[Q] Unbricking Zte Blade 3

First of all thanks for not caring. I spend days on Internet trying to find a solution. I have Blade which I bricked thanks to my noob skills with flashing and similiar ****. I just want my normal phone back. Couldn't give a **** bout roms anymore. Sorry for the lang but Im mad. When I boot it up it just sits there on green android logo not going past. I can enter download mode if it matters. As soon as I back it up Im getting rid of cwm mode and bull****. I use my sister phone to transfer files on my sd card. I cant enter my recovery mode since I installed that **** of cwm.When I try the key combo-android logo stuck with red light on. My phone has 90-100% battery Im sure. I need a solution where I can do something from pc with download mode or something that will automatecly start when I boot up my phone that I transfered on my SD card. Please guys let me have some sleep. I've been staying all night long just to unbrick it. Dont mention any flashing rooting ****ing...I developed alergy to those words. I want it simple ..please...any help is appreciated. And sorry for my language.

Solution.
I Love The Register Video said:
First of all thanks for not caring. I spend days on Internet trying to find a solution. I have Blade which I bricked thanks to my noob skills with flashing and similiar ****. I just want my normal phone back. Couldn't give a **** bout roms anymore. Sorry for the lang but Im mad. When I boot it up it just sits there on green android logo not going past. I can enter download mode if it matters. As soon as I back it up Im getting rid of cwm mode and bull****. I use my sister phone to transfer files on my sd card. I cant enter my recovery mode since I installed that **** of cwm.When I try the key combo-android logo stuck with red light on. My phone has 90-100% battery Im sure. I need a solution where I can do something from pc with download mode or something that will automatecly start when I boot up my phone that I transfered on my SD card. Please guys let me have some sleep. I've been staying all night long just to unbrick it. Dont mention any flashing rooting ****ing...I developed alergy to those words. I want it simple ..please...any help is appreciated. And sorry for my language.
Click to expand...
Click to collapse
Calm down dude. If you can get in Download Mode , you are lucky. I even know people who had not get to Download Mode and had began to cry , cause the phones were only 3-4 Weeks old. Back to your problem.]First download here the stock rom.[/URL]
Then you need the Android SDK and the platform-tools from Google , so download it , cause you need ADB. Click here to get Android SDK.Then you need the ZTE drivers. Click here to get the drivers.Now get into download mode and connect the device via USB to your PC. Copy the boot.img (or recovery.img if it is in the ZIP package) and flash it via Fastboot (command: fastboot recovery.img) . Now you got the stock recovery. Now push the FULL update.zip at your sdcard , and now go to recovery , and update from sdcard , choose the update.zip ... Flashing takes a while. DO NOT WIPE ANYTHING BEFORE OR AFTER CHOOSING "UPDATE.ZIP" . Now your Phone should fully works normally

Hello, I have also bricked ZTE BLADE 3(I flashed a wrong kernel....). It only turns the red light on when i turn it on and blank screen, does not respond to vol + and vol - key, no android logo, but when I connect it to the computer via usb in Device Manager a COM port opens with the name ZTE DFU(Diagnostic interface). If anyone has experience of reviving this device from this mess? Thank you for your time

Zmaj5 said:
Hello, I have also bricked ZTE BLADE 3(I flashed a wrong kernel....). It only turns the red light on when i turn it on and blank screen, does not respond to vol + and vol - key, no android logo, but when I connect it to the computer via usb in Device Manager a COM port opens with the name ZTE DFU(Diagnostic interface). If anyone has experience of reviving this device from this mess? Thank you for your time
Click to expand...
Click to collapse
Your download screen is destroyed , but you are still able to get into it.
Try to get into it and flash the kernel with fastboot , the screen will bug during fastboot procedure.

My screen is completely blank and black, just the red light showing when i turn it on and it is always on. It does not respond on power button + vol. down, power button + vol. up, power button + vol. down + vol. up. When I connect it to the computer it does not show me a usb flash drive although I have the zte drivers installed and another sd card inside, but in Device Manager I can see it as a COM port(DFU) Diagnostic Interface. I tried accessing the bootloader via adb but it doesnt even list it with command "adb devices". I also tried flashing the recovery image via "fastboot recovery recovery.img" and "fastboot recovery.img" and still no luck, it just hangs at "waiting for device"...

Zmaj5 said:
My screen is completely blank and black, just the red light showing when i turn it on and it is always on. It does not respond on power button + vol. down, power button + vol. up, power button + vol. down + vol. up. When I connect it to the computer it does not show me a usb flash drive although I have the zte drivers installed and another sd card inside, but in Device Manager I can see it as a COM port(DFU) Diagnostic Interface. I tried accessing the bootloader via adb but it doesnt even list it with command "adb devices". I also tried flashing the recovery image via "fastboot recovery recovery.img" and "fastboot recovery.img" and still no luck, it just hangs at "waiting for device"...
Click to expand...
Click to collapse
When the red light still comes up , you still got chances to get it fixed...

I think so too.. but how? The only method left is JTAG... I saw a thread about using a TPT image to flash low level firmware using ZTEflash.exe but that thread was for ZTE Skate I think, I could not find the tpt.img file for zte blade 3.... Is there any other method via usb cable? Or send it to the shop?

Well, here is my situation:
Got a BLADE III Pro
Tried to root it and i played with few tools found on xda and other places (android forums). No luck at all. Tried to flash a CWM and NO LUCK neither. Tried to go back to flash stock CWM (as i was afraid of bricking it), searched for stock cwm and there is my BRICKED phone. When trying to hold volume down and power botton (both for over 20 seconds even) it will show a green android and its stuck there for hours. When trying to go to fast boot mode the same happens (with volume up and power botton).
While trying these two options the PC (Windows 7 64 bit) wont recognize the phone pluged in.
The only way the PC makes a sound is when i hold both volume up and down bottons and power it or plug it in the PC (without the battery even).
I need to know how can i fix it to boot only. PLEASE. Is this a "throw on can" phone now or it can be brought to life? PLEASE TELL ME PEOPLE.
pm me or any info as soon as you guys can.
I will respond to any question you might have.
Thank you in advance.

I have sent my phone to the shop and they said that they would need a jtag box specific for this model or a new motherboard for zte blade 3.... I think this the end for my zte blade 3

My Storm is dead

I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help

1- turn off your phone
2- plug it on pc with vol + pressed
3- now type on cmd "fastboot devices" normaly it appear
4- if you haven't unlocked bootloader unlock it with the command "fastboot oem unlock"
5- download cyanogen recovery from cyanogenmod site !!AND CHECK IF WRITEN RECOVERY FOR KIPPER!!
6- flash it via fastboot, type in cmd "fastboot flash recovery cyanogenmod-recovery-kipper.img
And wait
7- now type fastboot reboot
And press vol - during the reboot
8- now you're in cyanogen recovery, so flash the ROM and do not forget to wipe

bobslesbricoleurs said:
1- turn off your phone
2- plug it on pc with vol + pressed
3- now type on cmd "fastboot devices" normaly it appear
4- if you haven't unlocked bootloader unlock it with the command "fastboot oem unlock"
5- download cyanogen recovery from cyanogenmod site !!AND CHECK IF WRITEN RECOVERY FOR KIPPER!!
6- flash it via fastboot, type in cmd "fastboot flash recovery cyanogenmod-recovery-kipper.img
And wait
7- now type fastboot reboot
And press vol - during the reboot
8- now you're in cyanogen recovery, so flash the ROM and do not forget to wipe
Click to expand...
Click to collapse
Appretiate your kind response
Unfortunatly, this wont work for my case, I think I need a way to unbrick the phone, cant access to fast boot, my pc can see the phone only as CUALCOMM chip.

What's OS you're using?

bobslesbricoleurs said:
What's OS you're using?
Click to expand...
Click to collapse
Windows 7 X64

Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?

bobslesbricoleurs said:
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
Click to expand...
Click to collapse
Sir, I really appreciate your concern, but believe me it's a hard brick case, so I cant access any usual boot neither fastboot nor recovery.
I wish someone tells me how to unbrick it.

Plug usb and try two vol button in same time, tell me if vibrate, if not let it charge during 1 hour and retry

bobslesbricoleurs said:
Plug usb and try two vol button in same time, tell me if vibrate, if not let it charge during 1 hour and retry
Click to expand...
Click to collapse
Nothing happened, even after recharging

There is a probleme, you've just flashed the swift ROM, not really a reason to brick...
And the swift have same partition like the storm.
Where do you live? Me in france

bobslesbricoleurs said:
There is a probleme, you've just flashed the swift ROM, not really a reason to brick...
And the swift have same partition like the storm.
Where do you live? Me in france
Click to expand...
Click to collapse
I'm in Egypt
When i googled my problem i found the same happend with oneplus one phones,
The problem was hard brick due to wrong rom, and windows can see the phone only as Cualcomm hs-usb Qdloader 9008, same as my case. And the problem solved for the oneplus one, so I have some hope that my phone will come back to life.

kazparoph said:
I'm in Egypt
When i googled my problem i found the same happend with oneplus one phones,
The problem was hard brick due to wrong rom, and windows can see the phone only as Cualcomm hs-usb Qdloader 9008, same as my case. And the problem solved for the oneplus one, so I have some hope that my phone will come back to life.
Click to expand...
Click to collapse
Good news, if your problem is solved please post how you do on this thread or new to explain the tutoriel

bobslesbricoleurs said:
Good news, if your problem is solved please post how you do on this thread or new to explain the tutoriel
Click to expand...
Click to collapse
Ofcourse I will.

bobslesbricoleurs said:
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
Click to expand...
Click to collapse
Hi I have a similar problem, I installed the correct cyanogenmod and recovery and it was working fine, but after today's update it shows the bootup logo and then gets stuck in a black flickering screen.
I can't seem to be able to boot neither to the recovery nor to the fastboot mode, no volume key combination seems to work.
All adb says is the device is unauthorized and fastboot doesn't seem to be able to even see the device.
I tried the vol+ and vol- and power and it does vibrate, if I use the vol+ only it seems to get stuck forever on the vendor's bootup logo and the device doesn't seem to be seen neither from fastboot nor adb.
Is there anything else I can try to unbrick it or is it gone?
Thank you in advance for your help

kazparoph said:
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
Click to expand...
Click to collapse
wow, exact same thing, kept saying my device is a crackling device so i flash a crackling rom, it went dead flash!

Please stop flashing crackling roms on kipper.
If it reports crackling is wrong maybe ota somehow messed up.

kazparoph said:
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
Click to expand...
Click to collapse
Have you tried to hold together for about 20 seconds the power button and sound button less ?

Strugglin
I have same problem, either stuck in bootloop (to the wileyfox screen and back to black) or just off. ONLY red charger light shows when I plug it in. Fastboot not working, recovery boot not working... NOTHING is working. On top of that I haven't even installed any roms, not rooted etc. All I did was reboot when it froze on a silly game I didn't mean to open WTFF

wileyfox dead
I have the same problem, bootloop, qualcomm 9008 no fastboot or adb recognition. I'm guessing was the OTA update cos I didn't install any roms at all. TOTAL waste of money, zero support too. It's a non-starter DO NOT BUY!!!!

maxxie00 said:
Hi I have a similar problem, I installed the correct cyanogenmod and recovery and it was working fine, but after today's update it shows the bootup logo and then gets stuck in a black flickering screen.
I can't seem to be able to boot neither to the recovery nor to the fastboot mode, no volume key combination seems to work.
All adb says is the device is unauthorized and fastboot doesn't seem to be able to even see the device.
I tried the vol+ and vol- and power and it does vibrate, if I use the vol+ only it seems to get stuck forever on the vendor's bootup logo and the device doesn't seem to be seen neither from fastboot nor adb.
Click to expand...
Click to collapse
Same here , interesting is the different device status between linux and windows,
at debian it's "offline" - at windows "unauthorized".

Help bricked my p8 lite

i tried rooting my phone huawei p8 lite but got stuck at installing super su now i cannot start my device ..i cannot boot into flash mode or recovery ..i need help ...it wont even charge

pepeline said:
i tried rooting my phone huawei p8 lite but got stuck at installing super su now i cannot start my device ..i cannot boot into flash mode or recovery ..i need help ...it wont even charge
Click to expand...
Click to collapse
What's your build number what version of supersu did you try to flash?
Shutdown your device, put your current build onto 'dload' folder in the sdcard and press the following key combo: POWER, VOL-UP & VOL-DOWN, it should enable automatic update process

amageek said:
What's your build number what version of supersu did you try to flash?
Shutdown your device, put your current build onto 'dload' folder in the sdcard and press the following key combo: POWER, VOL-UP & VOL-DOWN, it should enable automatic update process
Click to expand...
Click to collapse
My phone restarts right at the logo when i press power vol up and vol down

pepeline said:
My phone restarts right at the logo when i press power vol up and vol down
Click to expand...
Click to collapse
Shut it down amd press those 3 keys combo.. upon seeing Huawei Logo and vibration, release the Power key while holding the other 2... That ought to do it

Man, your phone is badly bricked. If you don't have at least access to fastboot, then you're screwed.

Good for me to I have the same problem. I was trying to get to stock ( I have made it several times), but the last time was a fail... The whole process of sending firmware was ok. then a reboot and brick.
Now the huawei screen and the short vibration appears and shutdown.
I was trying everything.
In device manager the phone is displayed as mobile devices \ volume f:\ (drive letter)
in connected devices the phone is detected as
hi6210sft
Phone is not detected in fastboot or ADB.

I met this problem yesterday(I hope the identical ). Because I have two booting animations, one from Vodafone, I guess I shutdown early during installation. It just froze. Then it didn't boot and stock recovery didn't help
My solution needs some recovery software like twrp. Press three buttons at the same time until twrp mode. Copy zip file for SuperSU to phone or sdcard, then flash it. After that my phone works again.
You mentioned that you cannot start recovery. Try more. After installing twrp, starting it is quite annoying. Sometimes it just doesn't start or stock recovery starts. An alternative way is to go to whatever mode, and try adb or fast boot to reboot to recovery. Pressing button requires techniques which j don't have

I can't enter TWRP non combination is working for me. Installing firmware using dload from sd card also.

okay if non of these worked you can try flashing the whole update.app file by fastboot..
tools you will need
1- download the official huawei firmware from the official site
2- download Huawei Update Extractor
3- download minimal adb and fastboot
check the unbricking chapter of this thread
Note: to get in fastboot make sure you connected your phone to computer and press the vol down and power down buttons.. if none of these worked your phone is hard bricked .-. .. try opening the phone and reconnecting the battery worked with someone
if you need any help just pm me or replay on this thread hope that help you

Ok thx. I have already opened the phone to reconnect the battery
And then I was trying the combinations;
Battery connected vol- +power - Huawei logo and vibration and shutdown, no fastboot
Battery disconnected, vol-+power and connecting cable to phone - the same
Battery disconnected combination vol + vol - + ppwer, with sd card dload, the same
Battery connected combination vol + vol - power, sd card dload, the same
Any other suggestions?
The phone is recognized in Windows in device manager as mobile device as volume with a letter, I cant change the drivers to the right ones. I can't enter the storage it's unrecognized format.

Any other suggestions?

mercom said:
Any other suggestions?
Click to expand...
Click to collapse
it is easy to suggest others.. I too advised you.. but today i am facing the same problem...
what I tried:
Reinstalling the same ROM using dload method
Upgrading to other ROM (using both dload and flashing 4 image method)
Downgrading
Restoring from the backup
At one point, the phone booted up all well except the Wifi Module... So I flashed another ROM and stuck again...

the worst thing that I don't have any connection to fastboot Each firmware installation method fails

mercom said:
the worst thing that I don't have any connection to fastboot Each firmware installation method fails
Click to expand...
Click to collapse
yes, mine too... or I could say flashing succeeds but there's some problem with the boot partition... will get my phone today from the Customer Care and try again (if they can't repair).
you can try removing the back cover and unplugging the battery... that is one of the few things I will do today as I get my phone back..

mercom said:
the worst thing that I don't have any connection to fastboot Each firmware installation method fails
Click to expand...
Click to collapse
ok made it back.. just flashed the boot.img from b594 (the one I was using when my mobile got bricked)... somehow made it back. But now I am having a problem with the battery. It doesn't charge when the device is switched on, only when the device is switched off... will see for few days, if there's problem will take it back to service centre again

I have already removed back cover and was trying to reconnect the battery to do clear run. But the only thing is discovered in windows is a driver for storage and I can't change the driver to ADB or FASTBOOT
Now I have connected phone w PC on adb devices I see only emulator-5554 device. In Device manager I see the storage as a Mobile Device.
Nope it was Bluestacks

mercom said:
I have already removed back cover and was trying to reconnect the battery to do clear run. But the only thing is discovered in windows is a driver for storage and I can't change the driver to ADB or FASTBOOT
Now I have connected phone w PC on adb devices I see only emulator-5554 device. In Device manager I see the storage as a Mobile Device.
Nope it was Bluestacks
Click to expand...
Click to collapse
Switch off your device and then connect it to PC but just hold the volume- key.. that should get you in fastboot mode... I did that and then flashed the boot.img of the current ROM. This should boot it up...

Nope it doesn't work I was trying it already

Huawei P9 lite stuck at booting "Your device is booting now..."

I unlocked my phone, and updated with wrong update.app. It booting non-stop, when I press 'power' - it's vibrate 2 times, show a logo and then "Your device had been unlocked and can't be trusted". I can't even go to Fastboot & Rescue Mode! Computer through USB don't see a phone. Soooo.... I'm stucked. What I can do ?

Plug your phone on pc.
Just after see the first charging screen launch:
"Fastboot reboot bootloader"
Try again more, it's work..

Therand said:
Plug your phone on pc.
Just after see the first charging screen launch:
"Fastboot reboot bootloader"
Try again more, it's work..
Click to expand...
Click to collapse
hm, don't work..

zukovsromsis said:
hm, don't work..
Click to expand...
Click to collapse
here will be a video - https://www.youtube.com/watch?v=2PtIJXZx6kE

zukovsromsis said:
hm, don't work..
Click to expand...
Click to collapse
Connect your phone to PC, hold the VOLUME DOWN button and then press and hold the POWER for 10 seconds, phone will reboot ,( with pray in fastboot ).

zukovsromsis said:
here will be a video - https://www.youtube.com/watch?v=2PtIJXZx6kE
Click to expand...
Click to collapse
I not see correctly.
On your video, your finger push power button or not?

bozka1 said:
Connect your phone to PC, hold the VOLUME DOWN button and then press and hold the POWER for 10 seconds, phone will reboot ,( with pray in fastboot ).
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=GsUqPRd3QFY Don't work ((((

Therand said:
I not see correctly.
On your video, your finger push power button or not?
Click to expand...
Click to collapse
In first video I didn't, in second - yes.

zukovsromsis said:
In first video I didn't, in second - yes.
Click to expand...
Click to collapse
Not push any buttons..
Just plug phone on PC and wait 3 sec*, launch fastboot command : "fastboot reboot bootloader"
*3 at 7 sec, try several times

Therand said:
Not push any buttons..
Just plug phone on PC and wait 3 sec*, launch fastboot command : "fastboot reboot bootloader"
*3 at 7 sec, try several times
Click to expand...
Click to collapse
it says "<waiting for any device>" and nothing more

zukovsromsis said:
it says "<waiting for any device>" and nothing more
Click to expand...
Click to collapse
Try waiting till the battery is fully discharged, then press a hold Volume down and connect phone to PC ,hold Volume down until your phone will turn on ( it may take 5 - 7 minutes ).
Or, try flash stock firmware via dload (create a folder on the root of the sd card called dload , then put the stock huawei uppdate.app in the folder then shut down and hold volume up, down and the power button at the same time and it will flash the stock firmware).

zukovsromsis said:
it says "<waiting for any device>" and nothing more
Click to expand...
Click to collapse
Is very strange, your bootloader has not disappeared...
You have try with HiSuite >> repair phone?
Follow on screen instructions, HiSuite is able to boot phone on bootloader.
Last try with command:
Tipe "fastboot reboot bootloader", you see "waiting for any devices", plug your phone on PC and wait or push power button if you see the warning phone can be trusted...

Therand said:
Is very strange, your bootloader has not disappeared...
You have try with HiSuite >> repair phone?
Follow on screen instructions, HiSuite is able to boot phone on bootloader.
Last try with command:
Tipe "fastboot reboot bootloader", you see "waiting for any devices", plug your phone on PC and wait or push power button if you see the warning phone can be trusted...
Click to expand...
Click to collapse
I really don't know what to do... The problem is that my computer don't see my phone, not ADB, not HiSuite. Any button combinations don't work too. The only screen appears is that in video. I really stucked.

bozka1 said:
Try waiting till the battery is fully discharged, then press a hold Volume down and connect phone to PC ,hold Volume down until your phone will turn on ( it may take 5 - 7 minutes ).
Or, try flash stock firmware via dload (create a folder on the root of the sd card called dload , then put the stock huawei uppdate.app in the folder then shut down and hold volume up, down and the power button at the same time and it will flash the stock firmware).
Click to expand...
Click to collapse
Naah... I holded 10 minutes... no way.
My computer don't see any usb connecting from my phone. Before I unlocked bootloader, it connected and could do anything in adb.... -__-

zukovsromsis said:
I really don't know what to do... The problem is that my computer don't see my phone, not ADB, not HiSuite. Any button combinations don't work too. The only screen appears is that in video. I really stucked.
Click to expand...
Click to collapse
I watch again your first video..
1. You see huawei logo
2.You see the screen "your phone can trust..."
3. See huawei logo again
4.You see a other screen but no options, just "your device is booting now".
Ok so the "pré-boot" is corect..
Just after the 4 point, launch fastboot reboot bootloader comand.. try again many time, at different (1 second after the screen 4 or 3 sec after screen 4, ...)
I sure at 100% work, it's forced..
It's the only solutions for that.

zukovsromsis said:
I unlocked my phone, and updated with wrong update.app. It booting non-stop, when I press 'power' - it's vibrate 2 times, show a logo and then "Your device had been unlocked and can't be trusted". I can't even go to Fastboot & Rescue Mode! Computer through USB don't see a phone. Soooo.... I'm stucked. What I can do ?
Click to expand...
Click to collapse
Ok . I understand that he phone don't boot and u don't have fastboot . Turn it off , hold volume down and plug in usb cable . If nothing will happen use dload. It's the simplest way to fix it phone and u didn't even try it ....
Or if it won't work flash rollback package via dload and then mm ROM
---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------
Dload rollback idk how it actually works but always I could flash any ROMs via dload after that . Even nugat ROM when I used it xD . Meaby its bug 4 me , meaby that's how it works . Idk . Try

Nahh, don't work anything.. 0 results... It's really stucked. ''Waiting for any device" and no any "update.app" work. Can't launch anything button combination, it says - "Your device is booting now..." and nothing more. I really tried everything.

zukovsromsis said:
Nahh, don't work anything.. 0 results... It's really stucked. ''Waiting for any device" and no any "update.app" work. Can't launch anything button combination, it says - "Your device is booting now..." and nothing more. I really tried everything.
Click to expand...
Click to collapse
Try this utility HERE for boot to bootloader..
Or try DC unlocker..
If you not have acces to bootloader, you not able to restore phone (in your state)

Therand said:
Try this utility HERE for boot to bootloader..
Or try DC unlocker..
If you not have acces to bootloader, you not able to restore phone (in your state)
Click to expand...
Click to collapse
Waiting for device...
Computer simply don't see my phone. Computer can't help in this situation.

Same
zukovsromsis said:
Waiting for device...
Computer simply don't see my phone. Computer can't help in this situation.
Click to expand...
Click to collapse
I have the same problem, any who know how to repair?? PLS