Problems in flashed ROMs - Xiaomi Redmi Note 4 Questions & Answers

Hey, I am using a redmi note 4 Snapdragon version,and I installed custom rom on my device,the installation was successful but hardware components are not accessible to me now.Like, wifi,bluetooth is not turning on, camera app is not present and even flashlight icon in notification shade is blurred out.
I installed resurrection remix and aex ROMs,I know they are fine cause i have installed them before(same versions) in the same phone,but now they are showing problems.And gapps are not installing either twrp recovery shows corrupt file even though its not for sure.
I think i messed up while wiping data ,I wiped the internal storage and formatted the phone too, that is the only thing i did that was different this time.
Please help if there is a link to any thing that i deleted and need to replace please provide that,
Thank You

Sounds like a firmware problem, get latest firmware here, and flash it from recovery.

RogueMoon said:
Sounds like a firmware problem, get latest firmware here, and flash it from recovery.
Click to expand...
Click to collapse
It worked!, Thank you man.
Also I have a problem with the same device that it charges in recovery or switch off mode but it does not charge while in system.Thinking of starting a new thread but if you can answer ,no need to do that.Again Thanks.

Weird. First I would make sure that the device indeed doesn't charge in system (install Ampere app, or use a USB power meter if you have one) - otherwise it might be a UI problem. Other than that, if that's indeed the case I would do a clean reflash, starting with flashing a latest stable MIUI in fastboot, then recovery again, factory reset (DONT format system) and ROM (which one are you using?) again. Maybe others could chime in. Good luck!

RogueMoon said:
Weird. First I would make sure that the device indeed doesn't charge in system (install Ampere app, or use a USB power meter if you have one) - otherwise it might be a UI problem. Other than that, if that's indeed the case I would do a clean reflash, starting with flashing a latest stable MIUI in fastboot, then recovery again, factory reset (DONT format system) and ROM (which one are you using?) again. Maybe others could chime in. Good luck!
Click to expand...
Click to collapse
Thanks i will try that.?

Related

[Q] USB connections stopped working?

I had USB connection working OK a few weeks ago but not now. It connects through fastboot and abd, but in normal device on mode, it will not show the internal or external devices anymore. I uninstalled the derives and reinstalled, but no luck. I also tried a different cable. I also could not mount the SD with 4Ext and tried different computer it was also set up on.
I am on latest Energy ROM (7-30-1012) but am not sure if I was on an earlier Energy ROM when I last connected. I was on the previous one when i tried to connect yesterday, so updated to the latest with no success.
Are USB connections working OK on Energy ROMs? If so, anyone have any suggestions.
I am making a backup and going to restore the OTA
Update - works OK with ICS OTA backup - so it is Energy ROM in this case.
gaww said:
I had USB connection working OK a few weeks ago but not now. It connects through fastboot and abd, but in normal device on mode, it will not show the internal or external devices anymore. I uninstalled the derives and reinstalled, but no luck. I also tried a different cable. I also could not mount the SD with 4Ext and tried different computer it was also set up on.
I am on latest Energy ROM (7-30-1012) but am not sure if I was on an earlier Energy ROM when I last connected. I was on the previous one when i tried to connect yesterday, so updated to the latest with no success.
Are USB connections working OK on Energy ROMs? If so, anyone have any suggestions.
I am making a backup and going to restore the OTA
Update - works OK with ICS OTA backup - so it is Energy ROM in this case.
Click to expand...
Click to collapse
Regardless of the Rom you are running, When trying to mount the USB in recovery, the rom you are running would have no bearing on whether it works in recovery or not. I myself run Energy Rom, and it work fantastic. If u decide to go with Energy Rom again, i recommend a full wipe. No phone is the same. Random issues do occur.
death4u said:
Regardless of the Rom you are running, When trying to mount the USB in recovery, the rom you are running would have no bearing on whether it works in recovery or not. I myself run Energy Rom, and it work fantastic. If u decide to go with Energy Rom again, i recommend a full wipe. No phone is the same. Random issues do occur.
Click to expand...
Click to collapse
I thought of that with respect to recovery - wondering if mounting SD works with 4ext.
I restored Energy 6-19 and it connected fine, so probably a bad install of the latter versions. Good news in any case, as I was afraid I had a hardware issue (connection socket, etc.)
Just flashed 7-30 version again (without full wipe as before) and now see both SDs OK - strange....
Try fixing permissions in recovery. I had that issue once and fixing permissions fixed it. Not saying it will work with everything but its worth a shot.
Double0EK said:
Try fixing permissions in recovery. I had that issue once and fixing permissions fixed it. Not saying it will work with everything but its worth a shot.
Click to expand...
Click to collapse
I had tried that but it did not fix it. I just had a bad install and restoring an earlier version and flashing over with the latest ROM version cleared it up.

