Respected Seniors. First off, I apologize for opening a new thread because i could not find answers to my queries in suggested threads
Some of my seniors know my problem and for those who don't know, I got superbricked while recovering Nand backup using an ICS Kernel. As soon as I wiped and factory reset my Note, its gone. Anyhow, i revived my phone using ADB method (Huge thanx to Forest1971 and hg42 ). I was good to go except lossing 3 GB space, which has since been a pain in *** and living with the knowledge that my Note is incomplete, is difficult for me. During the process, my binary count also rose to 5. So in order to claim my warranty, this is what i did:-
I upgraded from Stock GB to JPLPD- ICS. Than I rooted my Note and used Chainfire's Triangle Away (Special thanx to Chainfire) to reset my binary count from 5 to 0. After that i uninstalled Triangle Away and unrooted my phone. Now the position is :-
1. Galaxy Note is running:-
a. Android 4.0.3
b. Baseband Version N7000XXLPT
c. Kernel Version 3.0.15-N7000JPLPD-CL643396 [email protected]#3 SMP PREEMPT thu May 31 16:09:57 KST 2012.
2. The Note's Internal Memory space is 8.24 instead of original 11.3 or something.
3. Custom Binary Count is NO or O and Rom Version is : Samsung Official
4. The phone is unrooted and all apps requiring root access are gone.
Dear seniors, two questions are solicited now with respect:-
a. Will Samsung be able to detect the mess i have been doing with my Note now if i claim warranty?
b. Is there any plausible reason to explain Samsung how I lost 3 GB space? because i have just planned to tell them that i upgraded from GB to ICS through kies, during which phone restarted few times and once finally completed upgrade, i found out 3 GB space missing.
Guidance in this regard will be thankfully appreciated. :angel:
Today I visited Samsung CSC here in Pak and after having a look at my warranty, they didn't even had a look at my phone and dropped this shell over my head saying, " You have purchased it from Saudi Arabia?", i said, "Well yea" , they replied, "Its a limited warranty, claimable only in Saudi Arabia". Booom. Game Over.
I don't understand about the "losing 3gig" bit. Something has been downloaded to a system area? In that case can't it just be removed once the device is rooted?
I know about Linux but I'm still trying to figure out the inner workings of Android, so maybe I'm off the mark.
-- Sent from my phone using technological wizardry
i think will cost a charge from samsung....
Flash the original PIT file (can find from hg42 thread) then the partitions of your phone will be back to original stage again, and it will be in the brick condition again (as before you revived it). cheers.
NiceMrMustard said:
I don't understand about the "losing 3gig" bit. Something has been downloaded to a system area? In that case can't it just be removed once the device is rooted?
I know about Linux but I'm still trying to figure out the inner workings of Android, so maybe I'm off the mark.
-- Sent from my phone using technological wizardry
Click to expand...
Click to collapse
ADB method when used compelled me to segregate bad areas of emmc, i had to re-partition the factoryfs.img, Data and UMS by bringing them ahead of the corrupted blocks. Thats y i lost 3 GB. Practically, the space is there but being unpartitioned, i will not show up.
forest1971 said:
Flash the original PIT file (can find from hg42 thread) then the partitions of your phone will be back to original stage again, and it will be in the brick condition again (as before you revived it). cheers.
Click to expand...
Click to collapse
Now this sounds a gr8 idea
thank you dear forest. You always come to my rescue but just to be clear, in order to me to show its bricked, should i just flash the original PIT and thats it? or i should also install GB rom which would be bound to stuck at factoryfs.img. Also, please tell if even stuck at factoryfs.img would odin cause increase in binary count or not
thanks again
Should flash PIT file together with the official ICS (flash official roms will not cause yellow triangle), since it is the cause of the brick which happened while you update from GB. cheers.
Okie. So here I am, just to update and advice fellows something:-
I visited Samsung CSC today and tried to claim my warranty showing them my bricked phone Before having a look at my phone, they checked my warranty and replied that Since I purchased this set from Saudi Arabia, I cannot claim it in Pakistan because it has got a limited warranty. They further said that in order for me to repair the phone, i have to bear all the cost. After lots of arguing, i said, "Thanks but no thanks" and left out.
Here are my expressions:-
1. I have to live without 3GB space until Samsung does something for superbricked Notes due to emmc bug.
2. Never buy a phone outside your country, even if u find it a little cheaper than ur home country.
3. Be very careful in installing custom roms. Always flash from Stock GB or safe kernels.
Brick or no brick, you cannot claim warranty. Stick with your crippled storage space until you find a way to claim warranty from KSA.
Sent from my GT-N7000 using xda app-developers app
Did recover?
alvinasnow said:
Now this sounds a gr8 idea
thank you dear forest. You always come to my rescue but just to be clear, in order to me to show its bricked, should i just flash the original PIT and thats it? or i should also install GB rom which would be bound to stuck at factoryfs.img. Also, please tell if even stuck at factoryfs.img would odin cause increase in binary count or not
thanks again
Click to expand...
Click to collapse
hey I have the same problem with my GNote.. did you recover it?..
Just get a decent size SD card and be happy the phone still functions well... I would be glad that it works...many people aren't able to revive it
Sent from my GT-N7000000000 using Tapastalker 2
Related
Hi guys,
Just as the title says. And if it is possible to back up your original stock firmware , in case something goes wrong and need to be restored to the original firmware. I'm thinking to flash my phone but not sure which firmware to choose and its problems involved. Is flashing firmware is riskier than rooting? And how do I know if particular firmware will work with current carrier provider? Thanks a lot!
Yes, flashing can brick your phone(but repairable).
The original firmwares are available on this forum, so no worries. Just backup all your data, contacts, photos, etc., just in case.
Which firmware are you running right now??
It is possible to brick, but to be fair Android is a great OS. I myself have screwed my phone up to the point of saying "wheres the microwave" but with my friends google, and XDA I have always managed to sort it.
Rules I go by, always, and I mean always read all tutorials at least twice, compare tuts if you can. I always flash on over 75% battery power, always make sure I have everything I need before I start, from the original firmware and the custom rom. I always remove the external sd card and the sim, as I have had times where I managed to wipe both!!
Take the plunge mate, have a bash, and dont look back.
Cant remember how many different roms I have flashed on mine, and friends phones.
Above all, read and enjoy!!
steve19800 said:
Hi guys,
Just as the title says. And if it is possible to back up your original stock firmware , in case something goes wrong and need to be restored to the original firmware. I'm thinking to flash my phone but not sure which firmware to choose and its problems involved. Is flashing firmware is riskier than rooting? And how do I know if particular firmware will work with current carrier provider? Thanks a lot!
Click to expand...
Click to collapse
You can follow the video guide for flashing different roms.
itspb said:
Yes, flashing can brick your phone(but repairable).
The original firmwares are available on this forum, so no worries. Just backup all your data, contacts, photos, etc., just in case.
Which firmware are you running right now??
Click to expand...
Click to collapse
Currently running 2.3.3
PDA: I9000XWJVN
Baseband: SRJV1
CSC: PSJV5
Kernel: 2.6.35.7-I9000XWJVN-CL366455 [email protected]#2
So basically we don't need/ can not back up current firmware, only need to find the same firmware (including the kernel) and install it?
If the guide is followed properly from start to finish, is it still possible to brick your phone? Such as unforeseen problem. Is it highly likely to happen?
I'm thinking of upgrading to 2.3.5 JVT but is it worth the risk or not, is it originally release by Samsung? It seems to me it's hard to find perfect firmware for Galaxy S. Thanks.
If you've got an hour on your hands, Adam outler's unbrickable mod means no, it's not possible.
To be fair, it's pretty fxxkin hard anyway.
buttwad said:
It is possible to brick, but to be fair Android is a great OS. I myself have screwed my phone up to the point of saying "wheres the microwave" but with my friends google, and XDA I have always managed to sort it.
Rules I go by, always, and I mean always read all tutorials at least twice, compare tuts if you can. I always flash on over 75% battery power, always make sure I have everything I need before I start, from the original firmware and the custom rom. I always remove the external sd card and the sim, as I have had times where I managed to wipe both!!
Take the plunge mate, have a bash, and dont look back.
Cant remember how many different roms I have flashed on mine, and friends phones.
Above all, read and enjoy!!
Click to expand...
Click to collapse
Yes mate it is a great OS, but one thing I experience and hard to experience from my 2.3.3 is its stability and smoothness.
Have you found nice firmware for your droid? Sometimes I think Droid leaves this last finishing job for us to do
I have flashed mine too many times with too many different roms. The current one i'm using is galaxydroid 5.0, found here
http://forum.xda-developers.com/showthread.php?t=1344489
The battery life is very good as roms go, but am still playing around.
I have flashed mine to 2.3.6 at the mo as per instructions (above link)
Looks like from your current rom you should be opk for JVZ. (Going on the assumption your in europe as JVZ is open europe rom)
If you follow said above instructions on the link, you'll be fine. I also recommed flashing semaphore kernal after flashing the rom, I did this as it gave me the ability to add custom boot animation.
Another thing worth doing, is register on www.SamMobile.com as this is where all the samsung firmwares can be found, so backups are never too far away!!
woolf clubs said:
If you've got an hour on your hands, Adam outler's unbrickable mod means no, it's not possible.
To be fair, it's pretty fxxkin hard anyway.
Click to expand...
Click to collapse
I read somewhere their phone are dead after a month of flashing or rooting, any thought on that ?
So basically we don't need/ can not back up current firmware, only need to find the same firmware (including the kernel) and install it?
If the guide is followed properly from start to finish, is it still possible to brick your phone? Such as unforeseen problem. Is it highly likely to happen?
I'm thinking of upgrading to 2.3.5 JVT but is it worth the risk or not, is it originally release by Samsung? It seems to me it's hard to find perfect firmware for Galaxy S. Thanks.
Click to expand...
Click to collapse
Yes, yo do not need to backup your original firmware as it is already available on the internet. You just find the same CSC. Modem and PDA file and flash it to return to the original state of your phone.
No, if you follow the guide(word to word), 99% chances are that you will not brick the phone. Even if you brick it, it will mostly be a soft brick. Hard bricks occur only if you are flashing a bootloader.
You can flash to JVT, it is pretty stable. However, the latest is JVZ, 2.3.6.
There is nothing like perfect firmware. If you want to stick with the latest stuff, get JVZ. Since you are a beginner, i would recommend that you get comfortable with flashing Samsung ROMs at first. Then you can Root your phone, flash custom ROMs etc.
itspb said:
Yes, yo do not need to backup your original firmware as it is already available on the internet. You just find the same CSC. Modem and PDA file and flash it to return to the original state of your phone.
No, if you follow the guide(word to word), 99% chances are that you will not brick the phone. Even if you brick it, it will mostly be a soft brick. Hard bricks occur only if you are flashing a bootloader.
You can flash to JVT, it is pretty stable. However, the latest is JVZ, 2.3.6.
There is nothing like perfect firmware. If you want to stick with the latest stuff, get JVZ. Since you are a beginner, i would recommend that you get comfortable with flashing Samsung ROMs at first. Then you can Root your phone, flash custom ROMs etc.
Click to expand...
Click to collapse
What I meant perfect is best firmware for Galaxy S. I'm not a fan of Apple but it performs really smooth, relatively fast and stable.
Is JVZ official Samsung firmware? Do you have the link, looke like Samfirmware hasn't been updated yet. Thanks for your reply
I had few i9000's without imei after wrong flashing. I tried to do something (flash again correctly),but it didn't works. Central service was repaired them (price ~ 15€ in Poland).
Latest official rom in PL is JVT
I just remember one sgs that customer tried to flash it to i9001 or i9003. It isn't good idea . Phone dont start in any mode. Only service jtag helps.
Wysłano z GT-I9000 z użyciem Tapatalk
So I've just downloaded 2.3.6 JVZ, extract it and got five files, they are :
CODE_I9000XWJVZ - PDA
MODEM - PDA
Pit - Pit
Csc - Csc
Then what is file start with APBOOT? Can someone please shed some light, Do I need to put the apboot in bootloader or just those four files? Any reply would be appreciated.
steve19800 said:
What I meant perfect is best firmware for Galaxy S. I'm not a fan of Apple but it performs really smooth, relatively fast and stable.
Is JVZ official Samsung firmware? Do you have the link, looke like Samfirmware hasn't been updated yet. Thanks for your reply
Click to expand...
Click to collapse
SAMMOBILE as I previously said is the new site for all the OFFICIAL samsung firmware releases, both new and old. Register and goto the FIRMWARE tab at the top and see for yourself, just keep an eye on the region on the right.
buttwad said:
SAMMOBILE as I previously said is the new site for all the OFFICIAL samsung firmware releases, both new and old. Register and goto the FIRMWARE tab at the top and see for yourself, just keep an eye on the region on the right.
Click to expand...
Click to collapse
Yes Samfirmware/Sammobile, I found mate, heaps of thanks!
I've flashed to 2.3.6 JVZ. What I feel from this upgrade is the battery life slightly improved, and cosmetic appearance i.e. blue shade colour instead of bouncing when you scroll to the edge of the screen. Overall great firmware.
steve19800 said:
I've flashed to 2.3.6 JVZ. What I feel from this upgrade is the battery life slightly improved, and cosmetic appearance i.e. blue shade colour instead of bouncing when you scroll to the edge of the screen. Overall great firmware.
Click to expand...
Click to collapse
Good for you mate. I've flashed my phone well over 200 times (not including kernels or themes), it's still running same as day one. As long as you can read and don't do something stupid like flashing an incorrect kernel, repartition when you shouldn't or **** around with bootloader - you'll have no problems.
woolf clubs said:
Good for you mate. I've flashed my phone well over 200 times (not including kernels or themes), it's still running same as day one. As long as you can read and don't do something stupid like flashing an incorrect kernel, repartition when you shouldn't or **** around with bootloader - you'll have no problems.
Click to expand...
Click to collapse
Likewise, lost count how many times I've put different roms/themes/kernels on mine, and touch wood not an error in sight. I agree with the bootloader comment...some things best left alone as you can brick it doing that wrong.
Congrats! Now do some research on what you want to do next. You can root, install custom rom, themes etc! It is pretty much the same procedure for everything but be sure to read the instructions and warnings. Never do anything without knowing what you are doing and what effects can it have. And as mentioned before, do not play with the bootloader and you will be just fine.
Sent from my GT-I9000 using XDA App
I'm glad I did, congratulations.
Hello all,
During my travels in China, I picked up a GT-I9228G galaxy note.
Back in the UK now, and hoping I could change the rom to the english varient of GT-N7000? I am assuming GT-I9228G and GT-N7000 is the same device, just different regional roms(?).
The boot screen is chinese. It has chinese apps on it which I cant remove and no app store amongst other things. Ideally, would like to make the phone all english. Is this possible?
Just a bit of background on me:
I used to own a HTC PDA which I swap roms from developers here and very familair with jail breaking on apple products. Andriod however is new to me. I am a quick learner, so any pointers would be great please guys/gals.
mrharrod said:
Hello all,
During my travels in China, I picked up a GT-I9228G galaxy note.
Back in the UK now, and hoping I could change the rom to the english varient of GT-N7000? I am assuming GT-I9228G and GT-N7000 is the same device, just different regional roms(?).
The boot screen is chinese. It has chinese apps on it which I cant remove and no app store amongst other things. Ideally, would like to make the phone all english. Is this possible?
Just a bit of background on me:
I used to own a HTC PDA which I swap roms from developers here and very familair with jail breaking on apple products. Andriod however is new to me. I am a quick learner, so any pointers would be great please guys/gals.
Click to expand...
Click to collapse
I guess you could... Lots of other people bought their galaxy note from Hong Kong and also from china and they all changed their ROM for a same reason of yours.
Does not the 9220 using a snapdragons and not exynos? I not sure but I thing I have read it somewhere so carefully before flashing.
Sent from my GT-N7000 using Tapatalk
So, potentially I could just change to the one below?
N7000XXKKA ## 2.3.6 2011 November N7000CPWKK3 United Kingdom (Carphone Warehouse) Download
The box says 1.4 + <insert chinese characters here>
From wiki -A dual-core 1.4Ghz Exynos processor or a 1.5 Ghz Snapdragon S3 processor (AT&T, SK Telecom, KT, LG U+)
So my guess is Exynos. Anyway to double check?
ok, so I have downloaded the above rom and Odin3 v1.83 from sammobile.
I have opened Odin3 and specified the PIT file (Q1_20110914_16GB)
I have also ticket re-partition, auto reboot and F.reset timer.
I have loaded the rom under PDA (N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar), everything else is unticked.
I have the phone in download mode ready.
I just need to know if the above is ok or am I missing anything before I click START and brick my phone?
Thanks,
Chris.
well I tried anyway.
That didnt work.
Now the phone says "software update fail"
I can still get into download mode, buts thats about it.
tried with and without the PIT file.
Anyone know what I should do now please?
I'd say you'll have to find a rom for that model
maybe http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9220&r=2#regiona
You might have bricked your phone by checking repartition in odin. You should not have. Now you probably need to find a pit file for your model.
Sent from my GT-N7000 using Tapatalk
mrharrod said:
well I tried anyway.
That didnt work.
Now the phone says "software update fail"
I can still get into download mode, buts thats about it.
tried with and without the PIT file.
Anyone know what I should do now please?
Click to expand...
Click to collapse
If you could enter download mode then try these steps
1. Open Odin and flash Pit file only and Re-partition ticked. (do not attach any ROM)
2. After this again flash ROM without pit file and re-partition un-ticked
This should work.
ranjan.alva said:
If you could enter download mode then try these steps
1. Open Odin and flash Pit file only and Re-partition ticked. (do not attach any ROM)
2. After this again flash ROM without pit file and re-partition un-ticked
This should work.
Click to expand...
Click to collapse
Thanks,
The first part seemed to work ok, so then went onto flashing again without the PIT file. Failed
Back to square one (software update fail message).
Going to try the original ROM, but takes about 6 hours to download from china!.
Ideally, really dont want to use the original ROM though! I'm guessing the original ROM isnt going to work now anyway since ODIN3 has re-partitioned the device(?).
victorlht88 said:
god, you can't flash n7000 roms on the china note, you will surely brick your phone and good luck.
Click to expand...
Click to collapse
You're wrong. Several have tried and it's working perfectly with n7000 roms on i9220 phones.
Sent from my superior GT-N7000 using Tapatalk
I am also doing this on a macbook via Boot camp (windows partion). Maybe it has a problem with that. Will try it on a normal PC too.
Any other suggestions before I head home from work and play later?
Oh, I forgot to mention. I read somewhere (forgot where) that I should root the device prior to changing the ROM. Is that true? If so, I dont think thats something I can do in current state
mrharrod said:
Thanks,
The first part seemed to work ok, so then went onto flashing again without the PIT file. Failed
Back to square one (software update fail message).
Going to try the original ROM, but takes about 6 hours to download from china!.
Ideally, really dont want to use the original ROM though! I'm guessing the original ROM isnt going to work now anyway since ODIN3 has re-partitioned the device(?).
Click to expand...
Click to collapse
you can try flashing kernel with CWM in PC Odin, then flash any Custom ROM using CWM Recovery.
ranjan.alva said:
you can try flashing kernel with CWM in PC Odin, then flash any Custom ROM using CWM Recovery.
Click to expand...
Click to collapse
CWM is clockworkmod right? Dont I need a rooted phone in order to install it?
Or do I follow something like this? http://whatareandroidphones.net/root-samsung-galaxy-note.html
Yes... CWM recovery doesn't need root.
hello,
Didnt have the time to work out CWM, but was given a link to another rom which had three files for ODIN3 (http://hotfile.com/dl/149302861/1896440/N7000XXLA6_N7000XEULA1_XEU.rar.html).
So, loaded the above and the phone is back in action on a N7000 rom. Wohoo. Just glad it's working again more then anything else lol!
This rom is prerooted apparently too. know idea what I should be able to do now. What does one usually do when they have a rooted device?
mrharrod said:
hello,
Didnt have the time to work out CWM, but was given a link to another rom which had three files for ODIN3 (http://hotfile.com/dl/149302861/1896440/N7000XXLA6_N7000XEULA1_XEU.rar.html).
So, loaded the above and the phone is back in action on a N7000 rom. Wohoo. Just glad it's working again more then anything else lol!
This rom is prerooted apparently too. know idea what I should be able to do now. What does one usually do when they have a rooted device?
Click to expand...
Click to collapse
Thread accidentaly revived :S
Hello all,
Yesterday I wanted to try the Kingdroid V2.1 + GS3 addon. After installing, everything OK but no addon on the Note so I decided to go back to my good ol
GB Rocket Rom v23.
As the kernel was reported as safe, I did a full wipe and tried first to install my latest backup. --> Dodn't work.
I tried to wipe again to install zip from SD --> Wipe didn't work neither
I tried to install a stock rom KJ1 via ODIN --> Stuck at the end of Nand write start!!
Could anybody tell me what to do next?
Thanks a lot.
May be a case of Superbrick
BruXav said:
Hello all,
Yesterday I wanted to try the Kingdroid V2.1 + GS3 addon. After installing, everything OK but no addon on the Note so I decided to go back to my good ol
GB Rocket Rom v23.
As the kernel was reported as safe, I did a full wipe and tried first to install my latest backup. --> Dodn't work.
I tried to wipe again to install zip from SD --> Wipe didn't work neither
I tried to install a stock rom KJ1 via ODIN --> Stuck at the end of Nand write start!!
Could anybody tell me what to do next?
Thanks a lot.
Click to expand...
Click to collapse
Your post is slightly unclear. Can you please specify from which kernel you wiped the first time?
Kingdroid V2.1 used an unsafe LP8 Kernel. In that case you might have a superbricked phone on your hands. In that case I'm very sorry for you.
Now I cant find Kingdroid 2.1 anymore, it seems to have been taken down.
Hello all,
The Kernel version was indeed LP8! I should have used odin and not wipe
it at all...Sh**!!!!
After trying to restore KJ1 via ODin it failed and now my Note shows
a smartphone + yellow triangle + computer and saying Firmware encoutered an issue. Please select recovery mode in Kies & try again. When doing this I can't find how to recover with Kies.
Superbricked or not?
Do I have any chance to get it fixed in a Samsung Service Center?
Could I say that I was doing a firmware update and that is got stuck or do they have a way to see that I was actualle flashing?
Any idea of what this could cost me?
Thanks guys,
Bruxav
Try getting it to a service center and just tell them that upgrading via kies fooked your phone.
This problem started increasing because of Kingdroid V2. and bad guide on installation of the ROM.
I hope Samsung Service Center is the only solution for it.
I too have tried to use Kingdroid V2 rom and my samsung note is gone now.
for getting little things we wasted a lot time, and we are now paying money to get it to its original condition atleast.
Lesson Learnt is Never ever Root or try any S**t Rom. speciall on Samsung handset.
was good enough to do everything in HTC
I also bricked my device with KingDroid and don't seem to be able to recover. I even tried to repartition from ADB, but I get input/output errors, which means the emmc is corrupted, from what I can understand.
Really sad to hear that. How did you go abot to brick it?
That could be valuable info for others.
I found a threat on this forum and as far as I understood, the kernel I had LP8 was not listed as dangerous (might be misunderstood by myself)
I did install Kingdroid 2.1 without any problem and then the S3 mod too. After rebooting it worked smoothly but had no Svoice or any S3 specs. So I decided to get back to RocketRom V23 wich is to me the best (Quick, smooth, batteryfriendly) I've tried so far.
As I thought Kingdroid was safe I did what NO ONE SHOULD DO...wipe it and there began the sh*t!
I tried installing a KJ1 stock rom this morning using Odin but it got stuck at the end of the process. When I unplugged it said ther had been a problem installing software. As requested I tried to restore with KIES but it didn't recognize the device.
Finally I brought it to the service center saying I got stuck trying to upgrade the software with official release in Kies.
Let's just hope they won't be able to restart it and get to know it was rooted and flashed a dozen times
THanks anyway for all your messages, answers and tips.
See ya,
BruXav
Best of luck to you. Please tell us how it went
Also got bricked today. Also going from Kingdroid 2.1. I'am trying to get on stock rom,but not suceeded yet (sorry for bad english )
Do you have some news from Samsung Service Center?
Hi guys,
Here I am, two weaks after my initial post. My SGN just spent two weeks at the local service center. At least I bricked it so good that they couldn't realize that I had rooted and flashed my Note.
So, I got it back after a mainboard swap!
Thanks for your helpful posts and information!
BruXav
I'm glad you got it back.
have bricked my phone one month ago
tried everything no joy
finally contacted my insurance and they sorted out for me.
Hi guys , i did something stupid , i double wipe my n7000 running a 4.0.4 rom. At the first it stuck at the factoryfs.img when i trying recovery it by odin . Some body tell me to restore the PIT and PDA on odin and i did it ,now my phone can works as usual but thats something wire ,internal memory become 8Gb!!! It should be 11GB !! help
there is no cure for this unfortunately. just use a bigger capacity external sd card. that is why those with brick and those who have warranty are advised to go to samsung service centre instead of the pit method
And if your silly self read the pit recovery thread it states this. Duh
So now if you want flash original pit and rom have it get stuck and give it to samsung to fix. Or if your warrenty is up leave it as is.
Sent from my GT-N7000 using Tapatalk 2
There's every chance stock roms will face regular fc's on system apps and launcher too depending on where the damage is. If this is the case, best to flash cm based roms as they are much smaller in size. If you've got warranty, get it repaired.
Sent from my GT-N7000 using xda premium
Attempting to root my phone, I've flashed the wrong CF-Root through ODIN not realizing I had to match the version with the PDA number.
Though it boots to the Black/White Galaxy screen, I cant get past that. I don't have CWM installed.
ODIN still recognizes the phone. I've backed up all contacts etc, so I don't care if the contents of the phone are totally erased, and just need to get the phone operational so I can find out what kernel I should flash. Where do I go from here?
Yeah I'm new and stupid. I've looked on this forum for 3 hours, and found similar threads, but not i9000 specific.
Phone: Samsung Galaxy S GT-i9000 bought in China
jtdj said:
Attempting to root my phone, I've flashed the wrong CF-Root through ODIN not realizing I had to match the version with the PDA number.
Though it boots to the Black/White Galaxy screen, I cant get past that. I don't have CWM installed.
ODIN still recognizes the phone. I've backed up all contacts etc, so I don't care if the contents of the phone are totally erased, and just need to get the phone operational so I can find out what kernel I should flash. Where do I go from here?
Yeah I'm new and stupid. I've looked on this forum for 3 hours, and found similar threads, but not i9000 specific.
Phone: Samsung Galaxy S GT-i9000 bought in China
Click to expand...
Click to collapse
I figured it out. Followed this foolproof outline -
http://forum.xda-developers.com/showpost.php?p=14273114&postcount=2
Got it to reset to factory settings, Froyo 2.2.1
If you don't screw up, you're not learning.