Database Develop

[Q] Advice for Flashing custom ROMs

I have a friend that want's to flash a custom ROM to his captivate. He has it rooted but hasn't done anything else.
I said I would install CM7 or something on it for him. I had a Droid and Droid2 and am now on a Thunderbolt. So rooting and flashing ROMs aren't new to me. But, as with all three of my phones, things are a little different on the Captivate.
I see there's this Odin thing and I think no permanent clockwork recovery? How do you install ROMs on the Captivate? I see there's a new CW that doesn't need what ever Odin is. He's on the stock kernel and everything. So do I just boot into recovery and flash the clockwork update.zip and then flash normally through CW?
Also, being as he doesn't know how to do any of this, which is the most stable and bugless ROM that everyone uses. He won't know how to flash something else, so I need something that is as close to 100% as possible, speedy, and close to, if not ASOP.
Thanks

Hello,
Please post in Q/A as this is not a development topic. Suggest mod move the post.

I suggest that your buddy do some reading. Are you going to be there to hold his hand every day if something goes wrong with his flash? Tell him to educate himself. And if flashing is not new to you and your 3 phones, you should know what section a question like this goes in, is it "android development" related?
Sent from the frozen tundra known as Canada.

Most stable rom I have ever used is firefly 3.0. But your friend should see u do it and at least know how u did it to his phone. And yes from stock just do the clockwork mod update.zip and then flash through clockwork mod, there is a little more involved in flashing cm7 and it is not the most stable rom anyways. Good luck and I hope u take my advice on firefly you won't be dissapionted

The flashing procedure will vary depending on what ROM you want to run.
CM7/MIUI have their own set of procedures.
Flashing a Froyo based ROM you'll have to flash CWM 2.X then the ROM
Flashing a Gingerbread based ROM you'll have to flash the updated Gingerbread bootloaders first via Odin then flash the Kernel or CWM 3.X or higher, then the ROM.

Post in question section plz
I advice you to start flashing a not complicated rom (2.2) , once you get the hang of it then you go advance.

Moved to proper forum.

Odin is a program that is ran in the computer to flash a rom, bootloaders, and kernel at once. For it to work your phone has to be in download mode. Clockwork works with rom manager in the app store, some roms have it in the kernal.

Sorry, the forums I used before all root related things, including questions, went in the Root section. I thought Q&A was for non-root/development questions.
Thanks a lot Dustin, Kyuta, and bassplayer for the information.
I am going to show him how to do it. But I'm not going to hold his hand every time. That's why I wanted something stable where he wouldn't have to flash something else to get functionality that was missing.

[Q] Need help with ROM Manager

Hi Everyone,
I bought ROM Manager Premium v4.5.0.1, in order to do a Nandroid backup on my I896 running stock I896UXJL1.
I ran "Flash ClockworkMod Recovery", and it said my Current Recovery 2.5.1.2 was the same as the Latest Recovery. So far so good.
Then I ran "Backup Current ROM." Instead of doing a backup, it rebooted my phone into Recovery "3e" every time. I tried it many times and got the same result.
This is so confusing. For whatever reason the app decides to boot my phone into recovery instead of doing the backup, I would expect it to at least go into CWM Recovery instead of the stock 3e.
Questions:
1. Has any of you gotten rebooted when you try to do a Nandroid backup?
2. Has any of you gotten rebooted into stock recovery even when CWM is installed?
Thanks.
KK

In general ROM manager is trash for SGS. Don't bother with them. I would say find a kernel with CWM cooked in it but JL1 is a rogers only and I don't know any for that.

prbassplayer said:
In general ROM manager is trash for SGS. Don't bother with them. I would say find a kernel with CWM cooked in it but JL1 is a rogers only and I don't know any for that.
Click to expand...
Click to collapse
froyo wasnt so damn kenel picky. any froyo kernel will work.

