Related
Anyone please i need help!!!!!
so here is the scenario...
i flashed my asian galaxy tab to overcome1.4.4
i followed the pdf version of its install instruction...
i flashed over to JME-stock-safe via odin... ok PASSED!!!
then i flashed the kernel... ok PASSED
then upon installing the Overcome ROM 1.4.4 it stucked up to Installing new system in the CWM...
So i started back to the first step to redo the process
still no luck...
i tried it so many times still no luck...
what should i do now...
please help me out guys....
You say you flashed the overcome Kernel, did you get the sexy robot voice during the EXT4 conversion? What error are you getting IN CWM when it fails?
Sounds to me like you didn't let the system do it's conversion before you tried to flash the new ROM.
My advice would be to reflash the kernel, and let it boot after you have done so. Reboot into recovery and flash the ROM.
@btyork
yes i did hear the sexy robot converting and it even reboots at its own
then i followed the steps in installing the overcome room...
i even get to the point where it says " Installing New system"
then i've waited for it to finish..
but... i've been waiting for about an hour... so then i decided to redo the process to the top ( reinstalling again the JME-stock-safe) .... OK PASSED again
I did install the overcome kernel.... OK PASSED again
heard the sexy robot converting....
but now it didn't boot on its own...
i've been waiting again for about an hour then nothing happens...
its stocked up to " GALAXY TAB" screen
i didn't run the bootloader patch in the first placed though...
is it something connected to a signed bootloader???
what else can i do????
It may indeed be the bootloader, although I doubt it if you got the kernel installed....
Did you repartition with the hidden.pit file when you went back stock?
Sent from my GT-P1000 using XDA Premium App
hey buddy we can help u fix ur problem but u hav to ask it on the thread u got the rom from.... mods close this thread please
Try recovery mode, then wipe all the data and reboot.
Sent from my GT-P1000 using XDA App
If you are still able to enter recovery mode and you were wise enough to create a nandroid backup before you flashed overcome you could just use the recovery to get back to your phones state just before you flashed overcome. Sounds maybe asif your zip file may have been downloaded wrong or something ... that's why its also always a good idea to check the md5 of the Rom before you flash it ...
Sent from my Desire HD using XDA App
you probably tried this but just checking, did you try powering off, for some reason after the install mine just hung...it took 2 or 3 poweroffs to get it to start booting...been fine ever since.
Im still very new to this. Im trying to install Fasty II, and im stuck at the AT&T logo, and im pretty sure its because i cant wipe the Dalvik cache. When i tried to wipe it, it just would do nothing.
First of all, I did confirm the wipe, i didnt hit no on accident
Anyway, whenever I try to wipe it, I get no error or anything, it just goes back, basically as if i am pressing No instead.
Everything that I did in the following order
1. Went back to stock with the Odin One-Click
2. Went to Download mode and installed the Captivate Gingerbread bootloaders (ran as admin)
3. Wiped the data and tried to wipe the Dalvik cache but nothing happened
And btw the same thing happens when trying to wipe battery stats
Am I doing something wrong, is it that there isnt a Dalvik cache (again Im a n00b), or something else entirely?
Probably included a lot of extra info just wanna be thorough.
Thanks in advance
Ginger bread boot loaders for a froyo rom? That's your problem, wrong boot loaders, man. Flash back to 2.1 stock and give a reread on the fasty instructions.
if you could try any of the button combos to get into download mode, you could flash back to stock there.
Or take out the battery, Sim and sd card, plug the phone the USB cord into the phone, hold the volume buttons down and plug the battery in, if it worked, you should be in download mode. Flash back to stock.
If those two didn't work, look into a jig.
Sent from my SGH-I897 using XDA App
Born2BeMild said:
Ginger bread boot loaders for a froyo rom? That's your problem, wrong boot loaders, man. Flash back to 2.1 stock and give a reread on the fasty instructions.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
No its Fasty II, which is gingerbread
Really, strange, haven't seen it.
Edit: okay, I saw, my mistake, I thought you meant the fasty 2.0+ versions.
Sent from my SGH-I897 using XDA App
Born2BeMild said:
Really, strange, haven't seen it.
Edit: okay, I saw, my mistake, I thought you meant the fasty 2.0+ versions.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
No worries
Born2BeMild said:
Really, strange, haven't seen it.
Edit: okay, I saw, my mistake, I thought you meant the fasty 2.0+ versions.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Either way, the gingerbread boots are backward compatible. Doesn't matter if he was installing a froyo rom or gingerbread. They work either way.
OP: how did I install cwm? Could just be that version doesn't confirm when deleted although it is wiping it. Either way not wiping dalvik should not cause a boot loop, if it was all clustered you would be laggy and perhaps a few apps force close, but it should boot.
Try and re download the rom and reflash.
studacris said:
Either way, the gingerbread boots are backward compatible. Doesn't matter if he was installing a froyo rom or gingerbread. They work either way.
OP: how did I install cwm? Could just be that version doesn't confirm when deleted although it is wiping it. Either way not wiping dalvik should not cause a boot loop, if it was all clustered you would be laggy and perhaps a few apps force close, but it should boot.
Try and re download the rom and reflash.
Click to expand...
Click to collapse
Well I tried re-downloading and still get the boot loop.
After installing gingerbread bootloaders, im pretty sure i just did the update.zip way of getting cwm. idk if cwm has been updated since i got it, which was quite a few months ago, but ya idk if that means anything
EDIT: I think it actually was CWM, i tried flashing again, got the bootloop, went into CWM, and it was a diff color so im assuming it was updated, and flashed it again and it worked.
Thanks for the help
EDIT 2: Spoke too soon, stuck at startup now. Has been on the Galaxy S Screen for the last 10 mins
The cwm after the first flash is the one makes into the kernel.
If it doesn't loop the animation and is just staying at the S it should be re building dalvik which takes awhile
All right it works now thank you
Ive got a stock 2.2? froyo captivate and did the new [Guide] How To flash Captivate ROMs from Stock by TRusselo and when i go into recovery i cant access external sd. I put the latest nightly and gapps on the root of sd card and for some reason I cant see it? I did a clean wipe and everything. Is there something wrong that I'm doing. I've mounted everything and still nothing.
Read the instructions again INTERNAL SD not EXTERNAL and you can access it, browse sdcard to /external_sd folder, it takes you to your external sd.
you mounted what? why? dont.
BUT YOU CANT FLASH FROM EXTERNAL SD!!!!
thats why the instructions say INTERAL SD
So instead of downloading through the browser.....I'd like to move the new nightly and gapps on internal memory with a pc transfer....where would i put it in? so that CWM can see it? Thxs man. I appreciate it. noober here. htc aria was a breeze to root and flash custom roms, I'm not use to this puppy.
ANYWHERE internal sd in the root, or any folder (except external_sd)
what browser are you using? the stock brower downloads to sdcard/downloads not sdcard/external_sd/*whatever*
if you downloaded with stock browser it should be there... not in root. unless you moved it after.
Thanks so much..... I found the files I needed but when I try to flash nightly it gives me this craziness....what's going on! Thxs for the help though.
edit: Did a factory one click by odin.
seems like an error with the zip file. try a nightly from a day or two before.
The build prop doesn't match the built asserts in the Zip, they have to match for it to flash... what ROM are you currently on?
Sent from my I897 using xda premium
that would make scene by the error. hmm he said he went to stock odin one click...
which odin one click?
Maybe he just did that...
Sent from my I897 using xda premium
So I did the one click to revert back to stock. Then I did a one click root and now have SU. 10 hours later and a freakin home made jig that I've made i'm still on 2.1 with root. Please for the love of God I'd like to install current nightly of cm7 and CWM. There are soooooo many ways I've read to install. Now from you pro's can you hook me up with some links or direction to get this going. I've literally killed my Saturday reading my a$$ off. Thanks guys for replying to my lame noobness.
tommyguns818 said:
So I did the one click to revert back to stock. Then I did a one click root and now have SU. 10 hours later and a freakin home made jig that I've made i'm still on 2.1 with root. Please for the love of God I'd like to install current nightly of cm7 and CWM. There are soooooo many ways I've read to install. Now from you pro's can you hook me up with some links or direction to get this going. I've literally killed my Saturday reading my a$$ off. Thanks guys for replying to my lame noobness.
Click to expand...
Click to collapse
Just clear ROM managers data and then flash the original Captivate CWM not MTD and the reboot into recovery... reinstall packages 2 times, and flash in CWM
Sent from my I897 using xda premium
Thanks for the fast reply. I bought ROM manager premium and will try it out. Install twice I guess to be on the safe side right? Thanks again. My wife hates my life right now being i've spent all day doing this. So i'm down to try anything on her cappy at this point.
Not "to be on the safe side"...the first time you choose reinstall packages in stock recovery it'll boot back into stock recovery, then reinstall packages again and it'll boot into cwm.
yeah thats a must do.
So i've cleared cache and selecting captivate recovery galaxy s 2.5.1.x booted into recovery ROM manger and did reinstall twice and got this.......I don't understand why i'm getting this.
Edit: I got it to work! I kept trying to go through the recovery from ROM manager after installing and it hung up a couple times. Then when selecting install packages with which I did it twice...it was in cwm 2.5.1.7. Installed nightly after full wipe a couple times and it boot looped. Then if I remember correctly I pulled battery booting into recovery, the 3 button way. it booted into Cwm 5.x.x.x. What the heck!!! That was a fun ride, why did it do this? Anyways, glad to join your guys community. you guys are awesome. Thanks buttons hit. changing first post and thread to.....solved.
When you flashed the nightly it contained a kernel with cwm 5 baked into it.
from what i have heard sometimes the cm install needs to be done twice.. too. i dunno dont mess with cm7
Sorry
Hello Guys, Just Found this thread after messing up with my Galaxy S Captivate :| I Unintentionally copied my rom in EXTERNAL SD card and Proceeded further but when I got in Download mode I can't Locate my Rom Zip and I tried Everything as mentioned such as wipe & etc... but Now My Phone is Stuck on Samsung Screen and Can't go through that screen! Is there anyway I can move back to stock rom and then update with new Hellybean!
thanks in Advance!
ShahX said:
Hello Guys, Just Found this thread after messing up with my Galaxy S Captivate :| I Unintentionally copied my rom in EXTERNAL SD card and Proceeded further but when I got in Download mode I can't Locate my Rom Zip and I tried Everything as mentioned such as wipe & etc... but Now My Phone is Stuck on Samsung Screen and Can't go through that screen! Is there anyway I can move back to stock rom and then update with new Hellybean!
thanks in Advance!
Click to expand...
Click to collapse
Go in the Dev section (stickies) and get Odin KK4 without bootloaders. Flash it in download mode.
From there, Get Corn kernel, which you'll flash with Odin 1.85 and finally, you can get back to your ROM.
BWolf56 said:
Go in the Dev section (stickies) and get Odin KK4 without bootloaders. Flash it in download mode.
From there, Get Corn kernel, which you'll flash with Odin 1.85 and finally, you can get back to your ROM.
Click to expand...
Click to collapse
Thankyou Soo Much For your Reply Bro, But Can you please guide me in detail like what Exactly Should I do with My Phone, I can Use my phone its wont let me boot into menu I just stuck on Samsung logo, and As TRusselo Guided in his tutorial I have to put any ROM.Zip into INTERNAL SDCARD (Phone Memory) and I can't do that until my phone boot's up properly! right? so Can you please help me out like what Should I do to get it working and THEN trying again to Update it with Hellybean
Once Again thankyou for your kind Reply!
okay so I thought bricking android would be complicated but as it turns out it's quite simple.
Please cut me some slack because I am a n00b at all this. I am already googling for a solution and looking on forums but I haven't found anything YET so after a desperate hour of googling I thought of posting here (I will keep on trying to find a solution though).
Here is what I did:
A long while ago I rooted my Galaxy S. Rom was ClockworkMod (recovery says ClockworkMod Recovery v3.0.0.5) and the kernel was Talon. No problem with this.
Now I wanted to do a factory reset so I dialed that number yo need for a factory reset. I got a red text message warning me NOT to touch any button and it would reboot. The phone rebooted and I think I got into the recovery mode.
The icon was a top cat in an orange circle with an arrow. I guess that's part of the Talon kernel.
Anyways on recovery mode screen I saw an option called "wipe/factory reset" I've selected it - I was told it can't be undone- I've said OK- It said everything went fine so I selected reboot.
Now the phone won't reboot. It is stuck in a loop. It will always try to reboot.
So all I see is a GALAXY S i9000 screen followed by a Talos screen with a loading bar followed by the GALAXY S i9000 screen again and it will just loop.
No idea what to do :C
help, please! thanks a million everyone!
Try flash the talon kernel again or if u got a rom on your SD card flash that.
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
zodiaxe66 said:
Try flash the talon kernel again or if u got a rom on your SD card flash that.
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
Click to expand...
Click to collapse
well I've tried to put an update.zip on the internal storage of the phone because I don't have an external SD card.
I mounted the phone as mass storage device in the recovery mode but my win xp 32 bit would say it is a Samsung Galaxy S but there was an error with the new hard ware and it couldn't be mounted fff
so no idea what to do now?
This is normal, you delated youre whole System. First of all dont panik you able to enter ist downloadmode ? If so, than you'll bei able to install a new rom and you will be able to boot I'm also New here had the same problem with my phone. This is called a soft-brick. I was able to go in DM and flash a new rom with my galaxy s plus
Sent from my GT-I9001 using XDA
Diablob555 said:
This is normal, you delated youre whole System. First of all dont panik you able to enter ist downloadmode ? If so, than you'll bei able to install a new rom and you will be able to boot I'm also New here had the same problem with my phone. This is called a soft-brick. I was able to go in DM and flash a new rom with my galaxy s plus
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
vielen lieben dank
yeh i guess i did a soft brick. So what exactly do I do now?
I have managed to copy an update.zip file I've found on my computer to the phone but the download mode gives me an error and says it can't install it.
Can you link me to the files I need to install on it with the help of the download mode? Thanks a lot
so I have already tried installing different roms which seemed to have worked fine
I have tried just any random rom (Simplicity) I could find on this forum. It installed but I am still stuck in a boot loop. I don't see the Talon graphic anymore but the Galaxy S animation but I am still stuck in a loop.
help :C
zodiaxe66 said:
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
Click to expand...
Click to collapse
http://www.theandroidsoul.com/ezbase-rom-v3-0-full-installation-guide-w-video/
is what ive found when googling. of course ALL THE FILES are offline again. what a surprise.
really a shame. this looked so promising :C
i've flashed a different ROM in the mean time but it doesn't let me flash anything else anymore. that recovery mode is awful so i can only suggest no one uses simplicity rom
You need to flash a new firmware using odin, partition with 512 pit. Check this link for instructions and firmware. http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000 using xda premium
Hi, first post here so if I screwup any of the etiquette please tell me.
Ok, so I've had my P1000 for about two years now, no contract, not locked to sprint / verizon etc.
I had 2.3.3 at the start, but after seeing mannnny people flashing to ICS successfully I had to give it a go.
Attempted to flash using overcome kernel for CWM, failed and I had to odin back to 2.3.6 (couldn't find a 2.3.3 rom).
I kept it on 2.3.6, but I was unhappy and so am trying again:
It's important to know that I am now on a mac, so will not had access to odin, and instead am forced to use heimdall. Please don't post any odin specific instructions.
In order to get CWM I had to flash the overcome kernel, which includes the recovery mod.
I successfully used heimdall for this, following a specific instruction guide.
I then downloaded "cm-9-20120703-NIGHTLY-p1.zip" from get.cm, and copied it to my externalSD on my gt.
Booted into recovery, wiped all data/factory reset, wiped cache, wiped dalvik, and went to install form an externalSD.
I chose my file, and the installation / flashing (not sure as to the terms. ) began.
It went through a few messages, but however once it said "Checking state of BML/MTD" it reboots instantly and shows the cm startup for about five seconds before going into recovery. Always does this on startup, no way to change.
The only way to fix this is to go into recovery and wipe all data, but this leaves me on my 2.3.6 rom.
I have NO idea what's happening, and I can't use most guides due to them being odin specific.
If anyone can assist me, please do.
Don't link to any odin threads, and don't tell me to search, for I have been doing so for eight hours.
Cheers,
Zero
EDIT: SOLVED!!!
After flashing once it failed at BML/MTD, so I opened recovery and flashed from "internal sd". Worked a charm, now installing gApps.
Cheers for helping Priyana!
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
priyana said:
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
Click to expand...
Click to collapse
That's the thing - when I boot to recovery after flashing (and failing) CM9, it is a different sort of recovery and doesn't allow me to install from an externalSD.
Cheers for replying,
Zero
just the name change.
the internal and external got swapped around in that newer recovery
priyana said:
just the name change.
the internal and external got swapped around in that newer recovery
Click to expand...
Click to collapse
As I just noticed.
Installed PERFECTLY!
It's up and running - however I can't see a market?
Cheers,
Zero
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
priyana said:
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I gave up on instructions after five hours of them failing.
Reread now and just about to reflash with gapps
Cheers,
Zero
Yeah. Believe it or not, early adopter has advantages because we have read up all!
Sent from my GT-P1000 using xda app-developers app
Yeah
Works so well, already have tapatalk and all gapps are working perfectly.
And the instructions - I was following them perfectly, but they did not go in depth when it came to reflashing with the newly installed rom-manager of cm9.
All works perfectly now, thanks for your help
Sent from my GT-P1000 using Tapatalk 2
I've got this exact issue coming over from Frankenclean 2.8 on the samsung fascinate. I decided to update my rom as it was falling behind the 'curve' if you will.
I'm now stuck at a bootloop "samsung" and "S-cyanogen(mod)" screen. they just go back and forth. I'm following this http://forum.xda-developers.com/showthread.php?t=1238070 to the letter and still getting the issue. I've tried flashing a newer kernel that is for 4.x.x builds and no luck.
When I install or attempt to install cyanogen10 it fails on the bml/mtd check and it just reboots to those two screens.
I followed the 'fix' at section 9 but haven't had any luck getting cyanogen to install... I'd really appreciate a little help, ideas, questions, anything.
I know it's an older device, I'm just hoping someone out there with more dev knowledge than I possess "read: none" can help me out.
bump...
Got it to boot into a stock rom, but have 0 luck getting my nandroid to load up and be functional using CWM 2.4 (red). Which is what I made the recovery with.
Might end up with a stock phone if I can't figure it out, I don't mess with roms often.
Luckily I do have titainium backup so all my apps are saved. Just sucks to not have a sleek rom anymore. Not to mention I want jellybean. Any help is appreciated!
fixed it, 4.1 didn't like my phone, got hellybean 4.2 on it without a problem .
Only issue is that google voice to text doesn't work, nor google search.