stuck in pc odin - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

i was installing the ics repack zclp1 with pc odin but it stuck on data.img
what should i do?
can i remove the cable?

please help ...

you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig

antiguangenius said:
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
Click to expand...
Click to collapse
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.

Ok

chasmodo said:
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Click to expand...
Click to collapse
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....

Let me guess re-partition was on in odin?
If yes u need to call samsung.

avetny said:
Let me guess re-partition was on in odin?
If yes u need to call samsung.
Click to expand...
Click to collapse
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....

antiguangenius said:
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
Click to expand...
Click to collapse
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin

antiguangenius said:
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Click to expand...
Click to collapse
No, you read properly before you respond, and even more properly before dishing out any more useless advice to people with a very specific problem, i.e. bricked phones after flashing Angelom ICS kernel v1.2.
Read this, for instance:
http://forum.xda-developers.com/showpost.php?p=23256341&postcount=405
and this:
http://forum.xda-developers.com/showpost.php?p=23256829&postcount=406
I'll say no more about it.

androidindian said:
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
Click to expand...
Click to collapse
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...

antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
Those are some really interesting thoughts.
And this chap here http://forum.xda-developers.com/showpost.php?p=23305688&postcount=1
Did something similar and succeeded, though the root cause was different it seems to be matching with your analysis!!

antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?

androidindian said:
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
Click to expand...
Click to collapse
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...

antiguangenius said:
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
Click to expand...
Click to collapse
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?

androidindian said:
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
Click to expand...
Click to collapse
I didnt still on ICS but I did went back to GB once no issue,,, but all this ICS issues is hurting my head.... I'm going back to GB NOW... I'll report in a few mins....

Related

[Q] HELP HELP !!!! Looking Odin upgradable firmware

Hello all,
Bought a galaxy tab. And flashed it. With bad firmware.
I can set TAB in download mode.
So with ODIN I should be able to flash.
Can someone PLEASE!!!!?????? link me or tell me where to find A FULL EURO rom or P1000 compatible rom. That can be flashed with ODIN
Try latest Roto ROM here http://forum.xda-developers.com/showthread.php?t=939360, its okay for Euro Tab...
make a accout here, and you can choise the official firmware.
Samfirmware
Did that flashed and TAB boots and hangs at the SAMSUNG logo.
edit : DId a full whipe did not resolve hanging at the SAMSUNG logo
Used Jk5 with that. Downing Jk2 now.
ovigt71 said:
make a accout here, and you can choise the official firmware.
Click to expand...
Click to collapse
Why would u recommend this? Don't u know that they have locked bootloaders? People who don't understand stuff shouldn't be trying to help. Now he's gonna need to use the bootloader fix which has risks.
From the Tab.
www.twitter.com/ayman07
ayman07 said:
Why would u recommend this? Don't u know that they have locked bootloaders? People who don't understand stuff shouldn't be trying to help. Now he's gonna need to use the bootloader fix which has risks.
Click to expand...
Click to collapse
Only if he flashes one of the JMx series.
Flash the Rotohammer JMI firmware, it's a _complete_ firmware with the locked bootloader removed. If it doesn't work then you've either done something wrong (start again, read instructions carefully), or you've got a locked bootloader.
If you've already tried flashing a JMx firmware and are now having issues then you'll need to go back to whatever original firmware you had and then run the bootloader fix, which as long as you pay attention to the instructions is unlikely to be an issue, get it wrong however and you've got problems.
Also - this is not a development related question, should be in the general subforum.
TAB Dead
Tab is 3 days old and dead.
No recovery mode,
No Download mode,
only a blinking logo (screen of and on) that looks similar to the downloading logo when in flash mode when wall charger is attached.
No live indication or responsive s.
Indicates this a RMA to samsung service center.
Never had A flash or root problem of this kind before.
just the on of screen. If in wrong Category I hope some Admin might want to move it to the correct position.
ayman07 said:
Why would u recommend this? Don't u know that they have locked bootloaders? People who don't understand stuff shouldn't be trying to help. Now he's gonna need to use the bootloader fix which has risks.
From the Tab.
www.twitter.com/ayman07
Click to expand...
Click to collapse
Ok so you can give me a direct link to flashing boot of tab please ?
If it won't even get into download mode then there's nothing you can do to fix it, you'll have to take it back to the shop. Any fixes require being able to boot into download or recovery mode.
chetermaat said:
Tab is 3 days old and dead.
No recovery mode,
No Download mode,
only a blinking logo (screen of and on) that looks similar to the downloading logo when in flash mode when wall charger is attached.
No live indication or responsive s.
Indicates this a RMA to samsung service center.
Never had A flash or root problem of this kind before.
just the on of screen. If in wrong Category I hope some Admin might want to move it to the correct position.
Click to expand...
Click to collapse
Perhaps you mean the logo is phone at the left, middle is ! pc at the right, it's also a download mode, which you can flash thru odin, just flash with roto's rom, and do a repartition.
Basically if odin still able to detect your tab, it's not totally dead yet, if your tab's display is like what I mentioned above, just get roto's rom, AND MAKE SURE CHECKSUM IS CORRECT! Before flashing.
chetermaat said:
Ok so you can give me a direct link to flashing boot of tab please ?
Click to expand...
Click to collapse
Dutch!
http://gathering.tweakers.net/forum/list_message/35564050#35564050

