Develop Bugs

FB27 Downgrade, the saga continues

Ok... so if you saw my other thread, I couldn't get Odin to work. Turns out, I couldn't get Mass storage to work either. And neither windows nor osx (heimdall) was recognizing my phone in DL mode!
So I bought Mobile Odin off the market (thanks chainfire!) and tried to rollback using that. While the Kernel and ROM flashes were sucessful, no matter what I do, my phone still reports it's on FB27 Baseband.
So, my current status is, DL mode isn't working, and Mobile Odin is having trouble flashing the modem back to EL29 modem. Anything over my USB doesn't work right now (MHL, Mass Storage, Download) but the phone does charge over USB.

Did you verify that ##8778# is set to "All"?

"All" allows me to connect usb storage... Download mode still a no go. Thanks!
but

Just a long shot, did you happen to flash an International GS2 ICS release? I don't think you did or the USB port would be completely not functional.

Copy the 29 modem to root of SD and flash through stock recovery. Mobile hasntt been flashing modems for me since FB21. No idea why but was able to go back and forth through the stock.

sfhub said:
Just a long shot, did you happen to flash an Internation GS2 ICS release? I don't think you did or the USB port would be completely not functional.
Click to expand...
Click to collapse
absolutely not! phone would probably be beyond bricked... but thanks for the suggestion
Copy the 29 modem to root of SD and flash through stock recovery. Mobile hasntt been flashing modems for me since FB21. No idea why but was able to go back and forth through the stock.
Click to expand...
Click to collapse
Ah... since it's signed... I'll give it a try!

jfcooley said:
Copy the 29 modem to root of SD and flash through stock recovery. Mobile hasntt been flashing modems for me since FB21. No idea why but was able to go back and forth through the stock.
Click to expand...
Click to collapse
He would have to install CWM first. Unlike the stock recovery in ICS test builds, the stock recovery in GB builds will only install files signed by Samsung.

sfhub said:
He would have to install CWM first. Unlike the stock recovery in ICS test builds, the stock recovery in GB builds will only install files signed by Samsung.
Click to expand...
Click to collapse
correct... didn't work. I'm beginning to wonder is something is wrong with the hardware.

Got an idea though, since you got USB working for me... I turned on usb debug, and used autoroot to install the EL29 Rouge Kernel, which game me CWM recovery. I'm trying to flash Calk's EL29 modem.zip through there now...
wait for it... says success... rebooting now.... firmware report says... EL29. Thank god!
Thanks for everyone's help!
EDIT: AHAHAHAHA ODIN WORKS!!!!

MobileOdin and ICS leaks.

Just a quick FYI for those of you, and possibly a thread for culmination of MobileOdin and ICS info.
So far, I'm 0 for 2 in flashing ICS (FC05 and FC07) to my phone. Each time would spur a "kernel panic upload" right in the middle of flashing the system. I did not have a custom recovery in either case.
A battery-pull was required to reboot my device, and it became soft-bricked. I was able to boot into recovery and download mode.
Since I don't have a PC at home, and my work PC won't let me put Odin on it, I was stuck flashing a custom kernel with Heimdal. No big deal, which let me boot back into CWM and flash Caulk's 2.9.1 back onto the device (I keep a copy of a working, CWM-flashable, full ROM on the external SD card).

silversx80 said:
Just a quick FYI for those of you, and possibly a thread for culmination of MobileOdin and ICS info.
So far, I'm 0 for 2 in flashing ICS (FC05 and FC07) to my phone. Each time would spur a "kernel panic upload" right in the middle of flashing the system. I did not have a custom recovery in either case.
A battery-pull was required to reboot my device, and it became soft-bricked. I was able to boot into recovery and download mode.
Since I don't have a PC at home, and my work PC won't let me put Odin on it, I was stuck flashing a custom kernel with Heimdal. No big deal, which let me boot back into CWM and flash Caulk's 2.9.1 back onto the device (I keep a copy of a working, CWM-flashable, full ROM on the external SD card).
Click to expand...
Click to collapse
Good info. Ive flashed kernels to the ICS roms using mobile ODIN but ive always gone back to EL29 and flashed using Rogue CWM for new roms.

RainMotorsports said:
Good info. Ive flashed kernels to the ICS roms using mobile ODIN but ive always gone back to EL29 and flashed using Rogue CWM for new roms.
Click to expand...
Click to collapse
Same here. Mobile Odin for kernels and CWM for roms works for me, and I flash a lot.
Sent from my Galaxy S II, AOKP style.

[Q] "Cannot install to USB or sd card"

Hello, I'm the the latest Calk 2 1.3a leak based around FC24 with the FC24 kernel. This happened in previous versions but was fixed in FC18 for me. It's back now though. What happens is when I go to the market and the app would default to installing to the USB or SD card instead of the /data partition (Mainly games like DOOMgles, Minecraft) it gives me "Error: Cannot install on USB or sdcard". Is there anyway to fix this besides going to back to FC18 which had bad performance for me compared to FC24.

1. Remove SD card
2. Install
3. Reinsert SD card
4. Enjoy

If it's a game that HAS to be on the SD card than you need to install the stock FC24 kernel. All the modded ones have the problem of not being able to install to the card.

MeWarning said:
If it's a game that HAS to be on the SD card than you need to install the stock FC24 kernel. All the modded ones have the problem of not being able to install to the card.
Click to expand...
Click to collapse
What's strange though is that on FC18, I was able to install games just fine while using the rouge repack kernel. I read on the GS2 forum that samsung put this in on purpose. Why would they do that? :c

