Related
I need the stock radio for Kenzo. I flashed some radio firmware and it's buggy. I couldn't find the stock firmware, so I've tried flashing the Katr radio, and the cm13 radio. While they all work, they're buggy.
So, my question. Is there anywhere I can download the stock radio firmware for Kenzo?
Did you mean miui firmware?
If yes, then you can download below
miui 6.10.13 MM
miui 7.3.2.0 LP
No, I mean the radio. I saw the stock miui firmware, but after flashing I found that they don't restore the radio as there is no signal and no calls can be made.
which miui version installed in your phone?
If you need non-hlos.bin file only, then you can delete others file in folder firmware update using winrar or 7z file manager and lets the app do the rest.
download latest fastboot rom for kenzo (maybe you already have). search Non HLOS.bin inside that fasboot rom. exctract.. you can flash in fastboot mode or if you have cm13 firmware.. change Non HLOS.bin from CM13firmware with Non HLOS from kenzo fastboot rom..(so its flashable)
Which partition do I flash that to with fastboot?
I'm trying to keep the ROM I have installed, and just fix the signal issues. Is the non-hlos.bin file all I need for that?
Also, I don't have miui, I have the Nexus Experience ROM that came with a radios.zip for flashing, which doesn't work on my device. So that's why I'm looking for the stock firmware.
Weird...those nx radios file should be able to help your signal problem due to i also ever used nx rom. NX radios work as expected for me.
Anyway, you can try below step to solve it
1. Flash cm13 radio files, and see if this help. If still not help then you can try next one
2. Flash cm14 firmware from thestrix. I already used this firmware at aicp 11 when i downgrade from N rom. so far no issue about signal or deep sleep. Everything work as expected.
Anyway, for modem files...yes, it provided at non-hlos.bin file
I've tried the cm13 radio files already, and almost every other radio I could find. I saw a cm13 firmware.zip which I didn't want to flash before I found a way to revert to stock. I'll try that once I can and that cm14.zip. Thanks.
I have a question for you
For what stok radio frimware? Can you tell me
Non HLOS.bin and adspso.bin or follow this method http://forum.xda-developers.com/redmi-note-3/help/to-solve-dual-sim-problem-custom-roms-t3490279
Oh, I've just noticed that those files you sent are flashable firmware zips. I thought you sent me the full 1GB stock ROMs. I'll try these and see if it works.
did you already try to flash it? it's worked? how about your bootloader, relocked?
So what did you flash at the end?
Alright so I have a Kenzo I unlocked the bootloader unofficially(its locked again now),anyways after an entire day of ****ing up and reviving my phone I ended up bricking it again.Only the fastboot worked. This happened before too and I used a tool which let me transfer from fastboot to EDL using a cmd so I can re apply the ROM. However this time I tried applying the latest ROM with just the emmc file swapped out(This might have been the **** up) after which I went into bootloop,so I switched off my phone and re tried the process with 7.2.5(The one I initially used and worked,but this time once it flashed completely and i tried to reboot into the system I got the Mi logo for 3 seconds and then it went blank,another 3 seconds and then dead. I have tried formatting the cache,system and userdata through fastboot but the problem still persists. Any help would be appreciated
TH3GR4NDM4ST3R said:
Alright so I have a Kenzo I unlocked the bootloader unofficially(its locked again now),anyways after an entire day of ****ing up and reviving my phone I ended up bricking it again.Only the fastboot worked. This happened before too and I used a tool which let me transfer from fastboot to EDL using a cmd so I can re apply the ROM. However this time I tried applying the latest ROM with just the emmc file swapped out(This might have been the **** up) after which I went into bootloop,so I switched off my phone and re tried the process with 7.2.5(The one I initially used and worked,but this time once it flashed completely and i tried to reboot into the system I got the Mi logo for 3 seconds and then it went blank,another 3 seconds and then dead. I have tried formatting the cache,system and userdata through fastboot but the problem still persists. Any help would be appreciated
Click to expand...
Click to collapse
so lets start from basic things...
*the reason is your bootloader got locked which ended in bootloop..
*first things first..
(hoping you know how to flash using miflash tool in edl mode)
http://bigota.d.miui.com/V8.5.1.0.M...ED_20170619.0000.00_6.0_global_5e15f747f5.tgz
-get the latest fastboot rom for kenzo(if kate u can find download in mi site) from the link.
-dont replace any file(just unzip and we are going to use original bootloader file not the unofficial one)
-using miflash tool (if on 64 bit system use miflash beat)
-flash it and select wipe everything including storage from miflash tool..
-the first boot may take about 15-20 min(depends)
-unlock officially if you are able to get your phone alive after this
Thank
adithyan25 said:
so lets start from basic things...
*the reason is your bootloader got locked which ended in bootloop..
*first things first..
(hoping you know how to flash using miflash tool in edl mode)
[NoLinks.png]
-get the latest fastboot rom for kenzo(if kate u can find download in mi site) from the link.
-dont replace any file(just unzip and we are going to use original bootloader file not the unofficial one)
-using miflash tool (if on 64 bit system use miflash beat)
-flash it and select wipe everything including storage from miflash tool..
-the first boot may take about 15-20 min(depends)
-unlock officially if you are able to get your phone alive after this
Click to expand...
Click to collapse
Thanks for that,seems to be working now(I really am dumb) anyways the sim slots are not working,which was initially the reason because of which i did all the stuff which bricked.At first when I flashed the unofficial bootloader ROM the SIMs were not detected,then I applied a firmware for cm14.1 along with resurrection remix after which the SIMs got detected but No Service and finally I flashed the NON-HLOS.bin through fastboot to get to Emergency calls only. Dont know how to get them working again,so if you could help with that I would really appreciate it
TH3GR4NDM4ST3R said:
Thanks for that,seems to be working now(I really am dumb) anyways the sim slots are not working,which was initially the reason because of which i did all the stuff which bricked.At first when I flashed the unofficial bootloader ROM the SIMs were not detected,then I applied a firmware for cm14.1 along with resurrection remix after which the SIMs got detected but No Service and finally I flashed the NON-HLOS.bin through fastboot to get to Emergency calls only. Dont know how to get them working again,so if you could help with that I would really appreciate it
Click to expand...
Click to collapse
since you messed up a lot i will suggest you start from root.. put phone to edl mode flash the latest fastboot rom using miflashtool ...and after your phone boot up,make sure everything works....
edit:- this may come in handy
https://forum.xda-developers.com/redmi-note-3/how-to/fix-bootloop-redmi-note-3-recovery-edl-t3521297
only use the step to reboot to edl from fastboot..
once you are in edl follow methods from here
nb:- dont try to replace file ..let us not touch any files inside the extracted rom
hi everyone am on the last global stables 10.3.6 am facing battery drain and slow battery charging.
i want to rollback to the beta 10.9.6.24 everything is perfect there.
can you plz explain me how to do step by step .
do i need to unlock the bootloader ? use mi flash tool ? and falsh fastboot 10.9.6.24 ( where can i downloaded it )?
any help is welcome
There are 3 ways for rolling back:
1. download recovery rom and simply flash it via twrp ( which is the most common) but since you have locked BL and therfore no TWRP you can't use this method.
2. download fastboot rom and flash it via miflashtool (by putting fone in fastboot mode) this is the best method for you and one that works with locked BL. Also make sure that you are flashing the FASTBOOT version of the rom. Since there are 2 versions for each Rom. Recovery rom and fast boot rom. And as mentioned earlier, you will need fast boot rom for this method.
3. EDL method but you will never use that, it involves putting phone in EDL mode (back panel is remove and two short points are touched via wire on motherboard and usb cable is plugged in and then fastboot rom is FLASHED by miflash tool, this is usually done on BRICKED Xiaomi phones and MIFLASH asks for AUTHORISED ACCOUNT, which atm are only found in their official service centers.
alifarhad said:
There are 3 ways for rolling back:
2. download fastboot rom and flash it via miflashtool (by putting fone in fastboot mode) this is the best method for you and one that works with locked BL. Also make sure that you are flashing the FASTBOOT version of the rom. Since there are 2 versions for each Rom. Recovery rom and fast boot rom. And as mentioned earlier, you will need fast boot rom for this method.
.
Click to expand...
Click to collapse
alright i Will go for the second method .
do you know where i can find fastboot 10.9.6.24 rom I've searched but didn't find that one i found only the latest beta which haven't been as good as 9.6.24
heiZinberg said:
alright i Will go for the second method .
do you know where i can find fastboot 10.9.6.24 rom I've searched but didn't find that one i found only the latest beta which haven't been as good as 9.6.24
Click to expand...
Click to collapse
We never had a version 10.9.6.24. U can only go for 9.6.24 (beta rom) or 10.x.x.x (stable rom).
heiZinberg said:
alright i Will go for the second method .
do you know where i can find fastboot 10.9.6.24 rom I've searched but didn't find that one i found only the latest beta which haven't been as good as 9.6.24
Click to expand...
Click to collapse
This link below contains all MIUI roms that have ever been released to this date.
https://xiaomifirmware.com/roms/official-roms-for-xiaomi-pocophone-f1/
Also as someone else mentioned, there has never been a rom such as the one you stated. The latest global stable rom is 10.3.x.x and will probably take years to reach 10.9.x.x. You must be confusing it with beta roms that usually start with 9.x.x.x serial.
And as you will be going from stable to beta, make sure you backup EVERYTHING or you will loose it.
Going from stable to beta, or vice versa, wipes the phone of all data...
You have been warned...
My Poco sensors stoped working while o was flashing some ROM I don't remember but it was maybe an sGSI.
After flashing alot of vendors on miui or pixel e, iam still facing the same issue.
Any help would really be appreciated
Stock with miflash.....and always backup...lesson learned
seems like persist.img is corrupted!
if you have fastboot rom (miui10.3.7 (2.7gb) , extract it, and further extract it, i will come something 8 gb in total!
inside images folder there will be persist.img
flash that img file, in TWRP /persist PARTITION (BE CARE FUL !!!!!!!!!!!!!!!!)
or better use ORANGE FOX RECOVERY to flash PERSIST.img
then reboot device and check!
if it still doesnt work then use miflasher, and flash this FASTBOOT rom from image folder!
REMEMBER!!!!!!!! don't tick the box, "FLASH ALL AND LOCK" this will relock your bootloader! , simply select "FLASH ALL" button in miFLASHER (down-right)
YasuHamed said:
seems like persist.img is corrupted!
if you have fastboot rom (miui10.3.7 (2.7gb) , extract it, and further extract it, i will come something 8 gb in total!
inside images folder there will be persist.img
flash that img file, in TWRP /persist PARTITION (BE CARE FUL !!!!!!!!!!!!!!!!)
or better use ORANGE FOX RECOVERY to flash PERSIST.img
then reboot device and check!
if it still doesnt work then use miflasher, and flash this FASTBOOT rom from image folder!
REMEMBER!!!!!!!! don't tick the box, "FLASH ALL AND LOCK" this will relock your bootloader! , simply select "FLASH ALL" button in miFLASHER (down-right)
Click to expand...
Click to collapse
mi flash failed to do the job and came out with error. booted fine but sensors still broken.
twrp and orange fox have no persist.img chose when flashing.
anyways thx 4 help. i hope i can get out outta this:crying::crying:
iam using miui 9.6.18 bcz i want oreo
lokixd4x4 said:
mi flash failed to do the job and came out with error. booted fine but sensors still broken.
twrp and orange fox have no persist.img chose when flashing.
anyways thx 4 help. i hope i can get out outta this:crying::crying:
iam using miui 9.6.18 bcz i want oreo
Click to expand...
Click to collapse
according to this video https://youtu.be/JKShaUdpvQw?t=374 its platform file issue,
download latest version from
https://forum.xda-developers.com/android/software/tool-platform-tools-adb-fasbootdrivers-t3061441
extract platform folder, put FASTBOOT FILES of MIUI rom in Platform folder and then try flashing
also
put everything in root C:/ and only one folder "C:\images"
long paths are not recomended for MIflasher!
@YasuHamed bro I am facing the exact same issue with a window popup on screen says find device is corrupted your device is unsafe now. Did you find a solution . Please help .brother.
abhisheksh9999 said:
@YasuHamed bro I am facing the exact same issue with a window popup on screen says find device is corrupted your device is unsafe now. Did you find a solution . Please help .brother.
Click to expand...
Click to collapse
i gave up and started using custom roms! they are closer to Stock android and have amazing customizations!
Evolution / Havoc / AeX on android 10 is amazing!
Reloaded OS (android10) is CAF based rom and its faster than others but have no customizations!
CR droid has maximum customizations but its little laggy!
you may also use
Masik13.3 and XiaomiEu roms which are Modified MIUI versions! ( google MIUI ROM BUILDER) and you can predefine features!
these roms can them be flashed via Twrp!
lokixd4x4 said:
mi flash failed to do the job and came out with error. booted fine but sensors still broken.
twrp and orange fox have no persist.img chose when flashing.
anyways thx 4 help. i hope i can get out outta this:crying::crying:
iam using miui 9.6.18 bcz i want oreo
Click to expand...
Click to collapse
Did you find any way to fix the sensors?
I think i too made the same mistake some two months back after flashed peplus rom.. i noticed it only recently.
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?