[Q] Problem flashing back to stock rom

I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
everett1911 said:
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
Click to expand...
Click to collapse
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
prbassplayer said:
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
Click to expand...
Click to collapse
last time I had bothered to update cyanogen, it was a week ago. I don't remember the exact nightly build. The other roms I tried were miui, apex and something else that wouldn't boot and which I deleted quickly (apex wouldn't boot either but I spent a couple hours trying to make it work). I wiped everything prior to flashing.
as for the stock rom, it's a stock rom for the SGH-I896 (I896UXJI2), my phone model. before, the stock rom worked fine. I just can't figure out why it's suddenly not working now.
anyone? I really want to put the stock rom back into my phone.
Are you using a PIT file when flashing? If not try using this one with that package then report back.
I've already did that with odin.
and just out of curiousity, what are pit files for?
everett1911 said:
I've already did that with odin.
and just out of curiousity, what are pit files for?
Click to expand...
Click to collapse
I dont know what it exacly does BUT I know if you want to repartition your phone and you are on a AOSP like CM7 or MIUI you need a pit.
P.i.t.
Partitioning
Information
Table
Lol makes sense now
Sent from my SAMSUNG-SGH-I897 using xda premium
studacris said:
P.i.t.
Partitioning
Information
Table
Click to expand...
Click to collapse
*windows user* so it's a bit like a batch fdisk?
if so, is the internal sd card itself supposed to be wiped clean? because it didn't happen when I used mine.
Ok so using the PIT file didn't work for you. I've seen several Samsung devices suffer from a problematic internal OneNAND in the past but never one a Captivate. It's always been a TAB, i9000 or Vibrant. Can you try flashing the base files used in the Serendipity ROM? It's the stock Gingerbread installed before flashing the Serendipity ROM itself. You can find them in that thread. It will help distinguish whether you have an actual issue or whether you just need some in depth CSC scripts to help clean it up. In general that ROM has a very nicely built CSC cleanup script that is able to correct what I call "partition bricking" on the Captivate, i9000 and Vibrant. Give it a shot and report back...
Also, if that won't work, I have been able to correct this via JTAG. PM me if it comes to that. If JTAG won't correct it, then it is indeed a case of a partially dead OneNAND. It's rare but does happen.
I'll give that CSC script thing a try. What's JTAG, by the way?
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
anyone, please?
everett1911 said:
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
Click to expand...
Click to collapse
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
For2ndtwin said:
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
Click to expand...
Click to collapse
thanks but I think it's too late. while trying to flash serendipity two days ago, I used the odin flasher that site linked to, and it flashed my phone with at&t's firmware, which somehow completely ruined my phone. now, the phone won't boot, and I can't enter download mode at all. I'm not sure even a usb jig would help, and right now I don't have money for that, so I'll have to wait till I do.
And if this doesn't work, then what? All the phone does is show a spinning little circle, immobile for 3 seconds, and the phone turns off. when I insert the battery (after pulling it out), the phone automatically starts with the same screen, same result. if I plug in the usb cable, it shows the charging battery indicator, freezes, and reboots. This repeats over and over, with no end at all, and since I can't enter download mode in any way so far, I can't do anything about that. It's so bad that not even windows detect my phone, and I've plugged it into two separate computers, so I know it's not just my pc pulling a trick on me.
The worst part is that since I was using wifi tether on my phone (hello, pdanet), now I'm without any internet (right now I'm typing this on my little sister's laptop, from my dad's place.)
So... yeah.
By the way, the heimdall link is for i897 phones, even in the post for i896 phones. Is there any risks my phone will react as badly as it did with the at&t firmware?
^ I've read good things about Heimdall. Btw, if ur phone has any signs of life, then a Jig should get u back into download mode.
The fact that it was at&t firmware has nothing to do with it. Running I897 firmware on an I896 is fine. **** you can run I9000 firmware...
so many days after, I still can't get it into download mode at all. all it shows is a spinning circle, a spinning circle and then the charging battery image for a second when the usb cable is plugged in, and the AT&T world logo when the battery is low.
I could go for a solderless usb jig but even then I don't have cash for that right now (next week.), so until then I'm screwed.
I tried everything minus the usb jig, looked for many threads on the topic, and nothing works. nothing.
no matter how many times I do the battery trick or the three finger salute or the odin stuff, and it still doesn't work.
so... yeah. that usb jig better damn work.
I'll call it magic
First, I'd like to thank 4-2ndtwin for providing a complete stock rogers rom.
Second: how does a usb jig work, really? my thing's computers, software and hardware in general but not to the point of knowing how capacitors, resistors and all that stuff works, so for me the usb jig bringing back my phone from firmware limbo... that's magic. seriously.

