[Q]Flash Problems (GT-P1000) - Galaxy Tab Q&A, Help & Troubleshooting

Hello,
I can´t flash my Samsung GT-P1000
I tested many FW´s
Heimdall:
GalaxyTabP1000-JQ1-One-Click.jar (heimdall Driver)
No Errors but the Tab don´t start...
Recovery modus Errors (internal mmc checksum verify failed)
Odin(version 1.70/version 1.85)
gt-p1000_mr.pit / P1_add_hidden.pit versucht.
P1000XWJMG -> movinand.mst Complete(Write) operation failed
P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME -> hidden.rfs Complete(Write) operation failed
P1000XWJQ8_P1000PHNJQ1_P1000XXJPZ_HOME -> hidden.rfs Complete(Write) operation failed
Sorry for my english
can you help me ?
zer0x2k

zer0x2k said:
Hello,
I can´t flash my Samsung GT-P1000
I tested many FW´s
Heimdall:
GalaxyTabP1000-JQ1-One-Click.jar (heimdall Driver)
No Errors but the Tab don´t start...
Recovery modus Errors (internal mmc checksum verify failed)
Odin(version 1.70/version 1.85)
gt-p1000_mr.pit / P1_add_hidden.pit versucht.
P1000XWJMG -> movinand.mst Complete(Write) operation failed
P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME -> hidden.rfs Complete(Write) operation failed
P1000XWJQ8_P1000PHNJQ1_P1000XXJPZ_HOME -> hidden.rfs Complete(Write) operation failed
Sorry for my english
can you help me ?
zer0x2k
Click to expand...
Click to collapse
Hi, solution to your problem: LINK.
Follow it exactly as described!!!

Thank you for Posting!
I have already flashed
p1000xxjq1 p1000xxjq1 p1000xxjpz
but the same error with the hidden.rfs...
I cant download the Firmware from your Link!
Multiupload is currently down
Do you have a Mirror or Alternative Link ?

zer0x2k said:
Thank you for Posting!
I have already flashed
p1000xxjq1 p1000xxjq1 p1000xxjpz
but the same error with the hidden.rfs...
I cant download the Firmware from your Link!
Multiupload is currently down
Do you have a Mirror or Alternative Link ?
Click to expand...
Click to collapse
You could follow the instructions in the Overcome Guide to re-stock ONLY for your Tab? ...that will get you back to stock GB, you could of course then flash Overcome and/or other ROMS/Kernels.

