Hi i'm on Xioami.eu dev and i'm getting a toast every time my phone reboots that says "find device storage is corrupted, maybe unsafe now"
Please any way to fix it? Already try EU stable and dev, Revolution OS and same...
Thanks for your help
Related
suspect my new rom is corrupted on my jamin
does anyone know how to completely flash the rom before installing a fresh copy of the new rom. As i suspect the very 1st rom installed in it by the manufacturers were corupted. is there like a bootloader program i could use? or anything? pls help me
when i try re-installing the new rom come out with error message of [326] and [302]
but if i keep trying and try it eventually succeed but the rom does not appear clean pls help. keps on crashing and fading all the way white and taking ages to do a soft reset pls help, thx
i instaled a new rom when i instaled it the phone restarted and show me the pic of the rom or (htc)
after that the phone restarted and the same problem happening
i tried 5 roms to fix that but noting happen the problem stayed >_<
i wish there is some one can help me
thnx
"need more info"
What device do you have? (EU or TMO)
What system and cache sizes have you configured?
What ROMS are you trying to install? Do they require an SD-EXT partition?
If so, have you created that partition on your card?
When flashing the ROM, did you choose the correct option? (i.e. DataOnEXT or NativeSD)
You need to help us help you
P.S: This thread is now cursed.
(Bug Help Request) MIUI - Shiro - Inconsistent "No Service->Service->No Service" Bug
Hello all! Hoping to find some help for the problem which I have been dealing with for the last month and a bit or so.
I have a 1337m (Canadian/Bell SGS4) which I have flashed with the i9505 MIUI rom as they have the same specs and can be used more or less interchangeably, or so I have been advised over the past year or so.
Anyways, I had recently updated my MIUI version with one of the latest ones, "miui_i9505_shiro_5.9.4_17da645643_4.4", and then have also recently updated it with no problems to MIUI 7 (5.10.2 Beta).
The whole time though with this rom I have been dealing with having "No service" come up quite often, and then bouncing between getting mobile data and then going back to "No Service" for absolutely no reason (With other roms I have been getting constant Mobile Data connections on the same routes so I know it isn't an issue with my phone's hardware or data connection, and it must be the ROM). I have also searched around a bunch for this bug and have come across some threads mentioning the same problem, and people had mentioned that when the recovery was changed, or a certain kernel was changed, this " 'No Service' appearing when service is actually there, however locking out applications from said data connection" bug is fixed, however I don't claim to know the most about more advanced things like swapping kernels, or changing recoveries, etc. I have also heard that people were talking about how all of Shiro's ROMs for the i9505/SGS4 seem to have this problem, so hopefully I am not alone with this. Also, my APN settings are not grayed out if that happens to have anything to do with the whole thing and something can just be quickly changed there to fix it? (Sorry, I have no idea what the true problem with this issue is).
I am just a little worried that at some point in time when I really need to make a call or use the net and I can't at that exact time due to this bug that it may really complicate things... therefore I am hoping to get a hand with fixing it and understanding how I can monitor and fix this for any future issues as well.
Hopefully I can get a hand with this from you guys! It would be much appreciated!
TL;DR: MIUI Shiro i9505 Rom user with "No Service" bug looking for help on how to fix it; have heard that it is indeed a common problem with Shiro Roms, and also that it may be kernel or recovery related? Also, my APN settings are not grayed out if that happens to have anything to do with it and something can just be quickly changed there?
Thanks in advanced for any help, guys!
Flash with philz recovery resolv the problem
Enviado desde mi SM-T535 mediante Tapatalk
luistro said:
Flash with philz recovery resolv the problem
Enviado desde mi SM-T535 mediante Tapatalk
Click to expand...
Click to collapse
First of all, thanks for the quick reply!
I believe I tried with one .zip package and it wasn't flashing properly from within CWRM... I even placed it on my internal as I heard a lot of people recommending.
Any chance you might be able to direct me to the correct build/package I should be trying to flash, and also a few quick steps on how to go about flashing it? If it's just "update from .zip" in CWRM I'm alright, but if there's more too it I would appreciate any extra help! Also, it's just flashing the recovery so there shouldn't be any changes to data on my phone, (applications, etc.), meaning no need to full wipe.... correct?
I'm guessing I should be following the "Method #2 for rooted phones with CWM/TWRP Recovery" section in this thread which talks about flashing philz for the SGS4? Am I right in assuming that since I am running MIUI and have Clockwork Recovery pop up when I go into recovery mode, this would be the right one?
Sorry for all the noob questions... I just want to make sure I am doing the right things here.
Looking forward to your reply!
Just a quick update of where I'm at:
I have the latest version of Philz on my external, and have attempted to boot into recovery and install the .zip from my external sd, but I get the following error message string in CWM:
Code:
Flashing Recovery
assert failed: run_program("/tmp/loki.sh") == 0
E: Error in /external_sd/Roms/philz_touch_6.59.0-jflte.zip
(Status 7)
Installation aborted.
Looking for a hand! I'll try to flash it from internal storage also just in case that happens to work.
Update #2:
Just flashed with Odin as attempting to install from .zip on the internal brought up the same error message.
Everything seems to be working alright now!
Hopefully this thread / my replies can help out anyone else in a similar situation!
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.
Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.
Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon
Hello, it's been a while and the update doesn't fix this issue : the clock/time is TOTALLY off, for example now it shows we're in june 2018.. Is there a version that doesn't have this issue? Also backing up with encryption ALWAYS fail (unless you don't backup data partition so far)..
GoJo ^^ said:
Hello, it's been a while and the update doesn't fix this issue : the clock/time is TOTALLY off, for example now it shows we're in june 2018.. Is there a version that doesn't have this issue? Also backing up with encryption ALWAYS fail (unless you don't backup data partition so far)..
Click to expand...
Click to collapse
Format your internal storage don't set pin at lockscreen use patterns instead also download latest twrp from twrp website BTW wrong section of posting read the forum rules
...goodnight
Not having encryption or pin, that's a solution for you? Not for me!
Sent from my Redmi 3S using Tapatalk
I never had any worries with official version of TWRP. Once the clock is set, it remains .... unless you fully discharge the battery, which is not recommended at all.
You will also try the new Shrp_Land project, it seems very interesting and based on last version of TWRP.
Just tried that SkyHawk TWRP and SAME! The clock is OFF, it's still 2018.. This is not an hardware issue, i have other TWRP that displays time correctly, but sadly have some other (worse) issues so i cannot use. I downloaded my TWRP from official website, there must be a reason the clock is crazy.. Please help me find & fix the problem!