Develop Bugs

Multiple problems with MIUI 1.5.6

Hi!
This is my first time posting, but I have been using MIUI for about 6 months now. Its phenomenal. I recently updated to MIUI 1.5.6 on My EVO 4G. Ever since I did it The battery drains extremely fast compared to the previous version of MIUI i was using which was 1.4.3, I think.
The camera is also not working, it just goes to a black screen and then force closes.
I tries to change the kernel to Tiamat 4.0.1 and 4.0.2 but it fails each time I try to do it. I have tried other kernels including 2.6.35.8-bcblend-CFS-sim_io-classRCU, which may not be for gingerbread. Nothing works. I currently have 2.6.37.6-cyanogenmod-01493-g70877de Kernel installed and I need help getting a new one on here.
The phone burns through so much power now its insane. I used to get at least 14 hours out of it. Now, I had it fully charged about 20 minutes ago and its already down to 88%. Can anyone help?
Sorry if this is the wrong format or whatever:
Specs:
EVO 4G
Model: PC36100
Android Version: 2.3.4
Baseband Version: 2.15.00.11.19
Build: MIUI 1.5.6
I am almost a complete novice when it comes to this, so any help would be appreciated but if you could give explicit instructions on how to do everything that would be amazing.
Thanks!

Are you wiping cache and dalvik before flashing the new kernal?

Yeah, I reloaded MIUI after doing a format all and nothing changed. It still wouldn't let me flash the new kernel.

Use juicedefender beta for battery, use the camera fix from the miui.us forums (camera is a known issue, I had it at first, applied fix and all was fine) and flash a tiamat kernel manually through recovery, not kernel manager as for some reason kernel manager seems to screw up for me when flashing tiamat kernels.
edit: heres a link to the fix.
http://forums.miui.us/showthread.php?236-If-you-re-having-issues-with-your-camera-on-1.5.6
Also, I could be wrong but I believe some of the recent updates came stock with cm kernel, so flashing tiamat could also greatly help with battery. Try Tiamat 3.3.7 if youre having problems with newer releases as 3.3.7 seems to be the most stable.

I am flashing the kernel through recovery. Thats the only way I know how to do it. It always worked fine before and only now is it being problematic. I will try the defender app and see if I can find the camera fix. Thanks!

Jasonectomy said:
I am flashing the kernel through recovery. Thats the only way I know how to do it. It always worked fine before and only now is it being problematic. I will try the defender app and see if I can find the camera fix. Thanks!
Click to expand...
Click to collapse
Posted the link for the camera fix! and what do you mean your having a problem flashing kernels? Your still s-off correct? And make sure when you are transferring kernels to sdcard you unmount sdcard when done, some of the newer kernels have problems with transfering data to sdcard quickly, and when you unmount or eject your card it insures the transfer is successful instead off cutting it off half way through.

I noticed the link for the camera fix, Thank you so much! I an going into recovery and when I flash Tiamat 4.0.1 or 4.0.2 I get:
E:Wrong digest:
system/lib/modules/sequans_sdio.ko
E: Verification Failed
Zip Verification Failed!
Zip isn't signed correctly!
Installation aborted
I'll try 3.3.7 and see if that will install. Thanks again.

Try Kernal manager lite. It flashes the kernel for you. Battery drain is expected when switching Kernals. Wipe battery stats and give 3 days for Kernal to settle in.
Sent from my PC36100 using XDA Premium App

Jasonectomy said:
I noticed the link for the camera fix, Thank you so much! I an going into recovery and when I flash Tiamat 4.0.1 or 4.0.2 I get:
E:Wrong digest:
system/lib/modules/sequans_sdio.ko
E: Verification Failed
Zip Verification Failed!
Zip isn't signed correctly!
Installation aborted
I'll try 3.3.7 and see if that will install. Thanks again.
Click to expand...
Click to collapse
Usually mismatched libs mean youre using the wrong kernel. Cayniarb puts out multiple versions of tiamat for multiple devices. Make sure you downloaded the one for the evo (should say evo in file name) and not the one for the incredible, xoom, etc.

njonas01 said:
Try Kernal manager lite. It flashes the kernel for you. Battery drain is expected when switching Kernals. Wipe battery stats and give 3 days for Kernal to settle in.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Like I said, I recommend not using kernel manager lite for flashing Tiamat as I've had some problems flashing tiamat through kernel manager, most other kernels seem to be fine for me? Odd but it is the case. Although kernel manager would be good for downloading the kernels since it automatically picks out your device and you can be sure you download the correct kernel.

