Develop Bugs

[Q] Flashing Recovery With Flash Image GUI

I just need a little input from someone. If I'm wrong about any of this please correct me. I kinda imagine the recovery to be like a mini version of the normal os. I know u can't flash a Rom from within the Rom, just as you can't flash recovery from within the recovery. You flash Roms from recovery or hboot, and you flash recoveries from hboot. So to me, it stands to reason that it would be fine to flash a recovery from within the Rom. I've used flash image GUI with no issues, ever, but I see so many people scared of it. Saying they'd never use it. I'm reluctant every time I use it, but it just works. Each time I read that someone wouldn't use it it makes me not want to just a little bit more. Should I be worried? What's the worst case scenario when using it? Thanks in advance.

Out of curiosity, how many times do you need to flash a recovery? Once was good enough for me...

Recently, amon ra 3.06, 3.07 and 3.11

I've never used it to flash a recovery but have used it to flash kernel .img a few times on evo and to flash splash screens on my intercept never had an issue but then again I'm not scared of breaking something cuz I can more than likely fix it as long as I can power up
We are legion, for we are many.

I used it to flash a recovery after unlocking, using HTCDEV method. It worked just fine.
Sent with L*W*H.

xcpefrmreality said:
I just need a little input from someone. If I'm wrong about any of this please correct me. I kinda imagine the recovery to be like a mini version of the normal os. I know u can't flash a Rom from within the Rom, just as you can't flash recovery from within the recovery. You flash Roms from recovery or hboot, and you flash recoveries from hboot. So to me, it stands to reason that it would be fine to flash a recovery from within the Rom. I've used flash image GUI with no issues, ever, but I see so many people scared of it. Saying they'd never use it. I'm reluctant every time I use it, but it just works. Each time I read that someone wouldn't use it it makes me not want to just a little bit more. Should I be worried? What's the worst case scenario when using it? Thanks in advance.
Click to expand...
Click to collapse
hope i'm not in trouble for bumping this thread from last week. wanted to clarify some of the information for anybody else who happens across. also, as the author of Flash Image GUI, feel some responsibility to help clarify any misconceptions around how Android operates and thus how Flash Image GUI operates ..
you can't flash a ROM on top of a booted ROM because some of the system files can't be replaced while being used. you can load a ROM to a different partition, and then boot to the alternative partition, but thats those cases aren't as common.
from the normal android mode, booted into the current ROM, recovery and kernel can both be "flashed" as they are stored in different partitions than the current ROM. also, the kernel is already loaded into memory, so we're able to load a new kernel into the partition and upon rebooting, the current kernel in memory is dumped, as everything in temporary memory is dumped upon reboot, and the kernel is reloaded from the partition, hence loading the new kernel.
from the normal android mode, booted into the current ROM, the recovery can be "flashed" because it is also stored on its own individual partition and not being accessed/used.
both of these processes are fairly solid and used on my phones. there should be no issues while following these standard procedures.
hope that helps clarify! if there are more questions, feel free to post. thanks for the support of Flash Image GUI!

[Q] Recovery Mode Lost after flashing ROM

Maybe this is by design and I'm just missing something. I got a new e4gt and proceeded to root it using instructions found on epic4gtouchroot.com. Basically I used odin to flash a stock EL29 ROM and then install team Rogue's CWM.
All went well with this process so I proceeded to the next step, which was to download and install a custom ROM. I installed the VeNuM ICE 5.5 since I'm a comic book nerd as well as a computer geek.
This wasn't my first time rooting. I've been rooting my EVO for a year of so, and I've rooted my Wife's Nook Tablet too, so I was a bit shocked to see that the Team Rogue CWM recovery program went bye-bye after flashing the VeNuM ROM.
I downloaded ROM manager and tried to flash the latest CWM recovery program from there, but that dind't work. I haven't tried to download the touch recovery, but I was able to reinstall the Rogue CWM recovery program, which then hosed up my ROM. I actually thought I bricked my phone for a minute, but I was able to go back into Rogue Recovery and re-flash the VeNuM ROM.
All went well and I'm back into my phone, but now again when I reboot into recovery mode, I have "Android System Recovery <3e>" like an abridged version of CWM. I don't have near as many options and wonder what's going on.
I never lost my recovery mode before when flashing a ROM. Is there some sort of custom recovery included with this ROM, or am I doing something wrong?