Doesn't work with any ROM
I've tried ROM manager after flashing KH3 and KJ3, and the "Reboot into Recovery" still doesn't work. I get the triangle-exclaimation-droid screen with nothing else, and it stays that way until I use the 3-button reboot.
Since the app can't even perform one of the more basic functions, I am afraid to let it do anything else. I wish I hadn't paid for the premium version.

ROM manager doesn't work on Gingerbread..... Rom manager isn't very good for Samsung phones

KarateKick said:
I've tried ROM manager after flashing KH3 and KJ3, and the "Reboot into Recovery" still doesn't work. I get the triangle-exclaimation-droid screen with nothing else, and it stays that way until I use the 3-button reboot.
Since the app can't even perform one of the more basic functions, I am afraid to let it do anything else. I wish I hadn't paid for the premium version.
Click to expand...
Click to collapse
Stop what you are doing and read. ROM Manager sucks basically. Very few people on here actually use it. If you keep just throwing things at your phone though without knowing what you are doing you are going to end up with a shiny, expensive, paperweight. Then you get to spend upwards of 50$ getting that fixed. So please, for me, the forum, and your phone just read. Or at very least ask a directed, detailed question. As in: my phone is here, im trying to get to there, this is what im doing and this is where and how its failing.

Flashing using an app
I actually did weeks of reading before flashing my phone for the first time. I got scared by potential problems such as USB interruptions.
This is where I am at: I've been using mostly Odin to flash. I have successfully flashed KH3 and then KJ3 (with KF1 bootloaders and Boog's kernel); however, I am still nervous each time I do anything.
This is where I hope (or used to hope) to get to: I keep looking for a way to minimize the probability of human errors and technical hiccups. (It's a habit I've picked up while working as a software manager.)
I went for ROM Manager because the same developer wrote CWM. I do appreciate you guys sharing your opinion of the app's effectiveness with the SGS. I only wish I had been warned sooner (ideally by the app's developer).

Find ODIN packages that don't inlcude bootloaders. That will only minimize your risk to soft bricks wich can be recovered with a jig that are easy to make and only cost ~ $10 if you choose to buy them. I personally use KH3 as my "stock" setting when I need to flash to stock. I use Cezar's KH3 .tar that doesn't include them but there are atleast 1 1 click around.

CWM for Captivate Gingerbread UCKJ2
Sorry in advance for the noob question. I have read many posts but can't find my answer. I've installed the leaked gingerbread rom from Samsung called uckj2. I was trying to change the modem by flashing a zip file using clockworkmod recovery. I've heard the way to do it is by using a kernel that already has cockworkmod already baked in. Which kernel should I use?
Thanks in advance

KJ2 have 3 kernels that should work. Corn kernek, Samurai and Boog's kernel.

How can a Captivate phone SGH-i897 show different model in specs screen?

I'm hoping someone here can help in explaining this because this is something I've NEVER seen or heard of before and in theory, shouldnt be possible but i'm seeing it with my own eyes!
I'm (about to) purchase a slightly used Samsung Galaxy S CAPTIVATE model (SGH-i897) at least that is what the "boot up screen" shows.. I KNOW this is the Captivate.. i've seen the physical differences between it and the Vibrant.. they are basically the same phones hardware wise but do have a different physical appearance on the outside.. the Vibrant's model is GT-i9000..
now when I go to the "About screen"...the model shows the GT-i9000! How is this possible? I'm baffled because I know that i'm actually looking at a CAPTIVATE and the boot up screen shows the correct model number..but the android os (which shows the gingerbread 2.3.5 model in the about screen) is showing the model number as the VIBRANT.. gt-i9000, on the same phone!
I want this phone and was about to buy it but i'm thinking this could seriously cause problems when i go to root and mod it as the conflicting model numbers could create problems with the proper files and processes i'll need to follow when doing the root/mods...
Has anyone heard of this or can explain this because I am STUMPED!
THanks

