Related
Dear All,
I've found that my bootloader is automatically Locked after flashing Marshmallow Beta. So, I've tried to unlock it again to bring back my TWRP, but both official and unoffiacial methods failed to unlock and even temporary CWM also didn't work. Then I've flashed .139 droidboot image though fastboot and tried unofficial unlock method and got unlocked. Then I've flashed TWRP and got it worked.
Now I've flashed Supersu 2.65 through TWRP and rebooted my phone..... OMG, I've bricked my phone.... There is no display at all (Black Screen), but getting vibration at the Power On.
I've tried all the unbrick methods including xFSTK Tool method! But no use... I've used these methods previously to unbrick from USB Logo Issue. But now, it's refusing to help me...
It shows in xFSTK as like this...
Firmware download completed. Continuing to OS...
Click to expand...
Click to collapse
But it fails download OS after many attempts to reconnect my device. Then my device reboots (gives vibration) but nothing is displayed in the screen and it is still blank. It's not even booting to bootloader...
Kindly suggest me some tips to unbrick my phone (Z00AD-ZE551ML)....
Thanks in advance...
Edit: Sorry for the title mistake, it's Beta Update....
argggghhh ! now i understand where you went wrong relating to this
http://forum.xda-developers.com/showpost.php?p=67378070&postcount=88
too late now but your first paragraph ....
(........Dear All,
I've found that my bootloader is automatically Locked after flashing Marshmallow Beta. So, I've tried to unlock it again to bring back my TWRP, but both official and unoffiacial methods failed to unlock and even temporary CWM also didn't work. Then I've flashed .139 droidboot image though fastboot and tried unofficial unlock method and got unlocked.>>>>> Then I've flashed TWRP and got it worked......)
You should`ve flashed stock recovery for 139 -- then rebooted recovery -- select side load -- then adb sideloaded WW - stock 139 firmware.
i dont know where you go from here , if you do manage it, remember this ^^^ and anyone else --- i put this process numerous times but people just ignore !
possibly start again and try flash raw for 139 and correct the steps ^^^?
timbernot said:
possibly start again and try flash raw for 139 and correct the steps ^^^?
Click to expand...
Click to collapse
But from where I can start? There is no fastboot and no display at all... I'm struggling where to start...
ponnuvelpandian said:
But from where I can start? There is no fastboot and no display at all... I'm struggling where to start...
Click to expand...
Click to collapse
You are bricked my friend
Until , dnx and ifwi and os image for 6 comes about...
Find out how to extract them from the 61 firmware from marshmallow ?
Oh and the raw too .
Maybe , put here for others to use .
Come back and let us know how you go ?
timbernot said:
You are bricked my friend
Until , dnx and ifwi and os image for 6 comes about...
Find out how to extract them from the 61 firmware from marshmallow ?
Oh and the raw too .
Maybe , put here for others to use .
Come back and let us know how you go ?
Click to expand...
Click to collapse
I've already extracted dnx and ifwi from 61 firmware. But don't know how to convert droidboot.img to .bin...
But, I've tried to download dnx and ifwi extracted from 61 firmware, but it doesn't go well...
Edit 2: -but the same extracted from .184 firmware goes well..... But still no display at all...
Edit 1: Attachment....
Edit 2: -but the same extracted from .184 firmware goes well.....
goes well ?
what do you mean here ?
timbernot said:
Edit 2: -but the same extracted from .184 firmware goes well.....
goes well ?
what do you mean here ?
Click to expand...
Click to collapse
I mean it's getting flashed (only ifwi & dnx) but still no boot at all as like said at the OP... But the ifwi & dnx taken from .61 firmware is not at all flasing...
ponnuvelpandian said:
I mean it's getting flashed (only ifwi & dnx) but still no boot at all as like said at the OP... But the ifwi & dnx taken from .61 firmware is not at all flasing...
Click to expand...
Click to collapse
ok , have you just tried naming the droidboot.img to droidboot.img.bin ---longshot i know but trying to research this a little myself -- this is for another phone with an older downloader but maybe some clues here ...
http://onehallyu.com/topic/294288-a-fluke-that-save-my-phone-fonepad-7fe171cg-from-hard-brick/
timbernot said:
ok , have you just tried naming the droidboot.img to droidboot.img.bin ---longshot i know but trying to research this a little myself -- this is for another phone with an older downloader but maybe some clues here ...
http://onehallyu.com/topic/294288-a-fluke-that-save-my-phone-fonepad-7fe171cg-from-hard-brick/
Click to expand...
Click to collapse
Ya, I tried that too by renaming droidboot.img to droidboot.img.bin and tried it. But still as like before it's not even going to OS section after finishing the firmware section... So, I cant come to a conclusion that whether renaming like this is correct or not...
OK, all you can do is wait for people with more understanding than me on this topic ...apols ..
timbernot said:
OK, all you can do is wait for people with more understanding than me on this topic ...apols ..
Click to expand...
Click to collapse
OK my friend, I' waiting.... and I really thank you very much for your kind interest in solving my issue......
ponnuvelpandian said:
OK my friend, I' waiting.... and I really thank you very much for your kind interest in solving my issue......
Click to expand...
Click to collapse
I did read somewhere that letting the battery discharge itself completely --then try. Then try a fullcharge after , if not -- infact i`d try battery disconnect too lol but thats just me .
good luck and put what you find here :good:
---------- Post added at 11:01 AM ---------- Previous post was at 10:28 AM ----------
ponnuvelpandian said:
OK my friend, I' waiting.... and I really thank you very much for your kind interest in solving my issue......
Click to expand...
Click to collapse
Out of curiosity can you post a screenshot of the extracted ifwi that you have ?
Have you tried pressing (and holding) the "vol-up" button immediately after the "fw download completed continuing to os.."?
That's how I managed so the phone didn't reboot
pecholino said:
Have you tried pressing (and holding) the "vol-up" button immediately after the "fw download completed continuing to os.."?
That's how I managed so the phone didn't reboot
Click to expand...
Click to collapse
Yes, I also did it some times to try to go to bootloader, but didn't work...
timbernot said:
I did read somewhere that letting the battery discharge itself completely --then try. Then try a fullcharge after , if not -- infact i`d try battery disconnect too lol but thats just me .
good luck and put what you find here :good:
---------- Post added at 11:01 AM ---------- Previous post was at 10:28 AM ----------
Out of curiosity can you post a screenshot of the extracted ifwi that you have ?
Click to expand...
Click to collapse
These are the files I've taken from the ifwi.zip inside the Stock ROM Beta.....
timbernot said:
I did read somewhere that letting the battery discharge itself completely --then try. Then try a fullcharge after , if not -- infact i`d try battery disconnect too lol but thats just me . good luck and put what you find here :good:
Click to expand...
Click to collapse
But I've already opened my phone and tried disconnecting and reconnecting the battery to test. But it didn't helped me...
================================================================================================================
And this is the exact mistake I've did I think which they asked no to do....
What we know so far:
* DO NOT flash droidboot.img in Android 6.0 update when ifwi version is 94.17x
* The bootloader will be ' locked ' after flashing Android 6.0 update.
* The splashscreen of Android 5.0 and Android 6.0 are in different format and if you don't update after changing the ifwi version, your phone might not boot.
Click to expand...
Click to collapse
Which is stated clearly at ZenTalk forum here http://www.asus.com/zentalk/thread-79657-1-1.html
But I've flashed droidboot.img from .139 firmware over Android M Beta... This made the splashscreen not to work and my phone became unbootable...
But the sad thing is, I was really not aware of this before doing this to my phone...
Edit: Now the clue is splashscreen, is there any way to flash splashscreen using a downloader like xFSTK...?
Where to use it What is OS Dnx in xFSTK Downloader? Can I use splashscreen there?
ponnuvelpandian said:
But I've already opened my phone and tried disconnecting and reconnecting the battery to test. But it didn't helped me...
================================================================================================================
And this is the exact mistake I've did I think which they asked no to do....
Which is stated clearly at ZenTalk forum here http://www.asus.com/zentalk/thread-79657-1-1.html
But I've flashed droidboot.img from .139 firmware over Android M Beta... This made the splashscreen not to work and my phone became unbootable...
But the sad thing is, I was really not aware of this before doing this to my phone...
Edit: Now the clue is splashscreen, is there any way to flash splashscreen using a downloader like xFSTK...?
Where to use it What is OS Dnx in xFSTK Downloader? Can I use splashscreen there?
Click to expand...
Click to collapse
Well theres hope for you yet , i did just that what you did and bricked my fone a couple of hrs ago - i managed to get working bootloader using ifwi dnx fwr and droidbootPOSsignedbin for version 2.15.40.13 and the raw for it -it flashed like fastboot messages on fone and rebooted into system all by itself
just upgating now , leaving 5.0 stock till mm comes ota
ps , tried 3 times and 3 bricks - cycling between 4 colours - usb cable - bootloader - and blank screens -each time i tried the raw -- soon as i ticked the wipe data in raw flasher it took.
remember i was coming from mm beta
timbernot said:
Well theres hope for you yet , i did just that what you did and bricked my fone a couple of hrs ago - i managed to get working bootloader using ifwi dnx fwr and droidbootPOSsignedbin for version 2.15.40.13 and the raw for it -it flashed like fastboot messages on fone and rebooted into system all by itself
just upgating now , leaving 5.0 stock till mm comes ota
ps , tried 3 times and 3 bricks - cycling between 4 colours - usb cable - bootloader - and blank screens -each time i tried the raw -- soon as i ticked the wipe data in raw flasher it took.
remember i was coming from mm beta
Click to expand...
Click to collapse
Have you ever went up with the blank screen issue? (like me..)...
Edit 1: I forgot to mention one thing in the OP. After unlocking my phone with .139 droidboot.img, I got white splashscreen, then I've flashed black splashscreen (older one that I already had for LP).... I think this may be the issue...
Edit 2: Which RAW Flasher you are using to recover from blank screen?
I used 2.15.40.13 raw with the only flasher available I think 1.7
Downloader,1.14 cos it worked for me before, I have 1.34 but never used and didn't want to alter my successful flash stuff
Dear @timbernot
Thank you very much for giving me hope to unbrick my phone. Now I've unbricked it successfully by trying with xFSTK again and again repeatedly.... First I got the USB Logo, then four colours, and then fastboot.... Then I've flashed the raw firmware.... Feeling happy now....
There are many threads with users with the same problem: you can`t flash in recovery because of you locked bootloader, EDL is not working anymore, and the English PC suite is too old. So I downloaded the chinese version of PC Suite:
http://bigota.d.miui.com/MiFlash/MiInst.exe
And the full OTA ROM of global-Stable http://en.miui.com/download-334.html
Save it on your pc to access for later.
Boot your Mi Mix 2 in recovery:
Press and hold Power and Volume+, until Mi logo appears, release the buttons and a picture of a phone with cable appears.
Then connect it to the computer, en WITH THE SHIFT KEY PRESSED!, click to this:
Screenshot 1: http://imgur.com/riGFBtd
Browse to the rom file you downloaded, en click on the button (I think it is Flash, but I cannot read chinese)
Then it wil flash! It will take about 45 minutes:
Screenshot 2: http://imgur.com/GsBUy2h
Then is should boot to global stable.
Screenshot 3: http://imgur.com/sG4bENR
Update:1
Use an usb2 port, and not an usb3 if your flashing fails.
Update 2
Remember after flashing finished enter recovery mode and wipe data otherwise you will get Mi logo loop screen.
I tried this and now I have a brick. Stuck on the MI screen. Any ideas? Anyone know how to recover from this state? BL is locked. Thanks!
greanhouse1 said:
I tried this and now I have a brick. Stuck on the MI screen. Any ideas? Anyone know how to recover from this state? BL is locked. Thanks!
Click to expand...
Click to collapse
Fixed by "Reset" in Recovery mode prior to updating Rom. Don't forget everyone!
Works perfectly for me! Thanks
Thanks for the recovery tip. Phew...
This is for going from china rom to global stable right?
Hakim Farouk said:
This is for going from china rom to global stable right?
Click to expand...
Click to collapse
Yes that's correct and without unlocking bootloader, only one things not ok with this method ,after flashing global you can choose only one region China not all countries present in region list. which is ok nothing depends on this region selection, but if you want all regions its good to unlock bootloader and flash with the guide using fastboot method.
ITMASTER said:
Yes that's correct and without unlocking bootloader, only one things not ok with this method ,after flashing global you can choose only one region China not all countries present in region list. which is ok nothing depends on this region selection, but if you want all regions its good to unlock bootloader and flash with the guide using fastboot method.
Click to expand...
Click to collapse
The latest Chinese PC Suite seems to have additional extra pop ups and rearrangement. any translations? Cause I press shift and connect but can't seem to flash. there's a red wording but i didnt understand what it means
Hakim Farouk said:
The latest Chinese PC Suite seems to have additional extra pop ups and rearrangement. any translations? Cause I press shift and connect but can't seem to flash. there's a red wording but i didnt understand what it means
Click to expand...
Click to collapse
When you select correct rom, and popup appearing you should see no red but blue Chinese text (see attached screen) above and 3 other black texts below hit the upper one and process will go,
if you see red text it means the rom you selected can't be flashed on your device. usualy latest 8.5.1.0 can be flashed and latest 8.5.7.0 Chinese, other roms giving red error row. which says you need to unlock your bootloader.
I seem to be having issues on the very last step. I global rom package is verified (i see some green text) and it allows me to flash it. BUT once i press the button it immediately takes me to the screen in the link. I used the image option on the google translate app and it says something to the effect of "brush failed, please try again"'
The top button is retry, the lower one is cancel. The weird thing is, the screen on the phone changes from the recovery screen showing a phone being plugged in to one with a small loading bar and the words "Updating MIUI. dont reboot the device". That only goes away when i hit the retry button.
I could have settled for the global rom instead of flashing to the eu one once my bootloader is unlocked (30 hours to go) but if i cant get your help then eu ROM may be my only option.
EDIT:
Disregard, despite saying the flash failed i left it alone for half an hour and came back and it turned out it had flashed anyway
thezenith said:
I seem to be having issues on the very last step. I global rom package is verified (i see some green text) and it allows me to flash it. BUT once i press the button it immediately takes me to the screen in the link. I used the image option on the google translate app and it says something to the effect of "brush failed, please try again"'
Click to expand...
Click to collapse
Hi @thezenith
im having exactly the same problem, but the 0% doesn't go away.
I have a Chinese error red text adb.exe below the progression bar...
Can you help me? Thank you
I have the same issue. I'm currently stuck in a bootloop since the dev ROM crashes after I select the china region. I want to flash the global stable but get the previous errors
chris4500uk said:
I have the same issue. I'm currently stuck in a bootloop since the dev ROM crashes after I select the china region. I want to flash the global stable but get the previous errors
Click to expand...
Click to collapse
I am in the same boat. No idea what the adb error is.
I ended up taking the back cover off and doing a test point method to flash the global rom with a locked bootloader from the china ROM. Works fine now but didn't really enjoy it
chris4500uk said:
I ended up taking the back cover off and doing a test point method to flash the global rom with a locked bootloader from the china ROM. Works fine now but didn't really enjoy it
Click to expand...
Click to collapse
Trying my best to get out of having to do that. I posted on the miui forums looking for an expedited unlock, as I was able to register the phone on my account before it all went tits up.
I have exact same problem with 0%.
i want to flash from china dev rom to china stable rom. any advice?
I'm trying this method and got as far as flashing screen with 0%, red writting underneath in chinese. Not sure if it's working or not, any tips please.
Quick question
how to check which Rom I am running (global or Chinese, dev or not)
This post is a complete life saver
ITMASTER said:
There are many threads with users with the same problem: you can`t flash in recovery because of you locked bootloader, EDL is not working anymore, and the English PC suite is too old. So I downloaded the chinese version of PC Suite:
http://bigota.d.miui.com/MiFlash/MiInst.exe
And the full OTA ROM of global-Stable http://en.miui.com/download-334.html
Save it on your pc to access for later.
Boot your Mi Mix 2 in recovery:
Press and hold Power and Volume+, until Mi logo appears, release the buttons and a picture of a phone with cable appears.
Then connect it to the computer, en WITH THE SHIFT KEY PRESSED!, click to this:
Screenshot 1: http://imgur.com/riGFBtd
Browse to the rom file you downloaded, en click on the button (I think it is Flash, but I cannot read chinese)
Then it wil flash! It will take about 45 minutes:
Screenshot 2: http://imgur.com/GsBUy2h
Then is should boot to global stable.
Screenshot 3: http://imgur.com/sG4bENR
Update:1
Use an usb2 port, and not an usb3 if your flashing fails.
Update 2
Remember after flashing finished enter recovery mode and wipe data otherwise you will get Mi logo loop screen.
Click to expand...
Click to collapse
Do you happen to know if this method works for the Mi Mix 2s Chinese to Global with Locked bootloader?
Thanks!
How my phone got bricked - Yesterday when i was listening to music my phone restarted, i turned it back on and it restarted again with a black screen (or blue screen because i can see it lighting up a bit).
I tried restarting it multiple times, turning it off and also punching it but nothing helped. Later i installed miflash and went back to stock rom. But the problem still persisted , black screen .
My PC recognizes the phone as a device , but i cant get into recovery or edl mode because the phone just reboots.
I have tried holding the power + volume up and every possible combination to get into some kind of recovery.
Now when i press the volume button on my phone i can hear the sound it makes when it can't go any louder , so im guessing my phone works .
Has anyone managed to fix this?
Edit: My phone got recognized by pc as QD9008 , and i was able to flash it with qfil , but my phone still has a black screen. I also flashed it with miflash and still black. Should i try doing the deep flash cable ? Will it even do anything ? Thanks.
Really don't know.
New info in post.
Did you unlock it and flash recovery?
Can you boot into recovery or it's just a black screen from the beginning?
Have you tried any other versions of zui?
Indian/Chinese marshmallow/nougat?
sotosgolf said:
Did you unlock it and flash recovery?
Can you boot into recovery or it's just a black screen from the beginning?
Have you tried any other versions of zui?
Indian/Chinese marshmallow/nougat?
Click to expand...
Click to collapse
Before i flashed my phone with mi flash , adb was able to recognize it , but now it can't so i cant flash recovery.
Everything is black with no image at all. I have tried other versions of zui 1.9 and 2.3. But i haven't tried an Indian version.
daxtera said:
Before i flashed my phone with mi flash , adb was able to recognize it , but now it can't so i cant flash recovery.
Everything is black with no image at all. I have tried other versions of zui 1.9 and 2.3. But i haven't tried an Indian version.
Click to expand...
Click to collapse
Since the screen has light and the phone is recognized by pc my money would go on firmware issue. I would try more versions of zui. I have read that qfil is better for flashing zuk than miflash. (I'm not an expert on this, just suggesting)
Hi, i hope you don't have the similar issues as i had?
Have a read!
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-plus-stuck-edl-9008-port-help-t3713629
Flashed 3 different versions of zui and nothing . Let my battery drain but that didn't help either. So now i think my only option is to flash the unlock bootloader file , because i have read that could fix my issue but i cant get adb to recognize my device even in qd9008 mode or 900e . Any way i can get adb to work? Im really getting desperate here.
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
@daxtera, did you solve the problem? I had the same situation and still no luck
daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
open the phone and remove battery plug, then connect again
I have same problem. I disconnected battery, but nothing changed. I'm in stock ROM as it came from Bangood. Android 6.0.1 and ZUI versión 2.0.093 ST.
Problem came using phone normally without any flashing process. When connected to computer it is recognized as Qualcomm HS-USB QDLoader 9008. I tried to flash 2.0.093 ST ROM using QFIL but process always ended in Download file: Fire Hose Fail FHLoader Fail: Process fail. Can anybody help me to recover my phone usability? Pls give me any suggestion.
---------- Post added at 12:55 PM ---------- Previous post was at 12:54 PM ----------
I have same problem. I disconnected battery, but nothing changed. I'm in stock ROM as it came from Bangood. Android 6.0.1 and ZUI versión 2.0.093 ST.
Problem came using phone normally without any flashing process. When connected to computer it is recognized as Qualcomm HS-USB QDLoader 9008. I tried to flash 2.0.093 ST ROM using QFIL but process always ended in Download file: Fire Hose Fail FHLoader Fail: Process fail. Can anybody help me to recover my phone usability? Pls give me any suggestion.
daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
packpunk said:
@daxtera, did you solve the problem? I had the same situation and still no luck
Click to expand...
Click to collapse
Hello, would like to know, if you guys tried any further & were able to resolve this issue. Please advise.
daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
try this it might help ....
look at every post, many people have posted many different solutions, one might work for you
zukfans.eu/community/threads/deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily.3504/
:good:
Dhananjay_Yadav said:
try this it might help ....
look at every post, many people have posted many different solutions, one might work for you
zukfans.eu/community/threads/deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily.3504/
:good:
Click to expand...
Click to collapse
Thanks, the xda'ian who was facing this issue i.e. 'Black screen irrespective of QFIL success' reported that he was able to revive by opening the back cover & resetting the battery
Hope this helps everyone, who were facing similar issue.
kubersharma said:
Hi, i hope you don't have the similar issues as i had?
Have a read!
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-plus-stuck-edl-9008-port-help-t3713629
Click to expand...
Click to collapse
rocky459 said:
Thanks, the xda'ian who was facing this issue i.e. 'Black screen irrespective of QFIL success' reported that he was able to revive by opening the back cover & resetting the battery
Hope this helps everyone, who were facing similar issue.
Click to expand...
Click to collapse
This didn't helped bro
xyro8651 said:
This didn't helped bro
Click to expand...
Click to collapse
My zuk z2 was like that. Press the power button. Then press and release the volume up for 10-15 seconds, then press and release the volume down 10-15 seconds. You press the power button anyway. Do it for about 5-10 minutes or more. Until the device reboots. When the device boots, choose download mode or EDL mode. Do a qfill or mi flash to flash your zuk z2
adhieputra1 said:
My zuk z2 was like that. Press the power button. Then press and release the volume up for 10-15 seconds, then press and release the volume down 10-15 seconds. You press the power button anyway. Do it for about 5-10 minutes or more. Until the device reboots. When the device boots, choose download mode or EDL mode. Do a qfill or mi flash to flash your zuk z2
Click to expand...
Click to collapse
It is not working bro |
My phone is still with that condition
screen with blank dark color with backlight
Hi !
I've just flashed the phone using the last OB firmware+modem from https://jamal2367.com/downloads/?dir=OnePlus 3/Firmware + Modems/Android 8.0.0/Open Beta and now the phone can't boot !
There's no reaction when I press the ON button !
Is it a brick ?
Thx for helping
Imagitom said:
Hi !
I've just flashed the phone using the last OB firmware+modem from https://jamal2367.com/downloads/?dir=OnePlus 3/Firmware + Modems/Android 8.0.0/Open Beta and now the phone can't boot !
There's no reaction when I press the ON button !
Is it a brick ?
Thx for helping
Click to expand...
Click to collapse
3T is on OB23 not 33 , 33 is for OP3 not 3T...that's why.
now i don't think wrong firmware would cause a hard brick, but if you're getting no respond what so ever when holding the power button, it's concerning , try to hold it for longer (10-20 secs)...
also try power+vol up or down for also 10 sec or so, and try connecting to a PC, and see , and what happens when connecting to dash charger!!!
Imagitom said:
Hi !
I've just flashed the phone using the last OB firmware+modem from https://jamal2367.com/downloads/?dir=OnePlus 3/Firmware + Modems/Android 8.0.0/Open Beta and now the phone can't boot !
There's no reaction when I press the ON button !
Is it a brick ?
Thx for helping
Click to expand...
Click to collapse
Why did you flash the only the firmware? If you want OB23 then flash the complete ROM zip and not the firmware zip. As said above, you need OB23 for OP3T.
Imagitom said:
Hi !
I've just flashed the phone using the last OB firmware+modem from https://jamal2367.com/downloads/?dir=OnePlus 3/Firmware + Modems/Android 8.0.0/Open Beta and now the phone can't boot !
There's no reaction when I press the ON button !
Is it a brick ?
Thx for helping
Click to expand...
Click to collapse
Ye it's a brick. Use the unbrick guide and your golden (for the OP3T tho not the OP3 this time ).
Next time take a better look at what you are doing.
I'm not a beginner, I play with custom roms and firms since my HTC Desire HD 8 years ago :/
One must say that info on Kernel and Roms is fine here but concerning firmware, it's a bit more foggy !
I tried the guide here but it failed http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
daninantro said:
Why did you flash the only the firmware? If you want OB23 then flash the complete ROM zip and not the firmware zip. As said above, you need OB23 for OP3T.
Click to expand...
Click to collapse
Well you know that sometimes, you can't install a ROM if the firmware hasn't been updated first.
Imagitom said:
I'm not a beginner, I play with custom roms and firms since my HTC Desire HD 8 years ago :/
One must say that info on Kernel and Roms is fine here but concerning firmware, it's a bit more foggy !
I tried the guide here but it failed http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
No wonder it failed It is for OP3, for God's sake
tnsmani said:
No wonder it failed It is for OP3, for God's sake
Click to expand...
Click to collapse
I did'nt find any other unbrick guide, dude !
I turned again and again in the forum
I managed to find the mdm v3.0.6 for OP3T but it failed the same way...
Imagitom said:
I did'nt find any other unbrick guide, dude !
I turned again and again in the forum
Click to expand...
Click to collapse
Didn't it occur to you to search on Google? This impulsiveness has already landed you in trouble. Pl pay attention to what you are doing and what you are asked to do.
A search on Google throws up multiple options. One among them: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
No guarantees or liability!
That's what I've done and finaly managed after a few retries to recover my phone.
daninantro said:
Why did you flash the only the firmware? If you want OB23 then flash the complete ROM zip and not the firmware zip. As said above, you need OB23 for OP3T.
Click to expand...
Click to collapse
With OP3 its not needed. Full rom zip will automatically update the firmware.
It happened that a ROM (official RR for instance) cannot be applied without updating the firmware first)
Hi,,
I have a rooted red magic 5 International version that I am trying to update it, since I am new to this stuff I tried one of videos that led me to a black screen. I tried to charge, press power and volume buttons and there is no response. so please if any one can help me or suggesting anything to do will make me glad.
Thanks
RedMagic999 said:
Hi,,
I have a rooted red magic 5 International version that I am trying to update it, since I am new to this stuff I tried one of videos that led me to a black screen. I tried to charge, press power and volume buttons and there is no response. so please if any one can help me or suggesting anything to do will make me glad.
Thanks
Click to expand...
Click to collapse
I need help too.
You both have bricked your devices.
Please, if you haven't perfected customization, don't do anything you see online.
Go to this and download the unbrick tool for your device then unbrick.
zayidhs said:
You both have bricked your devices.
Please, if you haven't perfected customization, don't do anything you see online.
Go to this and download the unbrick tool for your device then unbrick.
Click to expand...
Click to collapse
I did try all the Unbricked tools from XDA. Nothing work. Seems like when it start flashing it disconnect the phone.
Salor123 said:
I did try all the Unbricked tools from XDA. Nothing work. Seems like when it start flashing it disconnect the phone.
Click to expand...
Click to collapse
Its mean?y device
zayidhs said:
You both have bricked your devices.
Please, if you haven't perfected customization, don't do anything you see online.
Go to this and download the unbrick tool for your device t
Click to expand...
Click to collapse
Its mean my devuce us aldo briked coz of my prblm as like same i was also try to local update i just copy and paste zip other directry and install to update then my device is shutdown i hv try many time to turn on but no response
" i just want to knw its possible to fix or not..