[SOLVED] Repairing bad flash i9000 - Galaxy S I9000 Q&A, Help & Troubleshooting

[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

Related

[Q] can't install update.zip?

Hi there,
i was trying to flash my samsung galaxy s and put darky's on it but for some reason i can't.
The recovery screen that pops op says recovery 3e (and every tutorial i found said 2e),
i try to "apply sdcard:update.zip
(i downloaded the update file from the darky roms thread)
and i get the error: failed to verify whole-file signature
signature verification failed, installation aborted.
i've got a samsung galaxy I9000XWJPA.
I've flashed the phone using z4root.
Then i've checked with terminal emulator that it's rooted.
I think that there's a problem with clockwork, or that i just didn't install that correctly, so i'm kinda stuck at the moment :s
could someone please help me?
First of all you should get the busybox file and flash it. Then copy the update.zip into the internal sd card and copy the darky rom too.
Before doing this i would restore it to factory settings. Dont root it with z4root, the busybox roots it and it allows you to open the update.zip
Try what i said and it should work.
Sent from my GT-I9000 using Tapatalk
You are on Android 2.2 which has the 3e recovery. 3e recovery doesn't allow using unsigned .zip files. You should first downgrade your recovery to 2e by flashing CF-root. After you downgrade your recovery, you'll be able to use any update.zip file.
You can find CF-root in this link:
http://forum.xda-developers.com/showthread.php?t=788108
Since you have XWJPA, you should download the JPA version from the second post. Instructions are in the first post.
Make sure you have 3-button recovery and download modes working before flashing.
oh that's via odin3 right?
i'll try that, thanks
Tell us if there's any problem.
Sent from my GT-I9000 using Tapatalk
hmm, i've followed all the steps, downloaded odin, and the CF-Root-XW_XEE_JPA-v1.2-Busybox-1.17.1.tar file, but the download screen only says "downloading, do not turn off target!!!
is there any particular setting or where to place the .tar file?
mavu said:
hmm, i've followed all the steps, downloaded odin, and the CF-Root-XW_XEE_JPA-v1.2-Busybox-1.17.1.tar file, but the download screen only says "downloading, do not turn off target!!!
is there any particular setting or where to place the .tar file?
Click to expand...
Click to collapse
Ok.
First of all disconnect the galaxy from the pc. Close odin. Open Odin, put in PDA CF-Root-XW_XEE_JPA-v1.2-Busybox-1.17.1.tar
Then shut down the galaxy. Reboot it again to download mode. Connect it via usb and then click start. Make sure re-partition isn't checked.
That's it. When setting up odin you can't have the galaxy connected to he computer. If something fails on download mode, you must always restart the download mode or it'll be stuck.
Good luck
aha, found the problem:
there doesn't appear a comport in odin
new problem, how do i get the phone recognized?
mavu said:
aha, found the problem:
there doesn't appear a comport in odin
new problem, how do i get the phone recognized?
Click to expand...
Click to collapse
It should recognize it when you connect it in download mode...
Mine recognizes it as COM4.
This may be simple, but restart your computer and phone and see if it works.
mavu said:
aha, found the problem:
there doesn't appear a comport in odin
new problem, how do i get the phone recognized?
Click to expand...
Click to collapse
It should recognize it when you connect it in download mode...
Mine recognizes it as COM4.
This may be simple, but restart your computer and phone and see if it works.
If not, re-install the drivers for your phone
hi mate i had exactly the same problems as you and it done my head in for about a day and a half but then someone gave me this advice and it worked a treat,
go to market
download sgs kernel
once done flash speedmod kernel using the app
re start phone
once done download darkys rom
reboot to download mode (should now have 2e)
flash zip
choose zip
find darkys
click yes instal darkys
job done
one thing i must point out in 2e is the back button on your phone is now the select button and the menu button on the bottom left is now your back button
hope this helps as it did for me
Restart your pc and make sure Kies is not working at all.
thanks man! reinstalling the drivers did the trick ten points for coldflid!!!
steve57925 said:
go to market
download sgs kernel
once done flash speedmod kernel using the app
re start phone
once done download darkys rom
reboot to download mode (should now have 2e)
flash zip
choose zip
find darkys
click yes instal darkys
job done
Click to expand...
Click to collapse
For the record, people do NOT have to flash Darkys or any other custom ROM to get 2e. Simply flashing a kernel that has Clockwork Recovery included will do the trick. Your reco to flash SpeedMod would have solved the problem without having to go further.
Very true but he wanted darkys which was the only reason I mentioned but good to point out for others reading the post
Sent from my GT-I9000 using XDA App
mavu said:
thanks man! reinstalling the drivers did the trick ten points for coldflid!!!
Click to expand...
Click to collapse
Im happy ir worked =]
Sent from my GT-I9000 using Tapatalk
steve57925 said:
Very true but he wanted darkys which was the only reason I mentioned but good to point out for others reading the post
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You're 100% correct - my mistake for missing it on the first go-around.
not a problem
Hello ,
I have a similar problem with my Galaxy S I9000 .
I've updated it via KIES to the latest Froyo ( 2.2 as it shows my phone ) .
Next , I tried to install the voodoo lagfix .
I downloaded the .zip file and renamed it to "update.zip" .
Then I copied it to my phone's sd card ( I connect to PC via usb and copied in the 'Phone' folder ) .
Next , I used the 3 buttons ( Volume UP + middle button + turn off button ) and it got into Recovery mode .
I selected the 'update.zip' file and accesed it , but it says :
"E: signature verification failed, installation aborted."
I have to downgrade to 2E first ?

