[i9001] The phone will just load up (FeaCore Phoenix) CWM Recovery.how to get out? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi everybody.
In the past I already flashed custom ROM to routers, so I thought I had the skill to undergo the path of flashing ROM to a phone.
Wrong.
I have countless tabs opened tried to solve my stucked phone, and my PC is running out of memory; and I'm running out of hope.
I own a S Plus GT-i9001.
I wanted to get rid of all the bloatware present in the phone, so I gained root privileges.
Like explained here. It worked perfectly.
Since deleting all the unnecessary apps didn't look working, I thought "well, it is a rainy day, you had this device for a while, why don't you flash some ROM?"
So,
1. I followed this guide, but, needless to say, Rom Manager was not fulfilling to its duty. Indeed I backuped everything I needed, but the stock rom
2. I followed then this guide, point 3, to install ClockworkMod Recovery directly. Before, everytime I tried to enter the recovery menu, I was bounced to the original recovery menu, because ROM manager did not succeed.
With this guide, I managed to boot into ClockworkMod Recovery.
I then started backing up the ROM to the external SD, and it seemed working.
It was popping out with a message "E:Can't mount /cache/recovery/command", but since all the operations went successful, I did not care much (fail, I suppose)
3. I tried to boot back into the phone, before installing the new ROM, just to double check I saved everything, and then the drama began. I was just continuously bounced back at CWM Recovery menu, no way to get in the phone.
I tried anyway to install the AOSP 4.0.4. and all the steps went successful, but still nothing, I would always reboot automatically into CWM Recovery.
4. I tried restore from backup in external SD, it ran successfully, but still couldn't load the phone
5. I then googled into the "E:Can't mount /cache/recovery/command" error, so I ended up somewhere that they were advising to flash FeaCore Phoenix Recovery tool. Indeed it did not display anymore such an error
6. I tried again with he AOSP 4.0.4 ROM, but it showed then the following error
Code:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
so I ended up here and changed the zip accordingly.
7. I also tried this instructions here to perform the most ultimate massive wiping.
8. I installed the AOSP 4.0.4, and the update-Gapps-ICS-20712.zip, it worked, no errors.
Still, it reboots into the recovery menu.
I can't get out of this damned recovery menu, it is crazy! I have used so many recovery tools in PCs, you usually are able to leave them, maybe not able to restore the OS, but you never get stuck into a circle of hell like this!
Please, does anyone has some advice for me? I don't want to waste a 6-months old device
thank you!

You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.

switchboy said:
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
Click to expand...
Click to collapse
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?

jv_guano said:
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
Click to expand...
Click to collapse
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!

jv_guano said:
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
Click to expand...
Click to collapse
Well, I sorted it out (absolutely, in a mysterious way!!! )
I downloaded the recovery-clockwork-6.0.1.2-ancora.tar.md5 from here, and I followed again your instructions for flashing it with Odino (rigorously NOT ticking one package).
When rebooted, I had the AOSP 4.0.4 Stock, shiny and sparkling!
without even entering the recovery menu and reinstalling!
but I guess I will need to do a clean install again, now that seems that CWM 6 is digested by my phone

Related

G1 Root help