hi. im pretty new at this also, but i think i know the answer to this. well. not really the answer, but i know how to get clockwork recovery back onto the venum rom you are using now. you need Odin3-v1.85 (just google it) and the clockwork recovery StockCWM-EL26.tar (google). Then you put your phone in odin mode, volume down and power from powered off state, run the program, check the PDA option and browse for the stockcwm file, plug in usb and hit start. That'll put the recovery back on your phone.
But as I've been reading, a lot of times, you cannot just download the rom onto the phone or sd card and flash new roms using the cwm recovery. something about the gingerbread and ics and different kernels. .... =D

Please read the "How not to brick your e4gt" or how ever it goes in general. You need to stay away from rom manager and any touch recoveries. To answer your question, rogue recovery went away because the Venum ICE rom has the stock recovery packed in because of all the custom recovery/bricking issues we've been having with ICS. So the Dev left out custom recovery included with his rom
Sent from my SPH-D710 using Tapatalk

I'm not sure what recovery Venum comes with but this might be by design since custom CWM recovery is not installed by design on most ICS roms.
First of all read through this thread: http://forum.xda-developers.com/showthread.php?t=1525495
You chose to flash ICS; if you had chosen Gingerbread this would not be an issue so please read on... ROM manager should NOT be used with ICS. Since you are new, the only CWM recovery you should be using is the stockcwm-el26 posted here: http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Lastly and most important:
Flashing ICS can be a very dangerous thing for your phone if done improperly. Even flashing back to Gingerbread from ICS can go wrong.
Please do not do any further flashing of ICS without reading and understanding the process of flashing ICS safely!
Also, please feel free to ask lots of questions until you are comfortable with the entire process. That is why we are here.
Edit: Sorry for the very strict tone throughout. You have a very nice WORKING phone and we see a lot of newbies flashing over to ICS without a full understanding of what can go horribly wrong. We also see users asking for help here daily because they have bricked their phone (many times with no hope for repair or recovery).

Maybe I'm just lucky?
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.

BBJon said:
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
Click to expand...
Click to collapse
Coming in late to this thread but I would like to re-iterate what was said about ROM manager and pretty much everything tdunham said. Because you have been, so far lucky, does not mean that luck will continue. Best advice is to remove it and not use it. If you read through some more posts you will see that the bricking doesn't always happen on the first, second, third flash. It can all of a sudden appear. We've had VERY experienced developers brick their phones, so to think you won't just because you've been lucky is not wise.
But some of the comanailities are clear - using ICS recovery to wipe/restore and using ROM manager. Just thought I'd point that out.
If you're coming over from a different phone (HTC etc) check out Qbking77's videos. They are very informative too.
Good luck and have fun.

I'm glad that the op did some reading and had some extra help here. Our phones can be confusing but with extra reading it can be figured out. We try to list the kernel that's in the rom and these are all listed in the development section in some form or another with explanations of what they have, ie cwm or rogue recovery... In addition most of our roms list a change log that you can read that will tell what each version of the rom has in it in case you would rather use an older version. And we keep the older roms posted too... anyway happy flashing !

I've bricked my phone a few time messing around with different ICS roms and kernals. I go back and odin EL29 rooted...start all over from scratch. Try using new recovey kernals posted on ACS. I'm on FE22 with the ACS recovery and am having no issues with flashing zips and making backups as well restoring.
Sent from my SPH-D710 using xda premium

There are some repacked recoveries that Steady used to make for ICS before he disappeared. Those were never and still aren't safe for flashing ROMs though. It's safest to Odin/Mobile ODIN CWM EL26 tar whenever you need recovery and then flash whatever and then reflash an ICS kernel without recovery so that your phone boots
Sent from my SPH-D710 using XDA

[Q] CWM Recovery not sticking

CWM Rogue Recovery doesn't seem to be sticking on my E4GT. Flashed CM9 Alpha 3 from stock rooted rom. When Alpha 4 was released, I tried to boot into CWM Recovery and ended up with stock recovery. Ended up having to odin back to stock and start over to get Alpha 4 running. Same problem now that Alpha 5 is out there, tried to boot into CWM Rogue Recovery and get stock recovery.
Doing a search shows that this seems to occur on other phones. They've resolved it by deleting a boot recovery file with Root Explorer. I was just hoping to confirm with someone that this method will work on the E4GT and the name and location of the file that needs to be deleted.
I'm assuming I'll have to odin back to stock and start the process over again and delete that file once I load up CWM Rogue Recovery again?
Thanks for the help.

