So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
MyNameIsRage said:
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
Click to expand...
Click to collapse
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only ? All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too ?
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
MyNameIsRage said:
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
Click to expand...
Click to collapse
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!! ?????
addymishra said:
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!!
Click to expand...
Click to collapse
lol, god bless our redmi note 4.
MyNameIsRage said:
lol, god bless our redmi note 4.
Click to expand...
Click to collapse
Yes!
addymishra said:
Yes!
Click to expand...
Click to collapse
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Jimmy_979 said:
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Click to expand...
Click to collapse
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
addymishra said:
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
Click to expand...
Click to collapse
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
Haha thats great congrats! Tip for custom rom installation is to follow install guide carefully and don't ever touch root partition lol! I've stopped flashing roms now... I'm on miui now permanently with bootloader locked lol
MyNameIsRage said:
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Click to expand...
Click to collapse
Haha @MyNameIsRage I'm thinking so ???
I m stuck in this same problem
But i never tried qflash
Wellll
I buy new op5t but i still wnt back to rn4
Will tell ya guys tonight nd please help me with proper procrdure
I downloaded everything but wich file have to flash
Or any video out there?
Saved my rn4
Thank u all
Thnx alot
my phone keeps rebooting
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
Pls bro am going Tru this same problem flashed through recovery flashed through fastboot but it keeps rebooting pls help me out with the exact steps u used to fix urs
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
I am in same problem on mido. Can you help me how to get in edl mode because QFIL Not detecting PORT.
Also my adb not detecting the device so i cant use adb commands.
But i can flash Stock ROM using MI Flash Tools.
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
hey guyz i have the same problem , please help me i tried all written in the replies but faces the same problem in the QFIL.
please reply, i'm dead :"(
Related
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
I tried to update my oneplus x to a new version of resurrection remix (the android 7.1 version) by flashing through twrp. Long story short I tried to update the recovery twrp and also update my bootloader but it all went to **** and now my phone is bricked. If I try and boot the phone into either the OS or into recovery I get a boot loop where the oneplus logo appears, the phone vibrates then reboots. I can get into fastboot but when I try and flash either a rom or recovery it tells me I can't because my 'device is not unlocked'. I know my bootloader was unlocked previously but am thinking that by trying to install a new rom it has re-lock or something and I'm not sure if this means my phone is now a paper weight..
Any help would be greatly appreciated!
edit: This problem is fixed. However twrp won't flash/boot correctly now..
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Tanner1294 said:
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Click to expand...
Click to collapse
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
lilfellabob said:
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
Click to expand...
Click to collapse
You're welcome! Like I said I was in the same situation. It kept rebooting and when I got into fastboot my heart sank when it said "Device is locked"
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
lilfellabob said:
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
Click to expand...
Click to collapse
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
saurabh40629 said:
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
Click to expand...
Click to collapse
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
lilfellabob said:
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
Click to expand...
Click to collapse
Yeah... This is the link.
All working, everyones help is much appreciated! <3 thanks
Hey guys! I am newbie of this forum just got heard from my friends to share u guys about my problem. Let me tell everything detailed. Last night i have installed Andvance tool pro from a site it required root access. Well my phone is rooted so i gave root access i tried to do some tweaks. First the app reuired a restore i did at the last i restored it but it doesnt happen anything. I was just getting Phone has stopped pop up so i restarted my phone. After i got to see the home has gone nothing is working all my system apps had deleted and only a few left. I can go to recovery option. Now tell me how do i get my system apps to install from recovery and whats the way to install. My phone is INew CXQ U1 version 2.0.0 Mt5672 os 4.4.2. I didnt keep backup so i am badly need of ur help guys. Please i am so much worried about this. I am using it as a useless phone now. Keyboard has gone launcher has gone. Huhu
Alaminkhan said:
Hey guys! I am newbie of this forum just got heard from my friends to share u guys about my problem. Let me tell everything detailed. Last night i have installed Andvance tool pro from a site it required root access. Well my phone is rooted so i gave root access i tried to do some tweaks. First the app reuired a restore i did at the last i restored it but it doesnt happen anything. I was just getting Phone has stopped pop up so i restarted my phone. After i got to see the home has gone nothing is working all my system apps had deleted and only a few left. I can go to recovery option. Now tell me how do i get my system apps to install from recovery and whats the way to install. My phone is INew CXQ U1 version 2.0.0 Mt5672 os 4.4.2. I didnt keep backup so i am badly need of ur help guys. Please i am so much worried about this. I am using it as a useless phone now. Keyboard has gone launcher has gone. Huhu
Click to expand...
Click to collapse
Seems like you need to install a new rom on your phone. Do you have a custom recovery? If yes, what recovery do you have?
I can give you a new rom and instructions on how to install it, but you will need CWM or TWRP for that.
Cheers,
Kuba P.
KiwiTheOne said:
Seems like you need to install a new rom on your phone. Do you have a custom recovery? If yes, what recovery do you have?
I can give you a new rom and instructions on how to install it, but you will need CWM or TWRP for that.
Cheers,
Kuba P.
Click to expand...
Click to collapse
Unfortunately, I didnt install any custom recovery into my phone. ?? Is there any way left to fix?
Alaminkhan said:
Unfortunately, I didnt install any custom recovery into my phone. ?? Is there any way left to fix?
Click to expand...
Click to collapse
If you don't have any custom recovery then you want to flash stock rom of your android.
Ashwinrg said:
If you don't have any custom recovery then you want to flash stock rom of your android.
Click to expand...
Click to collapse
No matter bro I will flash with stock rom. Please tell me process and files to use. I never ever flashed before so this will be the first time for me. I will go with your process step by step. I have pc also but it will be better by my phone only.
Alaminkhan said:
No matter bro I will flash with stock rom. Please tell me process and files to use. I never ever flashed before so this will be the first time for me. I will go with your process step by step. I have pc also but it will be better by my phone only.
Click to expand...
Click to collapse
You need to do some research before you make things worse. You will have to have a pc. Then it is a simple matter of flashing the device which will wipe it completely.
Alaminkhan said:
No matter bro I will flash with stock rom. Please tell me process and files to use. I never ever flashed before so this will be the first time for me. I will go with your process step by step. I have pc also but it will be better by my phone only.
Click to expand...
Click to collapse
Watch these YouTube video. You get flashing procedure in SP flash tool and download link of stock rom in video description.
You need SP flash tool to flash your android.
Download from here
Sorry for saying this , but you should be aware that Rooting a device has its own ups and down/
You should have researched more and must have had a custom recovery incase things go awry.
Now that things have gone bad , the only option you have is flash a rom for your device using SP Flash Tool.
Google for your phone model and download firmware and flash the rom
If you have any trouble finding a rom or flashing it , please feel to contact me.
-Edit:
https://drive.google.com/file/d/0B7IRNMn_vYgSLVVEdE5UQm5HTms/view?usp=drivesdk
Download the above file , extract it and follow https://www.youtube.com/watch?v=Y3bxYYX9Xk8
Make sure you have driver for your device installed properly.
Guys Thanks a lot. I have successfully flashed my phone with SP tools. It has been a great experience for me as I did it for the first time even I was really excited. I really knew it that u guys help will really work. Thanks once again and love u all. Now I wont dare to flash my phone with custom rom well I will install CMW first haha
lesson learned.
After unlocking the bootloader flashed magisk and data decrypt imei and baseband are lost can I restore it?before going to service center:crying:?
Download a global Stock ROM for your device and just run the flash all.bat file and let it run may take awhile and phone will be fresh again
HELP !!! I'm getting the same issue but don't care if i brick the phone.
No matter how many times i flash use different roms i still lose my IMEI/Baseband
I have an external SD card but it looks complicated to backup the EFS file to the SD card and then restore it to the phone but is that my only option ?
Doubtpablo said:
Download a global Stock ROM for your device and just run the flash all.bat file and let it run may take awhile and phone will be fresh again
HELP !!! I'm getting the same issue but don't care if i brick the phone.
No matter how many times i flash use different roms i still lose my IMEI/Baseband
I have an external SD card but it looks complicated to backup the EFS file to the SD card and then restore it to the phone but is that my only option ?
Click to expand...
Click to collapse
Don't disable forceencrypt, that's your problem.
Doubtpablo said:
Download a global Stock ROM for your device and just run the flash all.bat file and let it run may take awhile and phone will be fresh again
Click to expand...
Click to collapse
Already flash stock ROM, but my IMEI still null.
I flashed 10.2.8.0.
Please anyone, I'm stuck with my phone without my IMEI and Baseband
whothehellami said:
Already flash stock ROM, but my IMEI still null.
I flashed 10.2.8.0.
Please anyone, I'm stuck with my phone without my IMEI and Baseband
Click to expand...
Click to collapse
Did you flash a recovery rom or a fastboot rom? You should find flashing the fastboot rom restores everything correctly.
Robbo.5000 said:
Did you flash a recovery rom or a fastboot rom? You should find flashing the fastboot rom restores everything correctly.
Click to expand...
Click to collapse
I tried restoring the phone using a fastboot rom, but the baseband and IMEI errors still appear. Does anyone know about another solution or tool for this? I know both of my IMEI numbers, by the way.
Spikyman said:
I tried restoring the phone using a fastboot rom, but the baseband and IMEI errors still appear. Does anyone know about another solution or tool for this? I know both of my IMEI numbers, by the way.
Click to expand...
Click to collapse
Every time I got this problem I found that flashing a fastboot ROM fixed it. I never managed to find any other solution that actually worked. Googling the problem I did find some solutions, but I didn't try them all. I just gave up and kept stock ROM with Magisk, then debloated it as much as I could. All I can suggest is seeing what Google throws up and seeing if any solution works for you.
anyone found a fix yet?
I have the mistake of rooting my device and disabling the encrypt, Now I have unknown baseband and my imei is blank. What do i do now?
Anuvind98 said:
After unlocking the bootloader flashed magisk and data decrypt imei and baseband are lost can I restore it?before going to service center:crying:?
Click to expand...
Click to collapse
It happens to me only when i flash decrypt,if i try to flash another decrypt it doesn't work and data remains crypted.
It's not a big problem bit i would like to have a solution of this problem
still have this problem. any fix?
try this youtube
Hello dear fellow mido users. I am trying to solve a problem here and I would very much appreciate your help on this:
I am running latest MIUI Stable Global flashed from fastboot, I have IMEI, but I don't have mobile signal. WiFi & BT works fine.
How I got here:
Bricked the phone about half a year ago
Ressurected it a week ago via connecting the pins in the back and flashing via edl.
I have unlocked it officially, as I had it unlocked before.
I have flashed TWRP & latest official RR, but it bootlooped, because my /persist partition was freaked out, so I reflashed it from the extracted fastboot ROM and I booted.
However, both my IMEIs dissappeared, and I only had the first IMEI from the back of my phone. So I calculated the second IMEI per a tutorial (from a Czech site) and restored both IMEIs via the Qualcomm QPST xqcn file, verified both IMEIs are showing up on my phone and are valid as per online IMEI checkers.
However, the signal didn't work, so I reflashed another mido device's IMEI (I have my original IMEIs backed-up) and flashed latest MIUI fastboot ROM, still no signal.
And here I am, and I am asking you for help..
If anyone can help me or at least point me in the right direction I will be eternally grateful :angel:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
JouzaCZ said:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
Click to expand...
Click to collapse
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
crok.bic said:
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
Click to expand...
Click to collapse
Thank you so much for your reply. I just checked, the cable wasn't disconnected, but I dis-and-reconnected it just to make sure. Still no signal.
I should mention I reflashed my original IMEI and verified that its valid once again. I am attaching links to pictures of the back of my phone disassembled if anyone can spot something wrong: PHOTOS.
Still hoping for a solution.
JouzaCZ said:
Still hoping for a solution.
Click to expand...
Click to collapse
Okay, starts to be interesting. Did you play with the band selection? Probably the band has been changed to US?
Hope you have Magisk (root) - if not please flash Magisk.
I presume ADB is already installed.
Put the phone to airplane mode.
From a PC open a cmd and issue adb shell
or start a terminal emulator on your phone
Then issue these commands in the shell
su
pm clear com.android.providers.telephony
settings put global preferred_network_mode 10
settings put global preferred_network_mode1 10
settings put global preferred_network_mode2 10
Remove airplane mode.
Restart.
Check again.
If still not works:
Start phone in fastboot mode
Issue these commands from PC cmd:
fastboot devices << just to make sure you phone is recognised
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
It will restart.
Check again.
Anyway, if you issue *#*#INFO#*#* or better known as *#*#4636#*#* in the dialer then selecting Phone 1 or Phone 2 (according to the SIM slot you want to check) in the top right or lower left there is a band-select menu (not in MIUI but in other custom ROMs) so there you are able to select the correct band if you want (that would mean you flash any custom ROM from TWRP or any custom recovery for a couple of minutes, go to dialer and look around)
crok.bic said:
Ping
Click to expand...
Click to collapse
Tried everything you said in order, still doesn't work. In normal fastboot, fastboot erase modemst1 results in this image isn't allow download. So I used mfastboot and it worked, however still no signal. When I try to switch the band in the options menu, there are two options: Automatic and United States. When clicked, both result in: Set [United States/Automatic] Unsuccessful.
And I just noticed it erased my IMEI again... Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
JouzaCZ said:
Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
Click to expand...
Click to collapse
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
crok.bic said:
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
Click to expand...
Click to collapse
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
JouzaCZ said:
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
Click to expand...
Click to collapse
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
crok.bic said:
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
Click to expand...
Click to collapse
Okay, I followed the first tutorial and successfully restored both IMEIs, still not working. I noticed, while flashing the xQCN file, it gives me a message about the model number of the phone not matching the model number of the xqcn file. Is that normal?
Last resort is to follow the second tutorial and redo everything.
JouzaCZ said:
gives me a message about the model number of the phone not matching the model number of the xqcn file
Click to expand...
Click to collapse
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
crok.bic said:
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
Click to expand...
Click to collapse
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
JouzaCZ said:
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
Click to expand...
Click to collapse
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
crok.bic said:
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
Click to expand...
Click to collapse
fastboot getvar product: mido
adb devices: 7e03cac30903 device
JouzaCZ said:
fastboot getvar product: mido
Click to expand...
Click to collapse
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
crok.bic said:
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
Click to expand...
Click to collapse
Pasting from a thread I made back when I bricked the phone:
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
Click to expand...
Click to collapse
JouzaCZ said:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Click to expand...
Click to collapse
Do you have this backup you made with RedWolf?
JouzaCZ said:
including the Firmware and EFS partitions, basically every partition
Click to expand...
Click to collapse
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
Do you have this backup you made with RedWolf?
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
JouzaCZ said:
Pasting from a thread I made back when I bricked the phone:
Click to expand...
Click to collapse
JouzaCZ said:
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
Click to expand...
Click to collapse
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Decent version. Specifically: 953_GEN_PACK-1.148143.1.163979.1
Also can we switch to some IM like WhatsApp so we don't have to keep pinging each other via quotes? I will post the solution/result in the thread.