[Q] Odin help

Hey guys... ok i have been looking and cant seem to find how to rectify this issue... i am really stuck and would appreciate any help possible..
Ok so i had stock 2.2 on my captivate, n tried to install a gingerbread rom using mobiletechvideos easy step guide using this link
http://www.youtube.com/watch?v=UOyx5JQ_8_I
... in doing that the first step of installing the bootloaders through odin, i inserted the pda files but it freezes at setup connection... now i think its soft bricked as i can still put it in download mode.. the thing is i have tried one click odin to revert back to 2.1 or 2.2 but it stops at set pit file... and then do not turn off target... its been here for over 25 mins n nothing... i have kept trying a couple of times and sometimes it wud just say fail.. Guys again i am sorry if this in the wrong place or has been brought up before.. i tried looking and was not able to find anything..
Thanks
Well your first issue there he says flash to stock 2.1 jf6 you where on 2.2 Unless your phone is a newer build 2.1 is always better to flash then 2.2. What build is your phone?
Reboot your computer, swap usb ports to one that is in the back attached to the motherboard (if already back there swap to a different one in the back) or port #1 on a laptop. Right click odin and run as administrator.
Thanks for the responses..
Yeah i know it said do it on 2.1, i figured it cud have worked on 2.2 i guess i was wrong... n in terms of switching port, odin still recognizes the port as i get the yellow screen but it doesn't move from there...???
It doesn't matter what's on the phone 2.1, or 2.2. **** you can be in a custom rom (I made the jump from firefly). If you are using odin its the same, if it will write 2.1 over anything why wouldn't do it for 2.3.3? No Difference.. The only way 2.2 would matter is if you weren't using odin then you would have to get around 3e recovery. But download mode is underneath the firmware does not matter what is on it odin will overwrite it.
And odin can be super touchy with the usb ports. And although it sees it the flash fails if odin is on the rag and didn't take any midol.
studacris said:
It doesn't matter what's on the phone 2.1, or 2.2. **** you can be in a custom rom (I made the jump from firefly). If you are using odin its the same, if it will write 2.1 over anything why wouldn't do it for 2.3.3? No Difference.. The only way 2.2 would matter is if you weren't using odin then you would have to get around 3e recovery. But download mode is underneath the firmware does not matter what is on it odin will overwrite it.
And odin can be super touchy with the usb ports. And although it sees it the flash fails if odin is on the rag and didn't take any midol.
Click to expand...
Click to collapse
again thanks for your help studacris... so basically if odin can read it but nothing happens i am screwed... i really need to know if there is absolutely anything else i can do to fix this as this is my only means of communication.. i am lost without my cappy...
Are you sure you are using a Motherboard usb port and that you are running on Admin? If odin is being stupid you can look in to Heimdall
prbassplayer said:
Are you sure you are using a Motherboard usb port and that you are running on Admin? If odin is being stupid you can look in to Heimdall
Click to expand...
Click to collapse
yeah i am sure i am using it on the motherboard port and running it on admin.. It basically freezes on differnt areas and doesnt completely reflash to stock on odin3 one-click downloader...
So there is nothing else i cud do with odin rite??
rheanjd said:
yeah i am sure i am using it on the motherboard port and running it on admin.. It basically freezes on differnt areas and doesnt completely reflash to stock on odin3 one-click downloader...
So there is nothing else i cud do with odin rite??
Click to expand...
Click to collapse
Try a different version of odin. If that dont work then use Heimdall
You can go to samfirmware.com-US SGS download wich ever version u want (id use JF6) download and decompress. Each .md5 file you need to decompress as well and get out the individual file in them. Here is a good how too with heimdall from mobiltechvideos. Hope this helps
prbassplayer said:
You can go to samfirmware.com-US SGS download wich ever version u want (id use JF6) download and decompress. Each .md5 file you need to decompress as well and get out the individual file in them. Here is a good how too with heimdall from mobiltechvideos. Hope this helps
Click to expand...
Click to collapse
Thanks.. i was hoping odin wud have come through but i guess i will have to try heimdall...
Ok guys i have downloaded heimdall and right now trying to install the jf6 2.1 rom... the thing is i am on load package and tyring to put the firmware package... this might be a stupid question but i am inserting the zipped file but it keeps saying - Tar header contained an invalid file size... Do i need to extract the files and then do this..???
rheanjd said:
Ok guys i have downloaded heimdall and right now trying to install the jf6 2.1 rom... the thing is i am on load package and tyring to put the firmware package... this might be a stupid question but i am inserting the zipped file but it keeps saying - Tar header contained an invalid file size... Do i need to extract the files and then do this..???
Click to expand...
Click to collapse
Wich Heimdall you using? I suggest 1.1.1 in wich you choose each file u want to flash individually.
i had downlaoded 1.3.0 will try this thanks..
ok so i have inserted factory fs, kernel,param,cache,database data,modem and clicked start, it took two seconds and then stated failed to retrieve config descriptor...??
also i haven't added anything in the pit or primary and secondary and recovery files
rheanjd said:
ok so i have inserted factory fs, kernel,param,cache,database data,modem and clicked start, it took two seconds and then stated failed to retrieve config descriptor...??
also i haven't added anything in the pit or primary and secondary and recovery files
Click to expand...
Click to collapse
Im not sure about your error but the Jf6 from samfirmware has FactoryFS, Param.lfs, Cache, Database Data, Modem and Recovery(Zimage). Maybe you put a file in the wrong place?
Thanks but istn't the zimage supposed to be for the kernel... i haven't inserted anything into the recovery field...
i am rite now left clueless
No your right. Its the kernel I had a brain fart. Well I honestly Do not know whats wrong, Im assuming you ran Heimdall as Admin... Well **** man any way you have access to another machine? Im out of ideas maybe someone else can help. =/
Hey thanks i really appreciate the help ...
guys if anyone else can help me out it would be really appreciated... the phone is all i got and i really need it to work today... i am just restarting my computer and will try again hopefully it will work otherwise i am out of options...
Ok restarted and giving the same issue...
"Failed to retrieve config descriptor"
what the hell is that???