ok, it appears like a custom Kernel was used cause this conflict. Make sense?
I looked at the About screen again and the KERNEL VERSION looks like something that is NOT the stock kernel. It states:
2.6.35.7-I9000XXJVT-CL617736
[email protected] #DarkCore_4.1_JVT_C
this has to be a custom Kernel right?
This phone must have been rooted and mod'd at some point (the seller didn't know and thought his cousin only unlocked the phone).
I assume a custom kernel that likely is typically for the Vibrant GT-i9000 was flahed with or without a custom rom to this phone and that is why there is the conflicting model numbers... this make sense?
Normally that wouldn't be good idea to use another kernel or rom for a slightly different model of phone but i guess it worked..
I would now like to confirm that this is the case and if so, that it is obviously ok..cuz the phone is working fine.
Should I now wipe the phone back to stock rom/kernel? Can I? if I want to do more mod'ing on the phone anyways.. different kernels and likely update os to ICS 4.0
Thanks for any help on this and hopefully this all makes sense now and explains what i'm seeing

Many of the custom builds for the Captivate are based on I-9000 framework. DarkCore is one of the custom kernels. This phone has been flashed. If you prefer a stock Captivate firmware, there are ODIN One-Click programs in the Development section that will put you back to an "Out-of-the-Box" state. Then do some reading if you plan on shopping around for different roms, as there are several different sets of bootloaders among them and a bootloader mishap is a surefire way to brick this phone.
Happy Flashing and good luck! Welcome to the Captivate!

The vibrant model number is T-959 or some ****..I9000 is the international galaxy s. The original.
It is really easy to switch what is displayed in about phone...it's all in the builds.prop located in /system
You can open that up with a plain text editor and change any instance of Gt-I9000 to sgh-I897 and Viola...
But as mentioned above, flashing to stock with Odin/heimdall will get you back to stock.
Btw what does "build number" say in about phone? Cause that is the name of the ROM that was flashed to it.

Build number says: Mosaic 8
So that is the custom rom that was flashed to the phone I take it?
Ultimately I dont want to go back to the stock rom/kernel but want to definitely flash to OTHER custom roms/kernels. With that being said will I have to go back to stock on either rom or kernel FIRST before doing another change?
I'd like a kernel that will allow me to play with some overclocking and the rom(s) can be one of many.. preferrably I want to put ICS 4.0 on this
Can anyone give me the links to the best info/tutorials to flash the kernel/rom's to do so on this phone?
As said, the actual phone is an unlocked and rooted AT&T Samsung Galaxy S Captivate SGH-i897 but has been already flashed with custom rom kernel as follows:
Model Number
GT-i9000
Firmware Version
2.3.5
Baseband Version
I9000UGJK4
Kernel Version
2.6.35.7-I9000XXJVT-CL617736
[email protected] #DarkCore_4.1_JVT_C
Build Number
Mosaic 8
Thanks

M8 is a great custom rom. You shouldn't need to flash to stock before flashing a new rom. Just follow the steps in the first post of each rom you want to flash. A good ROM to try next would be Mosaic 9

yeah...i hear great things about mosaic!

Thanks..i figured it was a good rom..i play around with it for a while.. it also came with the custom kernel from DarkCore..
I'm fairly new mod'ing rooted phones and all that so I'm curious if I can install a different custom kernel on this Mosaic 8 Rom and if so, what's best way? I want to use one of the many on this site that allow for oc'ing...is it ok to replace the Darkcore Kernel that came with this rom to any other or not?
THanks

hey buddy, i happen to be the lead developer for mosaic.
you are more than welcome to change the kernel, the best way to do that would be in cwm recovery...which can be accessed by holding down on the power button and choosing recovery. or by powering off and holding vol up and power til you see the first splash (that should actually say I9000) then let go that will boot into recovery.
if you see an at&t screen at all the its vol up AND down AND power.
as said above i have updated mosaic, and the latest version includes a kernel that is overclockable already, this one to be exact the .tars in post 1 are for use with odin. post 2 are zips to be flashed in recovery. ater the kernel is flashed it will install an app called semaphore, in there are a bunch of options including oc up to 1300Mhz
that being said...FIRST I would play around with it some more and get used to it WHILE DOING SOME RESEARCH AND READING...i mean you just got the phone...get to know it take her out on the town before you get her all nekkid and vulnerable