sorry but i have the same problems... :-(

zer0x2k said:
Hello,
I can´t flash my Samsung GT-P1000
Recovery modus Errors (internal mmc checksum verify failed)
can you help me ?
zer0x2k
Click to expand...
Click to collapse
There has been a thread already about this problem. It turned out to be a 'corrupt NAND' problem... Get Samsung to replace it, it's a hardware failure. If it's still under warrant, that is of course...

zer0x2k said:
Hello,
I can´t flash my Samsung GT-P1000
I tested many FW´s
Heimdall:
GalaxyTabP1000-JQ1-One-Click.jar (heimdall Driver)
No Errors but the Tab don´t start...
Recovery modus Errors (internal mmc checksum verify failed)
Odin(version 1.70/version 1.85)
gt-p1000_mr.pit / P1_add_hidden.pit versucht.
P1000XWJMG -> movinand.mst Complete(Write) operation failed
P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME -> hidden.rfs Complete(Write) operation failed
P1000XWJQ8_P1000PHNJQ1_P1000XXJPZ_HOME -> hidden.rfs Complete(Write) operation failed
Sorry for my english
can you help me ?
zer0x2k
Click to expand...
Click to collapse
Give it back to q Samsung Service point......you habe a Hardware brick.....i hope you habe Warrant.........
Greets

sgsoneofthefirst said:
Give it back to q Samsung Service point......you habe a Hardware brick.....i hope you habe Warrant.........
Greets
Click to expand...
Click to collapse
What kind of statement is this ?!?! You must be an idiot to say this kind of things... think before you say crap !!!
Imbecile

You don't have to scold him 4 months later.
Sent from my GT-I9300T using xda app-developers app

Related

Can't downgrade from XXLB2?

Hi, i tried to downgrade from XXLB2 to KJ1 with Odin, but it didn't work. NAND write error. Now i am stuck. What can i do?
Hi, where is download link of your new Rom ?
facepalms
Blackflip said:
Hi, i tried to downgrade from XXLB2 to KJ1 with Odin, but it didn't work. NAND write error. Now i am stuck. What can i do?
Click to expand...
Click to collapse
you can start by posting in the correct place... this should go in Q and A not development...
Here this may help you
http://forum.xda-developers.com/showthread.php?t=1318423
or maybe this might
http://forum.xda-developers.com/showthread.php?t=1321268
Moved To Q&A​
Please post all questions in the Q&A section​
sorry for posting in the wrong forum.
So i have tried everything:
- downloaded and tried flashing 2 different stock ROM's from Switzerland XXKK5 and XXLA4 with odin. no avail:
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried installing the AbyssNotekernel42CWTouchOriginalLogo.tar
got into the menu and installed Superuser-3.0.6-efgh-signed.zip
but my SGN still won't boot.
Can someone PLEASE tell me what i am doing wrong?
I just want to go back to stock ROM now since this has been a rotten experience for me.
I know that my SGN is only Soft-bricked, i can still go into Download mode, but Odin will just not take any ROM that i throw at it.
Thank you for your help!
Would be really great if someone could help! Please!
anyone here?
I'm kinda having a similar issue. If i find a way around it I'll tell you.
Blackflip said:
sorry for posting in the wrong forum.
So i have tried everything:
- downloaded and tried flashing 2 different stock ROM's from Switzerland XXKK5 and XXLA4 with odin. no avail:
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried installing the AbyssNotekernel42CWTouchOriginalLogo.tar
got into the menu and installed Superuser-3.0.6-efgh-signed.zip
but my SGN still won't boot.
Can someone PLEASE tell me what i am doing wrong?
I just want to go back to stock ROM now since this has been a rotten experience for me.
I know that my SGN is only Soft-bricked, i can still go into Download mode, but Odin will just not take any ROM that i throw at it.
Thank you for your help!
Click to expand...
Click to collapse
Right click odin and run as administrator
Sent from my GT-N7000 using xda premium
I finally found a way... I downloaded the 3 Part KJ1 Firmware (N7000OXAKJ1)
then i put into Odin (run as Admin of course)
- KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5
into the "Bootloader"
- MODEM_N7000XXKJ1_REV_05_CL1067428.tar.md5
into the "Phone"
- GT-N7000-MULTI-CSC-OXAKJ1.tar.md5
into "CSC"
and flashed my SGN.
Then i did it again but this time i also put the
- CODE_N7000XXKJ1_CL627135_REV02_user_low_ship.tar.md5
or the
- N7000XXKKA_N7000OXXKK5_N7000XXKK5_HOME.tar.md5
into "PDA"
finally my phone booted up again.
after that it was pretty straightforward with updating to ICS Stunner.
N7000 xxlb2 problem
how to root n7000 xxlb2? SuperUser will not install at all.
Can man say what or how to do it? i'll be pleased to hear from you guys.
Thx a lot.

Invalid Bootloader error. Phone stuck on bootloop

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

Galaxy Ace S 5830M Bootloop

Hello,
I have a friend with a Non-Rooted, totally stock Galaxy Ace s5830M that's stuck on a boot loop. He was playing a game and the screen started flashing and it rebooted. It is now stuck in a boot loop.
I've been able to get in to Stock Recovery and in to Download mode without issues.
We tried to flash Clockwork Mod Recovery. It apparently succeeds , but when we reboot it does not "stick". Flash CWM,reboot and it just shows the Stock recovery menu. I found this thread, regarding this issue.. But this phone is completely stock, bought on Amazon and shipped to Venezuela. I think it was running Gingerbread.
We then tried to flash to a Stock Firmware from my country from Sammobile.com with Odin.
Once a single file recovery ( a large file with a md5.tar extension) and it fails:
<ID:0/037> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830MWHLA1_S5830MUUBLA1_S5830MWHLA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/037> Odin v.3 engine (ID:37)..
<ID:0/037> File analysis..
<ID:0/037> SetupConnection..
<ID:0/037> Initialzation..
<ID:0/037> Get PIT for mapping..
<ID:0/037> Firmware update start..
<ID:0/037> sbl.bin
<ID:0/037> NAND Write Start!!
<ID:0/037> BcmCP.img
<ID:0/037>
<ID:0/037> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Then we tried another solution from another site, flashing a multiple file firmware (BOOT, PDA and PHONE). We get this result, apparently it is succesful:
<ID:0/037> Added!!
<ID:0/037> Odin v.3 engine (ID:37)..
<ID:0/037> File analysis..
<ID:0/037> SetupConnection..
<ID:0/037> Initialzation..
<ID:0/037> Set PIT file..
<ID:0/037> DO NOT TURN OFF TARGET!!
<ID:0/037> Get PIT for mapping..
<ID:0/037> Firmware update start..
<ID:0/037> BcmBoot.img
<ID:0/037> NAND Write Start!!
<ID:0/037> HEDGE_NVRAM8_RF_LE.bin
<ID:0/037> sysparm_dep.img
<ID:0/037> system.img
<ID:0/037> boot.img
<ID:0/037> param.lfs
<ID:0/037> sbl.bin
<ID:0/037> BcmCP.img
<ID:0/037> Transmission Complete..
<ID:0/037> Now Writing.. Please wait about 2 minutes
<ID:0/037> Receive Response form LOKE
<ID:0/037> RQT_CLOSE !!
<ID:0/037> RES OK !!
<ID:0/037> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/037> Removed!!
Click to expand...
Click to collapse
When we reboot the phone, we now get a boot screen that says the device is a S5830C instead of a S5830M. But it's still stuck on the Samsung logo at boot.
We really don't know what else to try. Any ideas? Is this phone bricked?
Thanks,
Rafael
Factory reset ur phone from recovery & wipe cache. Also, U need to place the individual firmware files at correct fields in odin (hope U did that) otherwise ur phone'll not be able to boot properly.
As far as I know there are four files (BOOT, PHONE, PDA, CSC) in full package & only one file (of extension:- tar.md5) in One Package firmware...
Sent Via XDA Premium
Galaxy_Rohit said:
Factory reset ur phone from recovery & wipe cache. Also, U need to place the individual firmware files at correct fields in odin (hope U did that) otherwise ur phone'll not be able to boot properly.
As far as I know there are four files (BOOT, PHONE, PDA, CSC) in full package & only one file (of extension:- tar.md5) in One Package firmware...
Sent Via XDA Premium
Click to expand...
Click to collapse
U managed to screw the phone ... It was as simple as as factory reset you were lucky! You could have hard bricked is ace ! Flash a proper rom to 5830 M and the enter STOCK RECOVERY! and do wipe data!
Sent from my GT-I9830 using xda premium
Yep, that's the first thing we did, we did a wipe data and wipe cache.
Here are the steps we took when flashing via Odin.
Settings we used:
Files we used to flash:
marcano said:
Yep, that's the first thing we did, we did a wipe data and wipe cache.
Here are the steps we took when flashing via Odin.
Settings we used:
Files we used to flash:
Click to expand...
Click to collapse
U used odin for 5830i ...
Sent from my GT-I9830 using xda premium
You need to do a hard reset after flashing the stock rom.
Enviado desde mi LG-P350 usando Tapatalk 2
SnowPluralism said:
U used odin for 5830i ...
Sent from my GT-I9830 using xda premium
Click to expand...
Click to collapse
The S5830i, S5830C, S5830M and S5839i are the same aka cooperve.
The only difference is the region, this version of Odin works with S5830M too!
Anyway, this rom you flashed is from Brazil, and works with your phone too. Try a wipe data/factory reset on recovery, this maybe works.
You should have a look at S5830i Development and S5830i General, there you will find more answers about your phone.
Stock ROM for SGA 5830M
marcano said:
Hello,
I have a friend with a Non-Rooted, totally stock Galaxy Ace s5830M that's stuck on a boot loop. He was playing a game and the screen started flashing and it rebooted. It is now stuck in a boot loop.
I've been able to get in to Stock Recovery and in to Download mode without issues.
We tried to flash Clockwork Mod Recovery. It apparently succeeds , but when we reboot it does not "stick". Flash CWM,reboot and it just shows the Stock recovery menu. I found this thread, regarding this issue.. But this phone is completely stock, bought on Amazon and shipped to Venezuela. I think it was running Gingerbread.
We then tried to flash to a Stock Firmware from my country from Sammobile.com with Odin.
Once a single file recovery ( a large file with a md5.tar extension) and it fails:
Then we tried another solution from another site, flashing a multiple file firmware (BOOT, PDA and PHONE). We get this result, apparently it is succesful:
When we reboot the phone, we now get a boot screen that says the device is a S5830C instead of a S5830M. But it's still stuck on the Samsung logo at boot.
We really don't know what else to try. Any ideas? Is this phone bricked?
Thanks,
Rafael
Click to expand...
Click to collapse
Hi Rafael. OK, I have made a detailed how to in Taringa that specifies the way to install a Stock ROM for SGA GT-S5830M. Just search in google "tutorial flashear samsung galaxy ace 5830m con odin - Taringa!" (without quotation marks) and enter the first result, it would redirect you to my post, check that the name of the creator is "jhonaff", if so, just download the files from there, and flash them via Odin 1.85 or 1.87. In the post there is a link to download the version 1.85, this version of Odin is the one that works perfectly with this device. Following that steps I gave life again to my SGA 5830M.
After you download, unzip the files in the S5830M.rar archive, you will get three .tar.md5 files; now put the files in the following order in Odin:
BOOTLOADER -> leave this section empty.
PDA -> select the PDA file.
PHONE -> select the MODEM file.
CSC -> select the CSC file.
Now click Start button and wait for the process to finish; at the end of the process the phone will reboot in recovery automatically and it will run a script, don't unplug it, and don't do anything yet. The phone will reboot once more and now it will pass the Samsung logo and will show you the Samsung bootanimation. Now you can unplug it and wait, the first boot may take 1 or 2 minutes and you will get your phone alive again.
PD: I can't give you a link to my post cause I'm new in this site and I don't have 2 posts here, so I can't post links in my replies.
PD2: My post in Taringa is in Spanish, I think it is understandable, but if not, use a traductor, after all you just want to download the correct files.
I hope this can help you. I speak spanish and has been years from the last time I spoke in English, so forgive me if something is wrote incorrectly.
Thank you jhonaff2
jhonaff2 said:
Hi Rafael. OK, I have made a detailed how to in Taringa that specifies the way to install a Stock ROM for SGA GT-S5830M. Just search in google "tutorial flashear samsung galaxy ace 5830m con odin - Taringa!" (without quotation marks) and enter the first result, it would redirect you to my post, check that the name of the creator is "jhonaff", if so, just download the files from there, and flash them via Odin 1.85 or 1.87. In the post there is a link to download the version 1.85, this version of Odin is the one that works perfectly with this device. Following that steps I gave life again to my SGA 5830M.
After you download, unzip the files in the S5830M.rar archive, you will get three .tar.md5 files; now put the files in the following order in Odin:
BOOTLOADER -> leave this section empty.
PDA -> select the PDA file.
PHONE -> select the MODEM file.
CSC -> select the CSC file.
Now click Start button and wait for the process to finish; at the end of the process the phone will reboot in recovery automatically and it will run a script, don't unplug it, and don't do anything yet. The phone will reboot once more and now it will pass the Samsung logo and will show you the Samsung bootanimation. Now you can unplug it and wait, the first boot may take 1 or 2 minutes and you will get your phone alive again.
PD: I can't give you a link to my post cause I'm new in this site and I don't have 2 posts here, so I can't post links in my replies.
PD2: My post in Taringa is in Spanish, I think it is understandable, but if not, use a traductor, after all you just want to download the correct files.
I hope this can help you. I speak spanish and has been years from the last time I spoke in English, so forgive me if something is wrote incorrectly.
Click to expand...
Click to collapse
Thank you very much jhonaff2, you solved my problem after some days
I know it is not related to this post, but do you know how can I enable my 3G radio in US T-Mobile? I can only get their 2G services
geniusbabak said:
Thank you very much jhonaff2, you solved my problem after some days
I know it is not related to this post, but do you know how can I enable my 3G radio in US T-Mobile? I can only get their 2G services
Click to expand...
Click to collapse
we have same problem in 3g. i can only get 2g services

Galaxy S i9000 No IMEI / No Network

Hello guys, I have a device with no EFS Backup. Baseband says "Unknown" and *#06# brings up just empty popup with OK button.
I have read a lot of threads about this problem, a lot of ways to fix it, but none of them worked for me.
I'm not trying to restore my IMEI, I just want to make network available, even with the generic IMEI (My Carrier doesn't have any problems with that)
Right now I'm on stock rooted 2.3.6 and waiting for help.
archildroid said:
Hello guys, I have a device with no EFS Backup. Baseband says "Unknown" and *#06# brings up just emty popup with OK button.
I have read a lot of threads about this problem, a lot of ways to fix it, but none of the worked for me.
I'm not trying to restore my IMEI, I just want to make network available, even with the generic IMEI (My Carrier doesn't have any problems with that)
Right now I'm on stock rooted 2.3.6 and waiting for help.
Click to expand...
Click to collapse
Network is not there because of the IMEI. Ideally, IMEI should not have been wiped as you are on stock. But anyways, flash to original STOCK ROM should i get fixed...just follow the link:
- Flashing To Original Rom - Using Odin on GT-i9000
- Flashing To Original Rom - Using Heimdall on GT-i9000
gopalasubramanium said:
Network is not there because of the IMEI. Ideally, IMEI should not have been wiped as you are on stock. But anyways, flash to original STOCK ROM should i get fixed...just follow the link:
- Flashing To Original Rom - Using Odin on GT-i9000
- Flashing To Original Rom - Using Heimdall on GT-i9000
Click to expand...
Click to collapse
hello and thanks for replying.
I tried flashing several stock roms on 2.2.1 and 2.3.6 but it didn't fix my issue (
Guys, I really need your suggestions.
I'm stuck with no signal ((
happened to me today too. i flashed semaphore jb then i flashed voodoo then
i flashed speedmod for the sake of testing it. now i have no imei and signal.
please help us asap. thanks.
EDIT:
hey i found a solution. i was able to restore my imei and mobile signal.
HERE.
Cedi0117 said:
happened to me today too. i flashed semaphore jb then i flashed voodoo then
i flashed speedmod for the sake of testing it. now i have no imei and signal.
please help us asap. thanks.
EDIT:
hey i found a solution. i was able to restore my imei and mobile signal.
HERE.
Click to expand...
Click to collapse
Thanks, I'll try it as soon as I get home and reply here.
Hope it will help.
I've been trying to solve my mum's i9000 out - I have an IMEI but it isn't the same one - EFS folder is empty. Tried everything I know. Still no luck :/
archildroid said:
Hello and thanks for the link. Please, can you tell me what steps did you exactly take? step-by-step.
Thanks in advance
Click to expand...
Click to collapse
I just flashed the three files in odin, the PDA, PHONE and CSC in the link i gave you.
LINK
Necessary files :
ODIN 1.85
ODINFILES
1.go to download mode on your phone. open up odin before you plug in your phone.
2.Plug in Phone with USB Cable To Computer
In ID:COM it should go yellow and you should see ADDED in the message box
3.Click PDA button and select : CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar
4.Click PHONE button and select: MODEM_I9000XXJVU_REV_00_CL1092175.tar
5.Click CSC button and select: GT-I9000-CSC-MULTI-OXAJVU.tar
(don't tick re-partition and flash lock)
When you have all the files needed in ODIN
6.Click Start let it Run.
it will boot up and open recovery and if it has red errors (the dbdata one)
just flash this file as PDA and don't tick re-partition and flash lock. Otherwise, skip these steps.
DBDATA.RFS
To root your device again, just flash this file: LINK (or this file can be found in the OdinFiles.zip). Flash this file as PDA again.
after doing so, my problem regarding missing imei and mobile network were gone.
however, i do recommend reading the thread if you weren't able to understand some things or whatnot.
CREDITS:
EwOkie's thread.
Source:
experience this morning lol
hope i could be of assistance.
Regards,
Ken
Great reply +thank'ed.
I haven't tried JVU yet, but I've tried quite a lot of other GB stock roms.
I'll give that a go now.
EDIT:
Did that and it came with "confirm password" error!
what do you mean password error? i haven't experienced an error like that
Sent from my GT-I9000 using xda premium
Cedi0117 said:
what do you mean password error? i haven't experienced an error like that
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
The photo is linked.
Don't worry nothing to do with the IMEI problem.
Cedi0117 said:
happened to me today too. i flashed semaphore jb then i flashed voodoo then
i flashed speedmod for the sake of testing it. now i have no imei and signal.
please help us asap. thanks.
EDIT:
hey i found a solution. i was able to restore my imei and mobile signal.
HERE.
Click to expand...
Click to collapse
I flashed the ROM medntioned in the link, but after succesfull flashing with odin and reboot I recieve error:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:Can't mount /efs
archildroid said:
I flashed the ROM medntioned in the link, but after succesfull flashing with odin and reboot I recieve error:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:Can't mount /efs
Click to expand...
Click to collapse
Sorry about that error. i forgot to mention it.
Download this file : LINK
Flash it under .PIT and tick re-partition together with the PDA, PHONE and CSC.
Tell me if it works.
Regards,
Ken
Cedi0117 said:
Sorry about that error. i forgot to mention it.
Download this file : LINK
Flash it under .PIT and tick re-partition together with the PDA, PHONE and CSC.
Tell me if it works.
Regards,
Ken
Click to expand...
Click to collapse
flashing right now. will reply soon
=====
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Sbl.bin
<ID:0/008> param.lfs
<ID:0/008> factoryfs.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> cache.rfs
<ID:0/008> zImage
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response form LOKE
<ID:0/008> cache.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
result - same error. flashing again
=====
re-flashed - same error (
archildroid said:
flashing right now. will reply soon
=====
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Sbl.bin
<ID:0/008> param.lfs
<ID:0/008> factoryfs.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> cache.rfs
<ID:0/008> zImage
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response form LOKE
<ID:0/008> cache.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
result - same error. flashing again
=====
re-flashed - same error (
Click to expand...
Click to collapse
Sorry about this mess. i'm trying to find solutions for your problem as i wasn't able to encounter it.
Did you by chance ticked on "Phone EFS Clear" ?
Or try flashing another stock rom - after factory resetting in recovery and pulling the battery.
flashed stock froyo - up and running.
No IMEI, No Baseband
==
I rooted it, and when I checked efs folder - it was empty, only .android folder.
I tried to insert another galaxy s efs files (thanks to Cedi0117 for providing them) - set proper permissions with root explorer, restarted - efs is empty again.
archildroid said:
flashed stock froyo - up and running.
No IMEI, No Baseband
==
I rooted it, and when I checked efs folder - it was empty, only .android folder.
I tried to insert another galaxy s efs files (thanks to Cedi0117 for providing them) - set proper permissions with root explorer, restarted - efs is empty again.
Click to expand...
Click to collapse
Same here.
I've contacted samsung btw - I'm waiting for their reply.
I even told them I flashed via ODIN (warranty is over so nothing to lose)
There should be some way at least to get the generic IMEI.
TotallydubbedHD said:
Same here.
I've contacted samsung btw - I'm waiting for their reply.
I even told them I flashed via ODIN (warranty is over so nothing to lose)
Click to expand...
Click to collapse
Any news?

[Q] Soft brick S3mini GT-i8190

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.

Categories

Resources