[Q] ODIN - Check image files !! Works for others though...

So I've downloaded the following kernels from a link here on XDA that should be swapping kernels to allow me root on my recently upgraded, stock ROGERS 2.3.3 Captivate. Odin is telling me to "Check image files !!" when I load the .tar files into the Select Intergrated Package (and yes, the one package switch is on). I opened the tar to double check it wasn't double-compressed.
What else would be giving me this problem? I'm using Odin 4.28. Curiously, it is showing my phone as detected, my phone IS in downloading mode, but Odin just says (Android) in the Title, no specific model. But it says it's found it on COM 6. <1> Added!! and Detected!!
It's when I load up the kernel tar's and try to start that it yells at me. Is this triggering anything in anyone's mind that I'm doing wrong? Or do I need to provide more info?
I am using Vista 32-bit (legit) on a Dell studioXPS. And I ran it as administrator.
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Pirateghost said:
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Click to expand...
Click to collapse
Yeah. That is def the wrong version of Odin. Download the i9000 bootloaders in my sig. Unzip it. Delete the pda.tar.md5 file. Use the included version of Odin (1.82 I think) to flash your kernel.
Alright, quick question - I accidentally flashed the phone, not the pda. I tried to flash the KH2 modem back via phone but ODIN failed. Kies is currently not detecting the phone, and so I decided to try flashing the PDA while I had it open and I would figure the modem out after. ODIN hung, so I closed it and rebooted out of downloading mode and got the Phone ! Computer error. So I figure now I have to flash back to the stock rom and start over again, but this time I would like some advice as to which step to take next. I downloaded I896UXKH2-HOMEBINARY.tar.md5 from another thread here. Can I flash this with Odin - and if so, which is the place to load it? Bootloader? PDA? Phone? CSC? I have no PIT files.
Think it goes into the pda slot. Go back to the thread t you got it from and read the first post of the thread. Also restart your computer before trying to flash again.
can someone upload the modem.zip, please thank you

