OK, I'm probably gonna sound like the biggest noob ever... but here it goes:
I never made a nandroid backup when I flashed my first rom and I have been flashing different ones since I flashed my first one. About a week ago, I flashed AOKP Milestone 5 ICS Rom. It was running PERFECT until today. I opened the Youtube app and while I was watching a video, the Tab just froze and rebooted. This resulted in a bootloop. I don't have any other roms on the internal memory and it didn't work when I tried reflashing the rom. Does anyone have any advice on how to fix this?
Again, sorry for being so stupid and thanks in advance.
Did you wipe data and dalvik cache? Other than that, you can download the stock rom from www.sammobile.com and flash it with odin.
Sent from my amazing 10.1 galaxy tab
I did wipe but I couldn't find the stock rom from the website, could you give me the direct link to the website?
Here is the link: http://www.sammobile.com/firmware/ . type P7500 and you should get a list with different regions and their latest updates.
This happened to me too. I tried flashing different ROMs as well as flashed CWM again, but only flashign a stock ROM works. Something about a damaged bln.
anushajayanti said:
Here is the link: http://www.sammobile.com/firmware/ . type P7500 and you should get a list with different regions and their latest updates.
This happened to me too. I tried flashing different ROMs as well as flashed CWM again, but only flashign a stock ROM works. Something about a damaged bln.
Click to expand...
Click to collapse
OK, I have downloaded the rom, now how do I flash it onto the device? My guess is with Odin.
1canine2 said:
OK, I have downloaded the rom, now how do I flash it onto the device? My guess is with Odin.
Click to expand...
Click to collapse
Correct. Unzip it first, so you have a .tar file. Then put it in PDA field in odin and have fun!
Sent from my amazing 10.1 galaxy tab
Related
I've spent the last 2 days trying to fix my mistake. I have the GS2 ATT version, and I didn't realise there was a difference between that and the GTI9100 S2.
I wanted to give some tips I learned on how to recover your phone if you make this mistake.
First, here are some posts you'll want to look at:
http://forum.xda-developers.com/showthread.php?t=1286432 - Stock firwmware
http://forum.xda-developers.com/showthread.php?t=1285823 - Clockworkmod for the ATT
http://forum.xda-developers.com/showthread.php?t=1286192 - Cyanogenmod for our phones.
Using Odin and the stock firmware, you can recover your phone to a 95% working state. Once I got my stock firmware on there, I found that while making calls my phone made no sound, and the mic didn't work. The mic did work when I wasn't making calls though.
I reflashed the modem.bin file found on the stock firmware, not sure if its required but that is what I did first. Then, I unpacked the rooted stock firmware, and flashed JUST THE zImage file. After doing this, I rebooted, and my calls were working again.
After that, I installed the correct version of Clockworkmod, and then CM7 nightly. Now everything seems to be running great on my phone.
Hope this helps someone out there,
-Orbital
Good job thanx man.
Sent from my SAMSUNG-SGH-I777 using XDA App
Been awhile since I messed w/ android. I forgot about the different models myself until I realized I was spending half my day in the wrong section
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Alucardis666 said:
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Click to expand...
Click to collapse
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Alucardis666 said:
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Click to expand...
Click to collapse
Those are NOT for our version of the GS2, International only. Our version is here in the development forum.
Sent from my SGH-I777 using xda premium
Yes, it will return a status error 7 which means it's unmatched. Ask me how I know. I flashed international roms last night and used this fix to get me good again.
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
connexion2005 said:
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
Click to expand...
Click to collapse
The simple thing would be to change out the sec_touchkey.kl with rootexplorer and take the sec_touchkey from system/usr/keylayout should fix the i9100 rom to work with the i777. Seeing as how this worked for the Captivate *i897* for jvr, jvs, and jvt darkyrom releases and I would assume that it would work.
daraj said:
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
Click to expand...
Click to collapse
Personally I would think that you had a bad flash? Did you flash through Odin or CWM? From what I have been reading the gb bootloaders between the i777 and i9100 are different and I can see if you used a custom i9100 rom flashing via cwm could cause that. Since I am not too sure on the sgs2 if the differences between the euro models versus the carrier locked, the Kernel will not fix the button mapping, I learned this with the captivate when I switched over to using DarkyRom jvr and jvs builds since they were the most stable of GB for the i897 captivate. Plus if you are going to run a i9100 rom, I am sure the modem will not work with the att kernel. Especially if the situation with the cappy is any indication that att kernel needs att modem and i9000 kernel needs i9000 modem. I will be able to know more as soon as I get my i777 tomorrow.
HTH,
Charlie
Does anyone know how to remove the i9100 splash screen?
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
spbluffmaster said:
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
Click to expand...
Click to collapse
wipe data/factory reset
tried that three times... didnt help..
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
DiscipleDOC said:
Does anyone know how to remove the i9100 splash screen?
Click to expand...
Click to collapse
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1311975
re: get rid of i9100 boot logo
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
Use a download mode jig or flash entropy 512's stock TAR kernel with Odin from the link below.
http://forum.xda-developers.com/show....php?t=1286432
Good luck!
highaltitude said:
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
Click to expand...
Click to collapse
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Entropy512 said:
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Click to expand...
Click to collapse
i messed up and flashed an i9100 rom and am having the call prob u described. can i just flash the modem or stock rooted kernel and be back to 100%? if so do i use odin and do i need to check the box for repartition or anything like that? thx in advance!!!
Is it possible to download back the old stock rom through ODIN and reinstall it on my ace? Or can I install it with CMW too from the SD card? Or is there some deleting and complexity involved in this backwards process?
Sure, you can instal any stock rom on your phone. Just have to have the firmware files. I just flashed back stock 2.3.4 after 7.1 CM BehradGH. And istaled BehradGH again I don't think u could instal any stock rom via CWM. Specialy the lower version u have.
Wojtys said:
Sure, you can instal any stock rom on your phone. Just have to have the firmware files. I just flashed back stock 2.3.4 after 7.1 CM BehradGH. And istaled BehradGH again I don't think u could instal any stock rom via CWM. Specialy the lower version u have.
Click to expand...
Click to collapse
Lmao nah bro it failed. I tried flashing it through ODIN and installing the stock 2.3.5 again and the phone was stuck in an endless boot. I got scared as hell and reflashed back to CM 7.1. I have no idea what happened though but everything is working fine. I guess I'll be sticking to CM7.
The reason I wanted to go back was because Heywire (txting app) was the only thing that stopped working after I flashed. I depend a lot on texting and I was thinking it'd go back if I went back to stock. I guess I'll have to try and find another alternative :/
Phone feels like a super phone though. LONG LIVE CM7!
Well, I'm not a developer or advenced user so I can't tell u the reason why you phone stuck in on boot. Today i was broke my CM7.1 Behrad and i could only go to download mode so i flash official 2.3.4 KPH and it's worked. Next i instaled CWM and BehradGH' rom again. Before useing BehradGH's rom i had Grif's KANG rom and after that i flash stock 2.3.4 to instal another CM7.1. It wasn't first time so I'm sure of that what i write here
Haha. I'm guessing we were both pretty lucky then. The first thing I did was to make sure I could boot into recovery. Then I reflashed CM7 from there. I'm still curious about the boot loop thing... I hope someone answers.
You need to flash a full package to not have a bootloop.
SuperAce609 said:
Lmao nah bro it failed. I tried flashing it through ODIN and installing the stock 2.3.5 again and the phone was stuck in an endless boot. I got scared as hell and reflashed back to CM 7.1. I have no idea what happened though but everything is working fine. I guess I'll be sticking to CM7.
The reason I wanted to go back was because Heywire (txting app) was the only thing that stopped working after I flashed. I depend a lot on texting and I was thinking it'd go back if I went back to stock. I guess I'll have to try and find another alternative :/
Phone feels like a super phone though. LONG LIVE CM7!
Click to expand...
Click to collapse
If u wer on cm7, then u should flash a full package bcoz cm7 converts ur system from rfs to ext. So wen u flash a full package, ur system is converted back to rfs.
Sent from my GT-S5830 using Grif's CyanogenMod
Dont jus say thanks, use d 'Thanks' button. [XDA-RULE]
Oh I see. How do I flash the whole package then?
SuperAce609 said:
Oh I see. How do I flash the whole package then?
Click to expand...
Click to collapse
You need to download something called a 5 file package, extract and then in Odin you deselect 'one package'. Generally for stock ROMs you select
OPS - cooper.ops
BOOT - APBOOT.......tar.md5
PHONE - MODEM......tar.md5
PDA - CODE......tar.md5
CSC - CSC.......tar.md5
easswar said:
You need to download something called a 5 file package, extract and then in Odin you deselect 'one package'. Generally for stock ROMs you select
OPS - cooper.ops
BOOT - APBOOT.......tar.md5
PHONE - MODEM......tar.md5
PDA - CODE......tar.md5
CSC - CSC.......tar.md5
Click to expand...
Click to collapse
Oooohh that. I remember doing that once before when I was flashing stock roms on my ace. Can you provide a link to these 5 file downloads? Thanks *clicks*
It's not 5 downloads.
Sammobile.com, find the KPH file. I know it's confirmed to be a full package.
It seems samfirmware.com is not updated with latest firmwares. So u can try sammobile.com which is updated.
Sent from my GT-S5830 using Grif's CyanogenMod
Dont jus say thanks, use d 'Thanks' button. [XDA-RULE]
dunno about now, but a long time back when i was flashing stock KPN, samfirmware.com had a one file KPN, so i flashed a 5 file KPE and then the KPN...
I think KPN is supposed to be better than KPH which was a leaked ROM.
SuperAce609 said:
Oooohh that. I remember doing that once before when I was flashing stock roms on my ace. Can you provide a link to these 5 file downloads? Thanks *clicks*
Click to expand...
Click to collapse
See attachment. Cooper.ops and Odin is already included in the zip file, just extract it. Happy flashing
http://hotfile.com/dl/134788696/23d069d/S5830XXKPH.rar.html
SuperAce609 said:
Haha. I'm guessing we were both pretty lucky then. The first thing I did was to make sure I could boot into recovery. Then I reflashed CM7 from there. I'm still curious about the boot loop thing... I hope someone answers.
Click to expand...
Click to collapse
Hey!
I think you was flashed the ONE package file, but jeah, you need MULTI package file for ODIN, flash from CM to STOCK ROM.
Just read the FLASHING TUT. before flashing!
CHEERS!
To back to stock rom i always use Odin Didn't said i do this by recovery. And always use multi-file pack. Never "one package" - some1 said it is unstable... So go to Download Mode and flash ur Ace by useing Odin and multi-file rom (OPS, PDA, BOOT, PHONE, CSC)
casiocas said:
Hey!
I think you was flashed the ONE package file, but jeah, you need MULTI package file for ODIN, flash from CM to STOCK ROM.
Just read the FLASHING TUT. before flashing!
CHEERS!
Click to expand...
Click to collapse
I know how to flash stock roms. I've been doing so since 2.2. I'm talking about going from custom to stock xD. But thanks for the link anyways, saving it just in case
droidtwoseven said:
See attachment. Cooper.ops and Odin is already included in the zip file, just extract it. Happy flashing
http://hotfile.com/dl/134788696/23d069d/S5830XXKPH.rar.html
Click to expand...
Click to collapse
Thanks a whole bunch! I didn't make a back up of my stock rom before flashing so it's really good to have this.
Wojtys said:
To back to stock rom i always use Odin Didn't said i do this by recovery. And always use multi-file pack. Never "one package" - some1 said it is unstable... So go to Download Mode and flash ur Ace by useing Odin and multi-file rom (OPS, PDA, BOOT, PHONE, CSC)
Click to expand...
Click to collapse
Unstable how? I've always used one packages for flashing stock roms and they've worked perfectly. Unless you're talking about the performance of the rom?
SuperAce609 said:
Unstable how? I've always used one packages for flashing stock roms and they've worked perfectly. Unless you're talking about the performance of the rom?
Click to expand...
Click to collapse
It's not unstable. You will only get boot problems flashing across android versions using one package files.
Hello guys,
I am experienced in flashing roms and whatever... I already did this hundreds of times with a Galaxy S, Asus Transformer and now with my Galaxy Nexus.
I have a Galaxy Tab 10.1 (3G+wifi). I tried to install CM9 but it didn't work. And man... I really tried a loooot!!!
Well... now I am trying to use the regular stock rom in my Galaxy Tab and everytime the screen turns itself off and I turn it on again, it flickers!!! It's VERY annoying since I have to turn off the tablet to be able to use it again.
I have a nandroid backup and I restored it, but it didn't work... it still flickers!!! =P
I also tried to flash some recovery files: http://droidbasement.com/db-blog/?p=2487 like you guys recommended in some other posts.
But it didn't work, too.
Guys... I am getting a little desperate in here... I have been searching for an answer for this for days.
Can anyone help me, please?
Have you tried to use ODIN to flash back to stock?
9xnine said:
Have you tried to use ODIN to flash back to stock?
Click to expand...
Click to collapse
Hello 9xnine, thank you for your reply. Unhappily I don't have a stock rom (and it seems there's none available - Brazil's model).
Anyway restoring a nandroid backup (like I did) would be the same than flash a stock rom back, right?
Theoretically yes but I often find that Nandroid's won't work for a number of reasons. ODIN is and always has been my friend.
Try this. Looks like the ZVV build is for Brazil
http://samsung-updates.com/device/?id=GT-P7500
Questions go in the Q&A section - not the Dev section
carlos_online said:
Can anyone help me, please?
Click to expand...
Click to collapse
Flash by Odin rom from this link:http://www.hotfile.com/dl/145473375/7dd41d4/P7510UEKMP_P7510XABKMP_XAB.zip.html
This is a rom for 7510 but it works with 7500. Then you have to upload the latest CWM and CM9.
For me it works.
The method described in this issue.
http://forum.xda-developers.com/showthread.php?t=1555984
niuniek24w said:
Flash by Odin rom from this link:http://www.hotfile.com/dl/145473375/7dd41d4/P7510UEKMP_P7510XABKMP_XAB.zip.html
This is a rom for 7510 but it works with 7500. Then you have to upload the latest CWM and CM9.
For me it works.
The method described in this issue.
http://forum.xda-developers.com/showthread.php?t=1555984
Click to expand...
Click to collapse
THANKS MAN!!!! IT WORKED LIKE A CHARM!!!!! THANK SOOOOOO MUCH!!!!!!:highfive:
After Upgrade my i9100g from stock ICS to Stock Official JB 4.1.2 France...my touch screen not functioning properly...
but when plugin to charger or usb its back to normal and smooth...
it never happen when i using stock ics and custom ROM...
example : when i try to draw 'S' it will be like on the picture...
it hard and imposible to drag and drop item..
i have try reflash and redownload firmware 5-6 times also root and w/o root but the problem still same...
sinsai said:
After Upgrade my i9100g from stock ICS to Stock Official JB 4.1.2 France...my touch screen not functioning properly...
but when plugin to charger or usb its back to normal and smooth...
it never happen when i using stock ics and custom ROM...
example : when i try to draw 'S' it will be like on the picture...
it hard and imposible to drag and drop item..
i have try reflash and redownload firmware 5-6 times also root and w/o root but the problem still same...
Click to expand...
Click to collapse
Did u update via kies or odin?
If u used a firmware and flashed via odin, please try another firmware.
Over this try to do a factory reset after u flashed the FW.
CHEERS
sinsai said:
After Upgrade my i9100g from stock ICS to Stock Official JB 4.1.2 France...my touch screkeen not functioning properly...
but when plugin to charger or usb its back to normal and smooth...
it never happen when i using stock ics and custom ROM...
example : when i try to draw 'S' it will be like on the picture...
it hard and imposible to drag and drop item..
i have try reflash and redownload firmware 5-6 times also root and w/o root but the problem still same...
Click to expand...
Click to collapse
Well your phone is i9100g... You sure you flashed ROM of i9100g and not of galaxy s2 i9100...coz many people make that mistake..
Post this in the i9100g...idk how much we can help you with this..
Anyways, try factory resetting the phone...if no luck take it to Samsung customer care...it can be a hardware problem. ..
And ya, which ROM are you flashing? The official stock ROM or custom ROM?
Custom ROM do have many bugs and vary from phone to phone. .. Try going to stick for one and check if problem is still there. .
Press thanx if I helped...
Hannibal226 said:
Did u update via kies or odin?
If u used a firmware and flashed via odin, please try another firmware.
Over this try to do a factory reset after u flashed the FW.
CHEERS
Click to expand...
Click to collapse
update via odin...trying both 3.07 and 1.85
i use firmware on this post http://forum.xda-developers.com/showthread.php?t=1679636
and done factory reset every time before and after done flashing...
after done several times flashing, im still facing touchscreen problem...
the weardest is the problem fix when i plugin charger...
umair241995 said:
Well your phone is i9100g... You sure you flashed ROM of i9100g and not of galaxy s2 i9100...coz many people make that mistake..
Post this in the i9100g...idk how much we can help you with this..
Anyways, try factory resetting the phone...if no luck take it to Samsung customer care...it can be a hardware problem. ..
And ya, which ROM are you flashing? The official stock ROM or custom ROM?
Custom ROM do have many bugs and vary from phone to phone. .. Try going to stick for one and check if problem is still there. .
Press thanx if I helped...
Click to expand...
Click to collapse
cannot post on i9100g dev becoz my post still under 10...
im sure i flash the right rom from http://forum.xda-developers.com/showthread.php?t=1679636
ya..done factory reset but still got the problem...
like i said before..the touchscreen work fine if i plugin charger or connect usb to pc/laptop...
i dont think it becoz hardware problem since it work perfect on stock GB, stock ICS, aokp, CM and 4-5 other custom ROM...
can it becoz of battery? i use 1650mah...i have try 1500mah and touch screen getting more worst...
i still cant find any solution for my phone..
already try many method like
- using re-partion on odin with pit file
- format data, system, cache, emmc
- wipe data/factory reset/dalvic cache
- flash using odin/cwm
- root/unroot
after done all above..touch screen laggy and still make dash line on drawing...
after my last post...i have try most rom on Galaxy S II I9100G Android Development Section and my touchscreen on all rom are working perfect except official stock JB or custom rom base on stock JB...
forgot to mention that the day on my 1st time installing stock JB i accidently flash Galaxy tab 2 p3100 firmware and got softbrick
but successfuly unbrick then done flashing stock JB...dunno if this incident can damage my phone...
or is other way to make FULL FORMAT internal SD? to make sure the file that i accidently flash completely remove...
sinsai said:
i still cant find any solution for my phone..
already try many method like
- using re-partion on odin with pit file
- format data, system, cache, emmc
- wipe data/factory reset/dalvic cache
- flash using odin/cwm
- root/unroot
after done all above..touch screen laggy and still make dash line on drawing...
after my last post...i have try most rom on Galaxy S II I9100G Android Development Section and my touchscreen on all rom are working perfect except official stock JB or custom rom base on stock JB...
forgot to mention that the day on my 1st time installing stock JB i accidently flash Galaxy tab 2 p3100 firmware and got softbrick
but successfuly unbrick then done flashing stock JB...dunno if this incident can damage my phone...
or is other way to make FULL FORMAT internal SD? to make sure the file that i accidently flash completely remove...
Click to expand...
Click to collapse
Search for nuke script and see if you can nuke your device.
FIND OUT, don't perform it without knowing if it's meant for your device.
Sent from the little guy
Touch not responding properly
gastonw said:
Search for nuke script and see if you can nuke your device.
FIND OUT, don't perform it without knowing if it's meant for your device.
Sent from the little guy
Click to expand...
Click to collapse
I have this problem to.
Any news about this?
---------- Post added at 01:53 AM ---------- Previous post was at 01:43 AM ----------
gastonw said:
Search for nuke script and see if you can nuke your device.
FIND OUT, don't perform it without knowing if it's meant for your device.
Sent from the little guy
Click to expand...
Click to collapse
I have this problem to.
Any news about this?
I dunno, I don't have an I9100G.
Sent from the little guy
you could try Blazing Kernel, it can be flashed via stock recovery. http://forum.xda-developers.com/showthread.php?t=2113545.
Or you could also flash original GB and upgrade to JB either through OTA or KIES.
acse1 said:
you could try Blazing Kernel, it can be flashed via stock recovery. http://forum.xda-developers.com/showthread.php?t=2113545.
Or you could also flash original GB and upgrade to JB either through OTA or KIES.
Click to expand...
Click to collapse
I have tried that two methods, Flashing GB (everything works great), flashing ICS (everything works great too), and then JB trough OTA and the touch screen doesnt work properly. I have tried the last Blazing Kernel too without success.
Thanks for the help.
Any ideas?
Try stock kernel. Customs aren't ready yet.
Sent from the little guy
gastonw said:
Try stock kernel. Customs aren't ready yet.
Sent from the little guy
Click to expand...
Click to collapse
The stock Kernel file is already on the Stock JB Odin file?
Like these : http://forum.xda-developers.com/showthread.php?t=1679636
Indeed it is.
Sent from the little guy
gastonw said:
Indeed it is.
Sent from the little guy
Click to expand...
Click to collapse
Dosent work either. :/
We have the same problem dude, touch screen not working properly after stock jb (xef) flash but working flawlessly when phone is plugged. I can't have a custom rom above 4.2.1, else I have the problem. Now I'm on CM10.1 4.2.1 and can't leave it because of this, the official rom I want is the official.
Did you got the screen of your phone replaced ? Because mine was and I was wondering if it was that.
samstacle said:
We have the same problem dude, touch screen not working properly after stock jb (xef) flash but working flawlessly when phone is plugged. I can't have a custom rom above 4.2.1, else I have the problem. Now I'm on CM10.1 4.2.1 and can't leave it because of this, the official rom I want is the official.
Did you got the screen of your phone replaced ? Because mine was and I was wondering if it was that.
Click to expand...
Click to collapse
Not sure if it was replaced because I bought it used on ebay.
But are you using CM10.1 4.2.1 without touch screen problems? Can you tell me the date of the release so I can try to flash my phone with that ROM?
Thanks
Yeah without touch screen problem. It's 20130213 nightly
Sent from my GT-I9100G using xda app-developers app
samstacle said:
Yeah without touch screen problem. It's 20130213 nightly
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
I just find the 20130214. Is that one? I will try it.
[SOLVED]
Hello! I have been rooting and flashing roms for a while now, and after sticking with a cm mod for a while i decided it was time for a change. I foolishly didn't back anything up and just flashed a rom to check it out. I have a Galaxy s3 19300 unlocked version (i have it on a plan for cricketwireless). I cannot get odin to work for me to flash a new custom rom, a stock rom, or even begin trying to flash. Odin either gives me the nanad write error or the program stops responding. I have samsung drivers installed and really need some help. I'd appreciate any help on getting me one step closer to a working phone. Thanks!
snoringdragons said:
Hello! I have been rooting and flashing roms for a while now, and after sticking with a cm mod for a while i decided it was time for a change. I foolishly didn't back anything up and just flashed a rom to check it out. I have a Galaxy s3 19300 unlocked version (i have it on a plan for cricketwireless). I cannot get odin to work for me to flash a new custom rom, a stock rom, or even begin trying to flash. Odin either gives me the nanad write error or the program stops responding. I have samsung drivers installed and really need some help. I'd appreciate any help on getting me one step closer to a working phone. Thanks!
Click to expand...
Click to collapse
Try with a pit file and other version of odin.If it still persists then use cwm to flash touchwiz based rom.
qasim799 said:
Try with a pit file and other version of odin.If it still persists then use cwm to flash touchwiz based rom.
Click to expand...
Click to collapse
Could you link me with the correct pit file, I haven't been able to find one for my Galaxy S3 8Gb 19300. And I have tried all versions of odin so far so Ill give each one a shot when you give me the link for the pit or I eventually find one. Thanks for the fast response by the way.
qasim799 said:
Try with a pit file and other version of odin.If it still persists then use cwm to flash touchwiz based rom.
Click to expand...
Click to collapse
Another question, should I be flashing the pit file (if you or I can find one) with a custom/stock rom or without a rom. Thanks in advance.
snoringdragons said:
Another question, should I be flashing the pit file (if you or I can find one) with a custom/stock rom or without a rom. Thanks in advance.
Click to expand...
Click to collapse
there you go http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
and one thing i still don't understand how your s3 is 8 gb it is always 16 gb confirm it.
and flash this pit file wih odin also put firmware. if you wana try some delicious roms then they are available under s3 development section.
qasim799 said:
there you go http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
and one thing i still don't understand how your s3 is 8 gb it is always 16 gb confirm it.
and flash this pit file wih odin also put firmware. if you wana try some delicious roms then they are available under s3 development section.
Click to expand...
Click to collapse
yea its 16 gb just 11 gb available and 8 gb available after firmware its stupid but w/e. anyway i got it to work by formatting sd card which got rid of corrupted custom rom and made it just a normal stock bootloop so i flashed stock firmware for a random region and then cf auto rooted and flashed a custom rom. All good now but ty for the help i wouldnt have looked into pit files which led me to the stock file and made me try it. I guess if ur willing to format sd card it gets a lot easier.
not sure how to close a thread but i guess this should be good enough for now. [CLOSED]