I flashed CF-root and stock kernel a week ago and didn't like CWMod so I reflashed stock firmware but now my Android recovery mode try's to install Multi-CSC when I havn't installed a multi-csc rom before, so I read I might be able to flash a new recovery.img or flash a .pit file/check re-partition with the stock firmware, which is better? as I want to fix recovery for warranty purposes and the multi-csc message is a dead give-away i've been messing with the firmware.
If the .pit files the way what other tools/files do I need? I have stock kernel, stock firmware, stock csc, insecure kernel, odin, s2root and the android sdk installed.
With Telstra
My csc is TEL, model GT-I9100T, kernel: DVKF4 android v 2.3.3.
Edit:
Short Version: I was new to flashing and rooting last week so I opened xda found CF-root, didn't know there's other methods and used it, I flashed my stock kernel, used zIMAGE and still had root so I booted recovery and the normal recovery was there but it was installing multi-csc when I didnt use a multi-csc rom I tried all methods to get rid of it except repartitioning or replacing android recovery img.
I need to get rid of this message if i ever want to take it back to Telstra or Samsung.
Sorry fail to understand your post .
Stock Roms .and csc follow the instructions .
http://forum.xda-developers.com/showthread.php?t=1075278
jje
You need to use a kernel like CF-Root to break the 3E recovery. You can use SuperOneClick to root,but flashing ClockworkMod through Rom Manager wont break it.
dylan1232 said:
I flashed CF-root and stock kernel a week ago and didn't like CWMod so I reflashed stock firmware but now my Android recovery mode try's to install Multi-CSC when I havn't installed a multi-csc rom before, so I read I might be able to flash a new recovery.img or flash a .pit file/check re-partition with the stock firmware, which is better? as I want to fix recovery for warranty purposes and the multi-csc message is a dead give-away i've been messing with the firmware.
If the .pit files the way what other tools/files do I need? I have stock kernel, stock firmware, stock csc, insecure kernel, odin, s2root and the android sdk installed.
With Telstra
My csc is TEL, model GT-I9100T, kernel: DVKF4 android v 2.3.3.
Edit:
Short Version: I was new to flashing and rooting last week so I opened xda found CF-root, didn't know there's other methods and used it, I flashed my stock kernel, used zIMAGE and still had root so I booted recovery and the normal recovery was there but it was installing multi-csc when I didnt use a multi-csc rom I tried all methods to get rid of it except repartitioning or replacing android recovery img.
I need to get rid of this message if i ever want to take it back to Telstra or Samsung.
Click to expand...
Click to collapse
Most Probably the ROM you installed had the Multicsc file with it with a default region CSC and after you reflashed the stock , its still trying to find the CSC folders for other regions.
What you can try is
1. Root your phone with CF-Root.
2. Boot up the phone, change the CSC to your area sales code ( TEL) by typing #*272*IMEI#
3.Boot to recovery, format cache,system,recovery
4.Boot to Download mode and flash the STOCK ROM which is just with your CSC.
Hope this helps!
Related
can cany one tell me what im doing wrong?
i updated my phone to xxki3 firmware via odin phone works great but i cant load any roms. i tryed and tryed and tryed to flash to different firmware but once odin is finished the phone wont boot. the best i can think is that in the xxki3 firmware there was a bootloader file and when i try to flash a rom the boot loader dosent match up witht he new software can any one tell me how to stock the bootloader to bell canada or tell me what im doing wrong?
You don't load ROMs in Odin, you load them in ClockworkMod Recovery.
Download ROM Manager from Market, Flash ClockworkMod Recovery.
Then install .zip from sdcard.
I updated to KP8 and have found it usable, however I fancied trying some MIUI. Unfortunately I am unable to flash anything with ClockWork Recovery. I initially tried and the update went through fine but the device said something about 'forced upload' after trying to boot. I tried flashing standard Clockwork Recovery via Odin and flashing the ROM again and it just stuck at the boot screen. I have tried a full reflash with MODEM, PDA and Phone with the KP8, KL3 and KL1 firmware. I am able to boot into stock firmware and it runs fine but as soon as I install a custom ROM zip via CWM I simply cannot boot. I have tried with both MIUI and DarkyROM HD zips. I have also tried flashing CWM with both the generic tar and the corresponding CFROOT file for each stock firmware and for each I get the same result. Sometimes it says 'forced upload' when I try and boot back into recovery and I have to flash the whole ROM (or CFROOT file) again to get a recovery back.
Does anyone have any idea what might be causing this problem?
As we speak I am running stock, unrooted KL1 firmware with no problems. I will be able to install CWM and subsequently boot fine but I know as soon as install a ROM through the 'install zip rom sdcard' method in the recovery menu I will just get a boot loop.
Thanks in advance guys.
Try
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Followed by root and your custom rom .
jje
Basically, I had attempted a kernel flash via CWM Recovery which failed and I bricked the phone, I had to then reflash a new firmware to the phone via Odin(counter is now 1).
Prior to this stupid thing, I had backed up my kernel and flashed it back after I flashed the new firmware(which also had a different kernel), so in Settings->About I see the exact same information I had prior to my reflash.
Perhaps my problem is in CSC. This is a screenshot of the phone info from dialing *#1234* http://i.imgur.com/zs34X.png.
P.S
When I flashed the new rom, I found a BBC iPlayer inside, which was not present before, indicating something about UK(GB).
P.S 2
I am running ICS 4.0.3, rooted(with the method that doesn't require flashing an insecure kernel and can be done through CWM Recovery).
dikidera said:
Basically, I had attempted a kernel flash via CWM Recovery which failed and I bricked the phone, I had to then reflash a new firmware to the phone via Odin(counter is now 1).
Prior to this stupid thing, I had backed up my kernel and flashed it back after I flashed the new firmware(which also had a different kernel), so in Settings->About I see the exact same information I had prior to my reflash.
Perhaps my problem is in CSC. This is a screenshot of the phone info from dialing *#1234* http://i.imgur.com/zs34X.png.
P.S
When I flashed the new rom, I found a BBC iPlayer inside, which was not present before, indicating something about UK(GB).
P.S 2
I am running ICS 4.0.3, rooted(with the method that doesn't require flashing an insecure kernel and can be done through CWM Recovery).
Click to expand...
Click to collapse
wipe and flash a stock firmware with its stock kernel, by then you'll be able to connect to kies
I've read the threads about CF-Root 6.4 and CF-Auto-Root and I'm aware of their differences.
My point is if I use CF-Auto-Root can I later install custom recovery like (TWRP) because I've used custom recovery on my previous device and I like the simplicity of making backups and flashing custom roms.
Also will there be any incompatibility with using TWRP and Mobile Odin.. I remember reading somewhere that mobile odin can't flash zip files, this is the reason I'm willing to install TWRP
Phone info:
Baseband: I9300XXDLID
Android: 4.1.1 JB (phone came with 4.0.4 used a OTA update)
also my phone and sdcard are encrypted.. should I decrypt them and do a factory reset before rooting?
I can provide more information about the device if needed.
So I reinstalled the stock GT-I9100T (Vodafone S2) 4.0.3 ICS firmware using Odin, and decided to use a method of rooting I found online which was simply installing "update.zip" using the stock Recovery. A SuperSU app is present and Root Checker says it's rooted. Now I want to install CWM to reflash AOKP, but I'm not sure what method to use, since it's already rooted.
Thanks in advance.
Save yourself hassles & avoid 'temporary' versions of CWM. Just flash the Odin version of the Siyah build which is compatible with the current Android version you're running. Read the first page of the Siyah threads to workout which build you need. You'll have a rooted phone + permanent CWM & you can then flash any rom/other kernel you like quickly/easily.