Help! Flashed Mi4 ROM and my phone is now half-broken

Hello friends,
In a moment of a severe mental handicap, I appear to have flashed a Mi4(cancro) ROM in EDL mode when I was trying to unlock my bootloader.
(The reason was that the guide I was using had a broken download link, so I searched for the filename and downloaded from one of the mirrors I found. I did not realize I was now downloading a file with a different device prefix (cancro instead of kenzo.).
So after the unavoidable brick, I was able to recover by flashing a proper Kenzo MIUI rom with disabled device checks (Since the phone now thought it was a Mi4, I guess).
MIUI is booting, but most of the functions are broken:
- No camera
- No SIM/Service
- Can't adjust brightness
- No rotation
Maybe there's more stuff broken, but I did not check every corner.
I moved on to try CM13, but that won't boot up at all (just sits there at the boot animation).
So far everything I've tried to get the phone back into a working state has failed, but I'm still getting used to this phone's specifics, so I may have missed something.
Please tell me there is something I can do.
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Abd121 said:
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Click to expand...
Click to collapse
Thank you. I can indeed get to recovery, but I always end up without sim card and camera when I flash an official rom.
I just tried to go back to the shop rom from geekbuying, that at least made brightness and rotation work, but still no signal/camera. I feel there's some firmware missing or was overwritten by my stupid action and now there does not seem to be a simple way to get it back up.
EDIT: So I just found out that my IMEI is gone. I will try to use a guide to re-set it. Hopefully, that will get mobile service running again. Dunno about camera, though

Moving from CM13 to OOS 3.1

Hey Guys. I currently have CM13 and TWRP recovery. I'm slightly confused on how I should try out the latest OOS 3.1.
Can I simply flash the OOS zip through TWRP? Or will I need to flash the stock recovery, flash 3.0.2 and then flash 3.1?
Any guidance here for a quicker turnaround will be helpful.
Thanks!
You need a clean flash. The way I prefer to do it is to get the pro version of Titanium Backup, and backup all your user apps. You can do the system apps if you think you might return to CM. You can also dump the backup to your PC or an OTG USB if you want. When you're ready to flash, go into TWRP and wipe all except Storage, then flash the OOS zip. When you get back in and setup, get Titanium Backup again, and restore your backed up user apps. Only do the user apps, system apps from CM will likely fail. You may want to stay away from any OTA updates though, I think it borks TWRP so you have to re-do all of that, maybe someone else can confirm this because I'm not 100% sure. Happy flashing, let us know how it goes.
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
level5music said:
You need a clean flash. The way I prefer to do it is to get the pro version of Titanium Backup, and backup all your user apps. You can do the system apps if you think you might return to CM. You can also dump the backup to your PC or an OTG USB if you want. When you're ready to flash, go into TWRP and wipe all except Storage, then flash the OOS zip. When you get back in and setup, get Titanium Backup again, and restore your backed up user apps. Only do the user apps, system apps from CM will likely fail. You may want to stay away from any OTA updates though, I think it borks TWRP so you have to re-do all of that, maybe someone else can confirm this because I'm not 100% sure. Happy flashing, let us know how it goes.
Click to expand...
Click to collapse
Not an issue with Titanium backup. I carry the load of backups along regularly.
I was concerned about flashing it via TWRP, which you confirm shouldn't be a problem. And I guess it shouldn't overwrite my recovery too? Perfect. I will try and spend some time on this over the weekend to compare with the CM. Thanks!
Techgod said:
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
Click to expand...
Click to collapse
Did you go the OTA mode, update flash or full flash? Also, I believe if it's a big change, a clean flash would be the better option over dirty flash.
You can also try wiping cache / dalvik and turning on app optimization. Might work? Can also try custom kernel?
I'm so intrigued where I read somewhere, that the Antutu benchmark jumped upto 80k on OOS 3.1.
Thanks!
rezapatel said:
Did you go the OTA mode, update flash or full flash? Also, I believe if it's a big change, a clean flash would be the better option over dirty flash.
You can also try wiping cache / dalvik and turning on app optimization. Might work? Can also try custom kernel?
I'm so intrigued where I read somewhere, that the Antutu benchmark jumped upto 80k on OOS 3.1.
Thanks!
Click to expand...
Click to collapse
I tried the OTA update like i do for every build. Its just not my problem, my friends phone is also behaving same even after factory reset. 3.0.2 was better in terms of battery. But the performance of 3.1.0 is better than 3.0.2. Its very smooooooth.
So I might as well stay away from it? Honestly I'm fairly happy with CM13 except for the fact that double tap feature turned on makes the phone vibrate when talking on a call!
Doesn't beat the snapiness on CM13. I'm back!
Techgod said:
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
Click to expand...
Click to collapse
That's not true. I get 6 hours of SOT and over 24 hours of standby with stock 3.1.0 with no modification at all.

GApps error after installing custom ROM

So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2

Return to official rom

Hello
I was using mokee 7.1.1 https://download.mokeedev.com/?device=nx531j so far and I want to go back to stock ROM: https://www.nubia.com/in/support.php?a=download
Boot TWRP (I believe is 3.0), I do wipe of everything except sdext (internal included, I do not care), install zip with official rom and restart ... Apparent boots ok but stays on the screen "be yourself" 15 minutes and nothing
I have to do something else?
Thank you
chascos69 said:
Hello
I was using mokee 7.1.1 https://download.mokeedev.com/?device=nx531j so far and I want to go back to stock ROM: https: //www.nubia.com/support.php? A = download
Boot TWRP (I believe is 3.0), I do wipe of everything except sdext (internal included, I do not care), install zip with official rom and restart ... Apparent boots ok but stays on the screen "be yourself" 15 minutes and nothing
I have to do something else?
Thank you
Click to expand...
Click to collapse
Is the stock rom version you are trying to use lower than android 7.0? Because there are many devices in which you can't easily downgrade the system, so results in bootloops.
I think not:
"【Update Info】
The upgrade this time updated to Android Nougat and Nubia UI5.0."
Is nougat too... 7.1.1?..... but mokke is 7.1.2
Is that the problem?! Is minorversion difference...
And... the solution?
And whats about flash boot.img, recovery.img first? https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=es
Ready:
- Repair system option (I do not know if it is necessary)
- Wipe advanced all included sd card
- Format sd card (TWRP option)
- Install zip
- Wipe advanced all included sd card
- Format sd card (TWRP option)
chascos69 said:
Hello
I was using mokee 7.1.1 so far and I want to go back to stock ROM:
Boot TWRP (I believe is 3.0), I do wipe of everything except sdext (internal included, I do not care), install zip with official rom and restart ... Apparent boots ok but stays on the screen "be yourself" 15 minutes and nothing
I have to do something else?
Thank you
Click to expand...
Click to collapse
Hello @chascos69, can I make you a little bit question?
Are you experience some bugs on this ROM (Mokee)? Because that's my girlfriend's phone and I flash this ROM for her, is the best ROM she's gotten, but sometimes, when battery goes to 30% or less, her phone shut down. I wipe battery stats on TWRP (Stalence Tools), calibrate (I think did right) battery, but nothing solve the problem.
Another bug, is when she goes to street and turn on the mobile data and turn off Wi-Fi, the mobile data apparently turn on, but she hasn't conection.
Smartphone is new, it doesn't reach year of life, this problems only have in this ROM, I'm not complaining of it, it's really awesome and I know it is nightly version, but I want to know: Have you this bugs too?
Thanks for all man
Axelbt said:
Hello @chascos69, can I make you a little bit question?
Are you experience some bugs on this ROM (Mokee)? Because that's my girlfriend's phone and I flash this ROM for her, is the best ROM she's gotten, but sometimes, when battery goes to 30% or less, her phone shut down. I wipe battery stats on TWRP (Stalence Tools), calibrate (I think did right) battery, but nothing solve the problem.
Another bug, is when she goes to street and turn on the mobile data and turn off Wi-Fi, the mobile data apparently turn on, but she hasn't conection.
Smartphone is new, it doesn't reach year of life, this problems only have in this ROM, I'm not complaining of it, it's really awesome and I know it is nightly version, but I want to know: Have you this bugs too?
Thanks for all man
Click to expand...
Click to collapse
Battery problem... yes! solved with battery calibration app
Mobile data... yes! Still appears... in moke 9 you can change operator and select again yours... it solve this problem

Categories

Resources