THANK YOU SO MUCH for this reply! I was just trying to get into recovery mode and I noticed this phone was allowing me.. this is due to the rom/kernel on it..but you're post with the info WORKED! I was about to start doing a bunch of stuff to try and fix.. THANKS
This whole double splash screen is very new to me with it showing the phone as TWO different models..
I see you have the new Mosaic 9 out..and that's the one you're takling about i take it? and it comes with another new custom kernel that will allow for oc'ing too? sounds good..and 1300 is more then enought.. I'm happy with 1.2 if I can.. dont need to get crazy and try for 1.6 like some..
Just follow the steps on the main page for that rom and all should be good? What will be the easiest way for me to flash to your new rom/kernel? Can I do it from a rom manager or use sd card or internal mem? Any help on this is greatly appreciated! Thanks again for posting a response to my concerns!

btw can i just update this Mosaic 8 rom to that new custom kernel you're talking about or do i have to update to the new Mosaic 9 rom first?

You can flash that on 8.
Don't ever use ROM manager, it doesn't work right on the galaxy line.
And whenever sdcard is mentioned, that is the internal sd, cwm does not flash from an external sdcard.
To flash mosaic 9 over 8 just put ROM on sdcard, boot into recovery, wipe data/factory reset, then go to install zip from sdcard, choose zip, and find the ROM you just downloaded.
Flash the kernel the same way, just don't do the wipe first.
The ROM flash will wipe all your apps, the kernel will not, use titanium backup to backup your apps, then restore them after the flash. Again only needed if you're flashing the ROM and you can flash the kernel on the ROM you have now,
but a backup is a good idea before any flash if something were to go arwy.
As for the 2 boot screens (and the different button combos for recovery, btw download mode is vol down and power), is because the phone has I9000 bootloaders, which is the first splash you see, the second splash is the kernel, both darkcore and semaphore use the same splash the one that says sgh-I897. some kernels use a custom image there instead.
But again, i urge you STRONGLY, PLEASE read, and understand completely what it is that you want to do, and more importantly how to fix a situation that doesn't go as planned, BEFORE you start flashing stuff. Please.

Thanks again bud this is all so helpful. I already downloaded your mosaic 9 zip. Quick question..do i have to format my sd card a certain way first for the update to work? on past.flashes on different phone certain.partioning had to be done on the sd card in order for the update to work.successfully.
Thanks n looking forward to this mosaic 9.
Sent from my GT-I9000 using XDA App

Nope, you're good. Anything that was needed, which was flashing gingerbread bootloaders, has already been done by the previous owner.

Thanks again bud. That last question was pointless cuz i read back again and u mentioned that the sd card stated is always internal and not external..so obviously i wouldnt need to format n partition etc. Thats a bit newer for me well on this new phone anyways. Used to using ext card in past.
As of now ive only updated the kernel to the new one and not the whole new rom...yet. Will play around with it for a bit. The oc was very easy and working just fine.
Btw any plans to do this mosaic rom on ICS 4.0 at all? Or maybe there is one u could recommend? i really want to check it out as so many are "raving" about the new ics os and that it the best by far, etc. Whats your take?
One other question about the flashing from the internal sd now, hope this aint silly but if the zip rom file is saved to the internal mem and im doing the usual data wipe/factory reset wont everything get cleared.including the rom file itself and then not find it when i go to do the update?
and again thanks for all the info, still a bit of noob when it comes to the phones side of things but fyi im definitely a techie when it comes to the pc hardware, software and networking side. Take care
Sent from my GT-I9000 using XDA App

Data wipe/factory reset only wipes the /data partition. Leaving all others including /sdcard intact.

