Related
Evening.
As it says on the tin I'm looking for a ROM that would be flashable via the 3 file way - pda, phone and csc - why? After having a great time with my i9000 I got two T959 veeeery cheap from a mate in U.S. and after sucessfully unlockin them both (manually via editing nv_data etc. - it's fun ) I stumbled upon a problem... constant FC's now am not sure if my i9000 and P1000 method of unlocking is unsuitable for the Vibrant or something was already messed up but I decided to flash it. Choose the JI6 one file .tar rom and flashed it as it's supposed to be flashed...
Now everytime I power on the phone it goes to recovery mode... I tried various things (most of the stuff is on xda already) but sadly I cannot get the stI10 to mount... I reckon the apps are screwed up so am lookin for a 3 file rom - or well any other way on how to fix this mounting problem (copy_dbdata_media:Can't mount DBDATA...).
Been at it for about 6 hours now without any luck... tried the flashing only pit 1st then only pda (JFD and later JI6) without luck... tried 8 different one file stock roms and no luck at all... Read up on costum roms and all I see is kernels and stuff with which I can't do anything since I can only flash things on the phone... can't use ADB, can't manually push files on the phone to get apps via install from sdcard update.zip etc...
Any help would be greatly appriciated
Cheers in advance, Nightravenn
Youactually need to find (in the vibrant bible there are links) to the JFD odin files. the reason you're not getting that to mount, is JI6 doesn't contain all the files for this like JFD does.
Flash JFD -> Then JI6 (don't check repartition).
Agreed, jfd is full, ji6 is just an upgrade, it doesn't even wipe data.
Sent from my SGH-T959 using XDA App
Cheers it did the trick
Now I just need to find a good way to unlock it since clearly my I9000 way is not the way to go...
Flashed ICS using odin. During this process we tick repartion checkbox and select a .pit file (along with PDA,PHONE,CSC). No other rom i have flashed requires this.
I wish to return to gingerbread rom at some point. the stock rom i have only requires me to select PDA as other packages-phone+csc are contained within it. However the .PIT file is not.
So my question is if i simply flash stock rom back, won't that leave the .pit in the same state it was running ics ??
PIT included in XXKP8 is the same PIT as before. So IMHO You do not need to repartition while flashing. There were people that flashed ICS sucessfully without repartition. It also means that no repartition is needed when returning to GB.
As far as I know there is only one official PIT for SGS2 - u1_02_20110310_emmc_EXT4.pit (md5: 1c7c7cf5a1955f7908a59181a52091ab), so flashing it does completly nothing (apart from increasing risk of bad flash) as Your device already contains it.
Regards
Slig
I did try flashing without .pit or repartition but didnt work.
the problems i foresaw =
Originally running 2.3.4, after flashing ICS, I now can not run any version before 2.3.6 only this and ICS.
If .pit is same maybe i should just tick repartition when flashing 2.3.4 ??
Try reading this thread, ultramag69 managed to fix the same issue you are having, and they list the steps they went though.
Solved. If i want to swap between gingerbread and ics i have to repartition and add .pit. Phone will not mount anything unless i do this. Others have had no trouble without but for me i simply have to repartition and add .pit.
Yesterday, I plugged in my tab to the charger over night. When I unplugged it today, I restarted it and after that it won't boot. The tab only shows the "Samsung galaxy tab 10.1" text for about 20-30 seconds and then it seems to reboot.
The device is rooted and running this rom. It is a 10.1" P7500 3g version.
Although I can still access recovery and bootloader modes, so I've tried wiping cache (normal cache can be cleared, but not dalvik) and data but nothing happens when I try to do it (It justs stays at formatting data forever when I do a full wipe). I've also tried flashing the same firmware and reinstalling the same rom again. I had an old backup of a earlier version of the rom, which I restored to but then I only get the boot screen to load for 2-3 seconds and then it freezes.
What should I do now?
Solved: Read my latest post.
Flash from scratch with Odin. No other choice.
Misledz said:
Flash from scratch with Odin. No other choice.
Click to expand...
Click to collapse
Alright, what files should I flash? Should I get a hold of a original firmware? Thanks for answering btw!
Ah you're welcome
Just get it off samfirmware.com, get HC 3.2 (Don't go for 3.1 as it is rubbish), Get the european firmware as it is the same and the most stable build (Also the first release for most new firmwares, if ICS were to come out, EU would get the firmware first)
GL and feel free to ask what you lack
Flashing guide's are pretty much simple.
Flash the unextracted file (must be in md5 extension) in PDA slot in odin in download mode and voila.
Ah la fresh tablet minion
Misledz said:
Ah you're welcome
Just get it off samfirmware.com, get HC 3.2 (Don't go for 3.1 as it is rubbish), Get the european firmware as it is the same and the most stable build (Also the first release for most new firmwares, if ICS were to come out, EU would get the firmware first)
GL and feel free to ask what you lack
Flashing guide's are pretty much simple.
Flash the unextracted file (must be in md5 extension) in PDA slot in odin in download mode and voila.
Ah la fresh tablet minion
Click to expand...
Click to collapse
I downloaded a 3.2 firmware from samfirmware.com, more specific:
"P7500XWLB1 3.2 2012 February P7500NSELA1 Sweden (Telia)"
It was zipped, i unzipped it and it was one .md5 file and one .dll file. I flashed the .md5 file with Odin in PDA. Odin tells me it is successful, and then the tab shows some scripts saying everything is succesful and then it reboots into the Samsung Galaxy Tab 10.1 text. After that I get a text saying "Manual mode, updating application..." for a while until it reboots into the same procedure again.
Atm I'm downloading another firmware just to be sure, I'll post when I've tried that one aswell. (It's named7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries)
Really appreciate your help
Edit: Tried the other firmware without any success.
But have you been able to boot into the tablet properly after flashing? Don't worry about the dll, I don't really know what it's for, actually no one know's since Samsung hasn't even told us what it's used for, and phone's don't read dll's
That manual mode updating is the stock recovery building the CSC and everything (Regional settings)
Which firmware didn't work? You can only use 7500 firmware on a 7500 And don't forget to flash a CWM recovery, just might save your life
Misledz said:
But have you been able to boot into the tablet properly after flashing? Don't worry about the dll, I don't really know what it's for, actually no one know's since Samsung hasn't even told us what it's used for, and phone's don't read dll's
That manual mode updating is the stock recovery building the CSC and everything (Regional settings)
Which firmware didn't work? You can only use 7500 firmware on a 7500 And don't forget to flash a CWM recovery, just might save your life
Click to expand...
Click to collapse
I flashed P7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries, and booted it but nothing happened. So I flashed a CWM recovery, and then it boots into Samsungs original-boot animation and then a text says Samsung. And then after a while it reboots again.
I'm at a loss right now, should I try to flash in a different order or flash with the device booting in between?
Ah, you ended up in a bootloop. Sometimes you may need to flash that firmware, then factory reset in recovery to get it to work. Depends if you had something in your previous ROM that conflicts. Or you can save the problem's and flash with a pit file. The overcome thread has a wonderful guide on that
rackadoosing said:
I flashed P7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries, and booted it but nothing happened. So I flashed a CWM recovery, and then it boots into Samsungs original-boot animation and then a text says Samsung. And then after a while it reboots again.
I'm at a loss right now, should I try to flash in a different order or flash with the device booting in between?
Click to expand...
Click to collapse
You can try the method described here;
http://forum.xda-developers.com/showpost.php?p=22964943&postcount=4
It will get you back totally to stock, and then you can re-root and reflash.
Hopefully that helps (should fix most problems).
Br,
/primpa
Thanks alot guys!! I followed the "Re-“Stocking” Yer System…"-guide at the bottom of the page you linked, and the tab is now booting correctly. You're my life savers! Thanks again
rackadoosing said:
Thanks alot guys!! I followed the "Re-“Stocking” Yer System…"-guide at the bottom of the page you linked, and the tab is now booting correctly. You're my life savers! Thanks again
Click to expand...
Click to collapse
That method has yet to fail me.
Used to go around suggesting it everywhere but others have used it with success and are stepping in when needed.
Sent from my GT-P7510 using XDA Premium HD app
Hi,
I received my GSII (I9100M) a few days ago and I already screw it up.
Coming from a I9000M, we could flash nearly any rom with PIT file without any problem, I assumed the same fot my I9100M but I realized yesterday that it is not the same.
When I received my phne I tried to install UGLD3 over Kies on it. The connection keeps cutting and as such I had to try to install it over ODIN. Didn't work. It gave me a "Kernel Upload Panic Mode" and I had to install UGKG2 (gingerbread) via Odin to make the phone works again.
Yesterday, I decided to try to install UGLD3 again via ODin but I also used a PIT fil included in Sammobile Odin software. Odin failed midway installing. I tried to reinstall UGKG2 and it failed again. I panic. I try UGKG2 again with PIT. It successfully installe but upon reboot, it gave me a E:failed to mount error on all the lines. I decided to reread some guides on XDA and found one that indicated that an guy with an I9100M with the same problem was able to recover the phone by installing a I9100 stock rom. Tried it. It worked. I tried to reinstall UGKG2. Failed again. Same error. Reinstalled the I9100 stock GB rom. Now the phone is working but I have a Rom not made for my carrier. I have all that junk that I don't want. I even realized that Bell is very good with it's bloatware.
So my question: What should I do to be able to make my phone works with UGKG2 again.
1) Should I reinstall UGKG2 with PIT and RE-Partition ticked this time? (it wasn't ticked last time)
2) Should I bring it to my carrier in order to be serviced?
3) Any other suggestions?
Thanks for all your help!
urself25 said:
Hi,
I received my GSII (I9100M) a few days ago and I already screw it up.
Coming from a I9000M, we could flash nearly any rom with PIT file without any problem, I assumed the same fot my I9100M but I realized yesterday that it is not the same.
When I received my phne I tried to install UGLD3 over Kies on it. The connection keeps cutting and as such I had to try to install it over ODIN. Didn't work. It gave me a "Kernel Upload Panic Mode" and I had to install UGKG2 (gingerbread) via Odin to make the phone works again.
Yesterday, I decided to try to install UGLD3 again via ODin but I also used a PIT fil included in Sammobile Odin software. Odin failed midway installing. I tried to reinstall UGKG2 and it failed again. I panic. I try UGKG2 again with PIT. It successfully installe but upon reboot, it gave me a E:failed to mount error on all the lines. I decided to reread some guides on XDA and found one that indicated that an guy with an I9100M with the same problem was able to recover the phone by installing a I9100 stock rom. Tried it. It worked. I tried to reinstall UGKG2. Failed again. Same error. Reinstalled the I9100 stock GB rom. Now the phone is working but I have a Rom not made for my carrier. I have all that junk that I don't want. I even realized that Bell is very good with it's bloatware.
So my question: What should I do to be able to make my phone works with UGKG2 again.
1) Should I reinstall UGKG2 with PIT and RE-Partition ticked this time? (it wasn't ticked last time)
2) Should I bring it to my carrier in order to be serviced?
3) Any other suggestions?
Thanks for all your help!
Click to expand...
Click to collapse
1. re-partition is very bad I think. You shouldn't have to touch anything in ODIN other than select the file you want to be flashed.
2. I don't think they are gonna help you if you have been using ODIN, but I could be wrong.
3. You should find this: I9100MUGLD3_I9100MBMCLD3_BMC (try to dl from HERE or just Google Bell stock ICS firmware). I9100MUGLD3_I9100MBMCLD3_BMC is the stock ICS firmware for Bell. Flash the TAR file using ODIN I think under PDA and not PIT. I think that should work. There are guides all over XDA to show you this so do a search before trying and follow steps in the guide you find and READ EVERYTHING YOU CAN, the more you read the better prepared you will be if something goes wrong. Actually you can flash any firmware you want the same way and then you should flash CF-Root kernel to obtain root and CWM recovery so you can never use ODIN again and just flash everything in CWM recovery. Once you get all set you should check out the development forums and I recommend to flash a custom ROM.
This is a good thread to browse through:
SGS2 Canadian Thread (Bell/Virgin/Sasktel/Rogers) Root/Unlock/Firmware/Modems/Mods
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
dingo dog said:
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
Click to expand...
Click to collapse
Hi - Thanks for the tip, but I already tried with my wife's laptop. Should have mentioned in the original post.
Thanks again.
Older versions of Odin do work on SGS3 .
evelopment where I thought it should go but I haven't posted at all before so it won't let me.
Development only posts not Q&A nothing to do with 10 posts .
Two thoughts could be the usual flashed multiple stuff and phone is confused plus wrong PIT file flashed .
Thats just firmware not hardware problem .
Or indeed at some stage Nand is corrupt .
Solution would be
Try correct PIT file first before a repair centre .
jje
Just wanted to say that I have the same problem, but mine is even more strange. I can boot into the system but I have to disable wifi and mobile data right away otherwise the phone will reboot after a couple of seconds. I see the phone if I connect it to the computer but I can not write or read the files on the phone. But I tried the toolbox and could push an apk to the phone.
CWM works but if I try to wipe or flash another rom it reboots, some stuff works and other just reboots the phone.
Download-mode works and Odin finds the phone but everything I have tried fails. I have tried standard stock firmware, 3 part firmware and PIT but it always hangs on NAND Write.
If anyone has some solution I would be thrilled.
Bananafische said:
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable
My problem:
[*]Won't boot into recovery
[*]Will boot into download mode
[*]Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
[*]Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
Thanks
Click to expand...
Click to collapse
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
Click to expand...
Click to collapse
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
I am glad that It worked for you
I am still stuck, I am guessing that if none of the PIT´s work then it is officially bricked?
u didn't try the link posted by me?
theonlyanil said:
u didn't try the link posted by me?
Click to expand...
Click to collapse
it dosen't work ,stop at Get PIT for mapping..
help me
Hy guys Im from Hungary and i would like to flash my i9300 tmobile phone. My question is: can i flash the poland xeo to it or i just have to wait for the official tmobile rom? Thank you!
Where did you got the pit file
Bananafische said:
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
Click to expand...
Click to collapse
Where did you got the pit file
Hello, the PIT Flash didn't work for me either.
I was CF-rooted while overseas and stupidly forgot to disable auto-updates. The tricky part was that the auto update probably was for a different region as I was in Europe when the brick happened, but I live in Singapore.
Have tried to flash the firmware several times using Odin and even the PIT but all have been unsuccessful. I've been stuck a "Firmware upgrade encountered an issue....".
Have been able to get to the download screen but not the recovery mode.
Any pointers or is my phone rightly bricked?
I fixed my half brick using Android 4.0.4 ICS XXLAF2 stock firmware
My old stuff is still on my sd card, but not usable tho :s
Any tips? cant seem to restore with rom manager. It only fails
Help with encrypted at&t GS3
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Hey Anil,
I have encrypted at&t samsung gs3 running CM10.1 nightly. For some reason I cannot undo the encryption. I want to use the method described on this link that you posted here to get rid of encryption.
I have downloaded official firmware from sammobile. But the .pit file available on that site is for internation version. I have at&t GS3 so i should be using the .PIT for at&t version. Could you please provide me .PIT for 16GB at&t Samsung galaxy s3, if you have one or you know the link? Ii appreciate your help.
please help me with this man.
-Ravi
Click to expand...
Click to collapse
Worked well
The method given by Anil worked fine.
And since my device was encrypted before, it asked me password after installing the firmware by Odin.
So for this I just entered recovery (Sam recovery) and did a factory reset, and the encryption was removed.:good:
Dude don't post ur serial or imie
Bananafische said:
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Click to expand...
Click to collapse
For ur own safety mate
Flashed Xperia's miui rom on S3-i9300
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
xcanpolatx said:
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
Click to expand...
Click to collapse
Before you pay for a repair you can try flashing stock rom via Odin .