Database Develop

Help please!

--------------------------------------------------------------------------------
Hey guys I'm not sure if this is the right place to post this but I just really need some help...
I just recently flashed my galaxy to JP6 and installed voodoo and everything was running fine. I then wanted to root my phone and tried Chainfires solution from here on this forum. It bricked my phone and I had to flash back to JM8.
I am now running JM8 but when I go to flash JP6 it says fail and wont let me?
I also tried flashing JMP and my phone screen went green halfway through and stopped flashing.
Any ideas why I cant flash to froyo anymore?
Is it because I still have voodoo installed?
If so how do I delete it? I've tried following th instructions from curios google page but I couldn't figure it out.
The error in odin reads "Can't open the serial(COM) port"
Any info on this would be greately appreiciated!
Thanks

GalaxyDroid88 said:
--------------------------------------------------------------------------------
Hey guys I'm not sure if this is the right place to post this but I just really need some help...
I just recently flashed my galaxy to JP6 and installed voodoo and everything was running fine. I then wanted to root my phone and tried Chainfires solution from here on this forum. It bricked my phone and I had to flash back to JM8.
I am now running JM8 but when I go to flash JP6 it says fail and wont let me?
I also tried flashing JMP and my phone screen went green halfway through and stopped flashing.
Any ideas why I cant flash to froyo anymore?
Is it because I still have voodoo installed?
If so how do I delete it? I've tried following th instructions from curios google page but I couldn't figure it out.
The error in odin reads "Can't open the serial(COM) port"
Any info on this would be greately appreiciated!
Thanks
Click to expand...
Click to collapse
Hey,
My guess is it's your recovery version. You need to boot to recovery mode and see whether the version is 2e or 3e. 3e won't allow you to flash unsigned updates.
Also, make sure you put a 'disable lagfix' folder inside your voodoo folder on the internal SD card. That may also be an issue.
Good luck!

I can currently only get onto download mode with my phone, I used to be able to get into recovery mode using the 3button technique but I no longer can.
I'm pretty sure it's voodoo that is causing me my problems, is there any way I can disable/un-install voodoo with only going into download mode?

GalaxyDroid88 said:
I can currently only get onto download mode with my phone, I used to be able to get into recovery mode using the 3button technique but I no longer can.
I'm pretty sure it's voodoo that is causing me my problems, is there any way I can disable/un-install voodoo with only going into download mode?
Click to expand...
Click to collapse
Not that I know of mate, you need access to the drive so you can pop a folder named 'disable lagfix' insude your /voodoo folder. If you can get into download mode, you should be able to use Odin to reflash a ROM, I think you need to tick 're-partition' though. I've never flashed a SGS with Odin (yet haha), so would pay to do some more reading. I do know that it is the only way to restore your phone to absolute stock, which I think I would be doing. Then you can start again!
Good luck!

[Q] Clockworkmod Recovery error: signature verification failed!

Hi all,
I installed JPY (2.2.1) Rom on my SGS yesterday, rooted my phone with SuperOneClick.
Tested the phone, everything is ok and the root is also ok.
Then installed Clockworkmod, flash cwm recovery 2.5.1.2, click on Backup, the phone automatic rebooted but presented my with a normal recovery screen.
In it I can do something like; a factory reset, clean card data, restart or click on update.zip (I thing that goes to the update.zip that cwm put on my sdcard).
But when I click it gives this error:
Install from package...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Tried everything... What can I do in order to cwm works and backups my sgs??
All the help is appreciated...
Thanks,

you loose 2e recover when going to froyo.. needed for clockwork ..
flash a kernel that restores it ie
chainfire/cf or speedmod or backlight notifiction ie bln kernel.

lgkahn said:
you loose 2e recover when going to froyo.. needed for clockwork ..
flash a kernel that restores it ie
chainfire/cf or speedmod or backlight notifiction ie bln kernel.
Click to expand...
Click to collapse
So what are you saying is that CWR doesn't work with 3e recovery? Only with 2e?

Because 3e does not allow unsigned zips hence the error message..
Sent from my GT-I9000 using XDA App

Sâmes problem for me... No solution found yet ...
Sent from my GT-I9000 using XDA App

install CF-root http://forum.xda-developers.com/showthread.php?t=788108 to get 2e recovery then reflash CWM recovery and try again...

striken said:
So what are you saying is that CWR doesn't work with 3e recovery? Only with 2e?
Click to expand...
Click to collapse
ah ya.. the "needed for clockwork" in my original message pretty much states that.