CM9 comes with stock recovery. Look up EL26 kernel and learn to use it. Its your best friend for flashing on this phone. Also read up a little more on CM9 as it explains this.

This method will not work. With our phone, recovery has to be packed into the kernel, its not separate from other partitions like it is on other phones. This is why whenever you flash a new rom, your current recovery is replaced by the new roms packed in recovery. The reason its stock Android recovery is because of the bricking issue we've been having in ICS custom recovery so devs aren't including it into the kernel<rom.
So when you need CWM, flash the directboot CWM under the tools page in the epic4g touch CM blog spot website. You Odin that and it takes you straight to a sage recovery where you can flash the alpha 5 update. Understand?
Sent from my SPH-D710 using Tapatalk

Thank you both for pointing me in the right direction. I realized that I would have to go back to the EL26 to flash new roms. I didn't realize that I would have to do that to flash over an existing rom with an update. Thanks for setting me straight.

hmmm....interesting. The CM9 instruction page does not mention that you need to Odin the DirectBoot CWM when upgrading. I can see why a lot of people are skipping that step.
Thanks for the heads up, I am going to upgrade to alpha 5 after work. I'll make sure to Odin the DirectBoot CWM kernel first.

mjs2011 said:
I can see why a lot of people are skipping that step.
Click to expand...
Click to collapse
It is a new kernel modification that did not exist a couple weeks ago. The EL26 CWM kernel itself has been around since the end of last year. Being completely optional to use the new modded one you probably wont find it in instructions. I for example will never use it but others will find it easier because they do not understand why the phone goes into bootloops.

[Q] Installing ICS CWM

I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?

mazdaspeed6 said:
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
Click to expand...
Click to collapse
You really should read more before hopping around like that without checking. Real risk for a brick here.
-Flash EL26 stock CWM kernel via the PDA option in ODIN/Mobile ODIN
-When phone begins reboot, Hold Power + Volume up until boots into recovery.
-Wipe data/factory, cache and dalvik cache
-Flash ROM
-Flash Gapps
-Reboot
Those are the instructions right from the developer's thread. This is an AOSP rom and it sounds like you're trying to install TW kernels.
http://forum.xda-developers.com/showthread.php?t=1662295
This is the kernel repository. It links to each kernel where you can read further and find out if they are safe for flashing things.

Seems like you've done a bunch of stuff. But you really should do a whole bunch of reading first or you will brick your phone.
My suggestion would be to use sfhub's one-click http://forum.xda-developers.com/showthread.php?t=1705730 to get to a fully stock rooted device. Then use his autoroot package http://forum.xda-developers.com/showthread.php?t=1342728 to add CWM (the lates in the package is FF11+CWM Agat I believe) then you can add Agat's latest kernel with CWM http://forum.xda-developers.com/showthread.php?t=1721065
But I would be very careful when flashing ANY ROM; use the developers prefered method. Some recommend using EL26 CWM. Some a different recovery or procedure. Be especially careful with CM9 and AOKP builds to follow the directions there.
Good luck

So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.

mazdaspeed6 said:
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
Click to expand...
Click to collapse
My friend some good suggestions above your post. Give yourself a day or two and do some reading prior to flashing. This way you may not end up at Sprint making up stories about why your phone wont boot up.

Let me just echo what everybody else has said, you're gotta read more. A lot more! If you're one goal is to get CNA in your phone I would recommend reading all of the very first post on that thread. They give step by step instructions.
If you need CWM there are several options to get it on your phone. Both sfhub and I have put together several one-click and automated options to get it on your phone.
One thing that hasn't been suggested yet but I would strongly encourage you to do is to read the "How Not To Brick Your E4GT" thread. It's sticked in the General section.
Good luck!

Two more things.
1) If you're going to ask for help give it a few minutes before trying something new. It takes people a minute to reply. Sometimes waiting that extra minute or two is all you need to be saved from bricking.
2) Don't be afraid to hit your thanks button for everyone who has offered advice already. I got them once for you but it might not hurt to do it again.

[Q] Phone Won't Boot Into CWM Recovery

