Hello everyone!
A few days ago I got a galaxy tab GT-P1000L from a friend, and since I have my milestone 2 happly running CM7, i think for tablets theres no reason to use stock roms, since all juice I have on the milestone is responsability from the cm7 i runned over the crappy motoblur thingamabob.
Well, googling a little I went to humberos, and since his blog is in portuguese (im from brasil) first tought was to follow up his posts about updating my tablet to his release, with cm9+ics, but the infos there were very raw, and then I went here to XDA foruns to get more datails on the run.
A few days of reading later, I was able to do many things, flash new kernel, roms use heimdall, odin, adb text console and so on.. much days of learning, BUT, some doubts still remains, the xda forums are quite nice, but too much content to filter up some simple questions, even on the "all your doubts are here" posts in the front SGT forum, so here they go:
- The clockwork recovery is separated from the kernels? Into a stock rom that wont allow me to install nothing claiming "signature verification failure" is there a way to install ONLY the cwm that has all the tools?
- From a stock rom, if I overwrite the kernel with another one without messing with any rom, can I brick up the tab?
- Which is the ultimate correct order to flash thinks up? (asking this 'cause seem lots of different answers)
total wipe > rom > kernel ?
rom > kernel > total wipe?
kernel > rom - and reboot, since the rom auto cleans cache?
- Is there a place on the forum, or a foreign site that has a table of Devices > roms avaiable > fully working > under development to jump from the repetititititve posts asking "what is the major biggest fully happy rom working for the device X" that mostly goes to personal opinions, with obvious 0 or 1 answers?
- Working with partitions, the stock for samsung is BMT or MTD? running back from a ext4 rom to stock would damage the device somehow?
sorry you all for the bunch of questions, since im a newbie I cant post im many foruns, cant post links, pictures and so forth, gound it easyer to compile a new topic in Q&A and wait for the gods.
Not a god but mere mortal to answer you:
1) yeah, there is no separate CWM recovery for our tab. Can't use ROM Manager for that.
2) No, flashing kernel will likely soft brick only if it is bad kernel. Only messing with bootloader can really hard brick the tab.
3) You can always wipe after all installations instead of before. Usually flashing kernel doesn't need a wipe. Usually you flash kernel before ROM so that you get the correct CWM recovery. So : kernel > ROM > WIPE > reboot
Having said that. No harm wiping. I always wipe twice to ensure clean wipe.
4) No such place in this forum. It is simply not organised that way and people are free to form their own opinion. Hint: just look for most active threads for most popular one.
5) Stock partition is BML not BMT. No, restocking in Odin with pit file selected will repartition the NAND for you, will not cause damage.
BTW, ext4 and rfs is filesystem. BML and MTD is partition scheme.
ext4 and rfs are both on BML. So "coming back from ext4 to stock" will not need repartition.
Confused enough yet? Hope not.
thanks
priyana said:
Not a god but mere mortal to answer you:
1) yeah, there is no separate CWM recovery for our tab. Can't use ROM Manager for that.
2) No, flashing kernel will likely soft brick only if it is bad kernel. Only messing with bootloader can really hard brick the tab.
3) You can always wipe after all installations instead of before. Usually flashing kernel doesn't need a wipe. Usually you flash kernel before ROM so that you get the correct CWM recovery. So : kernel > ROM > WIPE > reboot
Having said that. No harm wiping. I always wipe twice to ensure clean wipe.
4) No such place in this forum. It is simply not organised that way and people are free to form their own opinion. Hint: just look for most active threads for most popular one.
5) Stock partition is BML not BMT. No, restocking in Odin with pit file selected will repartition the NAND for you, will not cause damage.
BTW, ext4 and rfs is filesystem. BML and MTD is partition scheme.
ext4 and rfs are both on BML. So "coming back from ext4 to stock" will not need repartition.
Confused enough yet? Hope not.
Click to expand...
Click to collapse
thanks dude! that clarify a lot, and gave much more content to read and comprhend about. keep it up
Related
Scenario:
- I'm running Phoenix 4 ROM
- I want to try another ROM
- I have a copy of the JH7_OTA-1.zip
Can I just use ClockworkMod Recovery to flash the JH7_OTA ROM, then do a master clear from the phone and then apply any ROM I want?
Would that not accomplish the same thing as putting the phone in download mode and doing a stock restore via ODIN, followed by a Master Clear, and then flashing any ROM?
Can someone clear this up for me because it seems that both methods accomplish the same thing. They restore your phone to factory stock ROM as it's suggested by majority of the ROM before applying them.
Thanks
You can go from one rom to another without flashing stock.
I just went from doc jpy base to andromeda armani base. All I did was disable lag fix and kernel tweaks then flashed
I did so knowing I had odin just in case
What mcord11758 said except you don't actually need to disable anything. Just flash.
So that's the confusing part because:
Cognition ROM used to saynow there is just a DL link)
"flash back to I897UCJF6 (Recommended)"
and
How to flash PHOENIX Roms:
"1. BACK UP!!!
2. Use Odin One click to Flash Stock
2a. Wait for it to reboot and then re-enable debugging, hook phone back up to pc and Master Clear"
I got the concept that if running any lagfix it's best to disable it when updating the same ROM to a newer version but when doing a factory ROM it wipes out the ROM contents including the file-system format be it EXT4/EXT3 back to the Samsung RFS.
I would love to hear from one of the developers but I couldn't ask this question in the Dev Forum due too my n00b posting status.
Thanks for anyone who takes the time to provide some insight.
Phoenix and cognition both use ext 4 filing and the clockwork recovery built in understand it.
You have no less risk flashing jh7. in essence you are doing the same thing
flashing stock was more necessary when recovery could not understand ext 4. Today you can change to three different kernels in one day without ever disabling a lagfix
Vezee said:
I got the concept that if running any lagfix it's best to disable it when updating the same ROM to a newer version but when doing a factory ROM it wipes out the ROM contents including the file-system format be it EXT4/EXT3 back to the Samsung RFS.
Click to expand...
Click to collapse
The partitions get formatted either way (unless it's now wipe, in which case I guess data and datadb don't). If are running ext4 and your new kernel supports ext4 then why disable it?
mcord11758 said:
Phoenix and cognition both use ext 4 filing and the clockwork recovery built in understand it.
You have no less risk flashing jh7. in essence you are doing the same thing
flashing stock was more necessary when recovery could not understand ext 4. Today you can change to three different kernels in one day without ever disabling a lagfix
Click to expand...
Click to collapse
Thanks, that was the answer I was looking form I didn't exactly understand that the restriction was the recovery rom. It makes sense.
Simple question. If answered in another thread, please give me a pointer. I searched, but couldnt find an answer. Here is the question.
Why do we have to revert to Stock 2.1 before flashing a custom ROM? Why can't we flash a 2.2 custom ROM over another 2.2 Custom ROM? And finally, is there a CWM flashable version of stock 2.1 with root and cwm pre-installed?
Thanks.
before a lagfix was adopted as "standard" by the dev community this was necessary to reset the phone file system to n unmodified state. Now that all the devs are using the same type of awesome lagfix, reflashing to stock isn't really necessary anymore, IMHO. I never do it anymore. I just do a wipe user data from my recovery menu and everything seems to work fine.
The answer is not simple.
You do not have to flash stock. It used to be more needed. Devs still say so, but I believe that is largely to problem shoot issues from the get go. Threads are cluttered with comments like omg my phone is possessed. Well what were you running prior, and what was your setup? If stock well we know what was what. If ulk kernel with ext 2 loop, then yes there could be issues
Flashing stock at this point is just as risky, if not more risky then flashing directly over. If something feels wrong and you can't fix it, flash stock\master clear start over
So in essence, we can flash fine over an existing ROM and if there are issues, better go to stock and flash from there. Am I right? Can you list the steps you take to flash a new ROM without going to stock? Will there be issues if lets say I flash a 2.2 ROM over a 2.2.1 ROM?
I.do this but it may be redundant
Backup apps
Dl rom
Boot recovery
delete cache
delete davlik cache
Flash rom
delete davlik cache
Boot
I never did flash back to stock. I failed. Odin would not connect.
But for you guys out there - there is a way to bring recovery menu, that's what saved me.
Remove SIM and SD card.
Power+VolumeUp = reboot from any locked state
Power+VolumeDown=reboot into recovery
Power+both Volumes=download mode, never worked for connecting Odin, I could go there from Recovery
So my sequence:
remove old backups
create new backups
download ROM
boot into recovery
flash rom
clear cache partition and dalvik cache (probably the same)
run fix permissions
reboot
I think for most new ROMs that take advantage of the updated 2.2.1 filesystems you don't need voodoo or any lagfix. Can't even remember the last time I used ext4 when using speedmod kernel and JS3/JS5 Rom. Makes it easier to flash new roms when you don't have to worry about corruption.
But flash back to stock clears out any unnecessary gunk that could cause 90% of Force Closes and random vibrates on boot
I always thought of it as installing a new operating system or a different version of. It. Cming from the same roots of the ROM or OS, you can just install a different, major update over it (Different ROM) and be on your way.
However if sonething is built differently from the start (Windows and OSX), you cant just install right over the other because there are problems.
I always start back at the beginning because it onky takes a few minutes extra and it makes the phone a whole lot faster; you clean out alk the gunk and unused folders and whatnot.
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
mengbo said:
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
Click to expand...
Click to collapse
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Enhanced said:
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Click to expand...
Click to collapse
I use the oneclick odin to do master clear. The master clear works on i896 too.
I modified this post to recap the whole story. You can find the timeline development from the second post on.
My TAB is now bricked, it does not give any sign of life even after letting it charging for hours.
Not Odin or heimdall would recognize it to I cannot flash anything.
Samsung Mexico (where I am now) told me they cannot fix it because the mexican version has a different hardware configuration.
I also called Samsung US and they told me they cannot accept it, I should go back to china and repair it there (??).
I decided not to waste my time anymore on this, as it become anti economic.
(if anyone is interested in buying it as spare-parts, please let me know!)
what happened, for reference:
Chinese unicom GST p1000, previously flashed (and running) with success roto-JME.
I tried to flash JQ1 with bootloaders but ODIN failed at hidden.rfs. Since then I never manage to boot the tab anymore.
I then couldnt flash any ROM containing either hidden.rfs or movinand.mst, it would always FAIL. In order to PASS I had to remove these two from the flash, but TAB will hang at Samsung logo during boot (not sure if the reason for not booting is because of the missing files, or these 2 problems have the same cause, but are not related with eachother).
I tried a huge number of different ROMs, all give same results (even JME will fail at movinand.mst now)
in case you are wondering I already tried different computers, win and ubuntu, Odin and heimdall, changed USB cables, always the same problem.
Given the above situation (base ROM not complete and not booting + /data unmountable) I managed anyway to install Overcome and AF974, but they both hung at GALAXY TAB boot screen (the very first one) and keep rebooting every few seconds. (This is different from when it hangs at samsung logo - see above)
After this recovery started to report partition errors:
I cannot mount /DATA in either CWM or ADB , it says:
mounting /dev/block/mmcblk0p2 on /data failed: No such file or directory
indeed /dev/block/mmcblk0p2 does not exist.
I tried the flashing routine again, and new different partition errors came up
now the internal sd-card was not mountable anymore, instead it would read ext-sd as internal
I tried the flashing routine again, and it bricked completely to death
What I DIND'T do (learned about it too late!) prior to flash JQ1 was to neither ROOT or patch bootloaders before flashing, but I belive I should be ok:
I flashed JME successfully in the past and should be pre-rooted.
I also have reasons to think my bootloaders are not protected as:
I tried chainfire's SGTBootloaderCheck-1.0,it says I am clean.
I can flash CF-root, which is supposed to fail on protected bootloader.
I was brave and stupid enough to format /boot from recovery. Tab would not boot but I could flash it back from Odin with no problems (still, flashed an incomplete ROM without hidden.rfs)
i also tried other ROMS, but have the same problem with all of them
I tried chainfire's SGTBootloaderCheck-1.0 while on recovery mode, but it says I am clean
I cannot get out of this brick, can anyone point me in the right direction?
I'm not the one with the answers, but I casually saw these two posts hours ago:
How to unbrick tabs:
http://forum.xda-developers.com/show....php?t=1133590
This unlocks bootloaders so your SamFirmware.com rom won't brick you:
http://forum.xda-developers.com/showthread.php?t=888071
thanks but I have already seen and tried all of these.
The most commune solution to a soft brick in the forum is: "flash again".
but in my case it seems I just cannot flash anything.
Perhaps what I am looking for is a method/checklist to diagnostic the source of my problem?
or should I just keep trying flashing every possible rom? (i already tried at least 9)
2 cents
Hi,
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
thank you but I'd need more directions..
dirlan2001 said:
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
Click to expand...
Click to collapse
Thank you. this is a new approach and definitively worth trying it.
I would need more directions thou, as I only can flash roms using odin.
Are you saying I can flash this ROM from the recovery mode, I don't need Odin?
I am a bit confusing about the process: you are saying: 1) mount everything 2) format 3) flash.
1. What do you mean my 'mounting'?
when I go to my recovery mode i can see the option 'apply update from sdcard'. Is this what you mean by mounting?
2. Then format everything. what and how? you mean the SDcard? I am not aware of anything else I could be formatting. Please precise.
3. then flash everything.
how is flash different by Mounting, in this case? havent I already 'applyed' these files in step 1?
I am sorry if all these questions sounds idiot, I probably miss a lot of basic knowledge. I swear I did my homework, I spent DAYS reading all the forums. It's just hard to catch up everything from stratch without help.
thank you!!
i think i got it
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
Hi,
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
After reboot you should have a newer CWM that has more options to it. Note that the reboot may take some time... Then you can use the 'mount' to get all partitions mounted r/w... Then you run the kernel.zip and the ROM.zip from 'install zip from SD | go to external SD | choose the kernel.zip // redo the same for the ROM.zip without rebooting in between'
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
This sounds like you are in stock recovery and need cwm installed again.
________________________
Sent from my DROIDX X
dirlan2001 said:
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
Click to expand...
Click to collapse
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
jacopo3001 said:
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
Click to expand...
Click to collapse
On second thought, it may even be better to install the Overcome kernel first. That has the most recent version of CWM build in, and it makes your device ext4 instead of the old RFS. After that you easily can flash AF974's combo via CWM, whitout need to rename/copy anything. The link provides the guide to the mirror of OC, as their website isn't working anymore...
dirlan2001 said:
it may even be better to install the Overcome kernel
Click to expand...
Click to collapse
I have tried to flash GB-Stock-Safe-v5 (as for Overcome's docs) with Odin but it fails, just like all the other flashes I tried.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
jacopo3001 said:
I have tried to flash Overcome with Odin before but it fails, just like all the other flashes I tried in this period.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
Click to expand...
Click to collapse
Hi,
WCDMA is the 3.5G data-line : this means, it's NOT the WiFi alone version. If it's marked as P1000 just as is, then it's the GSM version. That means, you have EDGE/GPRS quadband @ 850/900/1800/1900 Mhz and HSDPA 7.2Mb/s=HSUPA 5.7 Mb/s triband @ 900/1900/2100 Mhz ...
Hmmm, what error did Odin give out when the flash failed ?
BTW, happy newyear etc ...
dirlan2001 said:
BTW, happy newyear etc ...
Click to expand...
Click to collapse
Happy new year to you, and that you very much for your help!
dirlan2001 said:
Hmmm, what error did Odin give out when the flash failed ?
Click to expand...
Click to collapse
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
here is how it looks like when I try GB-Stock-Safe (recommended by Overcome) for example:
Code:
<ID:0/018> Firmware update start..
<ID:0/018> boot.bin
<ID:0/018> cache.rfs
<ID:0/018> dbdata.rfs
<ID:0/018> factoryfs.rfs
<ID:0/018> movinand.mst
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I remove these files (Hidden.rfs or Movinand.mst) from the TAR i can flash with no errors, but the tablet wouldn't boot.
This apply to EVERY Roms i tried so far, with no exclusion.
I am making up a new theory: the first bricking error happened after I flashed JQ1, which has bootloaders. Could it be that those bootloaders go in conflicts with the chinese version of hardware, and thefore the brick?
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
jacopo3001 said:
Happy new year to you, and that you very much for your help!
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
Click to expand...
Click to collapse
Hi,
No thanks, you're welcome LOL
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Cheers, and good luck
dirlan2001 said:
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread.
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Click to expand...
Click to collapse
thanks, I know those threads already (read them all!)
the main problem I don't get about the bootloader fix is that chainfire released a APK, which assume you can boot the phone!
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
regarding AF974, that's not my priority, I am just trying to have this thing working again..
jacopo3001 said:
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
Click to expand...
Click to collapse
Hi,
He did a 200 mile trip to have the MoBo changed .. LOL That doesn't help you any further I guess...
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
PS : as long as you can get it in download mode (odin) or CWM it's not a brick, it just not booting completely...
dirlan2001 said:
Hi,
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
Click to expand...
Click to collapse
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
jacopo3001 said:
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
Click to expand...
Click to collapse
Hi,
Do I understand correctly your system is up and running again ? In that case I would certainly recommend to run the complete guide to make it first stock again. The kernel indeed does a conversion to ext4, which is a way better filesystem as the rfs from Samsung. Look in the Overcome thread for the mirrors as OC seems still to have serious problems with their serversystem.
And if you take courage (and the habit) you might start looking for a more recent kernel and ROM...
dirlan2001 said:
Do I understand correctly your system is up and running again ?
Click to expand...
Click to collapse
The system is NOT up and running.
It's hanging at the Samsung logo.
But I can at least get to both download and recovery mode.
What happens is that, regardless which ROM I try, I cannot flash neither hidden.rfs nor movinand.mst (depending on Rom's content), they always FAIL on ODIN.
If I flash a ROM removing those 2 it Odin would success, but the tab will not Boot and hang at Samsung logo.
That's why I say the system is not stable now, I am not sure whether it's a good idea to go into changing FS now or would it screw up things even worst...
Hello i was wondering if someone could help me with an issue which may seem very minor to you, but i am a new bee in the rom business. I was running MIUI and wanted to switch to the Fasty 3 V1.3, so i go into recovery and then clear the cache and then the dalvic cache then i wiped all the user data. Then i applied the zip from my internal SD card and after installing the zip i would reboot then it would get stuck on the cynogen mod boot screen. So whenever i want to change to another rom i always have to go back to stock Eclair and then reroot and then ad a rom. Could anyone tell me what i am doing wrong?
When leaving MIUI or Cyanogen Mod and returning to "standard or regular" Roms you have to go back to "Stock" And Repartition.
MIUI and Cyanagen Mod use a different Partition Map ---- MTD
The other standard or regular (for lack of a better word at this time) i897 and i9000 Roms use the BML Partition Map.
And so when changing from a MTD Rom to a BML Rom you must flash to Stock Firmware that does a Full Wipe and Repartitions.
4-2ndtwin said:
When leaving MIUI or Cyanogen Mod and returning to "regular" roms you have to go back to "Stock" And Repartition.
MIUI and Cyanagen Mod use a different Partition Map ---- MTD
The other regular (for lack of a better word at this time) Roms i897 and i9000 use the BML Partition Map.
Click to expand...
Click to collapse
I beg to differ on repartition. If you were to use my kf1 packaged to go back to"stock" there is no repartition involved. There is not a pit file packaged with it. I have always thought that you are merely reformatting your existing partitions. Double check with someone more learned than i. I don't want to misinform anyone.
^
Thanks Mike for the correction. I was wrong in my initial post... Used the strike out to correct it.
I just finished going to Cyanogen Mod and MIUI from Stock i897uckk4 with Corn Kernel and returning successfully to kk4 from both of those using ur Safe KF1 Odin 3 File No Bootloaders. The Full Wipe has got to be the answer then, not the Repartition. The Reformatting, Not the Repartioning.
I have always used the Repartition along with the Full Wipe when returning to Stock from those MTD Roms and I thought I had learned somewhere along the way that that is what was necessary.
I sure don't wanna give out bad info...so thanks again.
So to switch roms i always have to go back to stock? Because when i do go back to stock i lose my root and three button fix and have to re-do them.
Info for AOSP to i897, i9000 roms
Not always. Just when going from a AOSP (CyanogenMod, MIUI, ICS, etc) to a I897 or I900 rom. As for the 3 button fix just flash GB bootloaders you don't EVER have to reflash those unless you wish too. Just remember to use "safe" or no bootloader packages. Root isn't important since most roms are rooted and ALOT of kernels have root.
I should be more clear. You will need GB bootloaders for Fasty 3. After you flash them always use "safe" or "no bootloader" packages for odin and you will never loose 3 button fix and save you from hard bricking in general.
Mental note: Need to remind myself to put tittle so searching is easier.....
I been seeing a lot of SOC or any other method of rooting that confuses user
so i wanna do this little guide and direct n00bs to use this with out any confusion
of flashing roms with out complicated steps
I do admit some stickies are a little confusing and provide extra information which
may further confuse a user
so here it goes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!DISCLAIMER!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I am NOT responssible for what ever happens to your phone if steps are not
followed to the DOT
[Make sure proper drivers are installed in computer]
1.One Click ODIN this file
- http://www.multiupload.com/02H0BJWHKV
(this file will give you stock GB rooted with custom CWM recovery)
(unrar, place file on desktop, right click and select run as administrator, boot phone to download mode from a powered off state by clicking the vol up and vol down then inserting usb transfer pc cable, it should automatically boot up to a yellow triangle and an android digging picture, click the big START button on Odin and let it sit)
should take about 2-3 minutes..let it boot to see everything is ok
2.Download the rom of youre choice and place in sd card
3.Boot into CWM (pushing vol up + vol down + power)
4.Navigate to "intall zip from sd card"
5.Chose the Rom on youre sdcard and install.
(If its your first time flashing ICS your phone will reboot.. its ok just boot it back up to recovery.)
Youre all set enjoy your rom!!!!
(steps 6 and up are for flashing ICS proceed if youre doing so)
6.Youll have the blue CWM recovery
7.Install ICS rom once again (dont forget to wipe everything before doing so)... it should fully go thru this time..
8.Wipe again and flash GApps (if using CM9 if not skip)
9.Reboot phone...and let it load up.. takes 5-6 mins
10.Enjoy ICS
i did these steps to the dot, so have others and it works!!!
How do I " one click Odin"???
and btw none of your links ever work...
not sure why you wrote this when you help out my guide, which is "stickied"
How To Flash Captivate ROMs from STOCK
and your instructions for ICS... "blue recovery" depends on the kernel.
double flash has not been necessary since RC2.0,
and the best instructions for ICS is after booting into CWM, flash nushor kernel from http://ics.darkirc.me/ , then flash ICS, boot into success.
**ICS SGS RC3.1 will NOT install on stock unless an MTD kernel is present (nushor)
TRusselo said:
not sure why you wrote this when you help out my guide, which is "stickied"
How To Flash Captivate ROMs from STOCK
and your instructions for ICS... "blue recovery" depends on the kernel.
double flash has not been necessary since RC2.0,
and the best instructions for ICS is after booting into CWM, flash nushor kernel from http://ics.darkirc.me/ , then flash ICS, boot into success.
**ICS SGS RC3.1 will NOT install on stock unless an MTD kernel is present (nushor)
Click to expand...
Click to collapse
since you know a lot about android can you help me. im on 2.3.5 and tried to do some one click odin flash thing and nothing is going right. and whenever i try and install a custom rom from my micro sd card it always gets stuck on like changing from stock recovery to cmw or something. and none of my apps are working right. please help im a newb.
TRusselo said:
**ICS SGS RC3.1 will NOT install on stock unless an MTD kernel is present (nushor)
Click to expand...
Click to collapse
Just to clarify it isn't the "mtd" fact, it ONLY installs from Nushor's kernel. Poorly made cwm scrip (at least in the beginning, not sure now).
@OP: That being said "blue recovery" is vague to say the least (some kernels have custom color recovery). That being said, as long as its cwm 2.5+ it will flash just the same, WITH the exception of ICSSGS RC3.1. Also links are down. Not sure why all of them are. And last bit, if the current .zip still has the "error 7" thing I would add the Nushor kernel bit.
P90 said:
since you know a lot about android can you help me. im on 2.3.5 and tried to do some one click odin flash thing and nothing is going right. and whenever i try and install a custom rom from my micro sd card it always gets stuck on like changing from stock recovery to cmw or something. and none of my apps are working right. please help im a newb.
Click to expand...
Click to collapse
"some odin one click" isnt very discriptive... one-clicks are *usually* stock Android that came from your carrier. Custom roms are usually installed in CWM. Odin doesnt use CWM. not sure what your problem is.....
prbassplayer said:
Just to clarify it isn't the "mtd" fact, it ONLY installs from Nushor's kernel. Poorly made cwm scrip (at least in the beginning, not sure now).
@OP: That being said "blue recovery" is vague to say the least (some kernels have custom color recovery). That being said, as long as its cwm 2.5+ it will flash just the same, WITH the exception of ICSSGS RC3.1. Also links are down. Not sure why all of them are. And last bit, if the current .zip still has the "error 7" thing I would add the Nushor kernel bit.
Click to expand...
Click to collapse
yes it was a problem with the install script. but without an MTD kernel, it wont install. so we are both right. lol
Sorry guys I tried to make this for the people who are always in the "bootloop" or "status 7" errors
@TRusselo I've got your guide linked on my sig but like I said some people may not understand what to do or how to do or get confused when you start talking about bootloaders n stuff... so with that being said this is just a "first do this then this then than" tutorial with out confusing or further confuse a first time flasher with the technical terms...
But if you guys feel this isn't necessary I can ask for it to be taken down
Just tryn to help out and not get first time flashers to post in wrong sections or ask or do the wrong things
Wasn't trying knock it. Pointing out few "flaws" as I see them
Sent from my ICS powered Captivate using Tapatalk
While your effort is commendable, nothing can replace reading and research about what a user wants to do on their phone. In the long run, it creates a more positive experience for the user, as well as builds their confidence for future modding.
TRusselo said:
not sure why you wrote this when you help out my guide, which is "stickied"
How To Flash Captivate ROMs from STOCK
and your instructions for ICS... "blue recovery" depends on the kernel.
double flash has not been necessary since RC2.0,
and the best instructions for ICS is after booting into CWM, flash nushor kernel from http://ics.darkirc.me/ , then flash ICS, boot into success.
**ICS SGS RC3.1 will NOT install on stock unless an MTD kernel is present (nushor)
Click to expand...
Click to collapse
This guide save my captivate
How To Flash Captivate ROMs from STOCK
I did use one kernel with CWM and then uploaded the other roms.
No need to create a new guide...