[Q] Soft Bricked, Odin doesn't set up partition

I have done hours of researching and this isn't my first time i bricked a phone so I kind off have some experince fixing the phone but this seems harder than before.
I first tired to flash a kernel through odin on my captivate because i wanted to try out cyanogen mod but somehow the kernel had failed on me. When i tried to restart my phone, I got the phone---!---pc logo.
So i did some research on how to get the phone out of the soft brick. First thing I did was trying to get into recovery mode with the 3 buttons, but didnt work out. After that I tried to get into download mode and it worked. My first thought was too use odin and reflash, and that is what i did. Now the problem is, I had put the correct pit file and stock rom, because I had reflashed using these two same files before, but the thing is, it gets stuck on "set partition". So I did everything from, trying on different computers to changing usb cables to using different versions of odin and finally to taking out the sim card and sd card and taking out and placing the phones battery back in. And i had everything checked too so that wasn't the problem. The following were checked: Auto Reboot, Check Re-Partition and F.Reset Time.
If anyone knows the solution can you please help me out, thank you in advance!
When you check repartition, you need to load a pit file in the pit slot/tab for Odin. You have two options.
1) Flash froyo stock(kb2), if you don't want/need Gingerbread Bootloaders. The Heimdall package from Adam Outler is an easy 1 click solution.
2) Flash KF1 if you need GB bootloaders. This will also fix ant previous 3 button combo problem you may have. Use the package with a pit file and bootloaders.
It also sounds like you may need ajig to get into download mode, but if you follow the Captivate sig link below, you should be able to find everything you need to get going.
Thank you !
Thanks a lot mrhaley30705 ! I have gone through of some guides and done more research about these two, and I was thinking of flashing kb2 on to my phone but I'm really worried if it might brick my phone, because the captivate I have is the rogers one not the ATT&T one.
I just had a few questions like, before I do the Heimdall One-Click, is it required to install the Zadig file ? because it had came up before I opened up the Heimdall One Click program. I think i had used the Heimdall One-Click before (the video that is posted on youtube) by outleradam, but the thing was, it wasn't recognizing my phone. So I'm guessing it has something to do with Zadig file, because I made sure I ran it as Administrator also so I'm kinda lost.
My other question was, the consequences, if this program would not work for me, would it hard brick my phone? I really want to make sure I go ahead with it.
And my last question is, if I were to go ahead with this, it said on the forum I would have to reset my APN settings, so would that be applying another software to the phone or can i configure that manual ?
And Thanks again for all your help !
If you want the Canadian firmware, search for TRusselo's stock threads. He has a full set of Canadian firmware.
Anytime you flash bootloaders there is a chance of hard bricking your phone, either from an interruption in communication between your phone and computer (think power outage or bad cable) or accidentally mismatching bootloaders (think the old 3 button fix on top of GB bootloaders). Just follow all of the precautions you can when flashing bootloaders.
APN editing is done manually.
Oh alright I got how put the APN information, thank you.
And oh okay, that makes more senses.
And for the Canadian firmwares, that's what I pretty much did with Odin, I took his stock firmware and tried to flash it with Odin but wasn't passing the "set partition" part like I mentioned before. I followed his instructions too. So, that's why I'm a bit confused now, because I'm guessing if Odin doesn't work then I would have to use the Kb2 link that is posted on your Sig. Do you have any suggestions maybe ?
The canadian version of the captivate will flash the US verson, it just changes your boot screen and kernel splash to an att one. I would flash the KB2, then if you absolutley had to have the canadian version, flash it.
Thank you !
Thanks a lot once again ! and I will give it a try and let you know how it goes !
Maybe try NOT checking re-partition. This sometimes can cause a problem, in fact most tutorials i have seen always say DO NOT check re-partition. It's worth a try