Hello everyone,
first off, I'm new to all this. Here's my situation,
I was trying to install a new ROM on my G1 and I found instructions on how to gain root access to my phone. I felt like I had followed the instructions but I can't seem to get the ROM installed on my phone. I downloaded Recovery Flasher and installed it. I chose "Backup recovery image" and then "Flash Cyanogen Recovery 1.4" and it all seemed fine, but then when I rebooted my phone and tried to install the new ROM it wouldn't let me. But I think I know what the problem was, I missed the step where I had to rename the folder of the ROM to "update." I went back to factory settings and tried to re-do the steps but this time, Recovery Flasher gives me the options to:
Download Recovery Image
Restore Backup Image
this confuses me because it's not the same as it was the first time I tried it. Does this mean my phone is already rooted? I tried to uninstall and install it again and same 2 options come up.
I know i was doing it right at first because I got all the correct screens that I saw on the instructions, but now I don't. I've been searching here and all over google to see if I can find an answer but I couldn't so I decided to make a thread to see if someone can help.
Thanks!
AFAIK the one-click method doesn't survive a full reboot, because when you reboot the OS it overflashes the recovery partition again with the original (unless you've flashed a new ROM)
Now your problem seems to be the "folder" bit. You do not unzip the ROM, you put, eg, "update-cm-4.0.4-signed.zip" on your SD card as-is. You also no longer need to rename it to use from this recovery partition.
I see,
well, when I tried it with update-cm-4.0.4 (that's what I was trying to install) it said that the file could not be found, and then I read that I'm supposed to change the file name to "update" and when I did that, it found it right away but it gave me the error "No Signature" (something along those lines) even though according to the place where I download it from, it is signed.
Should I just try to boot into recovery mode again and try it out again? I remember the very first time I tried it loaded the screen with a bunch of options, but now it just has 3, Boot Into Home, Wipe, and Apply SDcard zip, I might be wrong on the exact wording of those options but that's all I get...
and recommendations? Thanks for your response
nevermind, I got it to work! Thanks

Can't flash Nexus

My nexus has been a great platform for running roms for quite a while now, but after installing CM6 as of late it has been really picky about what it can flash. For instance the only way I got it to install the normal stock rom afterwards was by putting it in as passimg.zip. Every time I try to flash something to it now, the signature verification fails. Anyone else have this problem?
Edit: If I install a rooted room, it gives me
"assert failed: !less_than_int(1277930906, getprop("ro.build.date.utc"))
E: Error in /sdcard/update blah blah .zip
(Status 7) Installation Aborted
Did you lose root?
I don't think so, I could try unlocking the boot loader again but it says unlocked at the top already...and it won't even flash normal signed passion roms...
what recovery do you have? have yopu tried fastboot flash recovery? like amon rah
I ended up using
http://forum.xda-developers.com/showthread.php?t=614850
to fix it.
It still refuses any update.zip file that isnt OTA...
every signature varification fails instantly. So I guess until I throw this phone in the trash pile or just use it for an MP3 player..its not going to be doing anything in the way of modding
If you've used the original shipping ROM tutorial/passimg, then you'll have a stock recovery that will of course only install released signed things.
Rusty! said:
If you've used the original shipping ROM tutorial/passimg, then you'll have a stock recovery that will of course only install released signed things.
Click to expand...
Click to collapse
right and I flashed clockworks recovery to get it off the standard. I guess I could go out and get Root again without it, but at this point I don't see the point with Gingerbread coming out. I'm just glad to not have a paper weight sitting next to my computer again.
btw Calling Tmo/HTC doesn't help. Most of the guys there don't have a clue what FRG83 is even lol
Keep in mind, if you have the stock on there, it will wipe out your custom recovery and restore it to the stock recovery every time you restart the phone.
So if you flashed Clockwork, after a reboot the stock recovery will be there again.
Yes amonra and cwr have options to toggle off verification best to start with amonra recovery then go through the steps

[Q] Trying to flash Serendipity 6.3...

I've never flashed a rom before. I currently have stock froyo with the paragon kernel i flashed using the app sgs kernel flasher. I have clockwork mod rom manager, I created a backup of my current rom. So then I tried installing the serendipity rom from the sd card but i get an error message. I read on the sticky on how to flash a custom ROM you need to use ODIN and flash back to stock 2.1 then do a master wipe and re root it and stuff.
Their link to download ODIN is broken so I don't know how to get it. And is there really no other way to flash it besides doing a master wipe and using ODIN?
flash to stock and master clear is not needed. what IS needed are specifics on WHAT error message you get when trying to flash the rom you want
The error message is
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted"
Then it brings be to the blue menu so i just select reboot system now
bad download, re-download rom.
May be completely off, but it doesn't sound like you're actually in clockwork mod recovery, but rather stock recovery.
But here's the post with the one click odin with mirrors and I personally would suggest useing it since I generally like to stick to as clean a flash as I can:
http://forum.xda-developers.com/showthread.php?t=731989
Second, I don't know if you've ever seen MobileTechVids tutorial on how to flash custom roms, but I suggest you watch the full series first if you haven't already.
here: http://www.youtube.com/watch?v=MsafJ-9uRqk
I watch the series and try and stick as close to the tut as I can when I'm unsure (or the one provided by the Rom maker as they know what's best for their rom)...
One suggestion, when flashing Serendipity disconnect your phone from cable right before the actual flashing (gave me a glitch in which I couldn't mount storage via usb). Other than that, read read read. I feel it's all I do when it comes to this stuff, but proper research is indispensible.
thresherhorn said:
May be completely off, but it doesn't sound like you're actually in clockwork mod recovery, but rather stock recovery.
Click to expand...
Click to collapse
+1
Is the text on Recovery mode blue or green? If its blue, you're on stock recovery.
+2
Sent from my SGH-I897 using XDA Premium App
Ok I got the stock rom flashed back and rooted it using one click. Now for some reason I can't reboot into clockwork recovery mode. I flashed it successfully. So i click on reboot into recovery and nothing happens. I try clicking on install room from sd card and that doesnt work either
Power off, hold 3 buttons att screen will come on. Keep holding. Screen will go off. Keep holding. Screen comes on again let off the power button but keep the volumes held, this will boot you into stock recovery, since you said you flashed cwm already I'm assuming you mean with rom manager, so the update.zip should be on your sdcard, so just reinstall packages twice and you should boot into cwm.
AIO tools work well and make flashing roms for new people easy and painless
use a search for it
steph2 said:
AIO tools work well and make flashing roms for new people easy and painless
use a search for it
Click to expand...
Click to collapse
+1.
AIO and superoneclick for root/flashing roms makes the process much easier.
crag11 said:
Ok I got the stock rom flashed back and rooted it using one click. Now for some reason I can't reboot into clockwork recovery mode. I flashed it successfully. So i click on reboot into recovery and nothing happens. I try clicking on install room from sd card and that doesnt work either
Click to expand...
Click to collapse
On serendipities main "download" page they have instructions to install. In those instructions is a link to a file you can download. Place that file along with the serendipity 6.3.zip file in the root of your sd card. Use the " 3 button" technique or Rom managers "reboot to recovery" option to get into stock recovery. Hit "reinstall packages" once/possibly twice. That will put you into clockwork mod recovery. Select install zip from sd card, find the serendipity6.3.zip and click power to flash. Confirm. And after it does some stuff it will ask you to reboot. Upon reboot it will as if you want to enable lagfix. Hit plain "Yes". Watch it do its thing and viola...
You have the "dirty" way of how to flash serendipity... But first I please ask you to spend atleast a day reading this forum or others and understanding these instructions and the reasons behind them.
followed instructions off the website and still doesn't work
I was running 2.2 and have done a lot of reading a video watching (thanks Mobile Tech videos) and finally conjured the guts to flash serendipity.
I flashed stock using odin...that went great. Copied the update.zip to sd card. Installed zip twice in 2e recovery. Copied Serendipity.zip file to sd card. started in recovery mode, selected "install from sdcard" selected serendipity.zip file and it seemed to go through that process rather quickly. Then I selected reboot and then everything just started FCing all over the place. Can't even load the stock that I had on there. I don't know what to do. Help please. I can get it back into recovery mode. Tried doing the wipe data/factory reset. That did help either. Help please. I really want to try serendipity. Thanks again in advanced.
Did you run a restore using TiBu at all? Or was it just a straight flash from stock to Serendipity?
Plus, were you running a phone that came with 2.2 out of the box? Or did you upgrade to stock Froyo yourself?
m3thods said:
Did you run a restore using TiBu at all? Or was it just a straight flash from stock to Serendipity?
Plus, were you running a phone that came with 2.2 out of the box? Or did you upgrade to stock Froyo yourself?
Click to expand...
Click to collapse
I did run TB and I had originally flashed up to froyo (took me all night one night) and then went through the process I explained and hit the dead end. I finally was able to get odin to read the phone and flash back to stock. It was a learning process. I realized that I needed not only the Serendipity_6.3.zip file but ALSO the kitchen file to included with it. That wasn't in the directions I don't think. Finally got it all on there. I love it now. I appreciate everyone's help. Any word on a how-to for Bluedipity?

[Q] Stuck in bootloop...need help

So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.

[Q] Continuous boot, assert failed troubles (Help)

So I posted a help thing about EFS a while back and didnt get to much help with that but i managed to figure things out. Now however
ive got myself into another predicament i cant seem to get out of.
So, from the start, i have a galaxy s3 (GT i-9305T) it was rooted, i still had the stock rom, but was running the beoffla kernal.
The idea was to download and install "JustArchi I9300XXUGML2 stock, deodexed and all the rest" then start finding
some nice themes. Ive got philz_touch_6.07.9-i9305.tar installed for my recovery.
This is where the trouble starts...
So first off i wipe the cache and the davik cache, go to install the rom then i get this: (ill go from installing update)
assert failed: write_raw_image (" /tmp/boot.img" , " /dev/block/mmcblk0p5" )
E: Error in /storage/sdcard1/Just archi........zip
(Status 7)
Installation aborted
Now i looked up a whole heap of pages to see if i could sort it out myself and i tried a few different things,
none of which have prevailed. First i tried to reflash an insecure boot image then try again, nup. I tried to
flash back to stock recovery and re format (No errors) then back to custom. Mounted /data and /system
and re formatted which worked with no error, still same error when flashing rom though. Also tried flashing
with different custom recovery, no luck there either.
There were a few other things i tried but i cant really remember what i did because
this has been a problem for a while now. Some of the pages i looked over for
information were:
http://www.droidforums.net/forum/android-hacks-help/26658-assert-failed-write_raw_image-tmp-boot-img.html
http://forum.xda-developers.com/showthread.php?t=1045887
And this is the one im on at the moment, im currently downloading a stock rom from sammobile to try flash.
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305t-10-2-upgrade-boot-stops-unable-t2406422
"UPDATE"
Finished downloading the stock rom, tried to install with philz recovery and got this:
Installing: /storage/sdcard1/I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip
Finding update package...
Opening update package....
Installing update...
Installation aborted.
And thats it, no kind of specific error codes or anything.
Thanks in advance to anyone who can help me out,
really stuck on this one.​
IIEsoticoII said:
So I posted a help thing about EFS a while back and didnt get to much help with that but i managed to figure things out. Now however
ive got myself into another predicament i cant seem to get out of.
So, from the start, i have a galaxy s3 (GT i-9305T) it was rooted, i still had the stock rom, but was running the beoffla kernal.
The idea was to download and install "JustArchi I9300XXUGML2 stock, deodexed and all the rest" then start finding
some nice themes. Ive got philz_touch_6.07.9-i9305.tar installed for my recovery.
This is where the trouble starts...
So first off i wipe the cache and the davik cache, go to install the rom then i get this: (ill go from installing update)
assert failed: write_raw_image (" /tmp/boot.img" , " /dev/block/mmcblk0p5" )
E: Error in /storage/sdcard1/Just archi........zip
(Status 7)
Installation aborted
Now i looked up a whole heap of pages to see if i could sort it out myself and i tried a few different things,
none of which have prevailed. First i tried to reflash an insecure boot image then try again, nup. I tried to
flash back to stock recovery and re format (No errors) then back to custom. Mounted /data and /system
and re formatted which worked with no error, still same error when flashing rom though. Also tried flashing
with different custom recovery, no luck there either.
There were a few other things i tried but i cant really remember what i did because
this has been a problem for a while now. Some of the pages i looked over for
information were:
http://www.droidforums.net/forum/android-hacks-help/26658-assert-failed-write_raw_image-tmp-boot-img.html
http://forum.xda-developers.com/showthread.php?t=1045887
And this is the one im on at the moment, im currently downloading a stock rom from sammobile to try flash.
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305t-10-2-upgrade-boot-stops-unable-t2406422
"UPDATE"
Finished downloading the stock rom, tried to install with philz recovery and got this:
Installing: /storage/sdcard1/I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip
Finding update package...
Opening update package....
Installing update...
Installation aborted.
And thats it, no kind of specific error codes or anything.
Thanks in advance to anyone who can help me out,
really stuck on this one.​
Click to expand...
Click to collapse
Can anybody at all shed some light on my situation,
or at least a place for me to start learning myself...
Hi.
If you downloaded the stock ROM from sammy mobile are these not meant to be installed via Odin?
There are a few post if you search for some of the pre rooted stock ROMs that you can flash with odin.
I would start from there.
Sent from my GT-I9305 using xda app-developers app
johnnyblaze1977 said:
Hi.
If you downloaded the stock ROM from sammy mobile are these not meant to be installed via Odin?
There are a few post if you search for some of the pre rooted stock ROMs that you can flash with odin.
I would start from there.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
The roms i downloaded from samsmobile were in .zip files, which im pretty
sure has to be flashed with one of the custom recoveries.
Thanks though
at first seems you tried to flash rom designed for i9300
then, you downloaded an ODIN image and you have to flash it by ODIN, no way you'd flash it over any recovery
to be more specific:
unzip the file I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip you downloaded, you should get a huge file with extension of .md5 or .tar
read in the forums how to use ODIN to flash firmware
adamuadamu said:
at first seems you tried to flash rom designed for i9300
then, you downloaded an ODIN image and you have to flash it by ODIN, no way you'd flash it over any recovery
to be more specific:
unzip the file I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip you downloaded, you should get a huge file with extension of .md5 or .tar
read in the forums how to use ODIN to flash firmware
Click to expand...
Click to collapse
Yes ive just done this now and flashed the stock rom with odin
and i think everything has gone well (im not sure as my screen is
water damaged but i did here boot audio only once) so im
letting my phone sit in a bag of rice in pieces for the night
and am going to check things out tommorrow.

Categories

Resources