Updating Rom problems. - AT&T Samsung Galaxy S II SGH-I777

So i think i soft bricked my phone when i went to update from jellybam 6.4.0 to 6.6.0. I was using Jellybam 6.4.0 with Ajk 1.24b kernel. Went to flash Jellybam 6.6.0 then ran into problems. First when i selected the zip to flash it gave me the Assert failed: getprop("ro.product.device"). So i went to just reboot the phone and it hangs up on the AJK boot image. I then did a factory reset and tried reflashing the Kernel but it hangs on the Boot still. I can get into recovery and download just fine but can't boot up the phone. So any advice or am i looking at an odin/heimdall trip back to stock.

You don't have a ROM installed, that's why your phone won't boot: just flash a new one.
Sent from the i777

SteveMurphy said:
You don't have a ROM installed, that's why your phone won't boot: just flash a new one.
Sent from the i777
Click to expand...
Click to collapse
The problem is all fixed now. The kernel was the hang up but not sure why. It wouldnt let me flash the new ROM or a backup of the old ROM. Had to put the stock kernel back on the phone through recovery then flash the backup. When i did the update process again all went well.

Related

[Q] Galaxy S 2 Boot Error

Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).

[Q] Problems flashing kernel

Currently I have jellybeer with cyanogen mod 10.1 on it with s-on.
This rom http://forum.xda-developers.com/showthread.php?t=2315077 and I downloaded the kernel which is on the 2nd page as instructed.
I can flash roms no problem however when I attempt to flash a kernel via clockwork recovery it NEVER works. It says its replacing the boot image, install went great, no signs of trouble. However when I reboot the phone and check the kernel version its always default kernel and it never updates, in this case "3.4.10.cm-gc3a49c6 any incite on this would be great
eurofraid said:
Currently I have jellybeer with cyanogen mod 10.1 on it with s-on.
This rom http://forum.xda-developers.com/showthread.php?t=2315077 and I downloaded the kernel which is on the 2nd page as instructed.
I can flash roms no problem however when I attempt to flash a kernel via clockwork recovery it NEVER works. It says its replacing the boot image, install went great, no signs of trouble. However when I reboot the phone and check the kernel version its always default kernel and it never updates, in this case "3.4.10.cm-gc3a49c6 any incite on this would be great
Click to expand...
Click to collapse
S-on can't flash boot via recovery. There's an awesome app for this, flash GUI, or you can s-off and flash in recovery with the Roms. You can also fastboot flash it and move the modules over yourself.
Sent from my AT300 using Tapatalk 2

[Q] Stuck in recovery mode (TWRP)

Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
fr0z1k said:
Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
Click to expand...
Click to collapse
Can close thread, after installing another recovery via Odin it was fixed

[Q][GP4] Can't get any CustomRom working

Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
basti_b24 said:
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
Click to expand...
Click to collapse
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
TheKryptonite said:
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
Click to expand...
Click to collapse
Forgot to mention that: I tried various ways: first wipe data/cache, then flash ROM; first flash ROM, then wipe cache; wipe cache, flash ROM, wipe again...
In order to get CWM recovery and being able to flash a zip I flashed the Kernel first. For CM9 I followed this http://forum.xda-developers.com/showthread.php?t=2213152
As I couldn't flash any of the pre-flash zip from stock, I thought it's necessary to flash a kernel including CWM first. It was done in the same way in some youtube tutorial I watched, where the guy already had the terrasilent kernel on his device.
For odin, I will check if it works with first flashin the ROM and afterwards the kernel.
Cheers for your fast reply!

[Q] My phone stuck on Intro @ (Samsung Galaxy s3 gt-19300)

Hi,
I tried to update my cynagonrom nightly when my phone got stuck and was not working. I just went to my Teamwin recovery program.
I tried to wipe my cache etc but my phone just gotten worse.
Now I can only get into the recovery mode. Can i recover my from phone here
Easy solution...
joojo5 said:
Hi,
I tried to update my cynagonrom nightly when my phone got stuck and was not working. I just went to my Teamwin recovery program.
I tried to wipe my cache etc but my phone just gotten worse.
Now I can only get into the recovery mode. Can i recover my from phone here
Click to expand...
Click to collapse
Happened to me because i tried an upgrade of a CM unofficial without update the recovery
The solution is "easy": download a stock rom from samfirmware, flash it with ODIN (google: flash stock rom with odin) and your phone come back to life. After that make sure to update the Recovery (suggest Philz), add the zip file of the rom and flash it ...of course,don't flash the last rom that cause this
THE NEXT TIME, before flashing a NIGHTLY CM rom ,do a NANDROID Backup!!

Categories

Resources