android.francis said:
Because 3e does not allow unsigned zips hence the error message..
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks for the explanation,
Didn't know why it works with one and not the other...
Anyway, its working now, thanks for all the help!
For anyone that has the same problem, here is what I did:
Flashed the phone with I9000XXJPY and with Odin. You can find JPY here: http://www.multiupload.com/UHJNT0K1F2
Put PIT 512 in PIT and in PDA put the file JPY_JPY_JPY.tar (no repartition selected).
Shutdown the phone after it starts.
Start Odin again and in PDA put this file: CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
You can download it here:
http://forum.xda-developers.com/showthread.php?t=788108
After that you can install CWM. When you click in backup and the phone restarts see if 2e restore appears in top of the screen if so all is ok.
Also, if a normal screen appears just click in update.zip and after that you will see the cwm screen.
In the cwm recovery screen the sgs buttons are like this: back button is the “enter” and the “menu” is the back button.
P.S. If you need to install TPH for Portuguese language just tell me, cause the CSC installed is KOR and you don't have TPH in CSC file to install.
Once again, Thanks to all who help me!

striken said:
Thanks for the explanation,
Didn't know why it works with one and not the other...
Anyway, its working now, thanks for all the help!
For anyone that had the same problem, here is what I did:
Flashed the phone with I9000XXJPY and with Odin. You can find JPY here: http://www.multiupload.com/UHJNT0K1F2
Put PIT 512 in PIT and in PDA put the file JPY_JPY_JPY.tar (no repartition selected).
Shutdown the phone after it starts.
Start Odin again and in PDA put this file: CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
You can download it here:
http://forum.xda-developers.com/showthread.php?t=788108
After that you can install CWM. When you click in backup and the phone restarts see if 2e restore appears in top of the screen if so all is ok.
Also, if a normal screen appears just click in update.zip and after that you will see the cwm screen.
In the cwm recovery screen the sgs buttons are like this: back button is the “enter” and the “menu” is the back button.
P.S. If you need to install TPH for Portuguese language just tell me, cause the CSC installed is KOR and you don't have TPH in CSC file to install.
Once again, Thanks to all who help me!
Click to expand...
Click to collapse
Great explanation but for the record (for anyone looking for a solution), if you're already on a 2.2 firmware, you can simple start at the step of flashing a custom kernel that supports CWM (i.e. there's no need to first flash to JPY).

gtg2 said:
Great explanation but for the record (for anyone looking for a solution), if you're already on a 2.2 firmware, you can simple start at the step of flashing a custom kernel that supports CWM (i.e. there's no need to first flash to JPY).
Click to expand...
Click to collapse
That's a thing I didn't know.

Winrar is asking for a password?

imprezzadude said:
Winrar is asking for a password?
Click to expand...
Click to collapse
On what files?

On the I9000JPY file. Sorry i didnt specify. Been a loong day lol

I am Facing Similar problem...
i wanted to install new rom on my phone ...i.e. darky's v 8.0
so i rooted my phone with z4root, then downloaded the rom and the update.zip file for clockward mod on to internal sd card..
and when tried to run update.zip file in normal recovery mode to get into clockward recovery i got the same signature error
i looked for solutions..got to know about rom manager..downloaded it and installed clockward mod through it..and then tried to reboot into clockward recovery ...it will bring me to same normal recovery screen...so basically stuck and cant get to clockward recovery...please help
my phone details
model gt-i9000
firmware:2.2
baseband : i9000zsjpe

deepumalik said:
I am Facing Similar problem...
i wanted to install new rom on my phone ...i.e. darky's v 8.0
so i rooted my phone with z4root, then downloaded the rom and the update.zip file for clockward mod on to internal sd card..
and when tried to run update.zip file in normal recovery mode to get into clockward recovery i got the same signature error
i looked for solutions..got to know about rom manager..downloaded it and installed clockward mod through it..and then tried to reboot into clockward recovery ...it will bring me to same normal recovery screen...so basically stuck and cant get to clockward recovery...please help
my phone details
model gt-i9000
firmware:2.2
baseband : i9000zsjpe
Click to expand...
Click to collapse
How about
1. Repartition with a 512 pit from odin.
2. Flash Stock JM8 or JM9 (Usually i am flashing JM8 when things get messed)
3. Use update zip and install clockworkmod from it . (you will not have any signature errors because now you have recovery 2e)
4. Sometimes you will have to apply sd card update twice to get to CWM.
5. Vola, now you have working clockworkmod recovery and you can flash whatever the things you want with it

