Had some issues with my galaxy tab.
Long story short I went to nandroid restore and **** got worse. The tablet was repartitioned before creating nandroid and I thought it would restore okay.. NO.
I used factory reset package and tried to get it back to factory, no dice. NO matter what i try IT BOOTS, BUT old apps are there. I can manually uninstall them, restart the tablet and they are back and Force Closing like crazy. I tried a factory reset from the device and same. I don't know what to do I need some sort of superwipe.
I have tried about everything I can think of. Anyone else have any ideas here? A superwipe zip etc?
Fix permissions in CWM.
Sent from my SCH-I510 using xda premium
kvswim said:
Fix permissions in CWM.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Tried but no cigar. Don't think there is a whole lot i haven't tried at this point seems like the card may be going bad.
Repartition?
Sent from my SCH-I510 using xda premium
I would say if wipe doesn't work, flash back to stock using odin/heimdall then flash what you have right now... repartition doing so...
However Factory reset not working is kinda strange...
Waiting for more details or info
I'm reaching a bit, but one problem you *could* be having is that since you've added new roms you've updated your filesystems from RFS to EXT4. I'd have to look at the ROM package you are using to determine how it's moving data onto your filesystems, but if it's true stock then it may not know anything about EXT4 and be trying to mount the filesystems as RFS (which would fail if you've converted to EXT4).
I've found in playing around with flashing a lot of different kernels and builds to my phone that a flashing "everything" using Heimdall is the most thorough approach. What you want is a build that will replace the cache, data, system, root and kernel "/dev/block" devices, as well as the primary and secondary bootloaders. This link:
http://forum.xda-developers.com/showthread.php?t=1275031
Has the stock rom (it's a TAR file, like you would use with ODIN, but un-tar it and you can use with Heimdall) for a Sprint Tab. I don't know if that's what you have, but I'm sure you can find an appropriate stock for your tab. If all you get is a big TAR file, what you want to do is un-tar it and the contents should be something like:
zImage
recovery.bin
factoryfs.rfs
params.lfs
cache.lfs
dbdata.rfs
boot.bin
Sbl.bin
...and there will probably be a modem.bin. I would avoid flashing that if you can. I've just had some very bad experiences flashing the wrong modem.bin by mistake (had to take the tab apart, solder a JTAG to it, and use the JTAG ressurect to bring the tab back to life).
While all this "should" work that same with ODIN, my experiences have been more reliable after reflashing with Heimdall. By reflashing something like "factoryfs.rfs" you will not only be flashing the files, but also in effect be reformating the filesystem for the "factory" system files you need.
Keep in mind doing this kind of reflash will return your filesystems to a "pristine" RFS state... but it should get you back to a place where you can then restore your nandroid backup with Heimdall.
I have been having the same problem with my cdma tab, no matter what rom I install or the method (heimdall,Odin,or cwm) I have apps that will not delete and non stop force closes. These apps will come back after data wipes, and from rom to rom they are automatically reinstalled.
Miui is the only gingerbread rom that I had limited success with, but with miui I get non-stop keyboard fc's. And the unwanted apps still come back.
I have tried everything suggested in this thread, and the only thing that has semi worked was flashing an ice cream rom to the tab. But of the two ics roms I found, one has no wifi, and the other says encryption unsuccessful on boot.
Any help would be greatly appreciated.
Sent from my Inspire 4g using ICS
I have the same problem with my tab few montsh ago.Nothing help.I took tab to samsung service.It was damage mainboard.In service they replace mainboard and after that it works like charm.I think that you should do the same. Sorry for my bad english.
Thanks for your input jdiem. I tried what you suggested on heimdall as well. Didn't work.
Sent from my PG86100 using Tapatalk
xena0709 said:
I have the same problem with my tab few montsh ago.Nothing help.I took tab to samsung service.It was damage mainboard.In service they replace mainboard and after that it works like charm.I think that you should do the same. Sorry for my bad english.
Click to expand...
Click to collapse
Thanks, my tablet is currently at Samsung repair awaiting repair parts. Meaning that as you mention here, if you have this problem it appears to be a hardware issue. Mine was around 1 month old so still in warranty. Sucks to have to live without it though.
Sent from my PG86100 using Tapatalk
Follow up, they changed the PCB. All was well initially, however, after a couple weeks the tablet began having the same issue all over again
Really weird.
Related
I'm sorry if someone already asked this question but I was not able find an answer. I am running a custom ROM now, do I have to go back to stock before flashing another ROM?
It is usually not necessarily to do it but it a very good idea to return to stock and master clear with the odin-1-click
Sent from my GT-I9000 using XDA App
No you don't need to go back to stock. Nor is is necessary to master clear. Most if not all the roms on here will do a full wipe of your SD card during the install. Flashing back to stock just adds another chance to mess up your phone. This was advised, several months back but it's not necessary now. This doesn't apply if you want to flash to CM7. They have their own install procedure that is different than anyone elses.
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
BWolf56 said:
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
crystalhand said:
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not what I meant.
If he flashed, lets say, FireFly (which is 2.2 based) then he can't flash over with, lets say, CM7 (which is 2.3 based). Just simple logic
@ OP - You can look on the ROM's thread to see what it is based on.
Thank you for all your help. I'm using Phoenix Ultimate now and want to try out the other ROM.
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
One less time touching Odin is one less time tempting fate. But that's just me. I'm pretty sure every rom dev in here has bricked a phone at least once...
much agreed. less odin. less potential for problems.
roms do a wipe now. doesnt matter what you had on it 2.1 or 2.2
2.3 is the only rom version that has a different partition table.
there is no issue flashing a 2.2 rom over 2.1 or vice versa. how CAN you upgrade from 2.1 to 2.2?? CWM anyone? oh **** right!
the only issue with flashing over 2.2 is the 3e recovery... and thers a fix for that. you dont need to go back to 2.1 to avoid the signature verification error... @crystalhand...
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not all devs put it in their op. Some devs say flash first thru clockwork and only use odin when there are problems. Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Click to expand...
Click to collapse
EXACTLY as it should be.....
No, odin is potentially more dangerous than any standard rom flash. as has been mentioned, use in case your in some s
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Juanmail15 said:
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Click to expand...
Click to collapse
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
+1
Odin should only be used as a "Oh S**T I bricked my phone" program. But then again, if you read and know what you're doing than it should never be "needed"
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
Completely agree just want to clarify 1 thing. The roms don't do a complete wipe of the sdcard. The wipe the /data /cache and /system partitions, leaving the /sdcard completely intact, just like flashing to stock would. Master clear just reformats /sdcard partition and is not really needed as the os doesn't use this to function and including this in a rom would be catastrophic if the zip is in fact on the /sdcard partition you are wiping with it.
The most I do is clear cache, data and disable lagfix.
quarlow said:
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Lancered said:
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Click to expand...
Click to collapse
Yup. That's how u do it, if you have no need to root before hand and back up, I'm assuming you've done that if I remember right you are the girl I told to brick her phone yesterday to return, is the replacement on eclair or froyo? Ig it on froyo you will have to get past the 3e recovery that's why I ask.
Looking for data about flashing rom over other roms and their status of being stable. Feel free to tell whatever. Thank you.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes. Try the serendipity q&a thread.
Caution swyping! Read at your own risk.
Thanks but I was hoping I could get serial flasher who flashes over this rom only to help me with this experiment. This experiment is only for froyo and not gingerbread.
Sent from my SAMSUNG-SGH-I897 using XDA App
I did, I flashed over serendipity and went to continuum. Serendipity works with ginger bread boot loaders.
Sent from my GT-I9100 using XDA App
Are you serious? Ginger bread bootloader? That is a first I heard. how you do it without getting bricked
Sent from my SAMSUNG-SGH-I897 using XDA App
Sigh...don't worry about gingerbread bootloaders unless you going to gingerbread. He was just saying the new bootloaders are backward compatible, why he brought that up idk.
Otherwise in cwm wipe data/factory rest, wipe cache, go into advanced wipe dalvik. Flash whatever froyo rom you want.
Thanks! Very much appreciated.
but I'm still looking for flasher who actually done it to list what type of rom they flash over serendipity and if it work properly.
I know some people who flashes and got good results and some with poor result.
Sent from my SAMSUNG-SGH-I897 using XDA App
studacris said:
Sigh...don't worry about gingerbread bootloaders unless you going to gingerbread. He was just saying the new bootloaders are backward compatible, why he brought that up idk.
Otherwise in cwm wipe data/factory rest, wipe cache, go into advanced wipe dalvik. Flash whatever froyo rom you want.
Click to expand...
Click to collapse
Beyond help.
jaydenboy said:
Thanks! Very much appreciated.
but I'm still looking for flasher who actually done it to list what type of rom they flash over serendipity and if it work properly.
I know some people who flashes and got good results and some with poor result.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
studacris wouldn't steer you wrong.
I gave you that suggestion because that's what I do I have been to stock like 6 times. Total. Flashed every rom over every rom.
If you have any problems after you flash over it, just flash back to stock like you normally do.
cappysw10 said:
Beyond help.
studacris wouldn't steer you wrong.
Click to expand...
Click to collapse
Lol, thanks for the endorsement ;p
Hold on a minute. no disrespect! I appreciate your response and answer. I'm looking for other people/flasher as well. I counted you already. I'm looking at the what rom and results after the flashing. That's all. So no disrespect to anyone. Trying to listen to whoever experience flashing over serendipity. And I thank you for your time.
Sent from my SAMSUNG-SGH-I897 using XDA App
jaydenboy said:
Hold on a minute. no disrespect! I appreciate your response and answer. I'm looking for other people/flasher as well. I counted you already. I'm looking at the what rom and results after the flashing. That's all. So no disrespect to anyone. Trying to listen to whoever experience flashing over serendipity. And I thank you for your time.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I don't really know what you are expecting to hear. A rom will wipe system/data/cache/dalvik so technically it IS a fresh rom. Flashing over an old rom doesn't affect ANYTHING in regards to the actual rom.
Sent from my HTC Desire Z
That is what I'm researching because others claim flashing over roms causes the new rom to not work properly while others have no problems at all. Then there are others who flashes back and forth to the same rom before and notice it doesn't work like it's suppose to when they had it the first time around.
Let me ask you...could it be titanium backup or bad flash. Could never really understand what a bad flash is technically.
Sent from my SAMSUNG-SGH-I897 using XDA App
lets put this into perspective, and think of it like your home computer.
on your phone, you have a few partitions. lets think of these combined, representing your C drive
/system /data /cache /datadata (these are the main ones to focus on)
when you format to load a new OS, there is NOTHING remaining of the OLD OS that could possibly cause conflicts. because essentially the drive is clean after the format and you load the new OS, and never see any traces of the old OS on the drive.
if you look at the update-script located in every single CWM flashable zip file, you will see a few things.
Code:
format SYSTEM:
format CACHE:
format DATA:
format DATADATA:
then after that you should see:
Code:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
copy_dir PACKAGE:updates TMP:/updates
this creates the new partitions, essentially for the system and data
as you can see, the rom flash will wipe the OLD system and data off and put a new one on. what is left from the old rom???
That about covers it lol
Thank you very much! So if some thing goes wrong then it's pretty much the file which results in a bad flash.
Sent from my SAMSUNG-SGH-I897 using XDA App
jaydenboy said:
Thank you very much! So if some thing goes wrong then it's pretty much the file which results in a bad flash.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
the only reason to go back to stock with ODIN prior to flashing is if you wanted to repartition and reset the file system. i did it many times while working on the Andromeda builds, because I wanted to make sure that coming from stock people would get the appropriate filesystem configuration and setup
Is there any problems you would encounter if you didn't have your partitions and file systems reset?
Sent from my SAMSUNG-SGH-I897 using XDA App
jaydenboy said:
Is there any problems you would encounter if you didn't have your partitions and file systems reset?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
very unlikely with the 2.2/2.2.1 roms. the kernel devs are pretty much all on the same page with using similar lagfixes that offer compatibility across the board. think of using ODIN and going back to stock as a last resort. 'when all else fails' type of thing
You said very unlikely. Its that part that I'm more interested in. The part that causes us to odin back to stock. When all else fail
Is there something that we do or is it the results from flashing too much that causes our partitions and file systems to go out.
Doesn't flashing reset our files systems and partitions?
Just letting you know that I am very grateful for your time and input. Your elaboration and explanation. You are helping way more than you know.
Sent from my SAMSUNG-SGH-I897 using XDA App
It's not caused by flashing too much, as far as your phone is concerned each fish is its first because it wipes first thing.
sometimes something just doesn't write correctly in cwm, for any number of reasons. thats whats known as a "bad flash." but that can be solved by a reflash. you would need odin if say the battery were to die during a flash and all you get is the "phone....!.....pc" screen
Hi all.
My wife hqs a I9003. She was running rooted stock 2.2.1 KB1FW on it. Everything was fine untill about 4 days ago. Thay's when without reason the whole Android system started to fail. Clock, Maps, Messaging, TW Launcher, etc all gave error and forced closed. She only had about 10 or 15 apps installed and all on phone memory. So I did a Factory Restore thinkg it would help but it was all still the same.
So I flashed KPE (all 4 files) and a new error started: after 1 or 2 after the factory restore on new FW, phone crashes and goes in to a boot loop (Samsung logo and intro screen). Once I manage to get back to Android, it's reset to factory settings (install wizzard). I've flashed KPH, KB1, KB3 etc and it's the same problem all the time. Was flashing the APBOOT file from KPE a mistake?? How can I fix this?? I don't have a backup and even if I did, I can enter download mode but not restore mode (Vol Up + Home + Power).
Please, I need help urgently
Thanks
Sent from my GT-I9000 using XDA App
Before this all started did she install some unknown kinda software/app from the market?
Also while flashing did you use Latona.pit file?
Sent from my GT-I9003 using Tapatalk
Nope. Thay's the weird thing. On mine, I'm constantly installing/deleting from the market, blackmarket and other sources and have no problems. All the apps she had, I installed myself and were all "safe".
As far as the pit file, I used it first joint with the other 4 files (like I did for my I9000) and after I used it on it's own. I've tried first the pit file, then the FW files, just the FW files and the pit + FW files with and without re-partition checked... I'm running out of ideas and getting desperate...
Sent from my GT-I9000 using XDA App
Sounds to me like the phone has developed a hardware fault.
Things do just up and die sometimes..
Could it be the battery??? She hasn't dropped or banged it at all. Mine had a slight swim.and is still perfect. If I flash it back to a European KB1, would the warranty still cover me??
Sent from my GT-I9000 using XDA App
Try to do the following:
Select only latona (.pit) and repartition in odin. Put the phone in download mode and flash.
Next reset all. Select pda, modem, csc file from XXKB3 firmware. Dont choose repartition and flash.
hope it works
Sent from my GT-I9003 using Tapatalk
Tell me teh method what you followed to flash? Like first, the pit file with re-partion,auto-reboot and F.reset time checked. And, then, the other 4 file of the SAME Fw with the auto-reset unchecked. Also, Did you click on the reset button after flashing the pit file?
Try to do the following:
Select only latona (.pit) and repartition in odin. Put the phone in download mode and flash.
Next reset all. Select pda, modem, csc file from XXKB3 firmware. Dont choose repartition and flash.
hope it works
Sent from my GT-I9003 using Tapatalk
Click to expand...
Click to collapse
Had done that before but just did it again. So far it has crashed once but didn't revert back to factory default this time and I now have the recovery mode again.
Tell me teh method what you followed to flash? Like first, the pit file with re-partion,auto-reboot and F.reset time checked. And, then, the other 4 file of the SAME Fw with the auto-reset unchecked. Also, Did you click on the reset button after flashing the pit file?
Click to expand...
Click to collapse
I've done it various ways as I explained in the first post. With and without re-partition, with and without the pit file, etc.
But I had a minor brainwave this morning after the first crash on XXKB3. The microSD she had in her phone was an 8GB she got with her old Xperia. It was used under Symbian and when I put it in her Galaxy, I think I had formatted it with the PC but not with the phone. Can't remember (she has it since May). In any case, she didn't have apps stored on the SD but she did have all wallpapers, photos, music, ringtones, etc. I've now removed the SD and see how it goes. Just thinking that maybe the SD is f****d and could be creating a shortcut or inestability with the phone... Worth a try as I'm all out of ideas.
Thatnks to everyone for the help you're providing me with this issue. I suppose it's weird that after flashing many different ROMs the problem persists and is still the same. If all else fails and I re-flash the XXKB1, do yo guys think Samsung will take responasability for the problem?? I have it unlocked with the app thats on the market, but AFAIK I have the EFS folder backup stored somewhere.
Well phone still switching off with the XXKB3 FW. It's only switching off now tho... No boot loop. And at least now I know it's not the SD at fault. I'll try re-flashing XXKB3 tomorrow as I only flashed it once today. Then I'll do a factory format and reset battery stats once I flash the CWM. If after that it's still the same, I gues I'll have to restore the EFS folder, flash the XXKB1 FW and send it off to Samsung and hope for the best... Unless anyone has any other idea I can try???
Sent from my GT-I9000 using XDA App
i am not sure bout this but if you flash xxkph it shouldnt void varanty since its official rom? right o.o
xGiox said:
i am not sure bout this but if you flash xxkph it shouldnt void varanty since its official rom? right o.o
Click to expand...
Click to collapse
No. Anything that is done using Odin voids your warranty so when visiting service centre just flash to the firmware that your phone came out of the box then tell the service centre staff the phone just went crazy or anything like that just dont talk about Odin to them. And try this out.
1. Download an app called Rom manager from the market.
2. Make sure you are rooted.
3. Go into rom manager and hit fix permissions.
4. Reboot.
That should do it. Or else its the service centre.
Sent from my GT-I9003
crazbanditz said:
No. Anything that is done using Odin voids your warranty so when visiting service centre just flash to the firmware that your phone came out of the box then tell the service centre staff the phone just went crazy or anything like that just dont talk about Odin to them. And try this out.
1. Download an app called Rom manager from the market.
2. Make sure you are rooted.
3. Go into rom manager and hit fix permissions.
4. Reboot.
That should do it. Or else its the service centre.
Sent from my GT-I9003
Click to expand...
Click to collapse
i mean they wont know if he used kies or odin.
xGiox said:
i mean they wont know if he used kies or odin.
Click to expand...
Click to collapse
But if you dont come from russia which the csc says ser which is russia then they will know its definite you used Odin as there is no other ways you could get to a firmware of another region where you don't even come from using Kies unless you hacked Kies which also voids the warranty.
Sent from my GT-I9003
crazbanditz said:
But if you dont come from russia which the csc says ser which is russia then they will know its definite you used Odin as there is no other ways you could get to a firmware of another region where you don't even come from using Kies unless you hacked Kies which also voids the warranty.
Sent from my GT-I9003
Click to expand...
Click to collapse
LOL., you can say you travel to RUSSIAN..
madi3d8 said:
LOL., you can say you travel to RUSSIAN..
Click to expand...
Click to collapse
Then the warranty will be voided didnt you see they said warranty will be voided if not bought within the country or something like that.??
Sent from my GT-I9003
That is complex! In, India, You just go into the service center and tell him your problem! He will check the FW version and tell that you void warranty. Just SHOUT at him and tell him you are a developer ..VOILA! He will service it! He will take a hell lot of time for a small problem though!
And if I'm willing to pay for the repair?? Or maybe load a europe CSC file on it... Had a bit of a bright idea today: switch batteries. She's using my I9000's battery at the moment. Let's see if it doesn't turn off. My I9000 fell yesterday, had a rubber cover on it so the bang wasn't bad BUT my loud speaker has blown out seems easy enough to replace and I do laptop repairs so shouldn't be too much hastle to sort it myself. But so much for the Galaxy S being the iPhone 4 killer... Sem to be quite delicate phones...
Bit of off topic: anyone know anything about the Galaxy S 3??? If and when it's coming out and some type of details.. Galaxy S 2 was a big failure with more problems than the one I have according to what I've read on the internet...
Sent from my GT-I9000 using XDA App
DigiRay said:
And if I'm willing to pay for the repair?? Or maybe load a europe CSC file on it... Had a bit of a bright idea today: switch batteries. She's using my I9000's battery at the moment. Let's see if it doesn't turn off. My I9000 fell yesterday, had a rubber cover on it so the bang wasn't bad BUT my loud speaker has blown out seems easy enough to replace and I do laptop repairs so shouldn't be too much hastle to sort it myself. But so much for the Galaxy S being the iPhone 4 killer... Sem to be quite delicate phones...
Bit of off topic: anyone know anything about the Galaxy S 3??? If and when it's coming out and some type of details.. Galaxy S 2 was a big failure with more problems than the one I have according to what I've read on the internet...
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
1) Galaxy S3 will be launched once Nexus Prime is out (also being made out by Samsung)
2) Nexus Prime will be released some time in October so S3 will probably be released late October or sometime in November (more or less - to compete with iPhone5)
3) Galaxy S2 is one of the hottest selling item in the WORLD right now - i guess you have read some biased reports about its performance issues.
Just thought I'd give you all a quick update on what's happened with my wife's I9003.
After trying everything possible to fix it via flashing, the whole internal memory collapsed. It wasn't even able to finish installing the last firmware I flashed on it.
I took it to the shop, told them what happened and the sent it off to the technical repair service. That was on the 5th of this month.
Got it back today fully working!!!
They changed the main board as a faulty part, so even though it was unlocked with no EFS backup and was flashed numerous times, the guarantee took care of the repair
Tomorrow I'll root it and install ROM Manager and do a backup of the firmware before I flash it to Gingerbread, as they've returned it with Froyo and carrier boot screen. And this time I'll keep a backup of the EFS folder too LOL
I wonder is there anyway to force a main board to break via software, would be interesting for those that have voided their warranty by unlocking or flashing, if the board is broke, any changes become untraceable.
While I'm here, just a quick question: When I do the backup via ROM Manager, will it backup only the PHONE part of the firmware or will the MODEM & CSC be included too?? If it's only the PHONE file, how can I backup the others???
Thanks to all of you that responded to my original post and tried to help me with the phone.
Sent from my GT-I9000 using XDA App
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Maybe he dont follow the instructions correctly
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
What method is he using to flash? If using pc Odin does the flash get stuck at factoryfs. Img?
Was he on ics stock and did he perform any factory resets on it?
If answers are yes, it's likely he's got traces of damage on his emmc chip, but we need to know where the flash is failing to understand further.
Sent from my GT-N7000 using xda premium
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
meminiau said:
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
Click to expand...
Click to collapse
Try flashing rom with pc odin instead of cwm.
Check out Dr ketan sticky thread in rom development for directions on how to use pc odin. It's simple.
Let us know how you progress.
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
No problem at all.
Sent from my GT-N7000 using xda premium
What?????
Swiped on my Gnex
Sounds very odd - only though is he's not following instructions correctly..
Hello there guys!
I tried to flash my Samsung Galaxy Tab (P1000) from ICS to JB yesterday, but it wen’t wrong and now everything is a mess
It all started with that that CWM didn’t start up properly when I tried to get in there. “Screw this”, I said, and tried to find another CWM to flash. I didn’t end up very well that either when I went from CWM 6.0.X.X to CWM 3. The recovery told me that everything was unreadable and I couldn’t do a damn thing.
So there I was, sitting on my chair, wondering what I was supposed to do. My conclusion was to flash the tab with GB stock firmware, and so I did. But even that screwed up since Odin reported “FAIL!” and that is where I am right now.
The stock recovery tells me that it “failed to mount /data”. I guess it’s my internal SD that’s been messed up.
So what do you recommend me to do? Since I can enter Download Mode and the stock recovery (which though is quite unusable), I guess this is nothing more than a soft brick, so I'm not that worried, but it's tiring that it won't work propely.
Any hints, guys?
Already use overcome method?
The link is in my signature
Sent from my GT-P1000 using xda app-developers app
Charlie, I had similar experience and in frustration and panic I resorted to GB_Stock_Safe_v1 and it rebooted and I had a new clean system on the tab. Actually it didn't reboot as expected after ODIN was finished. With the yellow download symbol still on the screen I had to unplug it and close and reboot manually.
Make sure to include modem.bin in PHONE or you will get NO SIM card error.
Set it up like this in ODIN
PIT - gt-p1000_mr.pit
PDA - GB_Stock_Safe_v1.tar
PHONE - modem.bin
You have to find the correct modem.bin from one of the folders in the GB_Stock_Safe_v1.ZIP
If you have success then insert 001007-Overcome_v2.0.1_HERMES_Wipe.zip into top level of your sdcard then into recovery and install then it should boot OK.
Any trouble locating the files or further suggestions just come back.
Stock safe v1 is so old. Hermes is old too.
Follow my signature for latest one.
Sent from my GT-I9300 using xda app-developers app
They may be old but anyone with a soft brick is just looking for a bailout and they do that very well.
In fact after rescuing my broken tab with these oldies I went into recovery with
Overcome_7_Series_v4.1.0_NoWipe.zip
and it worked without any problems, so I unbricked and got the latest firmware.
You know where to get your oldies?
Sent from my GT-I9300 using xda app-developers app
Hi priyana,
I am unable to locate them on the net now but if needed I could post them here.
I am never going to trash them that's for sure.
You are right in recommending Overcome, longbreak, but why would you want to use v1, especially if it's not even available on the net anymore? If someone wants to recover from a soft brick, just follow priyana's link, and you will find v5. This is the latest version, and I'm sure it will work just as well, if not better.
Thanks, I will try that next time. Only reason is I had version 1 and 3 for some reason and when I was trying to save my brick version 3 would not work for some reason and version 1 worked so It's really academic whether to use 1, 3 or 5. Whatever works does the trick and then it opens the gate to get to the higher level.
I disagree that it is merely academic.
V5 was the last version team overcome packed, and it made a very reliable baseline.
By saying that , I mean v1 will work for some, v3 for others, but v5 for all.
Sent from my GT-P1000 using xda app-developers app