Related
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of 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"
}
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
1. download and extract this file someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
Click to expand...
Click to collapse
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
AgentXGhost said:
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of this.
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
Click to expand...
Click to collapse
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Holy Sh!t. this just absolutely worked!! I didn't think I could bring this thing back to life, but the files you linked just did it! Really, I don't know how to thank you enough for this.
corasman said:
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
Hi folks,
had the exact same issue and indeed the 1st link offered (https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view) worked like a charm.
The second link is to download the "Intel platform flash tool lite", but I used my existing version of the Intel Phone Flash Tool (5.2.1-0) which worked fine with the image.
In other words, Corasman, it appears you have saved 2 people's life (or at least tablets) with your solution, so Thanks ! :good:
Regards.
Make that 3 people! Thank you so much corasman - your post has finally fixed my yoga 2 tablet, which I was sure would be going in the bin. Can't overstate how grateful I am - Cheers!
update 830f with 1050f rom?
updating 830f with 1050 rom? does it work?
hello. I have the same problem. I update OTA to lolipop. Since the table is slow, i tried flashing some ROM (which i cannot recall) and the tablet stopped working. Now, I am trying to flash the link you provided and it succeed. However after that i get blank Screen. what Could be wrong. My table is YT2 830LC. Please help
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
i have a same problem with yoga 2 pro 1380f mr corasmancan help me
prabuddhadg said:
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
Click to expand...
Click to collapse
i have same problem with my yoga 830lc this rom not work help me to run my tab agian
---------- Post added at 10:55 AM ---------- Previous post was at 10:47 AM ----------
corasman said:
This is the file you need
And this
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
hy sir downlod the rom from google drive but unable to download 2nd link (link not working)
i use latest intel flas tool light but the rom no flash to my device its show errors. plese sir help me to run my tab again
Hi guys,
It turned out this script can't really unlock the bootloader. Although I didn't see it, my phone must have come with an unlocked bootloader.
I did another test on the same script but for Redmi 4X and the result was the same - can't unlock the bootloader.
So the moderators can delete this topic as it now serves no purpose. There are other topics for flashing TWRP and rooting the phone.
I am sorry for misleading you guys...
Here's how to install TWRP and SuperSu.
I'm not responsible if you brick your phone or lose data. I did a test on mine and all worked fine.
Info found here - (https://www.gizdev.com/root-xiaomi-mi-5s-unlock-bootloader/).
What you need:
1. Mi Flash Tool - Link(or just the ADB driver - Link)
2. Flasher ToolKit for Mi 5s - Link.
3. USB Debugging enabled in Developer Options
Install the Mi Flash Tool or the ADB drivers. Windows might tell you the drivers cannot be verified. Click on Yes to continue with the installation.
Unzip the Flasher ToolKit files to a folder on your computer.
Start with FLASHER TOOLKIT Capricorn.bat.
{
"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"
}
Hit Enter and this is what you'll see:
First you need to unlock the bootloader, so click on 3. Bootloader Utility. - This only really checks if the bootloader is locked or not. Nothing else.
The program will inform that hitting Enter will restart the phone in Bootloader mode.
Once there the unlocking will begin and you'll see this:
Now the phone will restart.
Once it boots up Android, you can continue with the next step - installing TWRP. Now it's a good time to transfer the SuperSu zip file to your phone. In Downloads for example.
Select the first option - Flash ZCX-TWRP 3.0.2.X for Mi 5s.
The image will be transferred and the phone will be restarted in Recovery mode. It might take a while to load TWRP for the first time, be patient.
Now that you're in TWRP, click on Install, select the SuperSU zip file. Once flashed, go back to Reboot, System.
If something fails:
-The ADB drivers didn't work for me so I installed Mi Flash and unplugged/plugged the phone in the USB.
Check in Device Manager if the ADB drivers are loaded for your Mi 5s. If you don't see anything saying ADB, unplug the phone and plug it back in the USB. Or try another USB port. Or try uninstalling the current drivers and reconnect the phone again.
-If you've closed the Flasher ToolKit and you try to start it again, but nothing happens, open Task Manager and kill/end task the adb.exe *32 process.
- If your phone restarts in Recovery, but all you see is the TWRP logo for minutes, give it about 10 minutes. If nothing changes, restart the phone by pressing and holding the power button. Have you unlocked the bootloader first?
It might have been a good idea to take a camera and shoot every step of the process, but I was testing it to confirm it's working. Hence most of the screenshots are from the web.
Anyway, that's what I can think of right now. If I'm missing something or you can't get it to work, let me know.
yes do it plz
Yes, it's a great ideea. Do it pls.
it will be a good start to have a guide here, you should give all the ways you know, including the first step to unlock by contacting xiaomi, however if you find a guide for a certain section you can link to it (or copy it and add a link so it won't be broken) .
It would also be nice to have a guide for major roms, with some optional steps that not all are aware of, like switching to f2fp
Should be ready now. The good thing is that you don't need to contact Xiaomi to unlock the bootloader.
ok so i did everything you told me
but i fail
first i press the 3 and everything was ok my device is unlocked no problem and its restart automatic
next i go to fast boot... and when i press 1 its show me twrp is install
but after that noting happens ... i press vol up and power its go to mi recovery
my phone is on fast boot i check that with cmd
dont know way
eny idea what to do
eny other method ? can i install with mi flash tool ?
im so confuse
Did you see the TWRP logo when the recovery was supposedly installed? Repeat again the TWRP installation and let's see what will happen.
unicastbg said:
Did you see the TWRP logo when the recovery was supposedly installed? Repeat again the TWRP installation and let's see what will happen.
Click to expand...
Click to collapse
no noting show up ? eny other method ?
frozenline said:
no noting show up ? eny other method ?
Click to expand...
Click to collapse
I'd say the recovery image is not getting transferred to your phone. Do you see a confirmation that the img file was sent over? It usually states how much time it took to transfer over.
unicastbg said:
I'd say the recovery image is not getting transferred to your phone. Do you see a confirmation that the img file was sent over? It usually states how much time it took to transfer over.
Click to expand...
Click to collapse
yes exactly its not transferring
---------- Post added at 03:34 PM ---------- Previous post was at 03:01 PM ----------
ok i did it problem was the adb i install naked adb driver its on know...ok so how i install custom rom? its like my other phones but something new in mounting it seed read only ? i had to change that or something? witch to wipe?
When starting TWRP the very first screen asks if you want to mount the partitions in read only mode or full access. And a check box to never show this again. Have you seen that? If not, try to update TWRP to 3.1.x.x, don't remember the exact version, you can find it here, in the Mi 5s section of the forums.
If you get that working, installing a new OS is pretty easy - go to Install, select the ZIP file with the new OS and follow the instructions. You might want to wipe cache and dalvik to avoid force closures after that.
Usually instructions on how to install a specific OS version are found in that OS's forum section.
i all ready do that bye rename and replace the new twrp in the flash kit folder everything is don... what is the best rom right now to install?
That's really up to your preference. I'm on global developer 7.5.25. Some use LOS.
i tried your guide, but i cant unlock bootloader. After i select option 3, the phone restarts and the bunny appears but after that i only receive the message attached.
Can somebody tell me what i do wrong?
What's your current MIUI version?
I'm on 8.2.1.0 and on computer i have Windows 10. I enabled usb debugging and type on add device account
Trimis de pe al meu MI 5s folosind Tapatalk
To be honest I'm not really sure why it doesn't work for you. The phone restarts, so you have the adb drivers.
Here's a little something that deserves a shot - the very first post - http://en.miui.com/forum.php?mod=viewthread&tid=525726&extra=page=1&page=2&mobile=2
I'd love to hear back from you if that worked or not.
i make a request to xiaomi to unlock bootloader and they aproved it in 6 hours, so i will try with mi unlock tool when i get home today. i keep you informed. thx
In managed to unlock with official metod.
Trimis de pe al meu MI 5s folosind Tapatalk
I've taken a look at the code in the script and this method WILL NOT unlock your bootloader. This is only useful for flashing TWRP and rooting a phone, if your phone IS ALREADY UNLOCKED. The third picture provided in the original post is incorrect and that will not be printed on the screen. The script does not attempt
Code:
fastboot oem unlock-go
at any point.
You will probably have to go through the official unlock process.
Hi Dear Community ,
I have here a problem with the Razer Phone 2 ,
Its it possible somehow to unlock the bootloader without OEM Activating because it wont boot into the rom?
1 :Normal booting not possible (stuck at the Razer Logo)
2:Fastboot possible but locked bootloader (For Reflashing)
3:Recovery Menu its not possible
I let the phone for 30 minutes to try boot up but not signes of progess.
I am thankfull for every Information of possibilities.
Best regards
SimpleGek
Have you tried sideloading stock rom? through recovery you should be able to do "adb sideload xxxxx.zip" xxxxx feing the filename of the stock rom.
also maybe factory resetting.
Twiggy000b said:
Have you tried sideloading stock rom? through recovery you should be able to do "adb sideload xxxxx.zip" xxxxx feing the filename of the stock rom.
also maybe factory resetting.
Click to expand...
Click to collapse
The problem is it wont boot to Recovery
Its only possible to go into "Fastboot"
The options
Recovery dont work because its stuck again at Razer Logo and Wipe Userdata too
simplegek said:
The problem is it wont boot to Recovery
{
"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"
}
Its only possible to go into "Fastboot"
The options
Recovery dont work because its stuck again at Razer Logo and Wipe Userdata too
Click to expand...
Click to collapse
Do you have AT&T?
Boot into bootloader/fastboot
If you have AT&T just go ahead and download this zip then unzip and use the flash_all.bat
https://s3.amazonaws.com/cheryl-factory-images/bolt-o-att-1240.zip
Or flash global use same steps. https://s3.amazonaws.com/cheryl-factory-images/aura-o-global-2009.zip
Bootloader Locked
Warrior1988 said:
Do you have AT&T?
Boot into bootloader/fastboot
If you have AT&T just go ahead and download this zip then unzip and use the flash_all.bat
Or flash global use same steps.
_________
'Flashing through Fastboot is impossible because the bootloader is locked :crying:
Click to expand...
Click to collapse
simplegek said:
Warrior1988 said:
Do you have AT&T?
Boot into bootloader/fastboot
If you have AT&T just go ahead and download this zip then unzip and use the flash_all.bat
Or flash global use same steps.
_________
'Flashing through Fastboot is impossible because the bootloader is locked :crying:
Click to expand...
Click to collapse
You should be allowed to flash stock img just not custom img with locked bootloader.
Click to expand...
Click to collapse
I don't think they can without unlock critical.
Warrior1988 said:
simplegek said:
You should be allowed to flash stock img just not custom img with locked bootloader.
Click to expand...
Click to collapse
Unfortunately not , at the Razer Page is the same description that i should unlock bootloader, i cant believe what a joke OEM unlock activating in the Rom is when stuck at the boot and cant unlock bootloader.
Click to expand...
Click to collapse
What were you trying to do that resulted in it being unable to boot? Factory reset should at least allow it to boot if the firmware isn't corrupted
Edit: Yeah it seems like Razer doesn't have a way to flash stock images without bootloader unlock first. Thats...weird. Like if this thing's firmware is corrupt I'm pretty sure even the factory won't be able to recover it with opening it up or something.
CurtisMJ said:
What were you trying to do that resulted in it being unable to boot? Factory reset should at least allow it to boot if the firmware isn't corrupted
Click to expand...
Click to collapse
Before happend all things i Factory Reset over Settings Menu after that Phone has restarted and pop out ereasing and stuck after new restart got stuck at the logo.
I downloaded already Factory Image , set everything up for flashing , only the locked bootloader is front of me.
and i cant unlock the bootloader because cant activate oem unlock in rom setting. i lose my hope and thinking about if something possible over emergency download (edl) but i dont wanna open the phone or something like that and i am not sure that edl is possible for Razer Phone 2.
i never had so complicated situation like that.
Best regards
SimpleGek
Hmm. So from what I understand you did a factory reset from the settings app and it wouldn't boot afterwards? Are you sure you waited long enough for the first boot? It needs to regenerate some ART caches for system apps or something after a reset if I remember right. Usually it comes pre-generated from the factory but when a user resets it it takes like 5-10min to reboot the first time. I imagine if you force shutdown during the cache generation it breaks something which results in it failing to boot outright.
Maybe try a data wipe from the bootloader, and then give it 15mins to do the first boot? It doesn't sound like you messed with the firmware so I doubt corruption is an issue.
Solve it by replace a device under warranty
CurtisMJ said:
Hmm. So from what I understand you did a factory reset from the settings app and it wouldn't boot afterwards? Are you sure you waited long enough for the first boot? It needs to regenerate some ART caches for system apps or something after a reset if I remember right. Usually it comes pre-generated from the factory but when a user resets it it takes like 5-10min to reboot the first time. I imagine if you force shutdown during the cache generation it breaks something which results in it failing to boot outright.
Maybe try a data wipe from the bootloader, and then give it 15mins to do the first boot? It doesn't sound like you messed with the firmware so I doubt corruption is an issue.
Click to expand...
Click to collapse
Thanks for everybody that has invest energy to give me Infos and think about all this , i call my provider and they offer me to replace the device so i dont wanna bricking our heads with this situation anymore.
Best Regards
SimpleGek
May be solved under a warrenty (im doing the same thing) but ive done some reasearch and if we can get someone to boot up my twrp image and do DD commands we can get the program and patch files. then use miflash or qfil and flash files with locked bootloaders, though mines unlocked.
How I did it.
sudo fastboot flashing unlock_critical
Took me right out of that limbo.
have you solved this problem?
simplegek said:
Hi Dear Community ,
I have here a problem with the Razer Phone 2 ,
Its it possible somehow to unlock the bootloader without OEM Activating because it wont boot into the rom?
1 :Normal booting not possible (stuck at the Razer Logo)
2:Fastboot possible but locked bootloader (For Reflashing)
3:Recovery Menu its not possible
I let the phone for 30 minutes to try boot up but not signes of progess.
I am thankfull for every Information of possibilities.
Best regards
SimpleGek
Click to expand...
Click to collapse
have you solved this problem?I got the same problem,but I can enter both bootloader and recover mode,but with a locked bootloader I can do nothing.
Since OP can get into fastboot, OP should try the flash-all script found in the source
blackknightavalon said:
Since OP can get into fastboot, OP should try the flash-all script found in the source
Click to expand...
Click to collapse
Tried handrurds times .It just got stuck at the beginning.
capxcom said:
have you solved this problem?I got the same problem,but I can enter both bootloader and recover mode,but with a locked bootloader I can do nothing.
Click to expand...
Click to collapse
I solved it by Warranty. Hope you can a new Device ,i brick my head was still trying to fix it . so try to give it back and get new one.
simplegek said:
I solved it by Warranty. Hope you can a new Device ,i brick my head was still trying to fix it . so try to give it back and get new one.
Click to expand...
Click to collapse
Unfortunately my back glass is cracked I don't think they will swap a new one for me :crying:
capxcom said:
Unfortunately my back glass is cracked I don't think they will swap a new one for me :crying:
Click to expand...
Click to collapse
That hurts , maybe if you can repair it , probably you can get swap it. actually there are to less replacements parts at the market for razer phone 2.
Thats seems complicated for you :\
Best Regards
SimpleGek
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