Related
Model GT-19000
Firmware 2.2
Baseband I9000DDJP2
Kernel 2.6.32.9 root at SE-S605 # 1
Build Froyo.DDJP6
Rooted phone with z4 root.
Unable to install custom roms/backup current rom using ROM Manager
It kept saying signature verification failed in recovery mode when i tried to use update.zip
I understand that it is due to 3e recovery on my phone
So I tried CF-Root: (download mode and pda flash)
CF-Root-JP6-v1.2-Busybox-1.17.1
CF-Root-JP6-v1.2-Busybox-1.15.3
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1
None of them worked. Got All threads completed (0 succeed/1 failed) everytime.
I just want to install custom rom.
This is beyond frustration.
First the lagging Eclair and Froyo and this.
Plus I had to write this post twice cos this site thought that there is an email link somewhere.
Please Help. Anyone?
What do I need to do to get a custom rom.
Best thing to do to be sure it works fine is update to 2.2.1 JPY using the reg hack.
Flash speedmod kernel with CWM built into it via Odin.
Flash custom rom such as Darkyy rom via CWM recovery.
I will be posting some video tutorials later tonight in the development section showing how to flash etc.
Good luck
Trueblue.08 said:
Model GT-19000
Firmware 2.2
Baseband I9000DDJP2
Kernel 2.6.32.9 root at SE-S605 # 1
Build Froyo.DDJP6
Rooted phone with z4 root.
Unable to install custom roms/backup current rom using ROM Manager
It kept saying signature verification failed in recovery mode when i tried to use update.zip
I understand that it is due to 3e recovery on my phone
So I tried CF-Root: (download mode and pda flash)
CF-Root-JP6-v1.2-Busybox-1.17.1
CF-Root-JP6-v1.2-Busybox-1.15.3
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1
None of them worked. Got All threads completed (0 succeed/1 failed) everytime.
I just want to install custom rom.
This is beyond frustration.
First the lagging Eclair and Froyo and this.
Plus I had to write this post twice cos this site thought that there is an email link somewhere.
Please Help. Anyone?
What do I need to do to get a custom rom.
Click to expand...
Click to collapse
I think you should try to flash the latest Hardcore's Speedmod kernel with Odin (PDA + repartition unticked). It comes with CWM Recovery.
What version of Odin do you have? And it said "Added" when you plugged in the phone?
thanks zolah and rytkonen.
So I am installing speedmod-kernel-k13a-500hz.zip via ODIN (PDA).
Lets see if this sorts it out and enables me to install darky's/doc's magic rom
i have Odin3 v1.3. Yeah it mentions added and removed and the works.
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get.
I'll do the reg hack thing too now, I suppose. Whatever is that missing piece!! (aargh!)
Trueblue.08 said:
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get.
I'll do the reg hack thing too now, I suppose. Whatever is that missing piece!! (aargh!)
Click to expand...
Click to collapse
Have you tried different usb-port already? And you have the latest kies installed and not any kies processes active when using Odin? There seems to be some kind of problem with the connection to PC.
e. You also might want to try the Odin 1.7 (exe says Odin3 v1.7).
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> zImage
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
I killed all the Kies applications and got this.
And guess what my phone now has a black screen with the phone connected to a computer with a yellow exclamation mark in the middle.
All hands to the deck!!
Please tell me this is not the end and I have not bricked my phone. I cant go into recovery. Am I screwed?
Trueblue.08 said:
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> zImage
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
I killed all the Kies applications and got this.
And guess what my phone now has a black screen with the phone connected to a computer with a yellow exclamation mark in the middle.
All hands to the deck!!
Please tell me this is not the end and I have not bricked my phone. I cant go into recovery. Am I screwed?
Click to expand...
Click to collapse
This phone is relatively hard to brick for real. Pull out the battery for few minutes and try to boot to download mode. What did you try to flash? Did you try different usb port?
Did you try flashing through these steps:
1. Kill all Kies processes
2. Open Odin
3. Select the tar to pda section and make sure re-partition is unticked
4. Boot to download
5. Connect phone through usb
6. Flash
?
ok i figured that orange triangle out and my phone is working again.
Also I was able to install speemod kernel.
It now reads 2.6.32.9 [email protected] #32
However it still is 3e Android system recovery which means I am still not able to backup my rom install a new rom. - Same thing
E:failed to verify whole-file signature
E:signature verification failed.
EDIT: yeah, i followed the exact same steps. so after the orange screen i was lucky to go to download mode and did the odin install again. This time it worked. That's great, but the initial problem still remains - 2e recovery and custom rom
Trueblue.08 said:
ok i figured that orange triangle out and my phone is working again.
Also I was able to install speemod kernel.
It now reads 2.6.32.9 [email protected] #32
However it still is 3e Android system recovery which means I am still not able to backup my rom install a new rom. - Same thing
E:failed to verify whole-file signature
E:signature verification failed.
EDIT: yeah, i followed the exact same steps. so after the orange screen i was lucky to go to download mode and did the odin install again. This time it worked. That's great, but the initial problem still remains - 2e recovery and custom rom
Click to expand...
Click to collapse
Great, you are already a huge step closer to a custom rom.
Are you sure you were rooted before flashing? Something strange is still happening because I restored my phone to it's out-of-the-box state few days ago and I can confirm that you get the CWM when you flash succesfully the Speedmod kernel.
Rytkonen said:
Have you tried different usb-port already? And you have the latest kies installed and not any kies processes active when using Odin? There seems to be some kind of problem with the connection to PC.
e. You also might want to try the Odin 1.7 (exe says Odin3 v1.7).
Click to expand...
Click to collapse
I think this was the reason, I wasn't able to get it flashed. My Kies processes were on at the time. Now I redid the CF-Root after my success with the speedmod (again the kies processes were killed this time) and now I have 2e Android System Recovery.
Thanks again, mate. Super advice
Yeah, it is rooted all right. The second time around, it is actually creating a backup. So I just have to save the CWM folder on my computer and then I can add new custom roms right?
Thanks for the patience btw.
Trueblue.08 said:
Yeah, it is rooted all right. The second time around, it is actually creating a backup. So I just have to save the CWM folder on my computer and then I can add new custom roms right?
Thanks for the patience btw.
Click to expand...
Click to collapse
Are you speaking of Nandroid backup? You can save it on your computer but I think it is not very recommended to restore a nandroid backup. If you get your phone to a state that it wont boot (but Download mode is working) you can always just flash a new rom with Odin. Now when you got it working.
With CWM you can flash custom roms and kernels easily from recovery. Just remember to read the developer's instructions carefully before flashing.
e. I think this is an excellent thread to keep in mind when you want to flash back to stock or make a clean start (or in case of "brick"): http://forum.xda-developers.com/showthread.php?t=818556
Trueblue.08 said:
ok i figured that orange triangle out and my phone is working again.
Also I was able to install speemod kernel.
It now reads 2.6.32.9 [email protected] #32
However it still is 3e Android system recovery which means I am still not able to backup my rom install a new rom. - Same thing
E:failed to verify whole-file signature
E:signature verification failed.
EDIT: yeah, i followed the exact same steps. so after the orange screen i was lucky to go to download mode and did the odin install again. This time it worked. That's great, but the initial problem still remains - 2e recovery and custom rom
Click to expand...
Click to collapse
Do you have Rom manager app installed?
If you do then delete the app and boot into recovery mode again and see if you have CWM recovery.
[Q][i9000][MOD][GB] - How do I root stock DXJV9
How can I root my i9000 on 2.3.3?
Model number
GT-I9000
Firmware version
2.3.3
Baseband version
I9000DXJV9
PDA: I9000DXJV9
PHONE: I9000DXJV9
CSC: I9000OLBJV9
Kernel version
2.6.35.7-I9000DXJV9-CL216763
[email protected] #2
Build numer
GINGERBREAD.DXJV9
Bought in Thailand last year and updated via Kies only with the official updates.
I have been searching and reading for over a day (admin check my IP in the webserver logs if you like) to find out how I can root my Samsung Galaxy S i9000 International,
ideally keeeping my settings, launcher, homescreens, SMS, apps ... without having to restore backups ..
I am happy with keeping close to stock.
I backed up apps, sms, callhistory, kies backups just to be safe
Both 3-button combos are working
I came across SuperOneClick but it didn't work, it's not supposed to work on 2.3.3 Gingerbread
Then in severeal threads where ppl specifically asked about DXJV9, the FuguRoot Mod was suggested.
A question remains:
- there is no stock kernel listed for DXJV9 but the instructions say you have to flash with it afterwards, where would I find it
There are some kernel files listed in this guide but none of them for DXJV9.
Also I would be unsure if I need to extract the zImage-root.tar before specifying it in odin, inside is a file called zImage without file extention. Another guide said the .tar needs to be extracted first.
Are there any other ways to achieve this, all I want is root. Any tips appreciated!
I would use the latest Speedmod kernal to get root. I base this on my experience flashing the Chebon ROM which is a good rom for Asia. Basically, second step in Chebon is to flash speedmod latest version. This will give you root.
update: found the original kernel, bricked phone
I finally found a post with the original kernels by Ramad.
In another video guide I established that I don't have to extract the zImage-root.tar file before adding it to the PDA section of odin.
I followed the exact steps to flash the FuguMod Kernel and it worked fine:
odin3 v1.82
PDA: zImage-root.tar (the FuguRoot MOD)
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> zImage
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Removed!!
<ID:0/012> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Then everything fine, red fish, battery symbol appeas, I enter download mode again, ok
Then extracted the original kernel for my version
Kernel_DXJV9.tar (5600 KB)
closed odin, disconnected phone, opened odin again, connected phone, comms established, so I select the Kernel_DXJV9.tar , but then:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> zImage
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now can't be turned on. Brick at this stage.
Disappointed because of all the long hours researching for a safe method just to get root ...
Again I would appreciate any help on how to proceed.
I already tried to re-download and re-extract the original kernel, same result, odin fails.
update: worked!!
Update 2:
I kept trying two more times to flash the original kernel file from Ramad, Kernel_DXJV9.tar, with odin,
because I read somewhere that "odin is not the most reliable piece of software".
Eventually it worked, even though I did everything exactly the same way.
So my advice if anyone gets the fail message with odin, keep trying, even another 3, 4, 5 times ...
Redownload the file, reextract, re-open odin, re-connect the phone in download mode, re-flash, if it fails, try again ... odd as it is ...
So now I can see the SuperUser app
I can't see BusyBox, but I am checking on the market now.
update 3: Kies can't detect my phone anymore
update 3: Kies can't detect my phone anymore
Error
Reconnect the device in Samsung Kies (PC Studio)
mode. Current connection mode not supported by Kies
Click to expand...
Click to collapse
Just like some other people on the thread report, Kies no longer detects my phone, but the files
/system/bin/drexe
and
/system/bin/npsmobex
are there, they aren't missing if I look with Astro File Manager.
So I thought I need a file manager that can modify permissions, and I downloaded a couple of them, they mount /system as rw .. and then I can not not see those two files anymore, it's so strange.
If I open ASTRO I can see those two files but ASTRO can't change permissions.
I have yet to figure out how I can get into a command shell / terminal to modify the permissions with chmod on the command line.
I downloaded the BusyBox App from the market.
update 4: Kies connection problem not solved
update 4: Kies connection problem not solved
I used a root file manager to copy those 2 files from the FuguRoot thread to their location:
/system/bin/drexe
and
/system/bin/npsmobex
The permissions were fine.
I made sure to be on TwLauncher when connecting,
I also disabled USB debug mode
but Kies still keeps trying to connect to my phone, no luck ....
Since you have backups and the system is unstable I would just go back to stock.
The stock dxjv9 rom is found here:
[Firmwares]Stock I9000 and I9000M Firmwares collection [Latest: XWJVN, DDJV9, XWJVK] - http://forum.xda-developers.com/showthread.php?t=1102881
The instructions are pretty good and have used it to downgrade to JVQ 2.3.4 to DXJV9 2.3.3 to try out the Chebon Rom as mentioned (JVQ was a bit unstable for me but now JVR).
I've not tried the FuguRoot but I know Speedmod works.
Sorry URL got truncated but search the title. It is in the General section.
I'm happy that I finally have root, but I probably need to go back to stock when I want to sync with Kies again.
If I want to go back to stock, do I only need to flash the PDA part, or everything including Modem, .pit ?
I had a look at the link and seems like there are some special instructions. I haven't tried connecting this to Kies though so can't comment on that.
---
DXJV9/DXJV9/OLBJV9/Sbl (MultiCSC): Download (158.1 MB) (Build date: Wed May 18 19:32:07 KST 2011)
(MultiCSC: CCM, DGI, GLB, KOR, MIS, MM1, SIN, SMA, STH, THL, UMB, XEV, XME, XSE, XSO, XSP, XTC, XTE, XXV)
Special for DXJV9:
1. Flash with re-partition using 513.pit.
2. You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
3. Let the device boot all the way then turn it off.
4. Re-enter Download Mode and re-flash only the CSC file without pit and without re-partition.
5. Enjoy
update 5: back to stock
Zhousibo said:
I had a look at the link and seems like there are some special instructions. I haven't tried connecting this to Kies though so can't comment on that.
---
DXJV9/DXJV9/OLBJV9/Sbl (MultiCSC): Download (158.1 MB) (Build date: Wed May 18 19:32:07 KST 2011)
(MultiCSC: CCM, DGI, GLB, KOR, MIS, MM1, SIN, SMA, STH, THL, UMB, XEV, XME, XSE, XSO, XSP, XTC, XTE, XXV)
Special for DXJV9:
1. Flash with re-partition using 513.pit.
2. You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
3. Let the device boot all the way then turn it off.
4. Re-enter Download Mode and re-flash only the CSC file without pit and without re-partition.
5. Enjoy
Click to expand...
Click to collapse
I have followed these instructions now to go back to stock. All worked well.
I want to try getting root another way, I prefer to have root and still be able to use Kies, I could not get Kies to work with the fuguroot Mod. It was nice to have root though without having to do a complete wipe and data restore.
Next I'll try the suggested method with Speedmod.
Speedmod Kernel and Chebon Rom, the solution for DXJV9
Speedmod Kernel and Chebon Rom are a good solution for having root on DXJV9. It's running well and I can use Kies again.
Thanks to the apps Titanium Backup, "SMS Backup&Restore" and "Backup Call History" flashing everything did not cause much of a headache.
Good to hear. I always thought upgrading the kernel would prevent you from upgrading through Kies. I don't think it makes a big difference as once you start flashing though, not much incentive to go back. Beware, can be addictive trying new roms
can you teach me how you rooted ur galaxy s with dxjv9?
For me, the simplest option was to install SpeedMod kernel (check the Development forums and do a search for SpeedMod). Also check CF-Root. Follow the instructions and your should be good.
MrWil said:
Speedmod Kernel and Chebon Rom are a good solution for having root on DXJV9. It's running well and I can use Kies again.
Thanks to the apps Titanium Backup, "SMS Backup&Restore" and "Backup Call History" flashing everything did not cause much of a headache.
Click to expand...
Click to collapse
Sorry to bother! How can i find Speedmod Kernel, Chebon Rom and its instruction?
Search the Dev forums for Chebon and Speedmod. Should come up pretty quick.
Sent from my GT-I9000 using XDA Premium App
So did any of that process delete anything, because i just want to back up everything and then go to Darkyys ROM. And restore primarily contact data with all links intact.
Thanks
There are options for No-wipe but the cleanest method is usually a wipe.
Most ROM flashes will typically wipe your data which usually means wiping settings and applications (the SD card is usually not wiped). Contacts and stuff synced to Google are typically stored with your Google account (just make sure you have synced).
Titanium Backup is a good option to keep backups but is not free. I think there are others if you search.
Most likely you will have to wipe if going to Darky (but once on Darky's then No-wipe options are very good and you don't lose settings, etc.)
Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
max-thamer said:
Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
Click to expand...
Click to collapse
I too am facing the same situation. Hope someone comes up with a solution.
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
max-thamer said:
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
Click to expand...
Click to collapse
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
MR.change said:
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
Click to expand...
Click to collapse
my phone was ok on rocketrom and it was booting ok until i tried to install a rom using PC odin
and i uninstalled kies completly to avoid any problems
i even tried odin 3 and still no luck
i will try odin 1.87 and reply back
MR.change said:
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
Click to expand...
Click to collapse
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
just tried PC odin 1.87 and no diffrence
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
i tried to install the drivers again but it said the drivers are already installed
i think i will try another pc
max-thamer said:
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
Click to expand...
Click to collapse
yes speedmod is safe ,you have nothing to worry about a brick.
now there could be many things that effect a flash:
1.bad cable
2.running as a standard account (select run as administrator)
3.wrong set of drivers ,to resolve download and install the latest KIES ,then kill it's processes.
4.wrong ODIN version (1.87 recommended)
5.as a last resort you shold flash a pit file (but that's risky)
anyway go to this thread and download ODIN from there and flash a GB ROM
http://forum.xda-developers.com/showthread.php?t=1424997
note that the drivers are included in this thread if you do not wish to install KIES again.
just follow this guide to the letter and you should be fine.
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
max-thamer said:
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
Click to expand...
Click to collapse
If you can have it covered under warranty somehow, then try to seek help from SS service. Otherwise, the method in the thread below could be useful.
http://forum.xda-developers.com/showthread.php?t=1661590&page=2
cheers,
i think i will take to samsung service
thank you guys for helping
max-thamer said:
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
Click to expand...
Click to collapse
the risks could involve a permanent brick (not even download mod) , can you post exactly what ODIN says?
post ODIN log please
EDIT: maybe by any chance that you flashed an ICS bootloader? if so then it maybe the cause for this ,you should try to flash the official LPf using ODIN ,and if it works and the phone boots then flash Speedmod ics kernel on top of it (before wiping or anything).
here I found this pit file on the internet ,you need to choose your model (16gb or 32 gb) ,it's most likely 16gb ,right?
remember this is a last resort ,so don't use it
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
Click to expand...
Click to collapse
if you still have warranty then by all means ,take it to the service center.
if you don't however then you should not give up this easily ,unless you have some cash lying around and you wish to give it to them.
either ways it's your call
good luck
max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
Click to expand...
Click to collapse
weird ,it's failing to flash at factoryfs ,but it's not getting stuck during the operation.
I want you to try two things:
1.try to flash just a kernel ,try this http://forum.xda-developers.com/attachment.php?attachmentid=1068654&d=1337346991
this is the cm9 safe kernel ,if the flash with ODIN goes successful then you can boot into recovery and try to fire a nandroid restore from there
be careful flashing this with ODIN will give you a triangle and count ,so if you still have your warranty ,try to find and flash a stock kernel (which will not give you a triangle).
2.if none of the above works ,then select only the 16 GB pit file and flash it alone ,do not interrupt a pit file flash ,let it take as long as it wants . if you interrupt it then your phone is gone.
after that flash a full GB ROM with removing .pit and unticking repartition.
but I haven't done this before so if you want to go through with it I suggest you wait for someone with actual experience at this.
pit file
Here you go with 16 GB pit file
Hey guys. I have a peculiar problem with my friends Galaxy S. Yesterday, I tries to flash a Jelly Bean ROM from the forums. Straight from Gingerbread, I followed all the instructions to the line and finished flashing.
But sadly, the phone got stuck in a bootloop and is not booting right now. The three button combos aren't working - both download and recovery mode and I was pissed. Thankfully, I had a JIG with me (one I use with my Galaxy Note) and got my phone into download mode.
The problem now is that whenever I try to flash a stock ROM, it gets stuck at the boot.ini file and Odin says "Complete (Write) process failed". The phone (from inside downloaded mode) shows the text "Invalid Bootloader !!!" on the top.
I realize this is fixable but I just don't know what file to flash I am used to the Galaxy Note and the naming conventions and forum posts aren't quite clear to me. Can someone tell me what file I should be flashing to get the bootloader working again?
Thanks in advance!
Sent from my GT-N7000 using xda premium
gramessh said:
Can someone tell me what file I should be flashing to get the bootloader working again?
Click to expand...
Click to collapse
you can use any recovery kit from the My Androids Collections link below
I used the following recovery kit:
i9000 EzBase Rescue with CF Root & semaphore root repacked by slaphead20
No luck. Still the same error. Am I doing something wrong?
gramessh said:
I used the following recovery kit:
i9000 EzBase Rescue with CF Root & semaphore root repacked by slaphead20
No luck. Still the same error. Am I doing something wrong?
Click to expand...
Click to collapse
First remove battery, EXT SD card and SIM Card, press power for a few mins before reinserting battery to try
use the rescue kit with boot loader using heimdall or you can use those files with Odin too
recovery kit with bootloader? I am not sure which one that is. I can see a lot posted. I tried the Darky thing too and it failed.
Could you please provide me with a link?
gramessh said:
recovery kit with bootloader? I am not sure which one that is. I can see a lot posted. I tried the Darky thing too and it failed.
Could you please provide me with a link?
Click to expand...
Click to collapse
its i9000 Rescue Kit for i9000 using heimdall packed by ldq, it has its own bat.exe to do it automatically from PC, but you can also use the files on Odin or on linux, for linux , the configuration will be
primary boot > boot.bin
secondary boot > Sbl.bin
repartition > s1_odin_20100512.pit
factoryfs > factoryfs.rfs
cache > cache.rfs
dbdata > dbdata.rfs
param > param.lfs
modem > modem.bin
kernel > zImage
xsenman said:
its i9000 Rescue Kit for i9000 using heimdall packed by ldq, it has its own bat.exe to do it automatically from PC, but you can also use the files on Odin or on linux, for linux , the configuration will be
primary boot > boot.bin
secondary boot > Sbl.bin
repartition > s1_odin_20100512.pit
factoryfs > factoryfs.rfs
cache > cache.rfs
dbdata > dbdata.rfs
param > param.lfs
modem > modem.bin
kernel > zImage
Click to expand...
Click to collapse
sorry to get in like this
but i have the same problem
can u explain how to use the files with odin please?
thanks
benhouli said:
sorry to get in like this
but i have the same problem
can u explain how to use the files with odin please?
thanks
Click to expand...
Click to collapse
that package already has a bat.exe file, which will do it automatically when phone connected to PC, try that first
xsenman said:
its i9000 Rescue Kit for i9000 using heimdall packed by ldq, it has its own bat.exe to do it automatically from PC, but you can also use the files on Odin or on linux, for linux , the configuration will be
primary boot > boot.bin
secondary boot > Sbl.bin
repartition > s1_odin_20100512.pit
factoryfs > factoryfs.rfs
cache > cache.rfs
dbdata > dbdata.rfs
param > param.lfs
modem > modem.bin
kernel > zImage
Click to expand...
Click to collapse
xsenman said:
that package already has a bat.exe file, which will do it automatically when phone connected to PC, try that first
Click to expand...
Click to collapse
already did , but i get message heimdall not installed , do u what to install now ?
i say yes
but even i am with windows xp and with admim permissions
it say i need admin permissions and need to do run as admin
and even i do it, it don't stop say it . and won't continue
by the way
on the sticker on back the phone it say I9000GSMH
and what i start the phone i see logo of anycall
benhouli said:
on the sticker on back the phone it say I9000GSMH and what i start the phone i see logo of anycall
Click to expand...
Click to collapse
you need to verify, IF you have an Anycall M110S or i9000, check forv retractable Antenna on top right corner, IF you have one than its an Anycall M110S an usinh i9000 Roms will only make it worse.
If its i9000, check MY Android Solutions link below to identify the exact problem you are having , in using Odin, you normally use only 3 files http://forum.xda-developers.com/showthread.php?t=1102881
xsenman said:
you need to verify, IF you have an Anycall M110S or i9000, check forv retractable Antenna on top right corner, IF you have one than its an Anycall M110S an usinh i9000 Roms will only make it worse.
If its i9000, check MY Android Solutions link below to identify the exact problem you are having , in using Odin, you normally use only 3 files http://forum.xda-developers.com/showthread.php?t=1102881
Click to expand...
Click to collapse
it's without the antenna
and i know about the 3 files and the pit file...
i tried that
try a lot of roms from the link u give me...
the only one i could start the phone was
Froyo 2.2.1
Asia
ZSJPJ/ZSJPG/OZSJPG
but it was very slow , without sound , and no imei
all the others got me to invalid bootloader
and the version was installed on the phone when i got him was
android version : 2.3.4
baseband version : i9000zsjpj
kernel version : 2.6.35.7
build number : lidroid-i9000-1.2
but i didn't do backup
and i don't know how to get any normal rom to work
benhouli said:
android version : 2.3.4
baseband version : i9000zsjpj
kernel version : 2.6.35.7
build number : lidroid-i9000-1.2
but i didn't do backup
and i don't know how to get any normal rom to work
Click to expand...
Click to collapse
lidroid is a Chinese modified ROM, ok, If you want to try flashing under Odin follow this http://forum.xda-developers.com/showpost.php?p=22471340&postcount=1
xsenman said:
you need to verify, IF you have an Anycall M110S or i9000, check forv retractable Antenna on top right corner, IF you have one than its an Anycall M110S an usinh i9000 Roms will only make it worse.
If its i9000, check MY Android Solutions link below to identify the exact problem you are having , in using Odin, you normally use only 3 files http://forum.xda-developers.com/showthread.php?t=1102881
Click to expand...
Click to collapse
xsenman said:
lidroid is a Chinese modified ROM, ok, If you want to try flashing under Odin follow this http://forum.xda-developers.com/showpost.php?p=22471340&postcount=1
Click to expand...
Click to collapse
still no success
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and why the message invalid bootloader repeat itself ?
after every rom i try to flash?
benhouli said:
still no success
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
When you used Pit, was repartitioned ticked? , IF ticked and failed, download a 803 Pit (from, My android collections link below) and flash with boot loader and ROM package but untick repartition
xsenman said:
When you used Pit, was repartitioned ticked? , IF ticked and failed, download a 803 Pit (from, My android collections link below) and flash with boot loader and ROM package but untick repartition
Click to expand...
Click to collapse
still fail after i got 803 pit and untick repartition
and invalid bootloader too...
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
by the way
phone bootloader update stay unchecked...
and one more thing...
to flash everytime i must connect the jig to get the downloading mode,,,,
if i won't do it it will stay on anycall logo
benhouli said:
phone bootloader update stay unchecked...
and one more thing...
to flash everytime i must connect the jig to get the downloading mode,,,,
if i won't do it it will stay on anycall logo
Click to expand...
Click to collapse
Do you have KIES installed, if you do, kill all three KIES running files in your system using task manager and try again
This model with I9000GSMH, seems to have this problem, and I am not too sure why it has Anycall boot loader, as only M110S should be using it and the ROM package for it is different with hardware differences. I keep wondering if this model is a Chinese imitation or actually an M110S swiped with and i9000 casing or mother board .
I have come across a few persons having this very same issue on this very same model.
If you want to try using a Anycall Pit and Boot loader you can download from Pit Stop link below or try searching lidroid web site http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http://bbs.lidroid.com/ for a suitable ROM package
xsenman said:
Do you have KIES installed, if you do, kill all three KIES running files in your system using task manager and try again
This model with I9000GSMH, seems to have this problem, and I am not too sure why it has Anycall boot loader, as only M110S should be using it and the ROM package for it is different with hardware differences. I keep wondering if this model is a Chinese imitation or actually an M110S swiped with and i9000 casing or mother board .
I have come across a few persons having this very same issue on this very same model.
If you want to try using a Anycall Pit and Boot loader you can download from Pit Stop link below or try searching lidroid web site http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http://bbs.lidroid.com/ for a suitable ROM package
Click to expand...
Click to collapse
there is no trace on kies on task manager
and yes i know this is very weird thing that it's i9000 with anycall logo
about the pit stop link i will try
and about the lindroid i tried that too , it's very hard to find there something normal
by the way
thanks a lot for your help!
benhouli said:
there is no trace on kies on task manager
and yes i know this is very weird thing that it's i9000 with anycall logo
about the pit stop link i will try
and about the lindroid i tried that too , it's very hard to find there something normal
by the way
thanks a lot for your help!
Click to expand...
Click to collapse
can you try this bootloaders http://forum.xda-developers.com/showpost.php?p=14013450&postcount=1 with a JVU ROM or just the loader to see, IF it works
xsenman said:
can you try this bootloaders http://forum.xda-developers.com/showpost.php?p=14013450&postcount=1 with a JVU ROM or just the loader to see, IF it works
Click to expand...
Click to collapse
tried both...
both failed
You saod one of them worked... Froyo one i guess.
I think you should try to flash it after that get CM7.custom roms have boot images so...
I suggest this... But not sure if it works
Really sorry mate... I wish you luck .
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Hi
So problem started when phone would not boot, even twrp would show splash screen then reboot.
I tried to reflash cm11 using odin 3.07 it failed...
then had the "firmware upgrade encountered an issue. please select recovery mode in kies and try again"
I tired kies, failed does not recognise the phone.
followed unbrick/ restore baseband thread
odin failed again on flash
tried various builds of rom, (carbon, cm11, baseband). all fail seems to be at "system.img"
Tried to load twmp only with odin. got to reset in bule top left of odin. froze, did hard reset. odin says sucsess, but cant boot still shows "firmware upgrade encountered error"
I can get into download mode
custom binarys is also incrementing on each attempt. currently 7
Model gt- i8190
rom was cm11.0_golden.nova.20140817.ODIN_TWRP.tar
baseband I8190XXAMC1_I8190OJVAMC3_HOME.tar (South Africa)
Any help would be appreciated....
Kill_Switch422 said:
Hi
So problem started when phone would not boot, even twrp would show splash screen then reboot.
I tried to reflash cm11 using odin 3.07 it failed...
then had the "firmware upgrade encountered an issue. please select recovery mode in kies and try again"
I tired kies, failed does not recognise the phone.
followed unbrick/ restore baseband thread
odin failed again on flash
tried various builds of rom, (carbon, cm11, baseband). all fail seems to be at "system.img"
Tried to load twmp only with odin. got to reset in bule top left of odin. froze, did hard reset. odin says sucsess, but cant boot still shows "firmware upgrade encountered error"
I can get into download mode
custom binarys is also incrementing on each attempt. currently 7
Model gt- i8190
rom was cm11.0_golden.nova.20140817.ODIN_TWRP.tar
baseband I8190XXAMC1_I8190OJVAMC3_HOME.tar (South Africa)
Any help would be appreciated....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2159660
Try flashing:
http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404
KoolKid98189 said:
http://forum.xda-developers.com/showthread.php?t=2159660
Try flashing:
http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404
Click to expand...
Click to collapse
thx kookkid,
i already did do the param flash which passes, however then i still cant get into twrp, and i sit stuck on the samsung logo
if i then try flash the rom it fails again , and back to square 1
On the phone after failure i get in red text "movi_write card_status :0 (430) start_blk:1477552" (it overwrites the "current binary: custom" line that shows up in download mode
odin just shows this:
<ID:0/005> recovery.img
<ID:0/005> STE_boot1.img
<ID:0/005> STE_boot2.img
<ID:0/005> modem.bin
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kill_Switch422 said:
thx kookkid,
i already did do the param flash which passes, however then i still cant get into twrp, and i sit stuck on the samsung logo
if i then try flash the rom it fails again , and back to square 1
On the phone after failure i get in red text "movi_write card_status :0 (430) start_blk:1477552" (it overwrites the "current binary: custom" line that shows up in download mode
odin just shows this:
<ID:0/005> recovery.img
<ID:0/005> STE_boot1.img
<ID:0/005> STE_boot2.img
<ID:0/005> modem.bin
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try reflashing stock or if that fails then your eMMC chip is screwed! That happened to me so I called Amazon and they gave free replacement and never found out! Don't give it to Samsung! This is why I'm scared of rooting my S3 mini!
Please visit this forum and vote on the poll
http://forum.xda-developers.com/galaxy-s3-mini/help/previously-bricked-s3-minis-t2861724
KoolKid98189 said:
Try reflashing stock or if that fails then your eMMC chip is screwed! That happened to me so I called Amazon and they gave free replacement and never found out! Don't give it to Samsung! This is why I'm scared of rooting my S3 mini
Click to expand...
Click to collapse
process followed was flash param, then flash stock. thats when it fails........................
ARRGGGGG
thx anyway
anyone else got a new thought or how to test
Kill_Switch422 said:
process followed was flash param, then flash stock. thats when it fails........................
ARRGGGGG
thx anyway
anyone else got a new thought or how to test
Click to expand...
Click to collapse
Try flashing just the param and see what happens? Then try to flash the recovery then see what happens.
One more question, did you encrypt your device?
KoolKid98189 said:
Try flashing just the param and see what happens? Then try to flash the recovery then see what happens.
One more question, did you encrypt your device?
Click to expand...
Click to collapse
I didnt encrypt no.
If I flash only param, it passes. I then get the samsung logo on boot, and nothing more.
If I flash param, then twrp they both pass, but I get the please connect to kies firmware error. booting with power home vol down has no effect...
If I flash param then twrp then stock. fail on system.img
If I just flash stock fail on system.img
used heimdall to only flask kernal with system.img completes but at end gets error:
Ending session...
ERROR: Failed to receive session end confirmation!
then back to kies firmware error
Possibly related... I have found that my battery is not charging at all ...... is this dependent on a running phone? (dont think it is a factor, since I am able to flash param and twrp and pit without a problem) but covering bases.
Kill_Switch422 said:
I didnt encrypt no.
If I flash only param, it passes. I then get the samsung logo on boot, and nothing more.
If I flash param, then twrp they both pass, but I get the please connect to kies firmware error. booting with power home vol down has no effect...
If I flash param then twrp then stock. fail on system.img
If I just flash stock fail on system.img
used heimdall to only flask kernal with system.img completes but at end gets error:
Ending session...
ERROR: Failed to receive session end confirmation!
then back to kies firmware error
Possibly related... I have found that my battery is not charging at all ...... is this dependent on a running phone? (dont think it is a factor, since I am able to flash param and twrp and pit without a problem) but covering bases.
Click to expand...
Click to collapse
Try the stock recovery?
KoolKid98189 said:
Try the stock recovery?
Click to expand...
Click to collapse
when i do the stock recovery , it seems to flash ok, on reset, goes into connect kies error
odin gives pass:
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
recovery boot (vol up power and home, just shows same screen)
Kill_Switch422 said:
when i do the stock recovery , it seems to flash ok, on reset, goes into connect kies error
odin gives pass:
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
recovery boot (vol up power and home, just shows same screen)
Click to expand...
Click to collapse
Try flashing a stock baseband kernel, the stock recovery, the stock firmware and then finally the param and tell me what happens.
KoolKid98189 said:
Try flashing a stock baseband kernel, the stock recovery, the stock firmware and then finally the param and tell me what happens.
Click to expand...
Click to collapse
please confirm you mean the
boot.img -> baseband stock
recovery.img ->recovery stock
system.img ->firmware stock
then param
if so odin fails every time I try load the system.img
the rest load just fine.