Hi,
I have been using variiety of ROMs from 2 years on S2 i9100. Problem started with MIUI. Sleep of Death that used to be cured only with reboots. Then i changed the Kernel to "speedmod-kernel-s2-jb-k5-7-CWM.zip " and problem began.
I started getting Status 7 errors when i tried to update MIUI to newer version. I deleted asserts from Updater-Script and installed new version. Also, changed kernel to "Siyah-s2-v6.0b5-CWM".
But today, i opened MyTracks app and phone rebooted.
Since then, i would restart my phone. The phone will reach the "Media Scanning" stage and would then shut down (not SOD).
I restored my NANDROID backup but phone again shut down just after booting up --- right when "Media Scanning" icon appeared at top.
STRANGER -- when i tried to reboot phone after disconnecting phone won't start --- and doesn't go in recovery.
BUT when is being charged using charger phone is able to get into recovery.. and is able to reach and then shutdown at Media Scanning stage.
I made a mistake of flashing Official Firmware (from Sammobile) using ODIN from PC. Now, i do not have CWM recovery.
My phone behaving same even after flashing :-
1. Two different ROMs (Jellybam 7.8 and MIUI 3.7.5
2. Two different Kernels (Siyah-s2-v6.0b5-CWM and speedmod-kernel-s2-jb-k5-7-CWM)
3. Official Firmware Jellybean 4.1.2 using ODIN.
Now,
1. i can't go into recovery without charger
2. phone won't reboot normally without charger
3. shutsdown at media scanner, when rebooted after connecting charger
4. no NANDROID backup working -- same problem as above
5. Kernel changing did not help
6. Flashing ROM did not help --- MOSTLY switches off during installation process
7. ODIN-Flashing-Official Firmware has made me stuck with official-recovery (going to try deleting the asserts statement to see if installation succeeds without status7error)
Need expert help. Can anybody please help me out.
I won't mind paying for your efforts, too.
Please help.
Thanks.
Try new battery? Power problem.
shall try first thing in the morning
andrewwright said:
Try new battery? Power problem.
Click to expand...
Click to collapse
Have not tried new battery. Will buy a new one in the morning and see if that works.
Any other suggestions?
Thanks..
andrewwright said:
Try new battery? Power problem.
Click to expand...
Click to collapse
However, the battery is charged 100% and i am able to enter StockRecovery and browse. It fails only during installation of ROMs / Recoveries/ Kernels.
Run rom nuke and kernel nuke scripts from hawerkpaul then reflash rom+gapps see if that does it. So cwm works ok? with out charger connection? If so try the nuke scripts. Also try super wipe by biftor.
Edit your on stock recovery now or cwm? Dont run scripts in stock get cwm bk on ohone then flash nuke scripts. Or redownload stock firmware and reflash with odin. Then flash philz kernel that will bring bk cwm.
Solved
Hi Friends!
It was a battery problem.
:crying: sad i wiped my emmc before checking battery.
Thanks for support guys.
Nuke Scripts are new for me. Shall explore that area, might be helpful in future.
Thanks again.
Rom Nuke scripts will clean up your system ready for flash. Same as kernel Nuke scripts. I don't use them much. I format system,data,cache,preload if its 4.1.2 and then flash Roms. Always works ok with out problems. Only time iv used kernel nuke is to get of Apollo kernel. Glad you sorted your problem out. :thumbup:
Related
Hi there
So i tried to install Steve's Kernel, but my device is in Boot loop now... (my device is international, it has Physical home button....)
i did some search around and found this : http://forum.xda-developers.com/showthread.php?t=1531850
but i am not sure if this is the solution to my problem...
i can go to recovery mode and download mode by the way
so i am gonna assume i am not completely ruined....
Any ideas guys?
porkho biv9
after my first flash I was in the same situation as you. flashing the stock rom was the only solution.
But in my case it was no problem, because I had nothing important on the device. It was almost fresh out the box.
I've the experience, that doing a full wipe causes a higher possibility of getting bootloops. So I only clear the dalvik cache after flashing roms/kernels. If it boots -->everything is fine.
Do you have a backup? CWM or titanium backup?
Hi
Unfortunately i don't have any of those....
do you think that link i gave in the 1st post can be useful?
Thanks in advance....
Yes, I downloaded the .pit and .tar.md5 file and did everthing of these steps:
Flashing Time
1.3: If your device is bricked and you can go to download mode:
1.3.1: Download one of the roms (according to your device)
1.3.2: Open odin, take the .pit file and put the rom .tar.md5 in the PDA SECTION
1.3.3: Before flashing, ensure re-partition is checked.
1.3.4: Flash, when the flash is finished your device should reboot.
1.3.5: When you device reboots, you will be in recovery with red errors which are saying mostly of the time: Can't mount... To erase these errors, WIPE DATA.
1.3.6 Reboot and enjoy your restored device!
Click to expand...
Click to collapse
I had no backup too and tried everything. This (zaclimon's thread) was my last hope after 2 hours of searching and it worked.
Hey !
ah, did i read that right? Re-partition HAS TO BE CHECKED??
and do you recommend installing Steve's Kernel after i hopefully returned my device?
yes it has to be checked in this case.
I had terrasilent 1.1 and klassik rom for 2 days but I had a lot of freezes, so I flashed the stock rom 2.3.6 and steve's kernel because the main reason I wanted the SGP4.0 was the combination of wolfson DAC+wolfson+poweramp.
If you are happy with music only, than this is enough.
But now I'm using my device more often (GTA 3 is on sale right now) and flashed terrasilent v1.2 two days ago. Now I'm waiting for the next version of StratusROM and will give it a try. Because sometimes I am not completely satisfied with the performance (sometimes) and it often wakes up while deep sleep causing more battery drain than usual.
natkingcole said:
yes it has to be checked in this case.
I had terrasilent 1.1 and klassik rom for 2 days but I had a lot of freezes, so I flashed the stock rom 2.3.6 and steve's kernel because the main reason I wanted the SGP4.0 was the combination of wolfson DAC+wolfson+poweramp.
If you are happy with music only, than this is enough.
But now I'm using my device more often (GTA 3 is on sale right now) and flashed terrasilent v1.2 two days ago. Now I'm waiting for the next version of StratusROM and will give it a try. Because sometimes I am not completely satisfied with the performance (sometimes) and it often wakes up while deep sleep causing more battery drain than usual.
Click to expand...
Click to collapse
People were experiencing bootloops with steve's kernel. Right now I'm using the latest terrasilent with stratus and I don't have any bootloops. (and you can change to ext4 with terrasilent)
Hi there
you guys mind giving me link to that Transilblaba thing ?
Thanks in advance...
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
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.?