So, I have flashed CWM Recovery and CWM Touch Recovery onto my Epic 4G Touch. Rom Manager says both are installed. However, when I boot into recovery, I get the stock recovery. I've searched and searched and all I have found are people who aren't pushing the right buttons and others with junk answers that are no help at all, like instructions on how to flash the recovery.
Even if I reflash using Rom Manager or any other recovery installer, it boots to the stock recovery. It's as if any changes to the file system are being completely ignored.
The weird thing is, if I flash StockCWM-EL26 or rogue_ET-recovery-1.2.2-FB27-rc0 using Odin/Mobile Odin and get to whichever one I flashed once, then either the phone won't boot at all or subsequent reboots result in the stock recovery once again.
To reiterate, I have *no* problem booting the phone and I have *no* problem getting to recovery... it's the wrong recovery, but still.
Oh, and I'm using HyDrA ROM.

Wrong forum. Report your post & ask mods to move your thread here.

MistahBungle said:
Wrong forum. Report your post & ask mods to move your thread here.
Click to expand...
Click to collapse
That forum is for the Epic 4G. My phone is not the Epic 4G, it is the Epic 4G Touch.

Try here then (doesn't belong here regardless).

WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G

patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
^^^^^ this been there done that

patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
As I said, it either works once and never again or never at all no matter what I use to flash it.

Venum's Hydra rom? Wow, talk about a flash back..
Anyway, have you tried the el26 kernel one click?

No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.

Would you mind listing the steps of flashing and items being flashed?
Only reason a custom won't stick is that you're flashing something behind it. In my mind at least..

First Time
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Wipe.
Flash HyDrA twice as per instructions.
Flash GApps.
Flash Multi-DPI Play Market while I'm at it.
Reboot.
Setup ROM.
Attempt to get to Recovery - got stock recovery.
Decided to try again without wiping. Same results.
Decided to try something:
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Made a NAND backup of /system and /data.
Flash HyDrA twice as per instructions.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Restore the NAND backups.
Reboot.
Attempt to get to Recovery - got stock recovery.
Another thing:
<Download Mode>
Flash Rogue recovery.
Reboot.
Attempt to get to Recovery - got Rogue recovery - So far so good.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Reboot.
Attempt to get to Recovery - got Rogue recovery - Interesting, but I can only access the external SD card from Recovery.
Flashed back to EL26.
Reinstalled HyDrA.
Restored the NAND backups.
(The Touch Recovery version is 5.8.1.5).
ROM Manager
Attempt to flash either CWM Recovery or CWM Touch Recovery.
Reboot.
Attempt to get to Recovery - got stock recovery.
Here is a list of my apps if you want that, too.
https://www.dropbox.com/s/k67l6mb294ruyug/apps-list.txt
I'm hesitant on trying anything else because it's a pain to restore it if I can't boot to the OS.

Just went back to Venums thread.
:edit: Briefly reading the thread, you'll need to have and AOSP kernel to run the Rom, so no, EL26 will not work.
:2d edit: This is out of the second post in that thread. - *If you are restoring a nandroid that you backed up via the above process, you will need to wipe cache and dalvik, then flash an AOSP ICS kernel or the ROM wont boot because it is backed up with the EL26 kernel. Then reboot.
Hydra comes with FD26 kernel. As per the OP.
I don't know, and haven't tested, if Hydra will run with EL26 cwm. But you need to add that to the last step.
But that's why you're going back to stock. It's part of the package.
Please, please, please; STOP using Rom Manager to flash a recovery.
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.

egingell said:
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Click to expand...
Click to collapse
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository

bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.

MoHoGalore said:
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
Click to expand...
Click to collapse
I downloaded one, I haven't tried it.
I take it back, I did try it, but it wouldn't install. FF18 Rev2, for the record.
MoHoGalore said:
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
Click to expand...
Click to collapse
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.

egingell said:
I downloaded one, I haven't tried it.
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
Click to expand...
Click to collapse
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.

MoHoGalore said:
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
Click to expand...
Click to collapse
Odin wouldn't install it, if that makes a difference. It's not that the install failed and I had to start over, again.

Well, since my touch isn't my daily use phone at the moment, I'll test that setup tonight.

I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.

egingell said:
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
Click to expand...
Click to collapse
My apologies on not getting back with you on this last night.
But the SD issue is also seen on the repacks with JB. Depending on when and how FF18 v2 was built (without source at the time?) could be similar to the issues with current repacks.
I'd have to refer those issues/questions to Agat or Garwynn..