So I installed the latest Oreo Global ROM on my Mi 6. Everything was smooth until I decided to install some dark theme from the Themes app and the phone bricked.
I booted into recovery mode, wiped all data and rebooted.
As I reboot, it shows the MIUI 9 intro screen. Select language, then select region. AFTER I select region, the phone setup shows 'wait a second...' and then the error happens: a message 'Find Device has stopped' appears and it boots. Eternally.
So far I've tried:
1) Xiaomi PC Suite - says I should update my phone before using it.
2) Xiaomi Mi Flash - says I need to unlock bootloader
3) I asked to unlock bootloader, was authorized for my Mi account a few hours later, but when I use the Mi unlocker app, it says my My Account was not bound to the device (well it was but I wiped data...)
4) If I try an unnoficial flash tool, it says I need to enable USB debugging. I can't enable it anymore because the phone is stuck in the initial setup screen when it boots after Find Device stops.
Any suggestions please? I have no idea how to recover my phone.
Thanks!
Here is a method that worked for bricked Mi 5 devices.
I don't have time to look in your particular problem right now, but rest assured, as a last resort you can always boot into EDL mode and flash right away without unlocked BL. You need to open up your phone for that though.
mkioshi said:
Any suggestions please?
Click to expand...
Click to collapse
Alright, I might have worked out a solution, make sure to follow these steps:
Download Global Dev 8.1.25 ROM zip.
Download Xiaomi ADB, extract the 3 files and put them in a folder with the ROM zip.
Hold Vol + Power down and in the following menu select "Connect to Mi Assistant" or "连接小米助手".
Drag the ROM zip onto the XiaomiADB.exe, let it do its thing.
On successful flash the device will reboot. Enter recovery-mode again.
Via cmd, run xiaomiadb format-data.
Let me know if this works. If you have any questions, feel free to ask.
Good luck!
DavidRJ said:
Let me know if this works. If you have any questions, feel free to ask.
Good luck!
Click to expand...
Click to collapse
Damn, I thought this would work.
I tried to flash your dev rom, it said I can only flash Global ROMs.
So I tried 9.2.2.0,it said I could not flash this because it's older.
Then I tried the current ROM I had, the 9.3 (Oreo) and it flashed alright, I formatted data via adb like you said... But no way, I get the same MIUI welcome screen, choose language, choose region, and after I choose region (only China is listed) I get the same Find Device closed message and it reboots.
Maybe I'll be able to do this with a future MIUI release? Maybe it's a 9.3 OCAMIEK bug?
mkioshi said:
Maybe I'll be able to do this with a future MIUI release? Maybe it's a 9.3 OCAMIEK bug?
Click to expand...
Click to collapse
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
It happened to me exactly the same this weekend in a mix 2. After all the afternoon trying to fix it in this way.
Install a recovery through adb in fastboot mode, from adb restart the device by pressing the volume up button to enter the recovery directly. Once in recovery mode I made all the wipes and then I copied a custom rom to the internal memory of the phone and the flash in my case was epic rom. And the cell phone already works perfectly for me.
I write from a translator I'm sorry if you do not understand something, I hope it helps.
A greeting from Spain!
I just spent hours fixing the same issue. In the end the following method worked. Note that it requires an unlocked bootloader.
Sorry I can't post links yet so just have to refer to Google searching...
1. Download latest miFlash v2017.7.20.0 (Google search for it)
2. Go to "Fastboot Update - Xiaomi MIUI Official Forum" site (again just Google search)
3. Download "★ Xiaomi Mi 6 Latest Global Stable Version Fastboot File Download" from the website in step 2 (other ROMs probably work too)
4. Follow the above guide from the Fastboot section
Good luck!
Pc suite wont work on our mi6 because it only works until android 6 or so, so its not for us.
Id wait for the next global stable release and try that one out. BTW, have u tried flashing MIUI china versions? Maybe that one works out (althugh it said only global, maybe referring to developers and not china stable). GL!
I can't unlock the bootloader. Applied for it on MIUI, it authorized me but the unlocked app says the device is not bound to my MIUI account.
Although i have logged in and backup stuff from my Mi account in that phone, that unlock app says its not associated. Maybe because I wiped the data when it bootlooped, i don't know. Anyway unfortunately can't unlock it right now. Thanks!
Sent from my SM-N920G using Tapatalk
DavidRJ said:
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
Click to expand...
Click to collapse
Oh I'll try other Roms. You did help me a lot tho because i was finally able to at least flash something to my phone. That relieves me a ton, because at least i know it can be saved someday lol.
I'm using my Galaxy note 5 and traveling now but will definitely try other Roms like the Chinese one next week. Thanks again, friend.
Sent from my SM-N920G using Tapatalk
mkioshi said:
That relieves me a ton, because at least i know it can be saved someday lol.
I'm using my Galaxy note 5 and traveling now but will definitely try other Roms like the Chinese one next week.
Click to expand...
Click to collapse
Not too bad of a substitute phone.
Apart from trying other ROMs, the notable thing here is that you can kind of access ADB commands via that tool which might help you fix the issue with "Find Device" FC.
Anyways, if you have any more questions later, I'll gladly help.
David
DavidRJ said:
Not too bad of a substitute phone.
Apart from trying other ROMs, the notable thing here is that you can kind of access ADB commands via that tool which might help you fix the issue with "Find Device" FC.
Anyways, if you have any more questions later, I'll gladly help.
David
Click to expand...
Click to collapse
Thanks David. I'll take a look at all the options in the adb tool when i come back home Monday.
I love my note 5, the screen is gorgeous and the camera is better than the Mi 6 IMHO. Reason i bought the Mi 6 are the 128 tb of storage, the size (this note i too big for my small hands) and the Mi 6 is so much faster, besides having tremendous battery life. My note5 battery was always ****, and I have been using it for the last 2 years (go the Mi 6 like 2 months ago).
You've been extremely helpful, bud. Are you from Brazil too? (Asking because of the RJ in your Nick)
Sent from my SM-N920G using Tapatalk
DavidRJ said:
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
Click to expand...
Click to collapse
I managed to flash the last global dev via xiaomiadb. It all went smooth.
Obviously, after selecting language and region, I get the same Find Device closed unexpectedly and it reboots.
And now, when I try to use xiaomiadb to flash or format data, it says ERROR and the phone reboots, like he's "rejecting" any xiaomiadb command. SO cannot flash anything now.
I'm giving up on this horrible phone.
mkioshi said:
And now, when I try to use xiaomiadb to flash or format data, it says ERROR and the phone reboots, like he's "rejecting" any xiaomiadb command. SO cannot flash anything now.
I'm giving up on this horrible phone.
Click to expand...
Click to collapse
Sorry to hear that. I can't really say what's the issue here as your phone is definitely not hard bricked but I have never seen such behavior before.
Well depending on where you bought your phone, you could definitely file an RMA with the seller. You didn't unlock bootloader and your phone bricked itself basically. If you bought it in China, it depends on how easy it is to ship phones overseas in Brazil. In Europe, we can't easily ship phones with non-removable batteries sadly. (Sou da Alemanha btw mas falo um poucinho de Português )
In any case, your last bet would be the EDL method. You will lose your warranty though.
But I understand that this is way too much hassle for a soft brick caused by a damn theming engine... I'm so glad I switched off MIUI months ago.
Anyways good luck and let me know if you get any further.
David
DavidRJ said:
Sorry to hear that. I can't really say what's the issue here as your phone is definitely not hard bricked but I have never seen such behavior before.
Well depending on where you bought your phone, you could definitely file an RMA with the seller. You didn't unlock bootloader and your phone bricked itself basically. If you bought it in China, it depends on how easy it is to ship phones overseas in Brazil. In Europe, we can't easily ship phones with non-removable batteries sadly. (Sou da Alemanha btw mas falo um poucinho de Português )
In any case, your last bet would be the EDL method. You will lose your warranty though.
But I understand that this is way too much hassle for a soft brick caused by a damn theming engine... I'm so glad I switched off MIUI months ago.
Anyways good luck and let me know if you get any further.
David
Click to expand...
Click to collapse
You're a very nice person, David, thanks a ton!
Oh no xiaomi RMA here. And yeah I saw some people who bricked their phones by installing some dark theme (not the same as mine, but it was always a dark theme) after upgrading to the Oreo global rom.
And just my luck, my Note 5 took a dive yesterday so I'm phoneless lol. Thinking bout getting a Xiaomi A1 or a Moto X4, theyre not expensive and about the same price here...
If you can use adb commands. Try:
> fastboot erase system
> fastboot erase userdata
> fastboot erase boot
> fastboot erase cache
> fastboot erase data
Then try flashing the the latest developer rom as you did before.
mkioshi said:
And just my luck, my Note 5 took a dive yesterday so I'm phoneless lol.
Click to expand...
Click to collapse
Damn... Well you could still try the advice from @golfinry, I didn't think of regular ADB commands at all. Then again, if you can't do RMA anyways, what's stopping you from trying the EDL method? As far as I know you can flash any MIUI ROM you want without unlocked BL with that.
golfinry said:
If you can use adb commands. Try:
> fastboot erase system
> fastboot erase userdata
> fastboot erase boot
> fastboot erase cache
> fastboot erase data
Then try flashing the the latest developer rom as you did before.
Click to expand...
Click to collapse
Oh but I cannot use fastboot on locked bootloader right? Got the message after trying these commands
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.003s
DavidRJ said:
Damn... Well you could still try the advice from @golfinry, I didn't think of regular ADB commands at all. Then again, if you can't do RMA anyways, what's stopping you from trying the EDL method? As far as I know you can flash any MIUI ROM you want without unlocked BL with that.
Click to expand...
Click to collapse
Seems to require unlocked BL. Anyway have you ever seem this error:closed message when trying to do adb commands like adb usb (or xiaomiadb usb), adb format-data, adb sideload, etc?
Started happening after I managed to flash latest global. SO I cannot try to flash anything now
Figured as much... What about the data partition. Same thing?
Related
KillSwitch
Three different ways that I found to get rid of the KillSwitch
Through deactivating and then reactivating your google account/s.
Using the Hard Brick Recovery method.
Octopus/Octoplusbox.
Explanation
The one I actually tried was the Hard Brick Recovery Method (WillCracker), but
even after that I was still unable to bypass the KillSwitch. So I went back BoardDiag and decided to flash the System, UserData, and Cache since I still couldn't get into download mode.
After about 5-6 hours it was completed. I try booting up download mode and guess what?! KillSwitch is still there xD. I'm absolutely fustrated now and all I could think of is to flash the rest of the files that the HBRM didn't say anything about.
I started flashing in this order: Modem, Misc, Persist, and RCT. Everything is now flashed and I hope everything worksout.
I turn on the phone, waiting patiently. Bootloop over and over again, but guess what?! I tried download mode one last time before I was going to go ape $h!t. Then to my surprise the download mode screen turned on, I used the LG Flash Tool and I am now killswitch free.
KillSwitch did come back after a few updates, but I was able to enter in a pin code allowing me in the future to turn it off at will
Well thank you all for listening, just wanted to share my experience.
as my first post, I do apologize in advance if this is the wrong area for this.
Keep on keeping on xD
Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!
siredux said:
Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!
Click to expand...
Click to collapse
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963
Solved
JackTraits said:
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963
Click to expand...
Click to collapse
Link u shared shows Test points for G2 .... Correct test Points for G3 are Shown in following video
https://www.youtube.com/watch?v=04AgASAWJu8
Hey guys i have a serious problem..i tried to unlock bootloader and install another rom but my phone i think so its dead... :crying: I unlocked it succesfully,installed twrp,then rom by recovery mode,i made reboot the device,and the rom wasnt installed,so i made again reboot device in twrp by the tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and then it was like everything was deleted..no partitions nowhere,like everything had gone..and now i cant even reboot on twrp just on fastboot and i can only lock/unlock my bootloader.When i lock i take the message "Cant find vaild operating system,The device will not start....:crying: The case is that i didnt made any kind of wipe...how its possible this to happen?Can any professional guy help me here because i tried so much to bring it back to the normal condition but i dont see any solution anymore..
You have a Pixel/Nexus device. Download and flash the factory image the correct way from Google and start over.
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Good instructions at top of this page, then the download for your phone model is below.
If you do not understand any step, Google it, then read and understand completely
before proceeding. Be sure you have most current version of Android Tools.
https://developers.google.com/android/images#taimen
Don't panic and make it worse. Make sure you have adb/fastboot environment and drivers on your computer and follow the directions for reinstalling stock.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Yeah as others above have said, don't panic. I've been flashing/ rooting/modding since the way back and one thing I've learned is, it's VERY hard to brick a phone completely. Especially with newer ones, there's almost always a way to recover your phone, and especially since you have fastboot, you're not bricked either. Flash the stock rom through fastboot and you should be all set!
also make sure that your cable is good. i had major problems with many cables. finally one cable actually worked. took me hours to realize tha the cables were the culprits.
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
mac796 said:
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
Click to expand...
Click to collapse
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
Az Biker said:
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Click to expand...
Click to collapse
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Jinthegodstyle said:
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Click to expand...
Click to collapse
Dude. Start from scratch. Can you get in fastboot and is your bootloader unlocked? Are you doing this all with a tool or are you manually putting in commands It's hard to tell you what to do without all the info.
Edit.... Just saw you used a tool.... I don't care for tools. because of stuff like this. The tool should have installed the adb folder on your computer. Find that folder and open it. Download the Google zip file with stock os and Unzip into your adb foldee or SDK folder . Open the file from Google. While in there open a terminal. Have phone in fastboot mode and plugged in. Type "fastboot devices"
If it shows a number, you are connected.
Now run the bat file and it should install the os
Read all the way through then reread it .
Carefully follow steps. Forget about twrp for now.
https://developers.google.com/android/images
Don't forget to open terminal as administrator
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Jinthegodstyle said:
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Click to expand...
Click to collapse
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches ?
Badger50 said:
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches
Click to expand...
Click to collapse
Thx for advice mate!! Finally after yesterdays adventure with my new toy,today i flashed without any issues in 5 minutes the rom i wanted and it was more easy than i imagined..you see after many xiaomi phones i was confused and couldnt imagine how easy could be on google phones..Now i wont touch nothing since evertything works preety good!! Thx again!!
CyberpodS2 said:
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
Click to expand...
Click to collapse
when rma'ing it, one should defo go with locking bootloader though, i reckon.
xflowy said:
when rma'ing it, one should defo go with locking bootloader though, i reckon.
Click to expand...
Click to collapse
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
I always always always make sure the device boots before i ever lock the bootloader. I've read to many horror stories.
With this kind of phone, i think anyone should refrain from using any kind of so called "tool", aside from the basic adb n fastboot itself.
Badger50 said:
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
Click to expand...
Click to collapse
does this also apply to the critical unlock method or do i, at least, have to lock critical?
Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?
rahulkulhalli said:
Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?
Click to expand...
Click to collapse
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?
Puddi_Puddin said:
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?
Click to expand...
Click to collapse
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.
rahulkulhalli said:
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.
Click to expand...
Click to collapse
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
simonsmh said:
for those lost modem imei wifi carrier etc
Flash stock oos or h2os ROM then reboot to fastboot
fastboot erase modemst1
fastboot erase modemst2
good luck!
Click to expand...
Click to collapse
Puddi_Puddin said:
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
Click to expand...
Click to collapse
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Remove those files then flash the same OOS if possible
Click to expand...
Click to collapse
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!
rahulkulhalli said:
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!
Click to expand...
Click to collapse
Probably you meet the hardware issues. You can try it because it has no damage to your device.
simonsmh said:
Probably you meet the hardware issues. You can try it because it has no damage to your device.
Click to expand...
Click to collapse
Um, does that mean the h/w is faulty?
Hi everyone
Well im a type of guy who thinks that knows everything thats why im in problems right now. So i was using MIUI 10 beta since the first day it came out and i love it with weekly updates and noticable changes. Yesterday i saw that i can install Android P on my whyred i was pretty happy so i decided to try it today. I flashed everything and Android P worked like charm on my whyred.
But i wanted to go back to MIUI 10 and i was trying to flash using twrp but at the end i lost everything on my phone including OS. Then i downloaded MIUI 10 8.7.12 to flash it with MIFlash and i got the "Anti-Rollback" error. I found some toolkit on MIUI forum to remove anti-rollback so i tried again to flash rom but MIUI V.9.5.4.0 and it started to flash. Flash went good and it was completed but my phone turned off and its completly dead. No chance to turn it on or even to go in fastboot mode.
I dont really think that anyone can save it but if anyone heard or had that problem i will be so thankful if you could help! :fingers-crossed:
Have you try this?
https://forum.xda-developers.com/re...tutorial-unbrick-redmi-note-5-whyred-t3816260
I found some toolkit on MIUI forum to remove anti-rollback
Click to expand...
Click to collapse
There is no reported tool that can do that!
If it is the tool, I'm thinking of, it only allows unloking fastboot on ARP, so you can flash TWRP!
AlishaSama said:
Have you try this?
https://forum.xda-developers.com/re...tutorial-unbrick-redmi-note-5-whyred-t3816260
Click to expand...
Click to collapse
Thanks i will try. My pc can see my phone as "qusb_bulk" and i searched a little bit and i found out that is hard bricked so actually there is a way to fix this.
Dear seems that you flashed ARB 3 rom on ARB 4 enabled device
So hard bricked now you need mi authentication authorization to flash the latest rom.
All hard bricked users waiting for their permission from xiaome.
anyone here that has successfully flashed this model of the rm 6 pro with a global rom? does that work or will i brick it?
Bet your the first tester to find out
Pachacouti said:
Bet your the first tester to find out
Click to expand...
Click to collapse
no, im too scared im a newb in this and i dont want to brick it. if i brick it i will be lost cause im a newb
And noobs had to start somewhere. So say someone says it works, then what will you do?
Pachacouti said:
And noobs had to start somewhere. So say someone says it works, then what will you do?
Click to expand...
Click to collapse
i would give it a try ^^
But your replying to me. I'd be shredding cables by now lol, but hey, is it possible your fone is a rebranded redmi 6 pro? Plenty of tuts here for that, but I'll try to help/guide you should you need it, tell me, what stock flashing application will you use to flash your stock BACK in case of a mistake?
Pachacouti said:
Pachacouti said:
But your replying to me. I'd be shredding cables by now lol, but hey, is it possible your fone is a rebranded redmi 6 pro? Plenty of tuts here for that, but I'll trry to help/guide you should you need it, tell me, what stock flashing application will you use to flash your stock BACK in case of a mistake?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the problem is that the vendor from china put some crippled stock rom on my phone where they removed the system update service and so i cant do a local update with the phone. my rm 6 telegram group suggested that i install the qcom 9008 usb driver on my pc and boot my phone via adb into qcom 9008 edl mode and use miflash to flash it with a 4.15 unbrick package and if this would work i would have intact system update again and could flash it with a local update with the firmware id like. thanks for the help btw. gotta go out in 5 minutes but be back in a bit. please give me your opinion, i will read it once im back
What you wrote sounds good. Your flashing app is miflash. Download the 4.14 unbrick, and load it into miflash without fone plugged in, power fone OFF, start the miflash, hit download/flash (dont know the actual button to do the damage), then plug turned off fone into usb, miflash should auto find and flash, anything after that, feel free to ask.
Ps you could just jump in the deep end and flash the one you WANT, so that if it fails you'll know if it works or not, and will have tested a rom before flashing your stock back, kinda better than flashing stock first in a way.
Pachacouti said:
What you wrote sounds good. Your flashing app is miflash. Download the 4.14 unbrick, and load it into miflash without fone plugged in, power fone OFF, start the miflash, hit download/flash (dont know the actual button to do the damage), then plug turned off fone into usb, miflash should auto find and flash, anything after that, feel free to ask.
Ps you could just jump in the deep end and flash the one you WANT, so that if it fails you'll know if it works or not, and will have tested a rom before flashing your stock back, kinda better than flashing stock first in a way.
Click to expand...
Click to collapse
thanks for the suggestions! i want to give this a try as soon as i have some time. buthow do i backup my current stock rom in case the new rom wont work? i only know about rom manager app but that needs a rooted phone and mines isnt rooted. is there a way to backup the stock rom without having a rooted device?
Forget backing that up, your already at the stage where you learn if you back this up now, you MAY also back up the problem and have to do it all again, take my advice, keep it simple.
For your 'backup' - download latest official stock from your fone maker.
You may want to revert back AFTER you test the one you want to test.
So test first while it's 'broken' knowing once you go back to stock, it aint broke, dont fix it.
Pachacouti said:
Forget backing that up, your already at the stage where you learn if you back this up now, you MAY also back up the problem and have to do it all again, take my advice, keep it simple.
For your 'backup' - download latest official stock from your fone maker.
You may want to revert back AFTER you test the one you want to test.
So test first while it's 'broken' knowing once you go back to stock, it aint broke, dont fix it.
Click to expand...
Click to collapse
hey there! thanks for your tips, i appreciate it! ok just to clear things up, with "stock" firmware, you mean the official latest chinese firmware from the chinese nubia page, right?
Yup, if thats what you know is your STOCK, ie, not the one you wanna test, but in your scenario, I'd flash the test before stock, this way you gain experience flashing, and if you mess up, then you flash the stock, and learn not to. (again lol)
To clarify, stock is the firmware the fone maker has on their site.
Follow thir instructions, it's easier than you think, as my auld man told me, when testing, write down every step, so you REMEMBER instead of being unsure because I forgot....
Pachacouti said:
Yup, if thats what you know is your STOCK, ie, not the one you wanna test, but in your scenario, I'd flash the test before stock, this way you gain experience flashing, and if you mess up, then you flash the stock, and learn not to. (again lol)
To clarify, stock is the firmware the fone maker has on their site.
Follow thir instructions, it's easier than you think, as my auld man told me, when testing, write down every step, so you REMEMBER instead of being unsure because I forgot....
Click to expand...
Click to collapse
ok i got it. thanks for the help! i have the stock ready on my computer. unfortunately i cant flash my phone by following the manufacturers steps because my phone vendor flashed my phone with some custom chinese multi language firmware with google already pre installed. and whoever edited this firmware before flashing it on my new phone, removed the system service that is necessary to launch the "system update" options. therefore i have no way of making a local firmware update in my phone. unfortunately the red magic 6 pro also does not have a local update option in the recovery menu. thats why my only option is flashing the phone with my computer. but in the worst case i will have the latest stock rom on my phone in the end and this will have the system update options intact. thanks again for all the help!