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
Related
ANSWERED - Firmware Install - factory reset in recovery
I made a mess of a rom install rushing through rom Manager and now my phone can't get past the Samsung screen when booting, and I can't find out the version of my kernel to install the correct one without getting my phone on. I can get the phone into download mode and I have tried a number of different kernels but have had no luck. It's a UK phone so I know it's a XW or XX to start, I was wondering is their a kernel that works on any SGS2.
I have been having trouble with getting windows to recognize the phone and have found a number of fixes on this site which have worked and not worked (atm not connecting)
it's a sgs2 GT-i9100
Any advice greatly appreciated
Did you make a Nandroid backup? If so boot into recovery (vol up, power, home buttons) and restore the backup.
Can you get into recovery mode. Vol up plus home plus power. Then do a factory reset. this should get past the Samsung boot screen. Then flash another rom.
Sent from my ThinkPad Tablet using XDA App
Thanks for getting back, no unfortunately not, couldn't see recovery mode since the original failed rom install. That combination gets me to download mode now.
So as far as I can tell I need to get a firmware working properly or do a reset but I don't know which is the right firmware to use
Main thing is you can get to download mode. If you can do that, you can fix your phone 95% of the time.
You can find carrier/country specific firmware here or country-only/non-specific firmware here
owen5y said:
Thanks for getting back, no unfortunately not, couldn't see recovery mode since the original failed rom install. That combination gets me to download mode now.
So as far as I can tell I need to get a firmware working properly or do a reset but I don't know which is the right firmware to use
Click to expand...
Click to collapse
Just flash any CF-root kernel and then you have recovery back. Start flashing from there on.
Lennyz1988 said:
Just flash any CF-root kernel and then you have recovery back. Start flashing from there on.
Click to expand...
Click to collapse
I have tried a number of CF-root kernels and no joy. I tried a few more kernels this morning before work, including cf-root and siyahv2.6.4 and had no luck.
MistahBungle said:
Main thing is you can get to download mode. If you can do that, you can fix your phone 95% of the time.
You can find carrier/country specific firmware here or country-only/non-specific firmware here
Click to expand...
Click to collapse
I actually flashed some of those kernels XWKE1 for example and a few others with no joy.
The problem started when I tried to update the Galent Miui ICS which I see you are running. I (stupidly) didn't read through the statement as I had my NYE hungover and just put the update on my sd and used recovery to update which froze the phone at the boot screen. (I didn't do re-flash and I didn't wipe the data and everything else.) I know it sometimes takes time to boot but I had left it for a half hour to see if it would and no joy. I was no longer able to get to recovery mode so I tried a half dozen kernels with the same problems before putting up a post. I'm not sure would people find it inappropriate to talk about an this problem here, I thought as it's a kernel problem now it would be a better place to find the solution although my own lazy Miui install was the cause.
Flashing just the kernels obviously didn't fix the problem. Have you flashed any of the entire stock firmwares ? Choose the most recent firmware for your carrier/country from the first link I gave you (if there's more than two listed).
owen5y said:
I actually flashed some of those kernels XWKE1 for and a few others with no joy.
The problem started when I tried to update the Galent Miui ICS which I see you are running. I (studidly) didn't read through the statement as I was hungover and just pu the update on my sd and used recovery to update which froze the phone at the boot screen. I know it sometimes takes time to boot but I had left it for a half hour to see if it would and no joy. I was no longer able to get to recovery so I tried a half dozen kernels with the same problems before putting up a post.
Click to expand...
Click to collapse
MistahBungle said:
Flashing just the kernels obviously didn't fix the problem. Have you flashed any of the entire stock firmwares ? Choose the most recent firmware for your carrier/country from the first link I gave you (if there's more than two listed).
Click to expand...
Click to collapse
Yes I will try that. At work currently and so can't play with the phone. I will post the result this evening.
Thanks
NP. Let us know how you get on.
MistahBungle said:
NP. Let us know how you get on.
Click to expand...
Click to collapse
All good, I installed the firmware and was able to get into recovery mode from there. Did a factory reset because I was stuck in a boot loop. Going to give it a go again to upgrade to the new ics build. Any advice on the best process of getting there?
I installed the following firmware prior to the reset
UK
XWKE1:http://www.multiupload.com/15RY5CHHW9
Firmware info: PDA: XWKE1 Phone: NEKD5 CSC:H3GKD4
Yep. Given the problems you've been having, stay away from the currently alpha ICS builds that are floating around.
Frankly, that's a disaster waiting to happen.
Wait until CM (or someone else) releases something that's stable and has most things working in 4-6 weeks or so.
There's a ton of roms/kernels out there, do your research/reading & ask questions if necessary in the respective threads for those & then pick something out & try it.
And no, I don't do recommendations. Because nobody's phone come's out of the factory the same, nobody has the same phone setup & nobody uses the phone the same way.
owen5y said:
All good, I installed the firmware and was able to get into recovery mode from there. Did a factory reset because I was stuck in a boot loop. Going to give it a go again to upgrade to the new ics build. Any advice on the best process of getting there?
I installed the following firmware prior to the reset
UK
XWKE1:http://www.multiupload.com/15RY5CHHW9
Firmware info: PDA: XWKE1 Phone: NEKD5 CSC:H3GKD4
Click to expand...
Click to collapse
OK, I did like the Galnet Miui ICS rom I was running although there was a few bugs with it when it died it was difficult to charge again. That's fair if you don't want to give out recommendations it's shooting in the dark over the interenet I suppose. I will have a good look through the forum and se if I find something that I would think is suiting.
Thanks for your help, and the advice is appreciated
I have a mac, so no odin, and Heimdall won't recognize my sgs2. Originally i rooted my phone with a shell script. I then used Rom Manager to install Cyanogenmod 7.1. All was good til I decided to give ICS a spin, so I downloaded kp8 from this thread:
http://forum.xda-developers.com/showthread.php
And tried to flash using Mobile Odin. It flashed, rebooted, and now I am stuck at the boot screen. I am guessing that maybe I needed to get a CF-Recovery compatible build??
Anyways, just want to get back in working condition. I currently have no way to mount the sd card (no sd card mount option in normal recovery), so I have to wait until tomorrow when I can borrow a friends phone. Should I just try to update to a CF- kernel?
Do I need a pc?
Thanks
Do you have CWM recovery, or stock recovery?
If you have CWM recovery boot into it and wipe data/cache and it may boot or flash a rom of your SD card.
Otherwise borrow someones PC and use odin to flash back to GB, make sure to flash the GB bootloaders first. (On that note, did you flash the ICS bootloaders? As if you didnt that might be why its not booting)
Do you have CWM recovery, or stock recovery?
Click to expand...
Click to collapse
stock
Otherwise borrow someones PC and use odin to flash back to GB, make sure to flash the GB bootloaders first. (On that note, did you flash the ICS bootloaders? As if you didnt that might be why its not booting)
Click to expand...
Click to collapse
Wasn't aware I needed to, sounds logical. I'll do some more research before trying again.
Thanks
j_s_1 said:
stock
Wasn't aware I needed to, sounds logical. I'll do some more research before trying again.
Thanks
Click to expand...
Click to collapse
Yup, you need new bootloaders for ICS, but beware, the current ICS leaks are buggy and not really ready to be daily drivers.
As you have stock recovery, I would just borrow someones PC and use odin to flash stock gingerbread back.
never mind
Just an update. I got the ability to copy files to my sd card. I have tried to do an update from sd card with
i9100XXKG1
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4
Both resulting in "Signature verification failed".
As you have stock recovery, I would just borrow someones PC and use odin to flash stock gingerbread back.
Click to expand...
Click to collapse
Is my only recourse to find a pc or should I try something else? If I get a pc I will only have access to it for a short time, so want to make sure I am trying the right things.
That flash failed as Rom Manager likely broke recovery (has happened to me in the past, Rom Manager - bad).
PC as previously advised. I'd say you've exhausted all the non-PC options.
j_s_1 said:
Just an update. I got the ability to copy files to my sd card. I have tried to do an update from sd card with
i9100XXKG1
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4
Both resulting in "Signature verification failed".
Is my only recourse to find a pc or should I try something else? If I get a pc I will only have access to it for a short time, so want to make sure I am trying the right things.
Click to expand...
Click to collapse
Ok. And one last question, as far as flashing stock gingerbread (or a diff stock ROM), what would be the best, safest package to try? I do not know my kernel version, and can't find out (as I can't boot)
My phone is the international version of sgs2, purchased in Germany, csc code DBT.
searching for stock gingerbread for my phone seems to come up with a bunch of different builds.
Thanks
KI4 seems to be the most recent in Intra's thread, so I'd go with that. Not that it makes a massive amount of difference tho.
j_s_1 said:
Ok. And one last question, as far as flashing stock gingerbread (or a diff stock ROM), what would be the best, safest package to try? I do not know my kernel version, and can't find out (as I can't boot)
My phone is the international version of sgs2, purchased in Germany, csc code DBT.
searching for stock gingerbread for my phone seems to come up with a bunch of different builds.
Thanks
Click to expand...
Click to collapse
Update:
Got a pc and got odin working. Flashed MultiCSC_OXA_I91000XXKI2.tar . rebooted and it tried to go into recovery mode then gave me a dead robot with a red exclamation point, which doesn't seem good.
Ideas?
UPDATE:
Nevermind, I just had to get the full firmware :
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
for DBT (Germany). Flashed with Odin and I am back. Awesome. Thanks
I did say to get KI4 from Intratech's thread, didn't I ? Anywho, glad you got you phone working again
j_s_1 said:
Update:
Got a pc and got odin working. Flashed MultiCSC_OXA_I91000XXKI2.tar . rebooted and it tried to go into recovery mode then gave me a dead robot with a red exclamation point, which doesn't seem good.
Ideas?
UPDATE:
Nevermind, I just had to get the full firmware :
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
for DBT (Germany). Flashed with Odin and I am back. Awesome. Thanks
Click to expand...
Click to collapse
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 .
I'm in a bit of a tight situation over here. My mom's phone was having issues, so she wanted me to fix it before I left to visit my grandparents. I found a stock ROM for the phone (GT-i9100 International) and flashed it, but the phone always got stuck on the "Samsung Galaxy SII GT-I9100" boot screen (occasionally it would show the "O2" screen, as it was a ROM for Ireland). I tried a different ROM (can't remember what country it was), and I'm still stuck with the same problem. This time no O2 screen though. I've downloaded my ROMs through sammobile.com and I'm using ODIN v1.83.
The label under the battery reads:
Model: GT-I9100
SSN: -I9100GSMH
What ROM should I use and where can I get it? I found this thread with a link to the ROM for the international version, but Hotfile has been shut down, so I can't download it.
Sorry if I could've found the answer with a few more hours of searching, but I've got less than 24 hours to find a fix and I was hoping that someone else could help me. Thanks a lot!
EDIT: I'm in the U.S., if that matters.
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Any region?
MistahBungle said:
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Click to expand...
Click to collapse
Should any region work to get the phone up and running? I just need to get it back up so that I can root it and flash CM10. Thanks.
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
MistahBungle said:
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
Click to expand...
Click to collapse
Is 4.1.2 OK, or should I go for 4.0.3 or below?
Doesn't matter, take your pick.
More info on problem
I tried installing two other ROMs (from androidfirmwares.net), one 4.1.2 and one 2.3.6. The 4.1.2 didn't get me anywhere, but after I flashed 2.3.6 the phone said the assert check failed. GT-i9100 is on the list of what it checked for. (I've never had any luck with the assert checks on any of my Samsung phones: GS Captivate, GSII Skyrocket, or AT&T GSIII. I've always had to remove the check in my update script.) I attached a picture.
EDIT: Since the attachment doesn't seem to be working, here's a Dropbox link.
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
MistahBungle said:
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
Click to expand...
Click to collapse
My process:
Open ODIN v3.09
Plug in the phone, already in download mode.
Click the AP button and load my .tar.md5.
Click Start.
Wait for it to finish, leaving the phone untouched on the table.
I just tried another USB cable, but to no avail. I've also tried unplugging the phone right after it reboots and ODIN says "PASS!", but no luck there either. I just tried another ROM that just finished downloading and it's giving me a similar getprop() error. At the bottom of the output in red it says:
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I don't think there's any way for me to edit the update script, as the tar contains a bunch of filesystem images. Even if it was easy to edit it would ruin the checksum verification.
Check out the picture on Dropbox here.
What are you trying to do in Android recovery ? Given what your stated aim is - get a stock rom on the phone, re-root it, put custom rom on, you shouldn't be using Android (I.E stock) recovery at any stage.
The process should be:-
*Flash stock rom with Odin in download mode (I.E phone off - home/vol down/power, not home/vol up/power)
*Root phone with whatever method
*Flash custom rom with CWRecovery, which you'll get once you root the phone
So....You need to go step by step. Start with flashing the stock rom with Odin, and try to boot the phone normally/make sure that was successful before doing the next two steps. Look for Hopper8's 'Odin troubleshooting' guide if you're having trouble getting a successful Odin flash.
Once you've done that, root the phone & make sure you have CWRecovery working, then flash the custom rom.
The phone boots to the recovery screen after it finishes flashing with ODIN. I put it into download mode, run ODIN, and then it that error screen comes up on the next reboot.
Try flashing the three part firmware linked to in Hopper's thread first (this will wipe the phone). I can't help but think we're missing some info re: what's been done to the phone previously here if the phone is booting into recovery mode after being Odin flashed. It shouldn't do that. After an Odin flash/pass the phone should boot normally, assuming it's not a case of the NAND being corrupted (it probably wouldn't boot into recovery if that was the case/you'd be left with constant bootloop)
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
MistahBungle said:
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
Click to expand...
Click to collapse
At the top of the download mode screen it says "PRODUCT NAME: GT-i9100". I don't know any other way to tell besides this and the sticker on the back. There are no carrier markings anywhere, and this phone was purchased because it had an FM radio, which only the international version had.
And assuming by "Hopper's thread" you mean this one, I can't because the files are no longer available.
In that case, you're stuck with the other suggestions to try in his thread & continuing to flash stock roms until you get a properly successful flash I.E phone boots/works normally. There might be something really obvious here being missed, but because we're not there with you/don't have the phone in front of us it might be difficult to work out.
It's working!
Yay, I got it to work! I flashed a custom kernel (jeboo), which allowed me to get into CWM. From there I sideloaded CM10 and now it's up and running! Only I still have a problem with internal storage... (That was the problem I was trying to fix originally.) Would the next thing to try to fix that be flashing a PIT file? If so, any tips for doing that?
I'm going to put off trying to fix that problem and do it when I get back. For now it works as a phone, and that's what's most important to her anyway. Thanks for your help MistahBungle.
Solved!
For anyone else who comes across this thread, I was able to solve my problem permanently by flashing a new PIT file. I found the correct PIT files for the GT-i9100 in this XDA thread. It seemed my partitions had become messed up long ago, as the phone had been showing a 2GB /data partition and only a 2GB internal SD card partition (which should've been closer to 12GB) for some time.
I choose a 4GB data partition (since I was running low on /data space last time). Oddly enough, booting the stock ROM after flashing the PIT only showed a 2GB data partition. Once I flashed CM10 it showed as 4GB though.
Hi,
I got my hands on an i9300 that the previous owner had broken while trying to do a sim unlock.
I've tried flashing various ROMs and recoveries using Odin (1.85 and 3.07), and also from within the recovery.
I'm not able to determine if the EFS partition is completely intact, but I believe it is.
So far I have tried flashing the rescue firmware (http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6), various stock firmwares, resurrection remix, android revolution hd, and a few others.
I have philz recovery installed at the moment, and have tried the latest CWM as well.
I've even tried using kies to do an emergency recovery, but this also failed.
No matter what I do, I'm unable to make the phone boot up.
I do have adb access to it.. Anyone got any suggestions for what else I can try?
In odin mode it *does* display the model number, so from this I believe that it is safe to say that the emmc is still ok.
Any thoughts or suggestions?
Cheers!
Try the latest threepart stock firmware for the region (CSC) the phone originally comes from and flash firmware including PIT file (re-partition is ticked then). This solved my booting problems in such cases.
Edit: maybe also the bootloader is f***ed, does it start up to the Samsung logo or nothing at all?
If nothing at all it might be the bootloader, in this case there is SD-Bootloader-repair-files floating through the net, allowing you to repair bootloader just from your external SDcard - i9300 only.
Benko111 said:
Try the latest threepart stock firmware for the region (CSC) the phone originally comes from and flash firmware including PIT file (re-partition is ticked then). This solved my booting problems in such cases.
Edit: maybe also the bootloader is f***ed, does it start up to the Samsung logo or nothing at all?
If nothing at all it might be the bootloader, in this case there is SD-Bootloader-repair-files floating through the net, allowing you to repair bootloader just from your external SDcard - i9300 only.
Click to expand...
Click to collapse
I'll see about getting the latest 3 part stock, though that seems fairly similar to the rescue firmware I linked to - it includes a pit file.
Shall give it another go though
I do get the samsung logo/text, as from a standard boot, and then it launches straight into recovery.
Cheers,
EqUaTe
EqUaTe said:
I'll see about getting the latest 3 part stock, though that seems fairly similar to the rescue firmware I linked to - it includes a pit file.
Shall give it another go though
I do get the samsung logo/text, as from a standard boot, and then it launches straight into recovery.
Cheers,
EqUaTe
Click to expand...
Click to collapse
Ok, so bootloader is fine. This seems to be strange, how can you have ADB access if you can't boot up thus USB debugging's not enabled?
I had a similar disaster lately with Note 3, a real pain in the a** updating to KK. Also the 'firmware encountered blabla...' message, I got this fxed by flashing latest CWM right after the stock firmware flash, then it would finally boot.
Your case is different though since you even do get into recovery. Deep down I'm positive you just need to find the correct PIT resp. 3-part stock ROM.
Benko111 said:
Ok, so bootloader is fine. This seems to be strange, how can you have ADB access if you can't boot up thus USB debugging's not enabled?
I had a similar disaster lately with Note 3, a real pain in the a** updating to KK. Also the 'firmware encountered blabla...' message, I got this fxed by flashing latest CWM right after the stock firmware flash, then it would finally boot.
Your case is different though since you even do get into recovery. Deep down I'm positive you just need to find the correct PIT resp. 3-part stock ROM.
Click to expand...
Click to collapse
philz recovery has adb support built in, that's how I've accessed it. I believe CWM used to, but it doesn't seem to anymore.
Do you know which firmwares are likely to have the PIT file separately? I've got one downloading at the moment, but no guarantee it'll have the various files individually. Most of the ones I've come across are AIO files.
EqUaTe said:
philz recovery has adb support built in, that's how I've accessed it. I believe CWM used to, but it doesn't seem to anymore.
Do you know which firmwares are likely to have the PIT file separately? I've got one downloading at the moment, but no guarantee it'll have the various files individually. Most of the ones I've come across are AIO files.
Click to expand...
Click to collapse
Alright, never used philz 'cause I always loved TWRP, this could be a reason though
Well, they are hard to find indeed. On a quick random search I found this JB ROM:
http://uploaded.net/file/p8e4pasy
Though I must say I always had best results when repairing persistent devices with older firmwares, so I got used to finding the exact
version installed when factory delivered, when issues are fixed updating is no problem.
Have set that file downloading, and have also grabbed TWRP.
Will give it a shot when I get home from work tonight. Cheers for your help so far Sometimes it helps just to have another set of eyes on these things!
Balls.. That link is a passworded zip. Don't suppose you came across the password for it?
EqUaTe said:
Balls.. That link is a passworded zip. Don't suppose you came across the password for it?
Click to expand...
Click to collapse
Ok, found the password.. Extracting a bunch of zips atm, fingers crossed one will help!
Benko111 said:
Alright, never used philz 'cause I always loved TWRP, this could be a reason though
Well, they are hard to find indeed. On a quick random search I found this JB ROM:
http://uploaded.net/file/p8e4pasy
Though I must say I always had best results when repairing persistent devices with older firmwares, so I got used to finding the exact
version installed when factory delivered, when issues are fixed updating is no problem.
Click to expand...
Click to collapse
So, I've now flashed that 3-part ROM, sadly with no joy - it does the same.
It has made me go back and look at your earlier comments, and made me wonder if the logo we each refer to is the same one, so I'm attaching an image..
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
EqUaTe said:
So, I've now flashed that 3-part ROM, sadly with no joy - it does the same.
It has made me go back and look at your earlier comments, and made me wonder if the logo we each refer to is the same one, so I'm attaching an image..
Click to expand...
Click to collapse
It is indeed what I meant. If it was the bootloader it most likely wouldn't do a thing anymore.
But k-semler above this post is absolutely right, I forgot to pay attention to what model size you've got?
Of course PIT is different for 16 or 32GB model.
Just in any case, I attached two PIT from my collection, DBT region for 32GB model, you've got a 16GB one above (use his firmware with that), flash the size according to your model and try once again. Eventually it should work.
If your phone was branded originally, find the original branded firmware and try as well.
That's all I can think of right now.
Benko111 said:
It is indeed what I meant. If it was the bootloader it most likely wouldn't do a thing anymore.
But k-semler above this post is absolutely right, I forgot to pay attention to what model size you've got?
Of course PIT is different for 16 or 32GB model.
Just in any case, I attached two PIT from my collection, DBT region for 32GB model, you've got a 16GB one above (use his firmware with that), flash the size according to your model and try once again. Eventually it should work.
If your phone was branded originally, find the original branded firmware and try as well.
That's all I can think of right now.
Click to expand...
Click to collapse
It's the 16gig model, will have another go this evening
k-semler said:
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Click to expand...
Click to collapse
I'm curious, which version of Odin did you use when you fixed yours?
Interestingly, while I've had it available before, the bootloader update tickbox isn't available on 3.07/3.09 at the moment, stays grayed out..
Going to give 1.85 a whirl
So flashing with 1.85 has resulted in the same thing.. Wondering if it may actually be a 32gb one.. I don't think it is, but at this point I have no idea.. Are there any identifiers that distinguish it on the unit itself? FCC ID, SSN, etc.
Fairly sure it's not a 32gb as it hangs flashing if I use that pit.. Trying another flash at the moment.
So no joy with this so far.. Getting a bit annoying really, tried quite a few combinations now..
Fairly certain at this point it's a 16GB model, using the 16GB PIT I can flash other ROMs, but no joy on actual resurrection of the device.
Odin logs seem fine, with and without a bootloader update.. After the ROM flash, sometimes I get the Android with the spinning polygon for a while with a new progress bar, followed by a further reboot, and then the sick android (little red triangle coming out his chest).
All stock roms have the following text at the bottom (though the actual position varies from rom to rom as some of them have recoveries at much higher res than others):
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VOD
Successfully applied multi-CSC.
And yes, the typo is on the screen.. Appling.. Really?
Anyway, don't know if that is normal (while I've used other s3's, I can't remember what they showed with stock recovery as I rooted them pretty early on, and never really touched them again).
I can say I'm glad I still had the jig from my s2, as it makes getting into download mode much easier
I've tried several odin versions, different USB ports, different cables.
I can go through and provide details of the various ROMs I have downloaded, the majority of which are stock at the moment, and am happy to grab others if people think they may work..
Cheers,
EqUaTe
That's not nice, still busy with it... I must say, when I read the bit you wrote
After the ROM flash, sometimes I get the Android with the spinning polygon for a while with a new progress bar, followed by a further reboot
Click to expand...
Click to collapse
I thought yay, that sounds promising. That is exactly what happens after a successful stock flash. Also
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VOD
Successfully applied multi-CSC
Click to expand...
Click to collapse
is absolutely normal (incl. the spelling). The question is why does it not boot into system then? After a (what I consider) successful flash and then in stock recovery, have you tried a factory reset/wipe cache? Please try this urgently.
In my optinion you can stick to Odin 3.09, I could never confirm the reports of different versions working with certain devices, at least not with the new ones. Re-partition is forced and mostly greyed out when a PIT file is flahed with the ROM. Without PIT it should be not greyed out.
Benko111 said:
That's not nice, still busy with it... I must say, when I read the bit you wrote
I thought yay, that sounds promising. That is exactly what happens after a successful stock flash. Also
is absolutely normal (incl. the spelling). The question is why does it not boot into system then? After a (what I consider) successful flash and then in stock recovery, have you tried a factory reset/wipe cache? Please try this urgently.
In my optinion you can stick to Odin 3.09, I could never confirm the reports of different versions working with certain devices, at least not with the new ones. Re-partition is forced and mostly greyed out when a PIT file is flahed with the ROM. Without PIT it should be not greyed out.
Click to expand...
Click to collapse
I figured the spelling was normal, just a little disappointing Also thought it was normal that this appeared, but wasn't sure. Makes sense though.
I have tried a factory reset after pretty much every flash attempt, but will give it another go. Getting to the point where i'm tempted to try and do the sd card recovery, just to see if there is something fundamentally broken at that level.
I'm also downloading the latest ROM for the carrier (Vodafone UK) to see if flashing that here makes any difference..
Well, factory reset and wipe cache don't help. Other ROM won't be donwloaded for a bit, so will have to try it after work. grr.