[Q] BootLoop Problem PLEASE HELP! D:

Hey guys, ok so im superrrrrrrr new to this. Iv had an iphone and blackberrry half of my life and im just getting into the android world.
Point of the matter,
i have a galaxy ace, s5830m
just bought it a couple days ago here in venezuela
and everyting was running smooth, i really liked everything
since i sort of know about jailbreaking and all that stuff from having an iphone
i started reading up on how androids worked and managed to root my phone with out a problom
being that im a custom fanatic, i figured i wanted to update my gingerbread os to a ics using a custom rom from
cm9
this is what i did...
I downloaded the zip cm9 file,
loaded it into my sd card
went into recovery mode
and clicked update from sd card (totally forgot to clear cache and wipe/factory reset) as it was stated in the guide i was reading..
Anywhoo.. The instalation of the rom went fine, it said it installed correctly and with no errors
so i rebooted the phone, afterwards as it stated on the guide and boom!
Bootloop...
the phone is stuck on the samsung galaxy ace s5280m screen and wont finish booting up
iv left it like that for more then 30mins and nothing! Iv done several batter pulls and reboots and nothing
i went into recover mode and tried clearing cache and doing the wipe and rebooting again
but nothing! Its still stuck in the loop!
I did some reading and figured id load a stock firmware using odin hoping this would fix the problom
so i downloaded the latest one from my country from sammobile
downloaded the drivers
the cooper_v1.0 file
downloaded odin v4.38
did everything as the guide said but now odin isnt wanting to work,
i opened it as a administrator, i loaded the cooper file,
but when i want to load the single tar.md5 file..(the firmware)
it totally crashes on me, iv tried several times and it always crashes at the same point
iv tried on 3 diffrent computers and iv tried diffrent odim versoins and it always crashes at the same place!
This is when i started to worry, so i downlaoded samsung kies, to see if i can do a firmware update from there thinking itd be more reliable but now my computer doesnt want to reconize my phone
i can enter both download mode and recover mode having only the clear cache/factoryreset/and reboot options available.. Im really freakeddd out being that i just got this phone, and i feel pretty stupid i should have never done anything to the phone...but if anyone could help id really apreciate it!
Im desperate and i dont want to take it anywhere, cause im in venezuela at the moment
and i dont want to end up paying another dude a bunch of money to fix something that cud be fixed with some easy steps.
So any help is great!
I think that:
The s5830M is the same as s5830i
The s5830M is NOT the same as s5830
That might be your problem. I may be wrong but it's worth looking up.
If I'm right you will need to change Cooper file for correct one for your device. Also correct ROM too!
If I'm wrong, then, sorry.
Search more before you take any action. If you can get into download mode it can usually be fixed the way you are doing it but with correct files.
hmm
121C4 said:
I think that:
The s5830M is the same as s5830i
The s5830M is NOT the same as s5830
That might be your problem. I may be wrong but it's worth looking up.
If I'm right you will need to change Cooper file for correct one for your device. Also correct ROM too!
If I'm wrong, then, sorry.
Search more before you take any action. If you can get into download mode it can usually be fixed the way you are doing it but with correct files.
Click to expand...
Click to collapse
Ok i can look that up,
i kind have the same feeling,
being that the models are always divided as such..
So your saying (if this is right)
i need to find the Cooper File for s5830i
AND the ROM
and Odin should work after that?
The thing thats worrying me, is that all odin is doing is crashing on me,
but im going to look for another cooper file
being that the rom is especifcally for s5830M already
thanks for your fast response
im going to try this and get back to you...cause i really want my phone back D:
You need odin 1.85 i think, not sure.
And yes, 5830i and 5830m are compatible, but roms for 5830 and 5830L can brick your device.
ok
dxppxd said:
You need odin 1.85 i think, not sure.
And yes, 5830i and 5830m are compatible, but roms for 5830 and 5830L can brick your device.
Click to expand...
Click to collapse
ok so i did some investigation
after you told me about the models not being the same and ur right
i and m models are the same
and they only work with odin 1.85 as yu just said
and supposedly
only full package roms work not one package roms
and as i kepted reading in a spanish form,
there arent any ICS custom mods availbale for the M series
the only roms they run are the original stock roms.
so i guess i can forget trying to load a custom ICS rom into it
if this all works as the spanish forum explained
ill get back and confirm everything
ok so i have everything ready now,
but now my pc doesnt want to read my phone wile its on download mode
it will only read wile its on boot loop mode
and the only thing that happens on odin
is that it says ADDED!! (wile on boot loop mode)
but it never says my phone is reconized like its suppose to..
and when i click start.. nothing happens..
anyway to get my pc to reconize my phone on download mode?
or am i doing something wrong?
Maybe ask on the 5830i general thread?
I don't have the same phone as you so I don't really know what too suggest besides asking other people with the same phone as you.
121C4 said:
Maybe ask on the 5830i general thread?
I don't have the same phone as you so I don't really know what too suggest besides asking other people with the same phone as you.
Click to expand...
Click to collapse
i actually finally got odin to reconize the phone,
i uninstalled keis and installed the samsung drivers alone..
and got it to work
but now i have another problom!
(when will this stoppppppp)
when i finally have everything setup on odin,
and i click START
some movement happens
and then my pc restarts on its own by itself?...
:crying::crying::crying::crying::crying::crying::crying::crying:
JuniMatos said:
i actually finally got odin to reconize the phone,
i uninstalled keis and installed the samsung drivers alone..
and got it to work
but now i have another problom!
(when will this stoppppppp)
when i finally have everything setup on odin,
and i click START
some movement happens
and then my pc restarts on its own by itself?...
:crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try on another pc. Dont give up!! There will be a solution
Sent from my GT-S5830 using xda app-developers app

