Help!
I tried to installed technomancer's clockworkmod recovery (sorry, i can't post a link now) on my galaxy tab (gt-p1000) (gsm)
while in download mode, with heimdall, using the command "heimdall flash --kernel zImage --no-reboot".
the flashing went smoothly and after that i tried to boot in to recovery mode, but it's just stuck at the galaxy tab screen. It doesn't even boot into the stock android anymore.
Thanks in advance to anybody who can help.
Flashing CWM on its own is a hit and miss.
Use Overcome method.
What it does is it provides a baseline GB stock version that is sure 100% will work with Overcome Kernel 4.0 (which has CWM 5).
Follow my signature and download GB-stock-safe-v5 and Overcome Kernel 4.0 tar.
heimdall:
1) unpack the GB_Stock_Safe_v5.zip have a good look at the contents (unpack the .tar file as well) and modify the command below accordingly
2) go to download mode
3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage --modem ./modem.bin
4) at this point you can reboot to the stock rom.
I normally don't boot to the ROM, I just know it is a good base now, and I don't need it.
when done,
5)unpack the overcome kernel 4.0 tar and you get another zImage
6) go to download mode
7) Flash that zImage
heimdall flash --kernel ./zImage
tab will reboot
- ignore the robotic voice, just force the tab to off
From here I assume you want to flash a custom ROM, in here my example is AOKP SGT7
8) Boot into recovery and flash your latest AOKP.
It may throw you back to recovery but that is normal, then choose to flash AOKP again. You may notice the CWM is slightly different from Overcome one, and the internal and external sd is swapped around. Just explore to both to find your aokp zip if you are confused.
9) flash gapps
thank you! Priyana. Your method was extremely helpful. I am now running CyanogenMod 9.1 on my galaxy tab.(which i never dreamt of)
BTW.. I would still like to know what the problem was when I was trying to install CWM using heimdall directly.
Simply put, the technomancher cwm only works in certain condition. Overcome tried to create a standard condition that works every time.
Sent from my GT-P1000 using xda app-developers app
Related
This is how I got stuck in Darky's rom boot.
I have to mention that I'm on Linux and have Heimdall as my only rom flashing tool. Well I have XP and Odin setup in a Virtual Machine VB.
- First I started with the stock rom my phone comes with Froyo 2.2
- Flashed speed mod kernel with Heimdall "speedmod-kernel-k13e-500hz-CWM" which makes my phone much more responsive and stable.
- Downloaded Darky's rom 10.2 Resurection Edition from Darky's site.
- Extracted the content of the PDA.tar from Darky's rom archive.
- Within the directory containing the pit file and the extracted files from PDA.tar I executed the following command in the terminal
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --modem modem.bin --kernel zImage
This series of command is included in a txt file from Darky's rom archive namely heimdall.txt.
- Helmdall completes the flash with message saying all files being 100 percent uploaded to the phone.
- The phone auto restarts, went through the automatic initialization and arrives at Darky's rom logo and boot animation.
- :-/ Stucked at darky's logo and boot animation being displayed one after another.
- In a forum someone mentioned initial boot can be as long as 20 mins to 1 hour. Last night I left it for 8 hours without getting through the booting process.
- ???!!!
Problem solved!!!
As a Linux user, I use Odin in Win XP running in virtual machine (Virtualbox Oracle version, not opensource version)
Seems like Odin and Helmdall DOES produce different outcome after all, despite how many claims it is said to be compatible. So AT THIS TIME, I can say that there exist a certain things heimdall perform differently from Odin.
What was your fix? Mine is stuck on a Can't Mount error. Did yours do this at all?
Sissy2170 said:
What was your fix? Mine is stuck on a Can't Mount error. Did yours do this at all?
Click to expand...
Click to collapse
Are you on Linux? More info would be useful. I don't have problem what so ever with mounting Odin did its' thing smoothly. As a Linux fan I wish heimdall could manage though, but as I said it soft brick my phone for a day. Hope you get through the flash, IMO it is totally worth it.
my windows drive has failed i have come to learn.
i want to restock from a non-mtd version of aokp (build 31) in order to install the latest build 36.
i have never used odin or the other samsung specific tool so am a bit lost (my android experience is largely with htc where adb and fastboot is all i really need to know outside of a recovery like clockwork.)
i do happen to have CWM labelled HumberOS-v5.6.0 installed
dude, just follow the set of instructions on the team overcome website. its easy enough to follow even for a noob like me.
dude, he said Linux.
Overcome site don't do linux
BTW, this is what I do using heimdall on linux, and remember that restock is to GB-stock-safe, not to Overcome.
For most purpose, you only need restock (to get back to BML partition), then Overcome Kernel 4.0 to get CWM.
So here goes
1) naturally unpack the GB_Stock_Safe_v5.tar
2) go to download mode
3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage
4) at this point you can reboot to the stock rom.
there may be some error, mine did, but I ignore it
when done,
5)unpack the overcome kernel 4.0 tar and you get another zImage
6) go to download mode
7) Flash that zImage
heimdall flash --kernel ./zImage
then wait for the fembot voice to complete.
8) Boot into recovery and flash your latest AOKP.
It may throw you back to recovery but that is normal, then choose to flash AOKP again. You may notice the CWM is slightly different from Overcome one, and the internal and external sd is swapped around. Just explore to both to find your aokp zip if you are confused.
9) flash gapps
oops.. sorry, my bad!
priyana said:
1) naturally unpack the GB_Stock_Safe_v5.tar
2) go to download mode
3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage
Click to expand...
Click to collapse
it rebooted it itself. now i have a samsung that is "flashing". and it seems it is rebooting now and again. it's been doing this for 5 minutes.
priyana said:
dude, he said Linux.
Overcome site don't do linux
BTW, this is what I do using heimdall on linux, and remember that restock is to GB-stock-safe, not to Overcome.
For most purpose, you only need restock (to get back to BML partition), then Overcome Kernel 4.0 to get CWM.
So here goes
1) naturally unpack the GB_Stock_Safe_v5.tar
2) go to download mode
3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage
4) at this point you can reboot to the stock rom.
there may be some error, mine did, but I ignore it
when done,
5)unpack the overcome kernel 4.0 tar and you get another zImage
6) go to download mode
7) Flash that zImage
heimdall flash --kernel ./zImage
then wait for the fembot voice to complete.
8) Boot into recovery and flash your latest AOKP.
It may throw you back to recovery but that is normal, then choose to flash AOKP again. You may notice the CWM is slightly different from Overcome one, and the internal and external sd is swapped around. Just explore to both to find your aokp zip if you are confused.
9) flash gapps
Click to expand...
Click to collapse
as per usual priyana, you are a great help!
two things i will note:
dont use the latest version of heimdall, use the second last version for the best results. i had trouble with the latest version and flashing kernels
you dont need to wait for the fembot voice to do its magic (converting to ext4 is irrelevant when you are going to change partition types again anyway), after you flash the overcome kernel, restart and hold down vol up to go straight back to recovery, from there continue on to point 8
best of luck! there will be an updated and clearer tutorial for heimdall on the AOKP website once its completed!
how long should i wait for the horse head of aokp to go away?
milomak said:
how long should i wait for the horse head of aokp to go away?
Click to expand...
Click to collapse
Still nothing. Guessing after I wake up it will be the same story.
Since you have gone that far, try enter download mode and flash aokp again, wipe cache as well.
Sent from my GT-P1000 using XDA
thanks. yeah i rewiped data, cache and dalvik.rebooted and all is well.
I want to update this with one piece of info:
Somehow, the above restock using heimdall and pit, did not wipe internal SD.
I heard an Odin repartition with pit file will wipe it.
Do the steps above cater for the modem?
Hi milomak,
You are right! I missed out
--modem modem.bin
Of course I have been doing it hurriedly to restock only to flash AOKP mtd again.
For that purpose, I didn't even boot to gb, I immediately flash overcome kernel.
Then when it reboot to do ext4 conversion, I force it to power off, and then straight away boot to cwm, then flash AOKP.
Yes, to restock to gb jq1 or overcome (and stay in bml rom, you need to flash modem.bin during heimdall flash,
Or later using cwm recovery to flash modem zip that is for bml rom.
Mark that, because the cyanogenmod wiki now has zip for mtd rom. That one is for mtd only and in my opinion unnecessary.
For mtd rom just copy directly to /radio
Sent from my GT-P1000 using xda app-developers app
To clarify, is that for mtd; I would copy the modem zip to /radio?
Confirmed for mtd. Just copy to /radio
Sent from my GT-P1000 using xda app-developers app
There is any way to flash my GT-N7000 using img file but with DEKTOP odin ?
Thanks!
ahander said:
There is any way to flash my GT-N7000 using img file but with DEKTOP odin ?
Thanks!
Click to expand...
Click to collapse
No way. Can only flash .tar or .tar.md5 using desktop / PC Odin.
Thanks!
Can you help me about one more little thing?
I have rooted my Galaxy Note and downloaded the v08 file from the: http://forum.xda-developers.com/showthread.php?t=1516515
Inside the .tar file i found this files: cache.img; data.img; factoryfs.img; hidden.img and zImage.
What file i have to open in Mobile Odin to install the ICS in my Galaxy Note?
I guess it's:
Kernel: zImage
System: factoryfs.img
Data: data.img
Cache: cache.img
Hidden: hidden.img
Is that correct? Sorry about the silly question, but it's better sound like a noob to get a mobile bricked! lol
Thanks!
If you want to install stock ICS, you dont need to select it manually
Just in Mobile odin, select open file and point to tar file. It will popup and fill file autometically to according tab then just flash.
You can do it with PC Odin too.
Just select PDA tab and point to .tar file and flash.
dr.ketan said:
If you want to install stock ICS, you dont need to select it manually
Just in Mobile odin, select open file and point to tar file. It will popup and fill file autometically to according tab then just flash.
You can do it with PC Odin too.
Just select PDA tab and point to .tar file and flash.
Click to expand...
Click to collapse
I want to install the AOSP ICS from this thread: http://forum.xda-developers.com/showthread.php?t=1516515
Thanks!
In addition, mobile odin will not let you select the wrong file. So, don't worry. Everbody was once a noob
kopitalk said:
In addition, mobile odin will not let you select the wrong file. So, don't worry. Everbody was once a noob
Click to expand...
Click to collapse
thanks
So, i follow the steps to install the "imilka's AOSP ICS v08 [IMM76D/4.0.4]".
1. Downloading the latest version of "imilka's AOSP ICS v08 [IMM76D/4.0.4]" (v08);
2. Flash my Galaxy Note with Android 2.3.6 using Odin for WIndows;
3. Wipe Cache / Factory Reset;
4. Flash my Galaxy Note with Android 4.0.4 using Odin for WIndows;
5. Root my device and install the Mobile Odin Pro;
6. Flash my Galaxy Note with the latest (v08) "imilka's AOSP ICS v08 [IMM76D/4.0.4]" using Mobile Odin Pro;
But, when my Galaxy Note reboot, his show the status bar with the rest of screen black, some seconds after the android displays the following error: "unfortunately twlauncher has stopped" and reboot again.
Then, the Galaxy Note loads the Android 4.0.3 with TouchWiz just like the stock samsung version, with s-note, s-etcetera.. lol
Any sugestions?
Thanks!
ahander said:
So, i follow the steps to install the "imilka's AOSP ICS v08 [IMM76D/4.0.4]".
1. Downloading the latest version of "imilka's AOSP ICS v08 [IMM76D/4.0.4]" (v08);
2. Flash my Galaxy Note with Android 2.3.6 using Odin for WIndows;
3. Wipe Cache / Factory Reset;
4. Flash my Galaxy Note with Android 4.0.4 using Odin for WIndows;
5. Root my device and install the Mobile Odin Pro;
6. Flash my Galaxy Note with the latest (v08) "imilka's AOSP ICS v08 [IMM76D/4.0.4]" using Mobile Odin Pro;
But, when my Galaxy Note reboot, his show the status bar with the rest of screen black, some seconds after the android displays the following error: "unfortunately twlauncher has stopped" and reboot again.
Then, the Galaxy Note loads the Android 4.0.3 with TouchWiz just like the stock samsung version, with s-note, s-etcetera.. lol
Any sugestions?
Thanks!
Click to expand...
Click to collapse
You can flash the GB again, and why the need to flash 4.0.4 again?
So far as i heard it is a risky kernel.
Doesnt the custom rom zip you specified can be installed from cwm on gb kernel?
You can flash the GB again, and why the need to flash 4.0.4 again?
So far as i heard it is a risky kernel.
Doesnt the custom rom zip you specified can be installed from cwm on gb kernel?
Click to expand...
Click to collapse
Because i can't run CWM with 2.3.6 (for root it), i always got an error. And i don't found any source to download the compatible CWM
Usually AOSP based ROM is installed via CWM recovery, i.e. flash rom, flash gapps, done. How did you do it with Mobile Odin?
kopitalk said:
Usually AOSP based ROM is installed via CWM recovery, i.e. flash rom, flash gapps, done. How did you do it with Mobile Odin?
Click to expand...
Click to collapse
So, i'm confused because i follow the steps in the thread http://forum.xda-developers.com/showthread.php?t=1516515
And it doesn't work =/
kopitalk said:
Usually AOSP based ROM is installed via CWM recovery, i.e. flash rom, flash gapps, done. How did you do it with Mobile Odin?
Click to expand...
Click to collapse
1. I downloaded the rom v08 (.tar file) from the: http://forum.xda-developers.com/showthread.php?t=1516515
2. I have rooted my Galaxy Note (Android 4.0.4) with CWM
3. Install Mobile Odin Pro
4. Inside the .tar file i found this files: cache.img; data.img; factoryfs.img; hidden.img and zImage.
5. Select in Mobile Odin the following options:
Kernel -> file: zImage
System -> file: factoryfs.img
Data -> file: data.img
Cache -> file: cache.img
Hidden -> file: hidden.img
Modem -> none
Params -> none
Then, flash!
There are 2 parts of installation:
1. Install the base, which is official ICS -> odin
Root it, get a working CWM recovery with disabled brickbug,
2. Flash the aospgnxx.zip -> CWM
kopitalk said:
Usually AOSP based ROM is installed via CWM recovery, i.e. flash rom, flash gapps, done. How did you do it with Mobile Odin?
Click to expand...
Click to collapse
kopitalk said:
There are 2 parts of installation:
1. Install the base, which is official ICS -> odin
Root it, get a working CWM recovery with disabled brickbug,
2. Flash the aospgnxx.zip -> CWM
Click to expand...
Click to collapse
With Official ICS you mean "the" Samsung official ICS? Can be the 4.0.4 (Open Germany) recently released?
"Root it, get a working CWM recovery with disabled brickbug"
Ok about root. But CWM with "disabled brickbug"? How can i get it?
And where do i found the aospgnxx.zip to download?
Thanks!
The .tar file that you downloaded is the base file, i.e. ICS. The aospgnxx.zip you can download from http://download.imilka.eu if the file is still available. The CWM with brickbug disabled, you can try speedmod or gl_notecore or goku or franco.
kopitalk said:
The .tar file that you downloaded is the base file, i.e. ICS. The aospgnxx.zip you can download from http://download.imilka.eu if the file is still available. The CWM with brickbug disabled, you can try speedmod or gl_notecore or goku or franco.
Click to expand...
Click to collapse
http://download.imilka.eu is offline
but thanks anyway
so I soft bricked my p1000 by attempting to download and install the latest cm9 nightly (i'm pretty sure i tried to flash a bad zip.
it starts up, gets to the samsung galaxy tab logo and hangs until i force it to power off. I CAN enter download mode but not CWM recovery.
I would very much like to recover the data that is currently on my tab or i would simply restock as all of the unbricking guides suggest, but alas, I want my data.
I have a known good working rom image .zip on the internal flash. so I would like to just attempt to flash that, but I can't seem to access CWM recovery.
From what I gather, cwm recovery is a function of the kernel, so then, at this point I would very much just like to flash one of the modern cm9 cwm recovery-enabled kernels via odin OR a known good cm9 install package via odin.
does anybody know how I can go about doing this?
that is why I always use heimdall.
extract the boot.img from good package and
heimdall flash --kernel ./boot.img --recovery ./boot.img
I do realize that this is what the thanks button is for, but somehow that doesn't seem to be enough. thanks to your instruction, I was able to immidiately get my p1000 back online up and running. THANK YOU so very much! *super internet high five*!!
I could not find much help on this issue so starting a new thread. I was trying to install the CyanogenMod Android on my wife's Samsung Captivate I897 using the official instructions in the CyanogenMod Wiki page -
wiki.cyanogenmod.org/w/Install_CM_for_captivatemtd
While installing a custom recovery on Captivate, I screwed up on step 5 while running the below command.
heimdall flash --kernel zImage --no-reboot
I tried with zImage keyword and it didn't work and not sure what went into my mind, I copied the "Semaphore_2.5.0c.tar" into the Heimdall directory and pushed it into the device using the below command -
heimdall flash --kernel Semaphore_2.5.0c.tar --no-reboot
After this the device is not starting. Only the AT&T initial Flash page is coming and it freezes there unless I take out the battery. I can still get the device into the download mode using the USB and volume keys.
Appreciate any help in this regards !!
tom0044 said:
I could not find much help on this issue so starting a new thread. I was trying to install the CyanogenMod Android on my wife's Samsung Captivate I897 using the official instructions in the CyanogenMod Wiki page -
wiki.cyanogenmod.org/w/Install_CM_for_captivatemtd
While installing a custom recovery on Captivate, I screwed up on step 5 while running the below command.
heimdall flash --kernel zImage --no-reboot
I tried with zImage keyword and it didn't work and not sure what went into my mind, I copied the "Semaphore_2.5.0c.tar" into the Heimdall directory and pushed it into the device using the below command -
heimdall flash --kernel Semaphore_2.5.0c.tar --no-reboot
After this the device is not starting. Only the AT&T initial Flash page is coming and it freezes there unless I take out the battery. I can still get the device into the download mode using the USB and volume keys.
Appreciate any help in this regards !!
Click to expand...
Click to collapse
you will have to flash to stock using odin.
you can find the one which has cwm installed here
http://forum.xda-developers.com/showthread.php?t=1294849
then after the phone boots up shut it down
open the cwm and flash the rom which you want to flash