Thank you! Kernel Manager Lite seems to have worked! I'll see how the battery problems go after this flash.
The camera is the only problem left, and I can't apply the fix, I can't seem to find the /system folder...

You need to use root explorer as astro file manager and other basic file managers dont have the elevated privileges to view /system. The app is a couple of dollars but I HIGHLY recommend it to any and every rooted phone user.

MIUI 1.5.6
I downloaded and redownloaded the rom twice and flashed it twice, did the wipe/factory data reset and calkulin wipe and both times it would install different things for the rom, like the first time it didn't install Gmail or market den the next time it only installed market and settings and 3 or 4 other apps and thats it, and when i try sending a text, i choose a person and type the message, when i hit send it says, no valid user, message can't be sent, will someone please respond and let me know whats wrong? I would really appreciate it, my brain is going in all different directions, i hope you can understand what im typing because im very confused right now
Thanks,
Tj

[Q] Blu_Kuban Rom Updater E4GT

Currently running V1.0.3.3 and my Rom updater is broken and or not normal. Installed V 1.0.3.4 and same thing. Unable to install Part 2 because it is not available to select in the rom updater.
Installed Acquariusofts Rom Updater 1.3.0 but did not help. It shows version 1.2.0
in the settings section. Does anyone have an idea how to fix this? Would appreciate any help and or suggestions. Thanks

ctanner3409 said:
Currently running V1.0.3.3 and my Rom updater is broken and or not normal. Installed V 1.0.3.4 and same thing. Unable to install Part 2 because it is not available to select in the rom updater.
Installed Acquariusofts Rom Updater 1.3.0 but did not help. It shows version 1.2.0
in the settings section. Does anyone have an idea how to fix this? Would appreciate any help and or suggestions. Thanks
Click to expand...
Click to collapse
In the ROM thread he tells us what happened. He placed the Updater on his Dropbox and it got overloaded so it's down, for now. As soon as it comes back up you'll have access to everything you need. If you had 1.0.3.3 previously installed then you should still have the part two and you can just flash that through recovery.
Be patient, it'll be worth the short wait.

Check the posts towards the end he posted temp links to what you need till new hosting is found
http://forum.xda-developers.com/showthread.php?t=1625535
Sent from my epic touch blazing with the Blu Kuban FE10 build1.0.3.4

[Q] When flashing an ICS (or JB) ROM

Sorry if this was posted, the SGSII is active and sort of cluttered so its hard to find which one is what.
The question: So I successfully flashed, gained root, and got a custom recovery for my friends SGSII. Whenever I try to flash a ROM, like CyanogenMod 9 or MIUI.us it get stuck at boot, and yes I am on ICS. I also heard that the CWM Recovery for this phone is messed up, so can anyone fill me on that? Is there a special thing I have to do before flashing a ROM? Do I have to use TWRP instead of CWMR?
CWM Recovery version: 5.0.2.7
Android OS: ICS 4.0.4
SGSII Version: T-Mobile

th3controller said:
Sorry if this was posted, the SGSII is active and sort of cluttered so its hard to find which one is what.
The question: So I successfully flashed, gained root, and got a custom recovery for my friends SGSII. Whenever I try to flash a ROM, like CyanogenMod 9 or MIUI.us it get stuck at boot, and yes I am on ICS. I also heard that the CWM Recovery for this phone is messed up, so can anyone fill me on that? Is there a special thing I have to do before flashing a ROM? Do I have to use TWRP instead of CWMR?
CWM Recovery version: 5.0.2.7
Android OS: ICS 4.0.4
SGSII Version: T-Mobile
Click to expand...
Click to collapse
Yes try TWRP it never let's me down... make sure you wipe too!

iNeedICS said:
make sure you wipe too!
Click to expand...
Click to collapse
Thats what my mother always says!

vassosman said:
Thats what my mother always says!
Click to expand...
Click to collapse
Yes but in real life it unnecessary

I was having some problems too until I realized that I was using an ancient version of CWM. Flashed a newer CWM Touch and all was well after that - I was able to to perform a successful wipe and flash of CM10 - everything just worked perfectly after that.

Let me get this straight...
Flash TWRP
Use TWRP to flash Super Wipe
Flash a ROM
... and enjoy ROM?
Did I get it right?

I don't understand and believe me I'm not complaining but I have cwr5027 and use dark side scripts all the time and never have problems.
Is it just a matter of time? I flash often...very often.
Sent from my SGH-T989 using xda app-developers app

