After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
phonester said:
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
Click to expand...
Click to collapse
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
It worked, thanks.
link to download radio.zip?
This situation happens when you switch to an OFFICIAL Rom from an UNOFFICIAL one like Mokee or RR from Siddhesh or Santosh. This is because these ROMs lock the bootloader and cause other problems too.
Radio.zip may not always fix the problem. If you are really stuck, there is a lengthy process that is guaranteed to work.
1. Flash one of the MiUI Fastboot ROM (global or chinese stable works fine) for RN3SD with Mi Flash tool. Use Flash All in the options at the bottom.
2. If you had an officially unlocked bootloader, use the Mi Unlocker tool to unlock your bootloader. Otherwise, you need to follow the unofficial unlock guide.
3. Flash official TWRP or a variant if you now what you are doing. Refer to this thread if you are not sure which TWRP will work.
3a. Download and copy this file to internal storage - LazyFlasher. I have verified this file to work with MiUI7 and MiUI8 global.
3b Reboot the phone in fastboot mode. On your PC, copy the TWRP img file to the adb directory and open command window there. Rename it to recovery.img. Use this command
Code:
fastboot flash recovery recovery.img
3c Boot into recovery (using ADB or Vol-pwr button shortcut). DO NOT BOOT into the phone before you do this. Flash the Lazyflasher zip with TWRP. You could probably flash this using fastboot too, I just never tried it.
Dhanajay made a guide video here. The video is a little outdated, and the updated instructions are in the description and comments.
You phone is now rooted and you have TWRP. Happy flashing.
This method will soon be outdated as a graphical UI for ADB is already in progress. Others have done it before, but this one shows real promise. Check here for details.
It has been a few months now since the RN3SD launch and the time has come when unofficial ROMs are no longer the best option around. Most Official ROMs, including the ones from RR and XOSP among others work great now and are incredbilby smooth and efficient. The war for the best kernel is now starting, and custom kernels will be responsible for the next round of reasons for bricked phones. Be VERY careful when you are flashing a ROM with a custom kernel. Be prepared to do some legwork if things go wrong.
Joswin said:
link to download radio.zip?
Click to expand...
Click to collapse
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
talkaboom said:
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
Click to expand...
Click to collapse
Link isn't working...
Can you mirror it?
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
Seems to be down. Normally works. Give it some time.
But if you are moving from an unofficial ROM, flashing radios alone is unlikely to work. Radio zip fix is for undetected SIM and IMIE errors. Check your IMIE number in About Phone. If you are showing an IMIE number instead of '0', flashing radio may be pointless.
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
New Link available.
https://mega.nz/#!9hlljJKD!QmjwPqMOH...gOqWkEJ0QasGE4
talkaboom said:
New Link available.
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
virtualgates said:
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
Link is from August 8th. That **** has mirrored a hundred times by now.
Also, the problem is now tackled in a different way. If you're facing a similar issue, ask in the rom thread you are trying to flash.
If you are facing this problem now, just flash the correct CM firmware.
P.S. On XDA, please do not question why someone posted a link or method that did not work for you. Do your research. No one is obligated to solve your problems.
Flashed radio. Zip. Worked for me.
Sent from my Redmi Note 3 using Tapatalk
Hello talkaboom!
the link is not working anymore. Any chance to upload it again please? Thanks a lot!
Related
Hi guys!
I have a Z Ultra GPE (model C6806) on which I have tried to install CM11. Everything is working fine except the most important thing: I have no phone service. When I check the status, it's returning a blank IMEI.
I have tried to go into CWM (v6.0.5.1), tried to wipe the cache, date, etc, reformat all the partitions... then reinstalled CM11. No luck. Did all that again, this time installed the latest nightly build. No luck.
I really don't know what to do anymore. My phone is useless now.
Please help!!
PS
I'm new to Android and CM. Please give me instructions I can understand. Do I need to install a new kernel? I don't know how to do that. Do I need a modem update? I found this post - http://forum.xda-developers.com/showthread.php?t=2783288 - but it says not to flash. And I wouldn't know how to do that anyway.
Azra4 said:
Hi guys!
I have a Z Ultra GPE (model C6806) on which I have tried to install CM11. Everything is working fine except the most important thing: I have no phone service. When I check the status, it's returning a blank IMEI.
I have tried to go into CWM (v6.0.5.1), tried to wipe the cache, date, etc, reformat all the partitions... then reinstalled CM11. No luck. Did all that again, this time installed the latest nightly build. No luck.
I really don't know what to do anymore. My phone is useless now.
Please help!!
PS
I'm new to Android and CM. Please give me instructions I can understand. Do I need to install a new kernel? I don't know how to do that. Do I need a modem update? I found this post - http://forum.xda-developers.com/showthread.php?t=2783288 - but it says not to flash. And I wouldn't know how to do that anyway.
Click to expand...
Click to collapse
As I said in the other thread I suspect you flashed the togari version and not the togari_gpe version of CM. Just tlash the _gpe version over top (data and cache wipes) and all should be good
blueether said:
As I said in the other thread I suspect you flashed the togari version and not the togari_gpe version of CM. Just tlash the _gpe version over top (data and cache wipes) and all should be good
Click to expand...
Click to collapse
No, I flashed the correct CM, togari_gpe.
Anyway, since I don't have much to lose, I tried to flash togari and see what would happen. CWM wouldn't let me.
Azra4 said:
No, I flashed the correct CM, togari_gpe.
Anyway, since I don't have much to lose, I tried to flash togari and see what would happen. CWM wouldn't let me.
Click to expand...
Click to collapse
I'm not a developer but i'd tried all the solutions suggested everywhere but it's not working either until i extracted the modem from ROMs that work for me (with IMEI/Baseband) and suddenly everything work like it should.
View attachment FD_C6833_Patch4.4-761.zip is the original zip i obtained from thread somewhere here in xda few months ago. (Forgotten where) For reference only
View attachment C6802_Modem_Patch.zip is my version with all the files needed for cm11 to work with my no baseband/imei z ultra <-- Flash This
I am pretty sure it will work with other z ultra variant, just replace the files in /etc/ and /system/ within the zip with files from the rom that work for your device and flash it via recovery. Hope my solution work for you.
Edit: Sorry about the confusion. It's 6am i'm still awake..
wtfhax said:
I'm not a developer but i'd tried all the solutions suggested everywhere but it's not working either until i extracted the modem from ROMs that work for me (with IMEI/Baseband) and suddenly everything work like it should.
View attachment 2973638 is the original zip i obtained from thread somewhere here in xda few months ago. (Forgotten where) For reference only
View attachment 2973639 is my version with all the files needed for cm11 to work with my no baseband/imei z ultra <-- Flash This
I am pretty sure it will work with other z ultra variant, just replace the files in /etc/ and /system/ within the zip with files from the rom that work for your device and flash it via recovery. Hope my solution work for you.
Edit: Sorry about the confusion. It's 6am i'm still awake..
Click to expand...
Click to collapse
I have this issue after installing CM12 on c6802, I had try your soulution but it failed to flash ( using fasboot ), any suggestion how to do it correctly.
Thank you
ichanz69 said:
I have this issue after installing CM12 on c6802, I had try your soulution but it failed to flash ( using fasboot ), any suggestion how to do it correctly.
Thank you
Click to expand...
Click to collapse
The file attached was meant to flash via custom recovery
wtfhax said:
The file attached was meant to flash via custom recovery
Click to expand...
Click to collapse
I flashed it using custom recovery (CyanogenMod recovery) but it shows an error..please help
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)
Hello everyone, let me just go ahead and say that I'm a total noob in the android customization thing but I somehow manage to install Lineage OS on my L03 and at the time I thought it was done and I didn't messed anything up but somehow that backfire on me.
So right now my HAM 2 is on a boot-loop, it kept staying the Lineage OS loading screen and once it was done and show the device setup screen for like 3 seconds it goes black and load again.
I've tried everything to fix it, from reinstalling an older version of Lineage, install CM13, wipe all data cache and dalvik ( and yes I have install gapps everytime I install any custom ROM, and finally after looks around the web I thought It might be the power button that making it acts weird but when after cleans it with rubbing alcohol (70%) It's still happening.
Now I have 2 options, first is to downgrade the firmware ( I'm not sure if it safe and how to do it) and seconds is to downgrade or delete TWRP ( newest version on HAM2).
Please, if anyone knows how to fix this. Help me. I got this device from amazon and it'll be a hassle trying to claim warranty on it since I have unlock it's boot-loader and install a custom ROM.
Thanks in advance.
Im not trying to be an asshole but does no one know how I can fix this?.
Bl4ckAir said:
Im not trying to be an asshole but does no one know how I can fix this?.
Click to expand...
Click to collapse
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
divhandyman said:
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
Click to expand...
Click to collapse
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Bl4ckAir said:
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Click to expand...
Click to collapse
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
divhandyman said:
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
Click to expand...
Click to collapse
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Bl4ckAir said:
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Click to expand...
Click to collapse
Yes use ADB.
https://www.youtube.com/watch?v=OwY-K6-pmJU&feature=youtu.be
Bl4ckAir said:
Please, if anyone knows how to fix this.
Click to expand...
Click to collapse
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
hola
have you managed to solve it?
I have the same problem!!!
please help
Douglas_27 said:
have you managed to solve it?
I have the same problem!!!
please help
Click to expand...
Click to collapse
Hi, Douglas I have managed to solved it. Please tell me the step you have taken and I'll maybe able to help you.
Does it work for L01 the latest TWRP
EndlessFall said:
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
Click to expand...
Click to collapse
I tried the latest TWRP from MDMower but got stuck in a boot loop after I flashed it and went to turn off the phone to go into recovery mode.
i mistakingly delete a file on my huawei mt2-l02 and since then when i power on it will stuck on startup anyone with solution
Hello everyone, I hope you can help me in this huge problem, I do not deny being completely scared...
I'm not an expert in modding, actually I'm new in this discipline, I'm a holder of Xiaomi Redmi Note 4 Qualcom 3/32.
Today I wanted to follow a video on youtube that explained how to improve my device, making these changes:
ROM Pixel Experience: https://forum.xda-developers.com/re...her-development/rom-pixel-experience-t3723382
TWRP for Redmi Note 4 (mido): https://dl.twrp.me/mido/
All versions of the Google Camera: https://www.celsoazevedo.com/files/android/google-camera/
Direct link to the version for Xiaomi Redmi Note 4 (requires modified ROM, does not work on MIUI): https://www.celsoazevedo.com/files/android/google-camera/f/scrubber_GCam_5.1.018_24.apk
Kernel: https://forum.xda-developers.com/re...-development/kernel-stormguard-11-08-t3702031
So I convinced myself to take the appropriate online guides to get the same benefits described in that video.
- I managed to unlock the bootloader after three days from the request to Xiaomi.
- I followed the guide to install TWRP, the first attempt was successful, but entering the recovery I did not find the TWRP but the recovery of Xiaomi.
I realized that I should avoid starting Android first, as the system is as if it were self-protected by TWRP, replacing it with the original version.
- I made a second attempt, this time I managed to get into the TWRP screen first, but here I had to choose the "overwrite" option instead of "go into read-only mode".
Now if I restart the phone to get back to the system I am stuck with the Xiaomi logo and can no longer access the operating system.
- I have access to fastboot.
- I have access to TWRP.
- I do not have access to Android.
- I have unlocked bootloader.
- my phone is not rooted!
Panicked, I found on the internet guides that suggested to format "DALVIK" and "Data" and "Cache" via TWRP, so I did, but this did not solve the problem, I can not yet enter the operating system.
How can I recover access to my device?
What could have happened precisely?
Thank you so much ... I hope you do not have to throw the phone ...
Pleppo said:
... How can I recover access to my device?
What could have happened precisely?
Thank you so much ... I hope you do not have to throw the phone ...
Click to expand...
Click to collapse
If your ROM is miui, then you need to install lazyflasher. Search the forum for this.
DarthJabba9 said:
If your ROM is miui, then you need to install lazyflasher. Search the forum for this.
Click to expand...
Click to collapse
Thank you very... very much for your answer!
Yes, I bought my phone with MIUI international inside... I'm going to search it on the forum, can you please provide me a link you too?
My fear is that the phone won't turn on anymore following the guide of "lazyflasher"... how can "lazyflasher" help me? thank you
Pleppo said:
Thank you very... very much for your answer!
Yes, I bought my phone with MIUI international inside... I'm going to search it on the forum, can you please provide me a link you too?
My fear is that the phone won't turn on anymore following the guide of "lazyflasher"... how can "lazyflasher" help me? thank you
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
DarthJabba9 said:
https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
Click to expand...
Click to collapse
Thank you, that thread will explain how to "recover" the system by using "twrp + Lazyflasher" right?
I will follow this instructions, even if I already installed TWRP, is it right?
Download recovery*.img and Lazyflasher
Copy lazyflasher In your internal Phone memory
Run "fastboot flash recovery recovery-mido.img in command line
Boot into recovery and flash Lazy flasher (Important for miui, else you can't boot into system)
Reboot and enjoy it
Click to expand...
Click to collapse
Why do you think my phone has got breaked?
Thank you! (i'm sorry for my bad English)
Pleppo said:
Thank you, that thread will explain how to "recover" the system by using "twrp + Lazyflasher" right?
I will follow this instructions, even if I already installed TWRP, is it right?
Why do you think my phone has got breaked?
Thank you! (i'm sorry for my bad English)
Click to expand...
Click to collapse
You already have TWRP. Just boot into TWRP and install lazyflasher via TWRP. You should be able to reboot into your miui after that. As has been explained, miui will not boot after installing TWRP if you don't install lazyflasher.
DarthJabba9 said:
You already have TWRP. Just boot into TWRP and install lazyflasher via TWRP. You should be able to reboot into your miui after that. As has been explained, miui will not boot after installing TWRP if you don't install lazyflasher.
Click to expand...
Click to collapse
Thank you so much, then tell me if I understood correctly, I do not need to panic, because the "brick" is not a real "brick" but it's just a known side effect that happens when someone decides to install TWRP on their device Xiaomi, am I right?
Since my goal is to install the Google Experience ROM on my Xiaomi, in your opinion, can I proceed with the flash of the external rom? I mean, this kind of "soft brick" is part of the normal practice for installing a custom rom? How come no guide I read talked about it? "lazyflasher" is useful to solve a damage that I created, or just to return to MIUI?
The following instructions and the current situation of this "soft brick" may have damaged something in the phone, so I have to stop moving forward with the intention to flash the Google Experience?
format "DALVIK" and "Data" and "Cache" via "advanced wipe" from TWRP
Click to expand...
Click to collapse
Pleppo said:
Thank you so much, then tell me if I understood correctly, I do not need to panic, because the "brick" is not a real "brick" but it's just a known side effect that happens when someone decides to install TWRP on their device Xiaomi, am I right?
Since my goal is to install the Google Experience ROM on my Xiaomi, in your opinion, can I proceed with the flash of the external rom? I mean, this kind of "soft brick" is part of the normal practice for installing a custom rom? How come no guide I read talked about it? "lazyflasher" is useful to solve a damage that I created, or just to return to MIUI?
The following instructions and the current situation of this "soft brick" may have damaged something in the phone, so I have to stop moving forward with the intention to flash the Google Experience?
Click to expand...
Click to collapse
Installing TWRP damages nothing. Wiping cache and dalvik damages nothing. If that is all that you did, then nothing is damaged. If you can boot into TWRP, then almost anything can be fixed. And, yes, you should be able to install Pixel Experience or any other ROM (just make sure you follow all the instructions).
To be honest, if you are asking these questions, then you really should stay with your miui until you have secured deeper understanding of things. There are many pitfalls with regard to flashing custom ROMs, even for experienced people. Just install lazyflasher, boot into miui, and lurk round these forums for about a month, before trying anything else.
DarthJabba9 said:
Installing TWRP damages nothing. Wiping cache and dalvik damages nothing. If that is all that you did, then nothing is damaged. If you can boot into TWRP, then almost anything can be fixed. And, yes, you should be able to install Pixel Experience or any other ROM (just make sure you follow all the instructions).
To be honest, if you are asking these questions, then you really should stay with your miui until you have secured deeper understanding of things. There are many pitfalls with regard to flashing custom ROMs, even for experienced people. Just install lazyflasher, boot into miui, and lurk round these forums for about a month, before trying anything else.
Click to expand...
Click to collapse
Thank you very much, I managed to enter the MIUI 9, although I noticed that everything has been restored as factory, I wonder, which of the instructions I listed before applied the restoration, precisely?
In addition, about updates to the system coming from Xiaomi, nothing has really been changed, apart from the restore of the phone?
Pleppo said:
Thank you very much, I managed to enter the MIUI 9, although I noticed that everything has been restored as factory, I wonder, which of the instructions I listed before applied the restoration, precisely?
In addition, about updates to the system coming from Xiaomi, nothing has really been changed, apart from the restore of the phone?
Click to expand...
Click to collapse
Lazyflasher allowed you to boot into what was there before TWRP was installed (which still remained there, but was inaccessible under lazyflasher was installed). Wiping the data partition will reset the phone to factory.
Pleppo said:
Thank you very much, I managed to enter the MIUI 9, although I noticed that everything has been restored as factory, I wonder, which of the instructions I listed before applied the restoration, precisely?
In addition, about updates to the system coming from Xiaomi, nothing has really been changed, apart from the restore of the phone?
Click to expand...
Click to collapse
is you device fixed now?
MyNameIsRage said:
is you device fixed now?
Click to expand...
Click to collapse
Yes! Thanks to DarthJabba9! :laugh::laugh::victory:
Pleppo said:
Yes! Thanks to DarthJabba9! :laugh::laugh::victory:
Click to expand...
Click to collapse
cool ? also please add [Resolved] in the title so that any one else having same problem can find the soulution here :fingers-crossed:
Tried almost all pie roms. Wifi disconnects after a while i lock the phone. Or it won't use data even if it seems to be connected to wifi. Changing fw, kernel, recovery didn't work. Neither did flashing fastboot rom. What should i do? (i thought notification was the problem ,but no, i figured it was wifi)
Kaanarchy said:
I don't get notifications after 10-15 mins after i closed that application. (For example i'm starting whatsapp then i'm closing it again. After some minutes i won't get any notifications and whatsapp will not use data if i don't open it manaully.) And sometimes notifications will come, but so late. Every settings is ok. Tried havoc, aosp extended, crdroid, superior it is still same. Changed kernel, updated firmware, it is still the same. What can i do? I feel like my phone is forcing me to use miui roms
TWRP = 3.2.3-1 unofficial
Click to expand...
Click to collapse
use orangefox recovery for better flashing of the roms. and your problem will be solve
JR Bautista said:
use orangefox recovery for better flashing of the roms. and your problem will be solve
Click to expand...
Click to collapse
thanks i will try, but my friend using redmi 5 plus with same recovery menu (3.2.3-1 unofficial) and doesn't have problems. I wonder why i have problems
Kaanarchy said:
thanks i will try, but my friend using redmi 5 plus with same recovery menu (3.2.3-1 unofficial) and doesn't have problems. I wonder why i have problems
Click to expand...
Click to collapse
this is unofficial mean there's a bug that not expecting
using orange fox. on aex 6.4 rom. still having the same problem
JR Bautista said:
this is unofficial mean there's a bug that not expecting
Click to expand...
Click to collapse
the link has given me by a rom tester for redmi 5 plus on youtube. he said he didn't have problems too. I know 2 person using this and they don't have problems. But anyway i will try another one thanks. And also can it be related with gapps? i always flash nano and i always download my applications with google backup. But i tried to delete some apps and download them manually and that didn't work too.
Kaanarchy said:
the link has given me by a rom tester for redmi 5 plus on youtube. he said he didn't have problems too. I know 2 person using this and they don't have problems. But anyway i will try another one thanks. And also can it be related with gapps? i always flash nano and i always download my applications with google backup. But i tried to delete some apps and download them manually and that didn't work too.
Click to expand...
Click to collapse
if you are using treble rom then use orangefox if not use official twrp
i tried orangefox with havoc and xenon, still same problem..
Maybe a firmware update?
Like this fw_vince_miui_HM5PlusGlobal_8.11.15_dd40bfa136_8.1
joke19 said:
Maybe a firmware update?
Like this fw_vince_miui_HM5PlusGlobal_8.11.15_dd40bfa136_8.1
Click to expand...
Click to collapse
i tried 3-4 firmwares and that didn't work (new ones). Now I changed my recovery to red wolf and gapps nano to bitgapps. let's see if it works.. If it won't, i will try older firmwares.
it's still happening. I lock the screen and everything is ok for 10-15 min. But after that apps doesn't use data anymore so there is no notifications too. If i start something requires internet connection like google chrome, they will come. Pls someone help :/ i checked every settings
Kaanarchy said:
i tried 3-4 firmwares and that didn't work (new ones). Now I changed my recovery to red wolf and gapps nano to bitgapps. let's see if it works.. If it won't, i will try older firmwares.
Click to expand...
Click to collapse
The last Chinese work for me.
nothing works. I even flashed fastboot rom and went back to pie again. Wifi disconnects after a while i lock the phone. Or it won't use data even if it's connected to wifi.