androidsl said:
How about
1. Repartition with a 512 pit from odin.
2. Flash Stock JM8 or JM9 (Usually i am flashing JM8 when things get messed)
3. Use update zip and install clockworkmod from it . (you will not have any signature errors because now you have recovery 2e)
4. Sometimes you will have to apply sd card update twice to get to CWM.
5. Vola, now you have working clockworkmod recovery and you can flash whatever the things you want with it
Click to expand...
Click to collapse
horrible suggestion you both need to search b4 posting.. been posted multiple at least 20 times now.. you DONT need to go install a new rom and blow everything away on your phone just to get 2e recovery so clockwork works.. search search.. there are kernels out there you can flash to get back 2e recovery

lgkahn said:
horrible suggestion you both need to search b4 posting.. been posted multiple at least 20 times now.. you DONT need to go install a new rom and blow everything away on your phone just to get 2e recovery so clockwork works.. search search.. there are kernels out there you can flash to get back 2e recovery
Click to expand...
Click to collapse
Oh yeah. forgot to mention it. there is a post that have a kernel which gives you recovery 2e on JPY firmware. (Don't know other firmwares has it or not)
Anyway, in my case i like to blow everything and start all over when i got messed up. because i don't use my sgs for very precious works. i'm just playing with it
Kudos to the lgkahn for bringing this kernel thing up

lgkahn said:
horrible suggestion you both need to search b4 posting.. been posted multiple at least 20 times now.. you DONT need to go install a new rom and blow everything away on your phone just to get 2e recovery so clockwork works.. search search.. there are kernels out there you can flash to get back 2e recovery
Click to expand...
Click to collapse
I am really a starter..when it comes to all this will be able guide me a little bit please..what exactly do you mean and what do i search for...thanks a lot for all your help...

Okay..seems like this thread is getting nowhere..
Go to the android development section and look for hardcore's speedmod kernel. Download the latest version and flash it via Odin.
Btw, let me give you a tip once you are in hardcore's thread. PLEASE READ THE FIRST 3-4 POSTS AND FOLLOW INSTRUCTIONS.
I don't think you are exerting enough effort to research here in the forum so I just gave you one of the simplest and shortest step to have CWM directly.
Sent from my GT-I9000 using XDA App

is it OK to use Stericssion autosin.bat to sign the update.zip downloaded by CWM and then flash it using recovery 3e? We will not have to flash the CF Kernel.

[SOLVED] Repairing bad flash i9000

[SOLVED] Read on to find out how.
For this to work you must be able to access "Download mode" and make sure that your phone is recognized by the computer.
Here's what happened:
Phone was running CM7.2 and Glitch 13.1 and I wanted Slim ICS 4.2 so what I did was: wipe user data, cache and devik cache then installed Slim ICS 4.2 through CWM and it worked.
But when the phone was trying to do the initial install after it had rebooted from flashing Slim in recovery it just restarts and loops, always about to do the initial install.
Got fed up with this and sort of rage flashed back to stock loosely following THESE instructions, but I didn't follow the instructions like I should have. What I did instead was flash my stock JVC gingerbread firmware (Orange of the UK branded) TAR file as PDA with the 20100512 PIT file in Odin3 1.87. And yes I did check "Repartition" in Odin, because the instructions I had for Hemidall said to have repartition "CHECKED".
This is the result, from 3e recovery.
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: getprop("ro.product.device") == "GT-P1000" ||
getprop("re.build.product") == "GT-P1000" ||
getprop("ro.product.device") == "GT-i9000" ||
getprop("re.build.product") == "GT-i9000"
E:Error in /cache/recovery/sec_csc.zip (Status 7)
Installation aborted.
So then some poo came out... but I thought if I followed the instructions EXACTLY as they were writtin these problems would all go away and I can go back to not crapping myself
I followed the instructions perfectly and I still get the same screen as written above, in 3e recovery.
So now too scared to touch the phone without some brief guidance, can someone please please help as I'd really like to be able to start testing and benchmarking ICS roms.
Thank you again XDA

You can try flashing with my recovery kit, worth trying, just download it, unzip and read the .txt first, pictorial instructions included
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium

Thank you slaphead20
My only question is: What have I done, and why will ezbase recovery kit for gb fix it?
Before trying ezbase (which is downloading now and will take 22 minutes) should I try flashing to stock like I normally would with Odin where by I just flash the one TAR file in PDA? But if you don't think it will help then I wont touch it until recovery kit gets here :/

Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone

mod2max said:
Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone
Click to expand...
Click to collapse
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Sent from my GT-I9300 using xda premium

slaphead20 said:
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Click to expand...
Click to collapse
Well it's 2:00AM Sunday morning here in the UK, got home a few moments ago and had a brainwave "Why not use a virtual machine to install the phone's drivers and test Odin" so I did and it works fine I will flash the recovery kit in the morning (even though it is morning... ) and let you know how it goes.

Thought I'd reinstall the drviers on my PC since it worked on the virtual machine, got Odin back
However, I set up the flash as described in EZOdin and it got to HERE and then it got stuck... been stuck for about 20 minutes now.
In the white "Connection" status box in Odin it says "Set Partition"
Phone is still plugged in, haven't seen any progress bars on the phone or any change in Odin, is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
UPDATE
Ok so got the phone removed, safely I think...
It's gone a bit funny like it did when Hemidall crashed... so no boot logo or kernel splash etc, just a white picture of a phone and dotted line connection to a pc. But I fixed that by flashing again with exact set up from the instructions for Hemidall, it got logos back and recovery etc.
But can still access download mode and and Odin sees the phone, hope is not lost
Is it worth trying to flash the files in normal Odin3? I have version 1.87. It might be a one off crash (like Hemidall's was) but I crap my self when stuff like this happens and would rather it didn't do it again

mod2max said:
is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
Click to expand...
Click to collapse
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again

xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Ahhh that must be what it is, upgrade mode :/
Well I got the phone out and download mode still works and Odin can still see the phone, so I'm pretty safe atm (I think.....) battery has already been removed etc.
But while download mode and Odin work I'm not doing more to the phone now, if I carry on I will actually have heart failure. So I will pick this up again later on this afternoon.

xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Could you please explain what you mean by "using Pit first"? I thought pit files go in it's space in Odin at the same time as flashing everything else (when you use Pits of course).
My current plan is, install the usb drivers on a machine that has never been touched by me, Odin or anything else. So maybe this will determine whether it is EZOdin playing up on the latest version of Windows 7... if it's not either of those then I guess that means I am no longer able to flash PIT files and am screwed.
But I will find out, fingered crossed!
Slaphead20, I've taken the PDA, PHONE and CSC files you gave me and would like to flash them in Odin3. I've stripped the files of their ".md5" extensions and now they are just ".tar" but I was wondering if this would have any bad effects while flashing? Does Odin3 take ".md5" files like EZOdin does? Is it safer to leave the files in their ".md5" format?

How it was solved:
I took the "ezbase recovery kit" that was kindly made available to me from Slaphead20 and unpacked the "PDA", "PHONE" and "CSC" .md5 files, I first removed the ".md5" extensions from the end of each file name and then used WinRAR to unload the contents of each ".tar" folder into a normal uncompressed folder for use with Hemidall.
**I did find that while unpacking these files there was two "cache.rfs" files, they are both the same but we just use one when using Hemidall.**
The reason I used Hemidall instead of EZOdin (which is supplied with the recovery kit) or Odin3 is because firstly when I tried to use the recovery kit in EZOdin, it crashed and I had to unplug the phone unwillingly (that caused "Upgrade mode"). And the reason for not using Odin3 was fear of the same.
The process:
**Make sure your handset has plenty of juice cause the last thing you want is a bad flash and then not being able to charge the batter without an external charger.**
Firstly, get your phone into "Download Mode" with the USB cable unplugged from the computer
Set up Hemidall like so...
**Make sure "Repartition" is checked and "No Reboot" is unchecked for this bit!**
Partition ID______Partitions (Files)
____0___________IBL+PBL = boot.bin
____3___________SBL = Sbl.bin
____6___________KERNEL = zImage
____11__________MODEM = modem.bin
____21__________PARAM = param.lfs
____22__________FACTORYFS = factoryfs.rfs
____23__________DBDATAFS = dbdata.rfs
____24__________CACHE = cache.rfs
After the flash is complete the phone will reboot, the first ever boot of the OS is a long one so just be patent and it will eventually (fingers crossed) load.
Q: What is it doesn't load?
A: Flash the above again until it does, or your doing something wrong -_-"
Once the phone has loaded, shut it down and then go back into "Download Mode" with the USB cable unplugged. Now, with Hemidall select the same pit file as before but make sure that "Repartition" and "No Reboot" are both unchecked, then click "Add" and select "Kernel" for the "Partition Name", browse to the "zImage" file in the "CF -Root for EZbase" folder (or similar). Plug the USB cable into the phone, click "Start" and wait for the phone to reboot, then you will have Root (+ SU) and CWM.
**If any flash you make with Hemidall stalls (fails) after you click "Start" and you have to unplug the phone it will now be stuck in "Upgrade Mode" but get into "Download Mode" and follow this guide from the start.**
Thank you Slaphead20 for this one

hi, thx for such an informative insight here...
there should be a sticky thread for such kind of issues and which would get everyone going in quick !
not sure if mods are listening to this
anyways thanks again
Sent from my GT-I9000 using xda app-developers app

Just as a heads up, all credits to
Nitr8 for the ez components
Chainfire for cf kernel
Samsung for pit file
Link to recovery kit, unzip and read.txt
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium

dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?

banana_plug said:
dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?
Click to expand...
Click to collapse
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium

slaphead20 said:
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?

banana_plug said:
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?
Click to expand...
Click to collapse
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium

slaphead20 said:
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.

banana_plug said:
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.
Click to expand...
Click to collapse
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium

slaphead20 said:
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
yes. you probably understand why im actually posting here. i nearly never post, not because im a techie, im a total noob, its just that im good at research, and i dont like to bother others. but at this point im pretty tired. will go thru the procedure again (third time) and see what happens. ****ing 3e recovery!
p.s correct me, replacing the kernel with CFROOT one from the pack, should automatically flash CWM? if thats the case, i might go and find another kernel with such capabilities, am i on a right path? p.s when i get rich, ill donate to you a beer ;D

[Q] problem reverting to stock rom

i installed emanoN rom v7 a few months and reverting back to stock rom downloaded from samfirmware.com for some reasons
now i again flashed cyanogenmod 10.1 by rohan007(no doubt, its a great rom) :good: about a week ago
but it is too much for my mini to handle that....ram usage is always above 200 mb(why its said that mini has 384 mb ram while we get only 280 )
so i want to revert back to that stock rom which i dowloaded
but when i try to install from sd card-->choose file-->s5570ddkq7_ddkq6_INU
i get something like
e:/s5570_ddkq6_inu
(bad)
Installation aborted
WHY :crying: it worked earlier
PS: i tried from different microSD cards and copied for around 3 times to the microsd card

This will fix your problem (guides aren't mine)
Guide http://forum.xda-developers.com/showthread.php?t=1255305
Another good guide: http://forum.xda-developers.com/showthread.php?t=1551586
To root use "universal gingerbread root v.2.5"
I've tested with XWKTN ROM and all works fine.
Btw, test "chocobread" or "democracy" ROM's. Inmo they are good looking with good performance.

jeremypt said:
This will fix your problem (guides aren't mine)
Guide http://forum.xda-developers.com/showthread.php?t=1255305
Another good guide: http://forum.xda-developers.com/showthread.php?t=1551586
To root use "universal gingerbread root v.2.5"
I've tested with XWKTN ROM and all works fine.
Btw, test "chocobread" or "democracy" ROM's. Inmo they are good looking with good performance.
Click to expand...
Click to collapse
okk i got that...but do i need to download it again? (i am already past usage limit)
i have the file in .zip format which worked earlier through update from sd card in recovery mode

Galaxy_Addict said:
okk i got that...but do i need to download it again? (i am already past usage limit)
i have the file in .zip format which worked earlier through update from sd card in recovery mode
Click to expand...
Click to collapse
Open the ZIP (extract) in your computer. If you have 4 md5 files you need to flash using the 4 files method
If you have only 1 md5 file you need to flash using the 1 file method.
This is how you flash stock firmware, modded is flashed from SDcard using CWM.

jeremypt said:
Open the ZIP (extract) in your computer. If you have 4 md5 files you need to flash using the 4 files method
If you have only 1 md5 file you need to flash using the 1 file method.
This is how you flash stock firmware, modded is flashed from SDcard using CWM.
Click to expand...
Click to collapse
thanks mate for the info...there is a single .md5 file so i tried to flash using odin...but that odin is not detecting my phone
i think that my pc has all the drivers installed in it because i have the latest kies and usb mass storage,and usb tethering are working fine
odin worked when i first flashed my rom (emanoN v7)...but now its not working
any other alternatives please..!!!

you need to put the phone in download mode.
With the phone OFF, hold "volume down" + "power" + "home" untill you see the "download mode" screen.

Galaxy_Addict said:
thanks mate for the info...there is a single .md5 file so i tried to flash using odin...but that odin is not detecting my phone
i think that my pc has all the drivers installed in it because i have the latest kies and usb mass storage,and usb tethering are working fine
odin worked when i first flashed my rom (emanoN v7)...but now its not working
any other alternatives please..!!!
Click to expand...
Click to collapse
Just remove any model name from ops file & then place it in OPS field.
Remember, odin detects ur phone through the ops file..., no matter whether it's physically connected to pc or not (at that instant).
Disable kies b4 Starting.
Sent Via XDA™ Premium

jeremypt said:
you need to put the phone in download mode.
With the phone OFF, hold "volume down" + "power" + "home" untill you see the "download mode" screen.
Click to expand...
Click to collapse
i know that bro...i am not that much of a noob

Galaxy_Rohit said:
Just remove any model name from ops file & then place it in OPS field.
Remember, odin detects ur phone through the ops file..., no matter whether it's physically connected to pc or not (at that instant).
Disable kies b4 Starting.
Sent Via XDA™ Premium
Click to expand...
Click to collapse
so do i need to rename the file from tass.ops to what?

not a noob
how will you flash a tar file with cwm and you said you were successful last time
ops's name must be TASS.ops

dheeraj (dhlalit11) said:
not a noob
how will you flash a tar file with cwm and you said you were successful last time
ops's name must be TASS.ops
Click to expand...
Click to collapse
when did i say that i flashed a tar file using cwm....i flashed the .zip file using cwm
does usb debugging has anything to do with this..?

can you tell which firmware comes in zipped file
either the firmware would be tar or tar. md5
no usb debugging is not related download mode is

dheeraj (dhlalit11) said:
can you tell which firmware comes in zipped file
either the firmware would be tar or tar. md5
no usb debugging is not related download mode is
Click to expand...
Click to collapse
take a look here, they are the original samsung firmwares and they come in zipped files - www.sammobile.com/firmware/
secondly i think i found the problem....in devices and printers- when i connect the phone it automatically shows "MSM7x27" unspecified device
u are missing drivers for it
i troubleshooted the problem and searched and installed many drivers for it but still no luck

when you will open the zip you will see tar files
ok lets be on the topic this means you have not installed tar files
download Kies latest version and install it
close it completely
open Odin and select files
boot mobile into download mode and connect it (do this after opening odin)

dheeraj (dhlalit11) said:
when you will open the zip you will see tar files
ok lets be on the topic this means you have not installed tar files
download Kies latest version and install it
close it completely
open Odin and select files
boot mobile into download mode and connect it (do this after opening odin)
Click to expand...
Click to collapse
already installed latest kies...closed it from task manager
tried doing that...yes there are tar files in the archive
i 'll try doing this on another laptop and let u know if it works

i finally found d problem....it is the msm7x27 missing on my laptop
its bcoz i recently upgraded to windows 8 pro 64 bit...it will work on any other pc running 7
the problem is resolved but still i want those drivers for windows 8 pro x64..if u found them please let me know

[Q] bricked N7000. how to get working again

I tried upgrading my international N7000 to CM10.3 following the instructions in
http://wiki.cyanogenmod.org/w/Install_CM_for_n7000
but now the phone won't even boot into the recovery, all it shows is
Samsung
GALAXY Note
GT-N7000
/ \
/ | \
/--*-\
When i tried flashin from my Mac iusing Heimdall,
the download finished on the mac, but on the N7000
it still showed the blue line etc. I waited a lng time and tried
rebooting, but got the above.
Re-flashing in Heimdall had no effect.
I then tried flashing
hardcore-speedmod-ics-recovery-n7000.tar
using Odin 3.185 from my VMwars Fusion XP install,
and that seemed to finish ok, but no luck either.
I looked for the latest CWM 6.0.4.3 recovery, but I cannot find any
odin-flashable format for it, and of course I cannot use the sdcard
as I cannot even boot into any recovery as is.
Can anyone suggest next steps?

sejtam said:
I tried upgrading my international N7000 to CM10.3 following the instructions in
http://wiki.cyanogenmod.org/w/Install_CM_for_n7000
but now the phone won't even boot into the recovery, all it shows is
Samsung
GALAXY Note
GT-N7000
/ \
/ | \
/--*-\
When i tried flashin from my Mac iusing Heimdall,
the download finished on the mac, but on the N7000
it still showed the blue line etc. I waited a lng time and tried
rebooting, but got the above.
Re-flashing in Heimdall had no effect.
I then tried flashing
hardcore-speedmod-ics-recovery-n7000.tar
using Odin 3.185 from my VMwars Fusion XP install,
and that seemed to finish ok, but no luck either.
I looked for the latest CWM 6.0.4.3 recovery, but I cannot find any
odin-flashable format for it, and of course I cannot use the sdcard
as I cannot even boot into any recovery as is.
Can anyone suggest next steps?
Click to expand...
Click to collapse
1st things 1st. Why would u use heimdall or odin? And what is your current ROM before trying to flash CM 10.3, was it stock? You should have looked for CWM recovery or Philz safe kernels as base when doing ROM flashing ESPECIALLY custom roms. From what you said, then can you still boot into download mode? I have no knowledge of heimdall so just download Stock Firmware, flash it with odin and see if you can boot your N7000 first.
The worst case scenarios is you are experiencing emmc bug-brick. go to the thread and read carefully to deduce your type of 'brick' and find solutions there. Good Luck.

I was on a stock 4.0.4 (but rooted). I originally tried flashing the cwm from the sd card, but after starting to load it it also just hung,
so I looked for an alternative..
I found a post on stockroms (http://forum.xda-developers.com/showthread.php?t=1424997) but the links all point to hotfile.com. which my browser says it cannot find. is hotfile dead? Is there an alternative?

sejtam said:
I was on a stock 4.0.4 (but rooted). I originally tried flashing the cwm from the sd card, but after starting to load it it also just hung,
so I looked for an alternative..
I found a post on stockroms (http://forum.xda-developers.com/showthread.php?t=1424997) but the links all point to hotfile.com. which my browser says it cannot find. is hotfile dead? Is there an alternative?
Click to expand...
Click to collapse
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app

same problem
Jackwu696 said:
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
i have the same problem , only mine loads into the recovery menu , ive tried finding a working odin to nstall it back to factory.
when i had this problem last night , i wasnt sure what i done but i managed to install a custom rom and that worked but now i seem to be getting status 7 error ,
my computer wont recognise my phone so i cant do anything that way . any ideas or links to solutions will be appreciated

i have the same problem

conanbrapp said:
i have the same problem , only mine loads into the recovery menu , ive tried finding a working odin to nstall it back to factory.
when i had this problem last night , i wasnt sure what i done but i managed to install a custom rom and that worked but now i seem to be getting status 7 error ,
my computer wont recognise my phone so i cant do anything that way . any ideas or links to solutions will be appreciated
Click to expand...
Click to collapse
I'm sorry so did u succeed or did you not succeed in installing the custom rom? If your custom rom boots fine then all u need is to search for solving status 7 error thread. My advice to all noobs is to always try n avoid installimg anything except stock rom in odin. Always read and re read before flashing anything that's beyond your knowledge. Basic knowledge of flashing cusroms is :
1. ALWAYS make sure you're on SAFE and COMPATIBLE KERNEL. Most rom threads ALWAYS Include threads/links to a specific recovery/kernel to use. Read n RE READ that.
2. Wipe everything IN RECOVERY mode before flashing a rom.
Sent from my GT-N7000 using XDA Free mobile app

fixed miine
Jackwu696 said:
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
Jackwu696 said:
I'm sorry so did u succeed or did you not succeed in installing the custom rom? If your custom rom boots fine then all u need is to search for solving status 7 error thread. My advice to all noobs is to always try n avoid installimg anything except stock rom in odin. Always read and re read before flashing anything that's beyond your knowledge. Basic knowledge of flashing cusroms is :
1. ALWAYS make sure you're on SAFE and COMPATIBLE KERNEL. Most rom threads ALWAYS Include threads/links to a specific recovery/kernel to use. Read n RE READ that.
2. Wipe everything IN RECOVERY mode before flashing a rom.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
im not Sure what i did , i unbricked (soft) and successfully installed kitkat not sure exactly how but it worked.... still have root too ... had and error about needing to wipe data for suib i think but thats the only fallback i fell into

conanbrapp said:
im not Sure what i did , i unbricked (soft) and successfully installed kitkat not sure exactly how but it worked.... still have root too ... had and error about needing to wipe data for suib i think but thats the only fallback i fell into
Click to expand...
Click to collapse
If you're able to boot up properly n prompted to wipe, then do it. But do it in recovery not on device.

Ok, I downloaded one of the stock kernels for my internatinal N7000, but flashing that with Odin 3.185 hangs about 3/4 through (has now been
sitting there for >60 mins).
Looks like I am screwed?
The file I found is KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5
I f I wanted to try flashing this with Heimdall, I'd need to know partition numbers I think
Where can I get those?
Or should I get another file?

sejtam said:
Ok, I downloaded one of the stock kernels for my internatinal N7000, but flashing that with Odin 3.185 hangs about 3/4 through (has now been
sitting there for >60 mins).
Looks like I am screwed?
The file I found is KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5
I f I wanted to try flashing this with Heimdall, I'd need to know partition numbers I think
Where can I get those?
Or should I get another file?
Click to expand...
Click to collapse
Before that, do u have KIES installed? KIES is NOT compatible with odin and will cause potential trouble. So is some firewall and antivirus apps. You need to disable all of them before using odin. Please search the thread http://www.sammobile.com/firmwares/ for stock rom site.
Sent from my GT-N7000 using XDA Free mobile app

Ok. I downloaded two stock roms from sammobile:
[email protected] 1 mathias staff 808649674 May 9 10:53 N7000XXLT5_N7000MBCLT1_MBC.zip
[email protected] 1 mathias staff 750466356 May 9 10:50 N7000XXLRL_N7000OXELR5_MBC.zip
but both fail with some (unreadable, apparently character set issue) error under ODIN.
I found this:
http://droidangel.blogspot.sg/2012/01/samsung-galaxy-note-gt-n7000-all.html
which shows how to do a full flash , including PIT file, but the links again go to hotfile which seems to be down.
http://hotfile.com/dl/140099962/b9e0d63/Q1-20110914_16GB.pit.rar.html
Where can I get a) separate
CODE_N7000xxxxx_CLxxxxxxx_REVxx_user_low_ship.tar.md5
MODEM_N7000xxxxxx_REV_00_CLxxxxxx.tar.md5
GT-N7000-CSC-MULTI-xxxxxx.tar.md5
and the PIT file?

sejtam said:
Ok. I downloaded two stock roms from sammobile:
[email protected] 1 mathias staff 808649674 May 9 10:53 N7000XXLT5_N7000MBCLT1_MBC.zip
[email protected] 1 mathias staff 750466356 May 9 10:50 N7000XXLRL_N7000OXELR5_MBC.zip
but both fail with some (unreadable, apparently character set issue) error under ODIN.
I found this:
http://droidangel.blogspot.sg/2012/01/samsung-galaxy-note-gt-n7000-all.html
which shows how to do a full flash , including PIT file, but the links again go to hotfile which seems to be down.
http://hotfile.com/dl/140099962/b9e0d63/Q1-20110914_16GB.pit.rar.html
Where can I get a) separate
CODE_N7000xxxxx_CLxxxxxxx_REVxx_user_low_ship.tar.md5
MODEM_N7000xxxxxx_REV_00_CLxxxxxx.tar.md5
GT-N7000-CSC-MULTI-xxxxxx.tar.md5
and the PIT file?
Click to expand...
Click to collapse
Of course you fail... When using ODIN, U should have downloaded the .tar. if you downloaded a zip. then unzip it first to get the tar file, then you flash it with odin. All requests are included in the stock.tar And PLEASE DO NOT Play with PIT files if you don't know what you are doing.
So now what you need to do is. :
1. DISABLE KIES (Uninstall it better), Your firewall, antivirus.
2. Install CORRECT Samsung USB driver. (Search keyword "download samsung N7000 usb drivers")
3. Unzip your zip file and extract the tar.file.
4. Run ODIN as Administrator (Right click/run as)
5. Go to download mode. connect your device to Pc/laptop.
6. Wait until Odin detects your device, click AP/PDA and choose the tar file you extracted.
7. DO NOT tick partition.
8. Let it run

Of course I unzipped the zip to get a SINGLE .tar.md5, but flashing that fails on factoryfs about 3/4 through. consistently.

sejtam said:
Of course I unzipped the zip to get a SINGLE .tar.md5, but flashing that fails on factoryfs about 3/4 through. consistently.
Click to expand...
Click to collapse
Try updating your odin. Use the newest vers. And try and read this https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNGd2e3iG5hkDeo0KyAjGuCSfQSLUw . If All fails then it's a confirmed SUPER-BRICK and there's nothing except samsung service centre can help you now... Sorry for not being able to help more..

Thanks. That led me to
http://forum.xda-developers.com/showthread.php?t=1656635
where I found the PIT file, but for ROMs pointed to http://forum.xda-developers.com/showthread.php?t=1530501
which again points to hotfile and fileserve.com , which (besides being under maintenance) says
FileServe can only be used to download and retrieve files that you have uploaded personally.
which makes it useless for finding ROMs...

sejtam said:
Thanks. That led me to
http://forum.xda-developers.com/showthread.php?t=1656635
where I found the PIT file, but for ROMs pointed to http://forum.xda-developers.com/showthread.php?t=1530501
which again points to hotfile and fileserve.com , which (besides being under maintenance) says
FileServe can only be used to download and retrieve files that you have uploaded personally.
which makes it useless for finding ROMs...
Click to expand...
Click to collapse
His link to ROMS were basically the same ones you can download at sammobile.