Data factory reset clears (/data, /dbdata or /datadata depends on the ROM you are on, /cache, and /mnt/sd_card/android.secure

Definitely gonna wait a while before flashing any ICS4 roms as still too early and lots of bugs to workout. Im hoping u guys eventually come out with an ics rom cuz this mosaic 8 n 9 are damn good and high quality and read a lot of good things too.
Sent from my GT-I9000 using XDA App

So the bootloaders, when are they input or changed? Is it a seperate update or do they typically come with a rom or kernel? So the ones i have now with the dual splash screens (gt-i9000 then sgh-i897), will i keep those if i wipe and flash a different rom or will a new set of different bootloaders come with most other custom roms? I still dont fully understand that yet and would prefer to mess with them as little as possible cuz i know how important they are and thats an easy way to mess up a phone.
Another quick question i have is about the Captivate phone itself...i know all the specific hardware specs and its states it has 512 ram outside of the 16gb storage/2gb internal rom but why can i only find spec screens that show my phone having 323mb of ram and of that most of it is used up all the time even after a fresh wipe and flash of the mosaic 8 rom ane nothing new installed? Does this have something to do with the rom itself or am i missing something? a little puzzled by this. Part reason i upgraded to this phone was to get better hardware and have more memory cuz i like to eventually install a ton of apps but im thinking i could quickly run into issues with the numbers im seeing. Any thoughts on this? Thanks
Sent from my GT-I9000 using XDA App

Bootloaders ate only flashed with a pc flashing program such as Odin or heimdall.
The second image may change, that within the kernel itself, the first image will not.
As far as storage space goes, you have 16gb on the entire phone. 2gb of that is for user apps. About a Gb for the system, and about 13Gb on the sdcard.
you do have 512mb of ram, but some of that is always used by the system leaving the user with 323. And THAT being mostly used up is just they way Android handles memory. It keeps recently opened applications loaded in memory so that if you wanna access it again it will open much faster than having to reload it. It will also kill off apps as the memory load grows. Put simply: free ram is wasted ram.

Tried going from 2.2 Andrometa3 to ICS ROM 4.0.3. Houston we have a problem.

I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.

LOL OOPS thought i was in the dev section.... ignore..help below.

xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.

TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..

because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.

Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App

I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.

Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App

Any firmware should work, no need to go all the way to eclair...just flash gingerbread.

Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.

aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1

I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium

I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium

I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?

See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium

Custom Recovery Loop

I know a lot of people are in this sticky situation with me.
But hey guys, XDAers, Googlers, Developers & the rest of y'all
So I have a S3 Mini (with NFC so i8190N) and I hack it a lot, I mod, I do a lot of root-y stuff on it.
Well today's objective for my phone was to flash a Custom ROM that blended together TouchWiz and KitKat since I can't get that officially for my phone, I found LostVirginity V2 from the guy who made the Virginity ROMs (I forgot his name but big ups to him, thanks for the crazy cool ROMs bro!)
So I tried to flash it in TWRP.....and it didn't work because TWRP consistently freezes when I press anything and i have to do a battery pull.
Then I used Odin to flash CWM and it flashed it but when I rebooted it my phone decides to not listen and just go back to CWM like CWM has a leash on it or something, I mean come on! TWRP replaced you for a reason and you're trying to get us all back, you're old and forgotten CWM...
So now I've got that frigging annoying TWRP/CWM loop where whatever you do it just reboots to the custom recovery, pretty much the only thing I can do is use Odin to flash another custom recovery (only ones I can switch between are (any version of) CWM, PhilZ's Advanced CWM and any version of TWRP)
I've been trying everything, some guys on redmondpie, android central and rootzwiki (I think that was the website) fixed the problem on the ASUS Transformer Pad but they installed terminal emulator, I've got that but if I could access that that'd defeat the whole point of this thread because that would mean I'd have access to the Android system.
So my question is: Now that I'm imprisoned by the claws of the custom recovery, how do I escape?
Do I flash another firmware through Odin or something?
Somebody help me, and anybody who's been through this problem or is going through this problem at the moment, tell me what you did/what you're doing so we know what to rule out and stuff
Thanks guys