[Q] newbie - HELP PLS - bricked?

Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
strangermyself said:
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
First you should t have flash abyss through odin since now you are not rooted and do t have the warranty too, the counter of flashes increased to 1 (look at the download mode small text), for rooting you can use chainfire's tool (in the cf-root kernel thread look for it in devolepment section) next get a stock rooted kernel and flash using the tool (read instructions).
For now use pc odin 1.87 and get a firmware 2.3.6 use the pc odin select the file on PDA and flash it, make sure phone is charged 100% and press start, if it doesn't work then uninstall drivers, reboot machine, reinstall them and kill kies process if present in task manager and then goto download mode connect USB and open pc odin wait for the port to be ready aka green and select file then start.... you should be fine its a soft brick afterall.
Sent from my GT-N7000 using Tapatalk 2
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
strangermyself said:
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
Click to expand...
Click to collapse
When connected to charger make sure phone is off the battery meter will show as soon as you connect, case it doesnt leave it for like 3 hours is fine... next about that ROM redownload. The package cleanup you temp directories in PC and try again if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
... if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
strangermyself said:
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Whiskeyjack4855 said:
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
Dude its a GB rom not superbrick bug in it and he didn't mention LPY yet.
Sent from my GT-N7000 using Tapatalk 2
strangermyself said:
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
Click to expand...
Click to collapse
Sorry for tea doubled post its a dumb app X's
You wipe using the CWM file in the Iss root section, and a normal recovery wipe would do too (aka restore defaults)
Sent from my GT-N7000 using Tapatalk 2
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
strangermyself said:
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
Click to expand...
Click to collapse
If you have the stock recovery, restore default wipes everything.
If you have stock re every and want CWM temporary just to wipe goto n7000 devolepment and check how to root by dr.ketan and get files there
If you have CWM then wipe data, wipe cache, wipe dalvik.... and try. Old download another firmware like kk5.... something else not the new LC1 LX1 releases.... (Latest GB) get an old one to get root easly
Sent from my GT-N7000 using Tapatalk 2

[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.

Categories

Resources