Related
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.
joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...
a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.
Hi there.
First to say, i have already did a huge research here and even whole the internet.
I decided today to try one manual "how to debrand without unlocking blootloader" i found on internet and people said its working.
Everything was going easy and OK.
Last step was just to put in microSD update.app (it was C432B564 firmware) but this failed updating and now im stuck at bootloop.
Im not even able to make factory reset because everytime it fails
Im able to enter fastboot but trying to flash manually files (extracted from B564) fails with some unknown error (fastboot see my device, its listed here).
So now i have bricked phone which Im not able to restore with any kind of guide
Actually I spent over 4 hours trying to restore it.
I have ALE21 single SIM, it was branded by T-Mobile but stuck at FW B205, this is the reason I go for debrand.
Please can you help me what to do? I cant RMA mobile since i dont have any backup device during RMA.
Thank you all for help.
unbrick
DjKukuc said:
Hi there.
First to say, i have already did a huge research here and even whole the internet.
I decided today to try one manual "how to debrand without unlocking blootloader" i found on internet and people said its working.
Everything was going easy and OK.
Last step was just to put in microSD update.app (it was C432B564 firmware) but this failed updating and now im stuck at bootloop.
Im not even able to make factory reset because everytime it fails
Im able to enter fastboot but trying to flash manually files (extracted from B564) fails with some unknown error (fastboot see my device, its listed here).
So now i have bricked phone which Im not able to restore with any kind of guide
Actually I spent over 4 hours trying to restore it.
I have ALE21 single SIM, it was branded by T-Mobile but stuck at FW B205, this is the reason I go for debrand.
Please can you help me what to do? I cant RMA mobile since i dont have any backup device during RMA.
Thank you all for help.
Click to expand...
Click to collapse
There is a method to unbrick,but your bootloader must be unlock,if is not,watch this video tuttorial https://www.youtube.com/watch?v=63L7FBuWFrc, go to this thread and read all from there,i hope that this will help you
I dont have unlocked bootloader and now i cant unlock it since Im not able to start the phone to get S/N, Product ID and all the neccessary info.
DjKukuc said:
I dont have unlocked bootloader and now i cant unlock it since Im not able to start the phone to get S/N, Product ID and all the neccessary info.
Click to expand...
Click to collapse
all you need to unlock bootloader is your imei,the rest of them,there are describe in that video tutorial,at least give a try,and sorry for bad english
cristi.blidariu said:
all you need to unlock bootloader is your imei,the rest of them,there are describe in that video tutorial,at least give a try,and sorry for bad english
Click to expand...
Click to collapse
But i cant unlock bootloader because i cant get serial number which is in Android, i cant get it in fastboot mode do you understand?
DjKukuc said:
But i cant unlock bootloader because i cant get serial number which is in Android, i cant get it in fastboot mode do you understand?
Click to expand...
Click to collapse
k,try this method to enter in fastboot/rescue mod:
press and hold volume down,conect usb cable on pc and phone,the press power button,if is boot in fastboot you can send me a pm with your imei and i will try to get your unlock code,of course if you want
DjKukuc said:
But i cant unlock bootloader because i cant get serial number which is in Android, i cant get it in fastboot mode do you understand?
Click to expand...
Click to collapse
On honor 4x (almost same phone) imei and S/N are written on battery.
cristi.blidariu said:
k,try this method to enter in fastboot/rescue mod:
press and hold volume down,conect usb cable on pc and phone,the press power button,if is boot in fastboot you can send me a pm with your imei and i will try to get your unlock code,of course if you want
Click to expand...
Click to collapse
I can enter fastboot, but thats all. Im trying to get unlock code from emui.com but it says invalid product ID - I use huawei product ID generator.
keikari said:
On honor 4x (almost same phone) imei and S/N are written on battery.
Click to expand...
Click to collapse
But P8 have not removable battery and S/N isnt the same as product ID. My S/N is written at packing where mobile came along with IMEI.
I have tried to unlock bootloader but i dont have Product ID and those numbers from fastboot devices huawei website wont accept
DjKukuc said:
I can enter fastboot, but thats all. Im trying to get unlock code from emui.com but it says invalid product ID - I use huawei product ID generator.
But P8 have not removable battery and S/N isnt the same as product ID. My S/N is written at packing where mobile came along with IMEI.
I have tried to unlock bootloader but i dont have Product ID and those numbers from fastboot devices huawei website wont accept
Click to expand...
Click to collapse
just send me by pm your imei number and i will give a try
cristi.blidariu said:
just send me by pm your imei number and i will give a try
Click to expand...
Click to collapse
You have PM, thanks.
DjKukuc said:
You have PM, thanks.
Click to expand...
Click to collapse
Now that you have your code,just unlock bootloader,then you will be able to flash boot,recovery,system and cust by fastboot commands
cristi.blidariu said:
Now that you have your code,just unlock bootloader,then you will be able to flash boot,recovery,system and cust by fastboot commands
Click to expand...
Click to collapse
Thank you man, my phone is now unlocked.
I will try your guide for debrand/convert - https://forum.xda-developers.com/p8lite/help/single-sim-to-dual-sim-b575-t3489180 Since my phone is single SIM.
Hope everything will be Okay.
You are my hero
DjKukuc said:
Thank you man, my phone is now unlocked.
I will try your guide for debrand/convert - https://forum.xda-developers.com/p8lite/help/single-sim-to-dual-sim-b575-t3489180 Since my phone is single SIM.
Hope everything will be Okay.
You are my hero
Click to expand...
Click to collapse
K,i wish you best of luck
cristi.blidariu said:
K,i wish you best of luck
Click to expand...
Click to collapse
Unfortunately Im not able to flash system, still error here ..
Code:
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 6.368s
DjKukuc said:
Unfortunately Im not able to flash system, still error here ..
Code:
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 6.368s
Click to expand...
Click to collapse
Try with b132,just extract from update.app boot,recovery,cust and system by huawei update extractor and see if the problem persist
cristi.blidariu said:
Try with b132,just extract from update.app boot,recovery,cust and system by huawei update extractor and see if the problem persist
Click to expand...
Click to collapse
Problem persist
Im feel like at the end
DjKukuc said:
Problem persist
Im feel like at the end
Click to expand...
Click to collapse
download twrp recoveryand flash by fastboot,try to boot in recovery and wipe all,including system,then try again to flash those 4 files from b132
cristi.blidariu said:
download twrp recoveryand flash by fastboot,try to boot in recovery and wipe all,including system,then try again to flash those 4 files from b132
Click to expand...
Click to collapse
Nothing, it doesnt flash recovery, it does nothing, just blinking cursor like my image for 5,10 or even 15 minutes it still blinking
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DjKukuc said:
Nothing, it doesnt flash recovery, it does nothing, just blinking cursor like my image for 5,10 or even 15 minutes it still blinking
Click to expand...
Click to collapse
Well,to be onest,i am out of ideas,if your phone boot atleast in stock recovery,try to make wipe data factory reset,if is not working,i don't known what to do in worder to work
cristi.blidariu said:
Well,to be onest,i am out of ideas,if your phone boot atleast in stock recovery,try to make wipe data factory reset,if is not working,i don't known what to do in worder to work
Click to expand...
Click to collapse
Im out of ideas too, i cant Wipe data it does some error "failed...balong modem... failed" idk what is it :/
Hey guys,
now... i'm pretty sure my Redmi 3S is a goner and im f***ed at this point. Please read carefully as i tried SO many different things now.
(Short Disclaimer! NO! My Device doesn't boot anymore. NO! I didn't enable Developer Options or USB debuging... YES! My Bootloader is locked.)
Short story beforehand:
I got my 3S from Ebay and was pretty satisfied with it. After about a Month i realised, i didn't get any updates (which i should've just by Securitypatch date and a few things.)
So i found out that i was on a ShopROM which don't get any updates at all. Then i googled and found different tutorials on how to flash a new ROM.
I followed them point by point... But it ALWAYS ended up with Errors. After every "mistake" i tried turning it on which worked... That was until something went really wrong.
Suddenly i got stuck in a Bootloop. Only the "Mi"-Logo was on the screen and that was all it did.
Sooooo... I found out i bricked it. OKAY! After several hours of searching i came up with SOOO many different tutorials on what i can do.
One of the more popular ones where:
"just flash another ROM."... Jeah, didn't work. I got so many different errors that i can't even name them all.
"Bootloader locked, enable USB-Debuging in Settings (which i cannot do)..."
NOW i recently found another tutorial that involved the official "Mi Unlock App". So i registered... Wrote them my Story and a few hours later i got a message saying "OKAY. We give you access to the tool and grant you permission so you can unlock your Phone." Sweet i thought... Now... Time to get this to work...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hell Yeah... I even tried FOUR different versions of the tool by now... The ones at v1x couldn't verify my device and got stuck at 50%. Both the v2x ones behave the same as shown in the picture.
Now i found tutorial that claimed to flash a "locked bootloader" phone. I had high hopes... Did everything as the tut said...
And i can't simpyl unlock it with "minimal adb and fastboot"
And trying to install TWRP also fails as expected:
So... as stated above...
Locked Bootloader, no developer options or usb-debuging, not allowed to flash because of critical state, mi unlock won't work...
Is there ANYTHING i can do now? I read about this "deep flash" method by i'm not that into these things and don't have the tools to do this...
The ONLY thing i can do now is WAIT. I read a lot that people have to wait for about a week or even two to use "Mi Unlock". Which doesn't make sense to me as they granted permission
and the error that comes up doesn't remedy itself by wating. At least that's my interpretation.
Thx for reading!
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
After that try Mi Flash again. And don't care about security patch date. Our device have old security patch from april 2017.
Dont wait for the unlock code becuase it wont help. Post getting the code, your mi ID needs to be binded with the phone before you attempt the unlock.
Try the EDL mode even if the bootloader is locked(you'll need a usb cable to make your own flashing cable that helps to get in edl mode on a locked bootloader).Lookout for the videos on youtube. If this also fails which i am pretty sure should get you going, the last resort would be test point method. Refer to the test point guide on the miui forum.
Sent from my ONEPLUS A5010 using Tapatalk
Hey Krauzaa,
thx for the suggestion... Now i'm not sure if i did this right... At first i did what the manual said and i think i got it into EDL mode.
For the lols i tried to unlock it without success obviously.
After trying to flash it now i got this error with every flashing tool i have on my pc:
(of course i extracted it before. It's not compressed)
I tried then to paste the file on different harddrives but getting the same result. After i watched another videotutorial i suddenly got this!
No error or anything at all... The problem, as you can see in the screen, the part "Nothing at all" continued. Even after nearly two hours (got downstairs and played Mario Odysee )
it didn't do anything.
NOW first i have a question:
By "rebooting in edl mode", my device restart itself and is stuck on the "Mi-Logo" screen... Only by holding Vol- i go to the fastboor menu. What is right?
I don't get it. On Every video i watched the screen clearly shows the fastboot logo.
BUT i tested it anyways with both states... And suddenly i only get the "Critical flashing not allowed" error again without changing the setup.
Strange.
gillboyzz
Actually i already got the whole unlock thing and permission.
With the "selfmade cable" thingy... I'll try to look it up but i'm really a n00b when it comes to things like this. Thx for the suggestion tough.
Schnaki89 said:
Hey Krauzaa,
thx for the suggestion... Now i'm not sure if i did this right... At first i did what the manual said and i think i got it into EDL mode.
For the lols i tried to unlock it without success obviously.
After trying to flash it now i got this error with every flashing tool i have on my pc:
(of course i extracted it before. It's not compressed)
I tried then to paste the file on different harddrives but getting the same result. After i watched another videotutorial i suddenly got this!
No error or anything at all... The problem, as you can see in the screen, the part "Nothing at all" continued. Even after nearly two hours (got downstairs and played Mario Odysee )
it didn't do anything.
NOW first i have a question:
By "rebooting in edl mode", my device restart itself and is stuck on the "Mi-Logo" screen... Only by holding Vol- i go to the fastboor menu. What is right?
I don't get it. On Every video i watched the screen clearly shows the fastboot logo.
BUT i tested it anyways with both states... And suddenly i only get the "Critical flashing not allowed" error again without changing the setup.
Strange.
gillboyzz
Actually i already got the whole unlock thing and permission.
With the "selfmade cable" thingy... I'll try to look it up but i'm really a n00b when it comes to things like this. Thx for the suggestion tough.
Click to expand...
Click to collapse
That method won't work for new devices... I.e. Xiaomi patched that way in new devices... Only old Redmi 3S devices can support it... (Very old ;_
Btw. You can go to edl with test-point-method... There you can flash with MiFlash without unlocked bootloader
To use MiFlash does it need unlocked bootloader? Didn't knewed that ! Damn !
metro20 said:
To use MiFlash does it need unlocked bootloader? Didn't knewed that ! Damn !
Click to expand...
Click to collapse
All tools that use fastboot to flash images would require an unlocked bootloader.
Sent from my ONEPLUS A5010 using Tapatalk
gillboyzz said:
All tools that use fastboot to flash images would require an unlocked bootloader.
Click to expand...
Click to collapse
I really didn't knewed that ! Damn ! I'm using land with unlocked bootloader and custom rom , but hell thanks for the advice ! The next Xiaomi i'de buy certainly will unlock bootloader first !
If u stuck at bootlogo and tried miflash u have to wait for some days after u got message of grant permission coz the server isn't updated once it updates in days after then try it will work ur bl will be unlocked once unlocked flash twrp via fastboot mode and from PC well will get enter button to go twrp and then u can flash rom same happend with me but I used twrp and fastboot it solved my problems again plzz wait for some days after granting permission message it would work 100% I got message and after 4days I was able to unlock and now m using atomic os
Bootdead, HardBricked Land
Same here or worse can't showing any sign , no boot no edl no led , no screen , only led flashing when charging and that too blinking
Yesterday I've flashed rom via fastboot , redmi3 and it worked like a charm
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Oh, now I kind of forgot to edit this - My phone is back working again after RMA.
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
shawek said:
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
Click to expand...
Click to collapse
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
xnutzii said:
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
Click to expand...
Click to collapse
Can you sideload the OOS zip via stock recovery?
MarcoLK said:
Can you sideload the OOS zip via stock recovery?
Click to expand...
Click to collapse
Let me see, what's the cmd command for doing so?
xnutzii said:
Let me see, what's the cmd command for doing so?
Click to expand...
Click to collapse
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
Click to expand...
Click to collapse
Oh, alright, thanks. I'l try
xnutzii said:
Oh, alright, thanks. I'l try
Click to expand...
Click to collapse
Did not work. It says ''cannot read (name).zip''
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
Click to expand...
Click to collapse
Also, there is no sideload on the 6T's stock recovery.
xnutzii said:
Did not work. It says ''cannot read (name).zip''
Click to expand...
Click to collapse
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Edit:
There should be an option.
It should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MarcoLK said:
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Click to expand...
Click to collapse
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
xnutzii said:
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
Click to expand...
Click to collapse
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
MarcoLK said:
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
Click to expand...
Click to collapse
No problem, thanks for your support.
That was my last option, if nothing helped.
Also, I just saw your edit, there is no option like this, there are ''wipe data and cache'', '' Advanced'' ''Exit''
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
xnutzii said:
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Click to expand...
Click to collapse
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
hagar006 said:
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Click to expand...
Click to collapse
I never said it doesn't recognize my phone though. I know how the phone gets recognized by msmdownloadtool, thanks for your input though.
MRobbo80 said:
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
Click to expand...
Click to collapse
I have flashed the sh*t outta my phone already, it doesn't work out sadly enough. I have tried everything besides this ↓
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
This seems very unlikely, but I thank you for your input, let's see if this actually works for me. Hope I get the timing right.
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
xnutzii said:
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
Click to expand...
Click to collapse
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
twinnfamous said:
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
Click to expand...
Click to collapse
The problem is not that the phone doesn't connect, it connects right away without any issues with the volume buttons clicked together, the msmtool runs through too! But the phone does NOT boot up after all of this is finished. It goes straight to Qualcomm crashdump mode.
UPDATE: The issue was resolved and here is the [SOLUTION]first of all lets start with the problem, it doesn't matter if it's just hard reset loop or update loop problem, I actually did both, here's a thing this main issue comes with updates but somehow this time recovery mode was completely destroyed, so there is no escape you can only access fastboot which is a good thing in a way, follow the steps to unbrick your phone.
-if you can access recovery mode just download modified miflashpro and flash downloaded rom using it.
REQUIRMENTS: PC,USB CABLE,INTERNET CONNECTION.
SOLUTION:1. Install ADB on your PC with all the necessary drivers for your phone
2. Turn off your phone completely, press and hold volume down and power button together to go into fastboot mode
3. once you are in fastboot mode connect usb to phone and open cmd from adb directory and type in: fastboot devices (if device serial number is shown in fastboot mode everything is good so far... if not go to DEVICE MANAGER in your pc and check if driver is installed properly if anything ADB drivers and ANDROID USB drivers will come handy to install them manually)
4. now type in: fastboot continue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. your device will boot into system if it fails try going into fastboot mode and going with fastboot continue command again try until it boot ups into safe mode
6. eventually it will boot into safe mode system without your files being touched because nor update nor hard reset was completed fully, phone will be in airplane mode.
7. DO NOT TURN ON WIFI OR MOBILE DATA it will crash your phone, if your phone storage is full remove some stuff plus the apps.
8. Turn on USB DEBUGGING,OEM UNLOCK MODE. open file transfers and download apk of MIUI updater from pc to your phone ( LATEST VERSION ) and install it.
9. now DEACTIVATE AIRPLANE MODE and turn on WIFI FROM SETTINGS
10. once you got internet connection wait a little bit for all of the notifications and stuff to pop up be careful, once it's all good go to settings about phone and system update and CHECK FOR UPDATES
11. let your phone download the update it should be around 1.7GB depends honestly let it decrypt and once you are ready click on INSTALL NOW.
12. it will take time to install and reboot will happen many time you might think that it gets stuck at 90.49% but let it finish be patient it happens it just needs time, once everything is done you are good to go
WELCOME TO MIUI 12
SIDE NOTE:
I - MAKE SURE YOUR PHONE IS CHARGED
II - I DID TRY EDL TEST POINTS BUT YOU DO NOT NEED TO OPEN UP YOUR PHONE NOR TO DO IT.
III - BE PATIENT
F
Unless you're willing to do a test point boot, take it to a Xiaomi service center, take a receipt with you or some proof of purchase.
You can try buying an EDL cable and testing your luck, I highly doubt tho since Xiaomi locks it's EDL mode.
got good news I managed to actually get in the system
using fastboot continue command it lags as hell but usb debugging is on
so from the looks of it recovery is gone
I am in phone adb devices are visible
anything that you might suggest ?
it took me three times to do this but it finally managed to do something
I think it's safe mode and this is why it's not crashing yet
XDHx86 said:
F
Unless you're willing to do a test point boot, take it to a Xiaomi service center, take a receipt with you or some proof of purchase.
You can try buying an EDL cable and testing your luck, I highly doubt tho since Xiaomi locks it's EDL mode.
Click to expand...
Click to collapse
anyways phone is on and going well charging but is in airplane mode trying to flash rom using miflash but not working... recovery is most likely gone... any ideas guys what to do?
Update:turning wifi makes it crash
UPDATE II: WHATEVER HAPPENS DO NOT TURN ON WIFI IT WILL CRASH AND KEEP ON CRASHING UNTIL YOU GET LUCKY AND TURN IT OFF YOURSELF
UPDATE THREE: I NEED A WAY TO FLASH RECOVERY WITHOUT FASTBOOT AND BOOTLOADER IS LOCKED
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
XDHx86 said:
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
Click to expand...
Click to collapse
I mean device is locked... there is no way to unlock it with that MI account BS
is there a way to flash twrp?
XDHx86 said:
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
Click to expand...
Click to collapse
If i somehow manage to get into recovery even if I will be able to install it I will flash rom and it's over
You can't force flash TWRP. You'll have to wait those days with MI Unlock, that's the only way.
There is this thread about an unofficial method of unlocking, I didn't bother looking tbh since I'm very sure you can't unlock it unofficially, but if you do find something then do it on your own risk.
good news managed to get wifi to work now trying to download update from the phone it's slowly going lets see if it installs safely this time boyz will update
gotta admit was a rough one
NikoWulf said:
good news managed to get wifi to work now trying to download update from the phone it's slowly going lets see if it installs safely this time boyz will update
Click to expand...
Click to collapse
NikoWulf said:
View attachment 5248941 gotta admit was a rough one
Click to expand...
Click to collapse
Well that's good, I've never heard a Xiaomi update bricking a phone except MI A3 recent Android 11 update. So most likely it will work fine. Make sure you have enough charge in the battery.
Gotta ask, how did you fix it? Did you do a test point?
well it's not over yet my dude,lets see how it's going to update this one hopefully everything will work fine
well I did had to use test points for nothing lmao, plus tweaking with right drivers from device manager and stuff...
well lets hope it works out... it was a nightmare bud
XDHx86 said:
Well that's good, I've never heard a Xiaomi update bricking a phone except MI A3 recent Android 11 update. So most likely it will work fine. Make sure you have enough charge in the battery.
Gotta ask, how did you fix it? Did you do a test point?
Click to expand...
Click to collapse
well I can't leave it like that until the update cause I can see it's buggy plus I removed SIM
so airplane mode was deactivated
activated Wifi it works pretty decent rn laggy a bit but at least I am able to download so lets see where will this update take me
been stuck here for a while now
BOYS phone turned on without a problem ladies and gentleman
PROBLEM IS SOLVED
NikoWulf said:
well I can't leave it like that until the update cause I can see it's buggy plus I removed SIM
so airplane mode was deactivated
activated Wifi it works pretty decent rn laggy a bit but at least I am able to download so lets see where will this update take me
Click to expand...
Click to collapse
Well I know I'd want a way out of this fast, so if you're still looking for a way to flash another ROM I think Hydra tool can unlock bootloader through EDL mode.
NikoWulf said:
BOYS phone turned on without a problem ladies and gentleman
PROBLEM IS SOLVED
Click to expand...
Click to collapse
Although if everything is working fine then I advice against it.
XDHx86 said:
Well I know I'd want a way out of this fast, so if you're still looking for a way to flash another ROM I think Hydra tool can unlock bootloader through EDL mode.
Although if everything is working fine then I advice against it.
Click to expand...
Click to collapse
Thanks might try it out if this one gets funky again but so far everything is going smooth