piexil said:
What's strange though is that on FC18, I was able to install games just fine while using the rouge repack kernel. I read on the GS2 forum that samsung put this in on purpose. Why would they do that? :c
Click to expand...
Click to collapse
It's only my 2 cents, but it seems pretty lame that Samsung doesn't ship the phone with the ability to do a backup/restore from the stock recovery menu. Somehow I can't see Samsung repacking their ROMs themselves with CWM or Rogue kernels...

[Q] ghost device autoroot trouble?

I've used SFHubs Odin OC to move from ICS back to GB, and then the auto root tool to inject custom recovery. Specifically EL29 Odin OC and then Auto root Rogue Recovery. Several times, no trouble. From my laptop. Recently I used the same laptop to root my friends E4GT with El29 Odin OC (worked just fine) and then Auto root to install Rogue recovery. When I boot into recovery it looks and acts typical. But the recovery cannot properly flash any roms or properly restore a nandroid. It looks normal, but flashes zips too quickly and upon reboot I get a soft brick (hangs at splash screen). Luckily I was able to pull battery and get back to Odin mode.
Does anyone know why this happened? Is the auto root failing because I'm using the same laptop for two different E4GTs? Is there a ghost device borking the recovery installation? Thanks in advance for your help.

issues
Ive had the same thing happen to me.I did 2 things different at the same time so I dont know which one actually helped.
Used a difderntt USB cable(the cable that came for the.phone)
Deleted Odin the downloaded it again.
Worked after that I hope this helps.

Dr. Fed said:
I've used SFHubs Odin OC to move from ICS back to GB, and then the auto root tool to inject custom recovery. Specifically EL29 Odin OC and then Auto root Rogue Recovery. Several times, no trouble. From my laptop. Recently I used the same laptop to root my friends E4GT with El29 Odin OC (worked just fine) and then Auto root to install Rogue recovery. When I boot into recovery it looks and acts typical. But the recovery cannot properly flash any roms or properly restore a nandroid. It looks normal, but flashes zips too quickly and upon reboot I get a soft brick (hangs at splash screen). Luckily I was able to pull battery and get back to Odin mode.
Does anyone know why this happened? Is the auto root failing because I'm using the same laptop for two different E4GTs? Is there a ghost device borking the recovery installation? Thanks in advance for your help.
Click to expand...
Click to collapse
Are you sure your friend's phone has an external sdcard?
If not, pay attention to commands that work on internal or external cards. Some areas you toggle internal/external mode. Some areas you choose specific options that work with internal or external.

sfhub said:
Are you sure your friend's phone has an external sdcard?
If not, pay attention to commands that work on internal or external cards. Some areas you toggle internal/external mode. Some areas you choose specific options that work with internal or external.[/QUO
**********************
First of all, thank you for all your awesome work. I am honored by your reply.
I am not sure exactly what you mean by toggling external vs internal. Rogue gives you the option to choose where to read from or nandroid to; I typically use the external SD.
Yes, my friend's E4GT does have an external SD card. Rogue recovery did write to it when I nandroided her EL29 setup, and it did read the install zip from the SD card as well. I wiped with Calkulin's format-all, then installed the rom (in this case Phantom's excellent Blazer). I knew something was wrong when it flashed, because it flashed way too quickly. After the reboot and subsequent Galaxy S2 splash screen to infinity, I pulled the battery, booted to Odin mode, restored EL29 thanks to your fantastic Odin OC, injected Rogue thanks to your swanky Autoroot tool, attempted another rom flash, same result, Odin OC, back to EL29 stock, Autooot again. Then I attempted to restore the nandroid of her EL29 setup, and that resulted in an MD5 error, which also led to a soft brick. So I Odin OC'd once again and called it a day.
My phone has never had this problem. I think I'll Odin OC and Autoroot tonight, and then restore one of my nandroids just to see if it works. I don't know whats up, but the trouble started when a second phone was added to the equation.
Click to expand...
Click to collapse

Basically when CWM comes back right away from an operation, usually some error occurred. One error might be using an external sdcard when it isn't present. There are other possible errors, but that was the most obvious one to ask about.

sfhub said:
Basically when CWM comes back right away from an operation, usually some error occurred. One error might be using an external sdcard when it isn't present. There are other possible errors, but that was the most obvious one to ask about.
Click to expand...
Click to collapse
I appreciate your help. Thanks for FD10 btw, i just got done OC'ing it...awesome!

Ok i had this same problem. After OCing back to stock rooted EL29 Reinstall CWM rogue with adb auto root. This will give you a fresh copy of CWM rogue and shouldn't throw you into a boot loop. Also make sure you do a full data wipe and wipe all cashes then run Calkins format all zip prior to running the nandroid backup. Should be good. Hope this helps.

[Q] cant install apps to internal or sd

Hey guys im having a issue where i cant install some/most apps from the market. I get an error '' cant install apps to usb or external sd storage''. Thr issue only happens once i install agats ff11 recovery. When i used sfhubs ff11 odin oc the apps will install fine, but once i odin agats ff11 recovery it stops working. I can unmount the sd card and install the apps just fine but thats the only way. I also can no longer move apps to sd after flashing recovery. Ive searched and tried the unmounting sd trick. Ive read about deleting some market temp files qill fix the problem but i never could find the temp files on my phone. If anyone could provide any help or point me to what i should try next i would greatly appreciate it. I know i can just no t flash agats recovery but i hate the stock recovery. Ive also wiped cache and dalvik but it didnt fix my problem. Thanks in advance guys i appreciate everyones work here.

I am on Agat's ff02 and have the exact same issue. Tried installing Ringtone Maker and get the same error.
Sent from my SPH-D710 using Tapatalk 2

Thanks for your response. i havent noticed the issue until i upgraded from FF09 the other day, but then again i havent downloaded any apps lately. i just flashed agat's FF09 recovery and it has the same issue.
i would have posted this in his thread in the dev section but i dont have enough post yet so i posted it here.