Thank you guys! I cannot hold my gratitude so I have to post a thanks to those who have helped! TWRP is the best alternative recovery
I have now successfully flashed CM9.1 and my friend will be very happy indeed with the bloat gone and the pure ICS feel!

[Q] S3 4.1.1 Kernel

I can't seem to find this kernel on XDA or google.
Im on my SGH I747M 4.1.1
with kernel 3.0.31-538866 [email protected]#1
Where can I get this kernel to flash?
Reason why I'm asking is i'm trying to flash new kernels and want this as a back up to have it stored so i can restore it.
Unless....TWRP recovery images can recover the kernel when you restore that image?
Thanks!

mikoal said:
I can't seem to find this kernel on XDA or google.
Im on my SGH I747M 4.1.1
with kernel 3.0.31-538866 [email protected]#1
Where can I get this kernel to flash?
Reason why I'm asking is i'm trying to flash new kernels and want this as a back up to have it stored so i can restore it.
Unless....TWRP recovery images can recover the kernel when you restore that image?
Thanks!
Click to expand...
Click to collapse
When you restore your backup, it will restore the kernel as well.

and where to get the last kernel for my SGH-I747M.... ( shows this kernel 3.0.31-274808 [email protected] # 1 ) this kernel came with a rom called Hiperdrive RSL11...
but I need to reinstall the kernel to fix something wrong, for that reason I ask for the last or the better kernel for my Samsung galaxy S3 ???
thanks for your help

boni7010 said:
and where to get the last kernel for my SGH-I747M.... ( shows this kernel 3.0.31-274808 [email protected] # 1 ) this kernel came with a rom called Hiperdrive RSL11...
but I need to reinstall the kernel to fix something wrong, for that reason I ask for the last or the better kernel for my Samsung galaxy S3 ???
thanks for your help
Click to expand...
Click to collapse
It's in your ROM zip. Named zimage. Extract that file and you can flash it using Odin.
You can also dirty flash the ROM (without wiping) and it will reflash it.
Btw, reinstalling the kernel doesn't do anything if it's already on your phone. It won't fix anything. If you flashed another kernel though, that's another story.
May we know what you're trying to fix?

BWolf56 said:
It's in your ROM zip. Named zimage. Extract that file and you can flash it using Odin.
You can also dirty flash the ROM (without wiping) and it will reflash it.
Btw, reinstalling the kernel doesn't do anything if it's already on your phone. It won't fix anything. If you flashed another kernel though, that's another story.
May we know what you're trying to fix?
Click to expand...
Click to collapse
look what this member write in the Hiperdrive RSL11 rom :
Venom0642 said:
I would reflash the rom again clean make sure in aroma you chose full wipe system/data and make sure you don't select S Note and flash again once you do that don't reboot from aroma take check mark off aroma so you don't reboot then in recovery flash your kernel which ever your going to flash after that wipe cache davik then reboot do not set up Google account let it sit for 5 to 10 mins after that reboot one more time then let it sit 5 more min after that then start setting up your google account you should not get that popup or any other issues.
Click to expand...
Click to collapse
how to do and flash via odin, if I cant leave the installing rom, because that say Venom in his post ???
this its the post:
http://forum.xda-developers.com/showthread.php?t=2176793&page=113

Help getting from stock rooted 4.1.2 to CM11/DU 4.4.4

I just dug up my Epic 4G Touch and wanted to breathe some life back into it. I rooted it way back in the day but always left it stock. Now I'd like to get CM11 or Dirty Unicorns 4.4.4 on it with a custom recovery.
I've been doing a whole heck of a lot of reading trying to figure out how to avoid bricking my device in the process, but I'm still confused.
Device details
ROM: Stock 4.1.2
Baseband: S710.10 S.GB27
Kernel version: 3.0.31-1014481 [email protected]#3 SMP PREEMPT Fri Mar 1 04:27:41 KST 2013
Build number: JZ054K.SPH-D710.GB27
I have PRV/fwrev 0x19, so I'm apparently "susceptible to the EMMC /data corruption issue (which should now be referred to as EMMC lockup issue)", but it looks like I have a Gingerbread modem, so maybe not?
What I can't figure out is if I can or should fix/work-around that with a PIT file. I'd rather not make a stupid mistake, so I was hoping someone could point me in the right direction. What is my path to a custom Recovery + ROM (if any)?

I replied to your other thread, but maybe someone will else will see my answer here and help you further. I followed these directions. I'm sure it would work for you also, I have a MAG4FA 0x19 chip. Only problem is the links for the blasphemy kernel are dead so maybe someone can help you with that.

I just flashed philz_touch_6.19.3 recovery, rebooted, the flashed the CM11 nightly and gapps.

Space
grimdirge said:
I just flashed philz_touch_6.19.3 recovery, rebooted, the flashed the CM11 nightly and gapps.
Click to expand...
Click to collapse
Are you having any issues with space on the /ssystem with gapps?

MrLint said:
Are you having any issues with space on the /ssystem with gapps?
Click to expand...
Click to collapse
No. I used lanchon's script to repartition my internal storage.

shar88 said:
I replied to your other thread, but maybe someone will else will see my answer here and help you further. I followed these directions. I'm sure it would work for you also, I have a MAG4FA 0x19 chip. Only problem is the links for the blasphemy kernel are dead so maybe someone can help you with that.
Click to expand...
Click to collapse
Thanks for the guide. That got me far. Went down a few rabbit holes in the process, but now I know more about my phone. All good. The only reason this didn't work for me right away is because I canNOT find a live mirror of the blasphemy kernel anywhere. Dead end
grimdirge said:
I just flashed philz_touch_6.19.3 recovery, rebooted, the flashed the CM11 nightly and gapps.
Click to expand...
Click to collapse
grimdirge said:
No. I used lanchon's script to repartition my internal storage.
Click to expand...
Click to collapse
Do you have a link to lanchon's repartition script? I think I found the reference here and the download here, but not sure if that's right. I've also never repartitioned my Epic 4G Touch. Is there a walkthrough somewhere?

Lanchon gives a step by step tutorial and examples here:
https://github.com/Lanchon/REPIT

So here's my current status:
I ODINed back to stock rooted EL29 and loaded CWM Rogue 5.0.2.7. However, I can't install anything from CWM. I always get this error (see attached image):
Code:
This package is for device: epic4gtouch,SPH-D710,d710,smdk4210,SPH-D710VMUB,SPH-D710BST; this device is smdkc210.
I just reparitioned, following these steps, including formatting my partitions, so now all I have is my CWM recovery and no ability to install anything .
Do I need to ODIN to a different version or something?

Shoot, didn't see your reply before @grimdirge. Thanks! However, that guide requires TWRP. How the heck do I get TWRP on this thing? I would love it if I could get an ODIN flashable TWRP, but all I can find are zips, which you need a custom recovery for (and I have the above mentioned problem installing zips), so I feel like I'm caught in a Catch-22.

You'll need to use this recovery:
http://forum.xda-developers.com/gal...t/isorec-isolated-recovery-galaxy-s2-t3291176

grimdirge said:
You'll need to use this recovery:
http://forum.xda-developers.com/gal...t/isorec-isolated-recovery-galaxy-s2-t3291176
Click to expand...
Click to collapse
The instructions show how to install a .img file using ADB, but the links are all to .zip files (without .imgs inside them). Just tried installing recovery-Lanchon-IsoRec-CM-6.0.5.1-20160112-d710.zip as well as recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip from my CWM recovery. Both installations give me the wrong device error I mentioned above. Should I ODIN to something before trying this? Are there .img files or ODIN .tar files I can use to flash the recovery somewhere?
Sorry for all the questions. I've flashed hundreds of ROMs on 10s of devices. I've never had this kind of trouble before.

Got it!
Holy cow. I modified:
Code:
/META-INF/com/google/android/updater-script
To allow 'smdkc210' (apparently, my device).
I did that for all the .zip files I've collected during this process. FINALLY, I was able to install the philz recovery you recommended, and from there, I was able to install CM11! Thank you!

Yeah. This device is annoyingly complicated. Look here:
http://forum.xda-developers.com/gal...c-isolated-recovery-galaxy-s2-t3291176/page43
You'll need to install the latest CM11 nightly to get the isorec kernel.
I flashed the recovery-Lanchon-isorec-TWRP-3.0.2.0-D710.zip on the above link.

grimdirge said:
Yeah. This device is annoyingly complicated. Look here:
http://forum.xda-developers.com/gal...c-isolated-recovery-galaxy-s2-t3291176/page43
You'll need to install the latest CM11 nightly to get the isorec kernel.
I flashed the recovery-Lanchon-isorec-TWRP-3.0.2.0-D710.zip on the above link.
Click to expand...
Click to collapse
Never would have found that link on my own. Awesome. Feels good to have TWRP on my phone!

So something here, within this thread, has worked... and all the links are valid still? Welp, see you folks in 3 more days when I either give up, figure it out, or brick my phone beyond repair.