[Q] galaxy mini thinks its a GT-S5360

After installing JellyPlus and Cor Plenus kernel on my Galaxy Mini for program compatibility, I find the rom a little unstable, and wish to retun the phone to its origional status
Using CWM to load new rom gives error of there not being enough room on the device
Using Odin downloader, either the phone is not recognised, or the operation works, but sends the phone into boot loop, depending on the version of Odin I use
Using Kies, well, my phone is not 5570 any more, but a 5360 which is not supported for firmware upgrade
I am computer literate, Pc, Tablets, Windows, Android etc - No, I only thought I was
I have tried many things, and do not see how to revert the phone to factory (ie GT-S5570I STOCK ROM from its current status of GT-S5360)
Please, please help. I am happy to take a big kicking if this is easy, obvious, or many times previously covered - a push in the right direction would be greatly appreciated
Thank you, Paul
If you have bootloop, wipe data from stock recovery. And as I read read your post, you flashed Mini Plus ROM and kernel! So be happy, that your phone works!
Sent from my GT-S5570 using xda premium
no he flashed a galaxy y rom on his mini plus
lol
now what you can do is boot into recovery and wipe everything except sdcard from mount and storage option (do not format sdcard) then flash a custom rom meant for mini plus and then try to flash a stock rom through odin
dheeraj (dhlalit11) said:
no he flashed a galaxy y rom on his mini plus
lol
now what you can do is boot into recovery and wipe everything except sdcard from mount and storage option (do not format sdcard) then flash a custom rom meant for mini plus and then try to flash a stock rom through odin
Click to expand...
Click to collapse
Same thing lol
Be happy, it still works!
Sent from my GT-S5570 using xda premium
What I did.!
My phone was a GT-S5570I
I flashed the following, thinking that it was for my phone - see last bit?!
[ROM][KERNEL][ICS/JellyBean mod] JELLYBLAST V3 for Galaxy MINI/POP PLUS [GT-S5570i]
I am grateful that the phone still works, and very grateful to all of you who have replied
What I would like to know is how to enable enough free space on the phone so that I can flash back to stock 2.3.6 (as it was when I bought it)
should I pretend that it is a pop plus now, and look for solutions from there?
The 'trasto' has let me flash once again to the above rom / kernel, but often I am stuck without carrier - emergency calls only. Other than hat, it works very nicely!
hmm try to flash a kernel made for ur device , coz the kernel has the main properties of ur device for kies to detect, tat shud be ok,wont be requiring much space for kernel flashing i suppose :good:
btw there shudnt besuch errors, the updater script is acually set to swipe everything out b4 cpying the new files into ur rom
or else flash a custom rom, its easy tat way
just flash a firnware through odin
dheeraj (dhlalit11) said:
just flash a firmware through Odin
Click to expand...
Click to collapse
My thoughts exactly!
Can anyone recommend a method - have tried versions 1.87 (flashes, but boot loops afterwards), and 4.38 which does not recognise the phone
What I would really like to know is if there is a way to ´make room´ on the phone so I can flash through CMR - I too thought that a custom rom would clear everything out of it´s way, as did the jellythingyrom which has successfully put android 4.1.1 on the phone
rpaurey said:
My thoughts exactly!
Can anyone recommend a method - have tried versions 1.87 (flashes, but boot loops afterwards), and 4.38 which does not recognise the phone
What I would really like to know is if there is a way to ´make room´ on the phone so I can flash through CMR - I too thought that a custom rom would clear everything out of it´s way, as did the jellythingyrom which has successfully put android 4.1.1 on the phone
Click to expand...
Click to collapse
Fix for bootloop: wipe data from stock recovery. Is it hard to read/search?
Tapatalk 2-vel küldve az én GT-S5570-ről
rpaurey said:
My phone was a GT-S5570I
I flashed the following, thinking that it was for my phone - see last bit?!
[ROM][KERNEL][ICS/JellyBean mod] JELLYBLAST V3 for Galaxy MINI/POP PLUS [GT-S5570i]
I am grateful that the phone still works, and very grateful to all of you who have replied
What I would like to know is how to enable enough free space on the phone so that I can flash back to stock 2.3.6 (as it was when I bought it)
should I pretend that it is a pop plus now, and look for solutions from there?
The 'trasto' has let me flash once again to the above rom / kernel, but often I am stuck without carrier - emergency calls only. Other than hat, it works very nicely!
Click to expand...
Click to collapse
rpaurey said:
My thoughts exactly!
Can anyone recommend a method - have tried versions 1.87 (flashes, but boot loops afterwards), and 4.38 which does not recognise the phone
What I would really like to know is if there is a way to ´make room´ on the phone so I can flash through CMR - I too thought that a custom rom would clear everything out of it´s way, as did the jellythingyrom which has successfully put android 4.1.1 on the phone
Click to expand...
Click to collapse
Don't panic my friend ....
and YES, after upgrading to JellyBlast Samsung Kies recognized as 5360 ...
but everything is working well ..
I can backup / restore like normal phone ....
so why do u bother about that ...?
What I think is 5360 has the same hardware like 5570i ...
or maybe JellyBlast was ported from 5360 ... !!!!!
Here , your question is answered ...
U don't have to need the free space as flashing original FW doesn't need to put the file to phone ...
shwe said:
Don't panic my friend ....
and YES, after upgrading to JellyBlast Samsung Kies recognized as 5360 ...
but everything is working well ..
I can backup / restore like normal phone ....
so why do u bother about that ...?
What I think is 5360 has the same hardware like 5570i ...
or maybe JellyBlast was ported from 5360 ... !!!!!
Here , your question is answered ...
U don't have to need the free space as flashing original FW doesn't need to put the file to phone ...
Click to expand...
Click to collapse
Thank you, and .......... thank you!! I may be being hysterical, but main reason for wanting to go back to original is because the phone now often is stuck with emergency calls only. On rebooting I also sometimes get an Unlock Network screen (should I have unlocked the phone first? Hmm - I have read so much over the last few days that I am not too sure any more. Shall try flashing the original firmware cwm or odin, or both??!! Have you any views on the problems that >I have re the above posts? Kind regards, Paul PS sim works as normal in nokia phone
Hi Paul ...
According to your post I assumed that u have GT-S5570i like mine ...
I don't face any situation like you posted ...
The reason is may be ...
U didn't wipe the Dalvik cache
try wiping and see ...
And for the Network unlock screen ...
What I think is your country or region CSC code is different from the Jellyblast's default CSC code ...
in that case U need to know your original CSC code and need to change back ...
this is what I thought ...
all done and dusted
shwe said:
Hi Paul ...
According to your post I assumed that u have GT-S5570i like mine ...
I don't face any situation like you posted ...
The reason is may be ...
U didn't wipe the Dalvik cache
try wiping and see ...
And for the Network unlock screen ...
What I think is your country or region CSC code is different from the Jellyblast's default CSC code ...
in that case U need to know your original CSC code and need to change back ...
this is what I thought ...
Click to expand...
Click to collapse
Bueno, managed to find what I wanted (other than a functioning (for me!) 4.1.1 rom)
Phone back to original status, and only wasted 6 euros on a replacement sim which I didn't need!
Have located ´'stockrom+odin s5570i' zip - if anyone has similar problems can mail it to them
The zip has the PDA, PHONE(MODEM) and CSC all split up, and I zapped the BOOTLOADER as well, just in case
All as I want it, and at least I now know how to recover when I try a 422 Rom next time!
What a shame Odin not available for this phone in 'one packet option', and what a shame nothing like Nexus Root Toolkit for sgmini
Same problem
rpaurey said:
Bueno, managed to find what I wanted (other than a functioning (for me!) 4.1.1 rom)
Phone back to original status, and only wasted 6 euros on a replacement sim which I didn't need!
Have located ´'stockrom+odin s5570i' zip - if anyone has similar problems can mail it to them
The zip has the PDA, PHONE(MODEM) and CSC all split up, and I zapped the BOOTLOADER as well, just in case
All as I want it, and at least I now know how to recover when I try a 422 Rom next time!
What a shame Odin not available for this phone in 'one packet option', and what a shame nothing like Nexus Root Toolkit for sgmini
Click to expand...
Click to collapse
Hi, I have the same problem. Can you please send yours zip and instructions? For 5570 Odin not sees my phone and for 5360 See, but I do not know how to enter the pit. With it a little scared. I tried. Zip update, but everything just mods for 5570, which is now reports differently and therefore probably do not install via clockwork.
I play with it all day and google it to me a little laugh .. omg (when you have 20 tabs open and there is a mess).
Problem solved
So we solved the problem with rpaurey successfully. Odin really need to be right on the GT-S5570I and I think "I" even at the end.
Stock rom I had only a little English and other languages​​, but downloading Czech now. Thanks.

Categories

Resources