Related
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
this phone use mt6739.so i want to flash it the twrp to my phone.i dunno to unlock the bootloader but the twrp file not have for this device.
I just saw this post as I too have a Honor 7S
There is NO TWRP for our device.
The TWRP for the Honor 7A/7C/7X and Honor 7 doesn't work on our device and you got to pay 4 euros to unlock the bootloader before you can even flash TWRP (and there isn't one)
This Device is treble compatible but now I've found out there is zero development and no Devs Interested in it it's a complete and utter waste of time and has gone back into its box, never to be seen again.
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Samuel Ladziansky said:
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Click to expand...
Click to collapse
Hi I have a problem. I'm having brom issues in trying to flash it
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
usab1oy said:
Hi I have a problem. I'm having brom issues in trying to flash it
Click to expand...
Click to collapse
and little hint
dont flash whole rom if the phone can boot becasue after clean flash "format+download"
you lost log and cust partition because the image files are not secureboot signed and your phone get in to bootloop
and also you lost imei codes so no cellular after that
If you do so
you can fix it in that recovery were I enabled option to format log partition
after you format log to ext4, your phone will boot but without huawei/honor bootanimation
you dont need to worry about cust partition, if you didnt format it it still boot but without bootanimation and you lost some of garbage apps that are in that partition (amazon etc...)
(twrp boots in russian language, idk for now how to change it to boot in english or slovak lanuage (because Im from slovakia) and also it have Lenovo Logo becasuse I use sources from Lenovo A5 that have same cpu)
I will make in future separated thread for this....
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Samuel Ladziansky said:
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
Click to expand...
Click to collapse
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
usab1oy said:
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
Click to expand...
Click to collapse
you can patch it or flash it without disconecting the battery
Here is how:
turn it off
Push and hold volume down
While holding volume down connect usb cable
But is recomended to disconect battery because the phone can boot up instead to go in flash mode.
usab1oy said:
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Click to expand...
Click to collapse
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Samuel Ladziansky said:
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Click to expand...
Click to collapse
Yeah. For the flash mode, I wonder why his own he said I need to hold the volume up and down button at the same time. But thanks I'll do it and let you know.
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Samuel Ladziansky said:
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Click to expand...
Click to collapse
At this point. Might just abandon it. Thanks for everything. Ran into laptop issue on my third trial lol.
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Samuel Ladziansky said:
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Click to expand...
Click to collapse
Honestly. I spend a whole night researching videos for the phone. Only to get that link I send. And after all that. It still didn't work. Lol. I have a Poco x3 pro. I wonder if snapdragon android 12 can be rooted. Probably going to try it next month or so.
Snapdragon is eazy for root.
I have Redmi note 11 and it was easy, now I running on Android 13 from stock android 11, if you will need some help with something, I'm here, and I think there is device forum so there is community for that device
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!
Hi guys,
Hope it's ok if I start this thread, I just wanted to give new users some feedback before/ after unlocking and flashing an India ROM on my sealed China ROM K20 Pro (8/256). It might be useful to some, or maybe even help others. Thanks a lot to Robbo.5000, Madsponge and Hursty UK (hope I got it right?) among others for their help and advice.
- [BUYING PROCESS] My trip with the K20 Pro started here: https://forum.xda-developers.com/k2...ice-to-buy-t3939616/post79918346#post79918346 (about 18 days to get it from China during high season, not too bad I guess). (FYI, the real Global version will come out in Europe in a few weeks but the 8/256 won't be available here.)
- [UNLOCKING PROCESS] I then started the "infamous" unlocking process which triggered the even more "infamous" unlocking wait time. Why did Xiaomi choose to do that? Pretty strange if you ask me. Why should you wait 5 days or more? Anyways, in my case it was almost 6 days. That part of the process went smoothly (I run a kinda old Windows 7 PC). I rebooted the phone and it was unlocked indeed. Then started the stressful process: flashing a +400 euros phone without knowing if it would actually work. Kinda reminded of the time when we "backuped" PS1 (PSX) games, haha.
- [FLASHING PROCESS] I used the official MiFlash tool, with the official India ROM (fastboot file, .TGZ extension). First problem : MiFlash couldn't install the drivers because a /log/ folder was missing, which I had to create manually (didn't see that mentioned on the forum, but might be my OS? Oh well). The rest was OK until I launched the flashing process and hit the "clean all" button (I carefully didn't choose the clean all and lock which would have bricked the phone).
>> Link to the official India ROM Fastboot .TGZ -> http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
>> Link to the official MiFlash tool I used -> https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
>> Use the official Xiaomi USB-C cable - do not try another USB cable
>> Important reminder: please change the default option in the flashing tool and DO NOT choose "clean all and lock". Change it to "clean all" only (you don't want to lock it as you might brick it - see posts below about this)
- [STRESSFUL REBOOT] The flashing process ran for about 10 minutes, said "error: Not catch checkpoint (\$fastboot -s .*lock)". Needless to say I was very stressed out at that point, especially with the not cool red message "error" on the right of the tool, in the column "result". I thought the phone was bricked...but no, it just rebooted normally with the India ROM on it. Honestly I don't know what happened, if it was normal or something but I didn't see anyone mentioning this.
Some feedback post flash: everything is fine, the phone seems even faster than on China ROM but it might be just an impression. I do not like the POCO launcher at all, when you're used for 4 years with the classic MIUI launcher it's honestly a pain, I like to see all installed apps on the home and next screens. I had an issue with my Mi Cloud backup (home screen): Mi Cloud said there was no backup even though I did one just before flashing. The rest of the sync process (except home screen - maybe because of POCO launcher?) was fine though: pics, notes, calls, messages, etc. Too bad we're missing NFC but it feels good to be back on "Global" (was coming from a Mi 8 Global phone). Oh yeah, missing the multiple shots option from the China ROM (where you can choose the "best" shot), but it will come to Global one day I guess.
- [MI CLOUD BACKUPS] I can confirm the Mi Cloud home screen backup issue described above is indeed because of the POCO launcher: my previous backups didn't have it (Mi 8 Global, K20 Pro China) and so Mi Cloud couldn't restore from those backups. I now have a POCO launcher backup (daily in Mi Cloud) and I can restore from those. So keep that in mind: if you come from non POCO you won't be able to restore home screen, but same thing if you move from POCO to a non POCO launcher. If you're not familiar with those backups, it's very practical (usually...) when you change phone because you just have to restore it and you'll have all your icons, apps and stuff like before.
[UPDATE] As you might know, a European Global version will be released in a few weeks, let's see if it has the POCO launcher or not.
Thanks again all for the help and let me know if you have more feedback.
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
You need to fully unpack the ROM. It requires unzipping twice. You now need to extract everything from the tar file. After extracting the tar file you should have a folder with all the ROM image files and some .bat files. Point the Mi Flash Tool to this folder.
The phone needs to be booted into fastboot mode. The PC should recognise the phone automatically if it has all the correct drivers installed.
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
i failed multiple times to flash the global india rom before(using winzip to extract). and I tried again extract the files using winrar and it succeed. i'ved been using it almost 2 weeks now. the issue that i am facing is i cant use earphone mic on discord and whatsapp call. the rest is fine. for the updates, i get it from system app updater in settings.
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
I forgot to mention it, yes you do have to extract it (using WinRAR or similar) until you get an actual folder like Robbo.5000 said. I then renamed the rom's parent folder as "raphaelin" because another user mentioned we could have issues if the folder's name was too long.
About the USB connection i didnt change anything, i left it by default.
hippo2s said:
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
Click to expand...
Click to collapse
I'm guessing your phone is already in fastboot mode (with the little Mi cartoon guy)?
I installed ADB minimal, the MiFlash drivers but also ADB Lite drivers (mentioned in the big Madsponge thread where you can find the links). That might help.
In MiFlash when i hit Refresh it saw the phone as some ID like 1d23456 or something.
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
piqiee said:
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
Click to expand...
Click to collapse
I dont think there is an update since 10.3.3.0 but i guess we'll find out with the next OTA update. I read somewhere an automatic update might lock the phone back (and brick it) so i disabled them for now, until we know more...
Of course Chinese OTA was fine on the China ROM.
hippo2s said:
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
Click to expand...
Click to collapse
In fastboot mode you cant change it on the phone if i remember, and its set automatically in file transfer mode i think.
Yes I installed those drivers too. I might try a different laptop and usb cable tonight.
Thank you so far for your help.
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
DontDamnMe said:
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
Click to expand...
Click to collapse
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
theincognito said:
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
Click to expand...
Click to collapse
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
DontDamnMe said:
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
Click to expand...
Click to collapse
Thanks mate. Just one more thing. Could you play "Test Patterns" - S1:E1 video, zoomed out for 2 mins, in Netflix app?
It will initially show "960x540" (right top corner of the screen in zoomed out mode), but after 2 mins, does it change to "1280x720" or still stays at "960x540"??
Again, thanks in advance!
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
I think its only "soft bricked". Another user had a similar issue and created a thread below. Experts here will be able to help you for sure. If its locked i believe you have to reinstall the China stock ROM.
About Netflix it stays on 960, so no HD i guess...
hippo2s said:
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
Click to expand...
Click to collapse
Just download the china latest stock rom or china latest dev rom (recovery rom will be enough), no need of mi flash.
Then go to this link and follow the instructions. Since you can access the recovery, you are fine mate.
PS: Use the latest official Mi Assistant app from the MIUI site, not the one given in the link above. But the steps are the same.
Thanks guys I will try. Really worried that phone doesn’t shut down it keeps going into recovery (doesn’t power off) and charging doesn’t seem to work in all these conditions.
Will work quickly
---------- Post added at 12:15 PM ---------- Previous post was at 12:04 PM ----------
err... thats not the Mi PC Suite is it? when i google miphone assistant thats what comes up...
Err...not detecting my phone so the PC Suite can't find the device
Hi guys, I did something very stupid, flashed the wrong boot.img and ended up completely bricking my device. I tried changing the active partition to see if it would boot, that didn't help.
I was on the latest august update of official android 11 . Then I found a boot.img I found online, but apparently it wasn't from the exact same rom. The phone booted but no WIFI.
It wouldn't allow me to flash any update through settings - system update hence I decided to try to use a fastboot rom....tried that, but the process when I hit flash_all.bat gives a lot of FAILED (remote: Flashing is not allowed for critical particions) or FAILED (Error reading sparse file)....what am I doing wrong?
I can't do anything except get in fastboot.
Is there any way I can get the phone to work agan? Needless to say that as the idiot I am the whole phone is wiped so this doesn't matter anymore. As long as I can get it to work.
Please advise and thanks (The phone is OP7T Pro ME european).
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
leginhee said:
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
Click to expand...
Click to collapse
Thanks the problem is i can't get it to start qualcomm edl. I power off, press both vol buttons and conmect to usb but nothing happens. What am i doing wrong?
Qualcomm edl Mode is just a blackscreen
"I can't do anything except get in fastboot."
Your Bootloader was unlocked ?
You can try fastboot reboot edl.
Or you can find a ROM that works, extract all images and flash all of them.
I have a similar problem.. kind of. I just flashed a rooted boot to my phone but there is no wifi at all, and since i dont have a SIM card im not getting any updates. the Boot.img came from the oneplus software update and i did the payload dumper. Since I have rooted it ive lost the wifi capabilites. (its the 7T pro me international.)