Related
Firstly guys, I'd like to apologise for this being my first post. I'm usually a regular over at the SGS forums but am yet to have had a response. I'm ****ting bricks currently, so here goes...
ARGH wtf. Just as I thought I had the perfect phone, it messes up! Darky's ROM went mad on me. Kept rebooting the phone. Kept vibrating throughout. No idea what's wrong with it. Tried to do a wipe install of the ROM again, but the bloody thing has disappeared from the SD card! What am I going to do now? Reflash back to my previous firmware and start all over again, AGAIN? Ffs.
Just for the record, I'm basically stuck in recovery mode. It's either that or staring at the Nexus S logo as it attempts to boot, over and over and over... I'm so angry right now! I didn't do anything to the phone for this to happen! Bad luck or what. Really hope there is a solution to this. I don't suppose there's anyway of accessing the device's SD memory when in recovery mode? I just need to plant the update.zip on the SD card again so I can reflash it!
Click to expand...
Click to collapse
I would massively massively appreciate any help you guys could give me. I've had nothing but bad luck with my Galaxy S
[EDIT] Oh and by the way, I still have full access to my three-button combo modes. Clockwork recovery console and Download mode still fully accessible.
Hi
I'm also new here and got my SGS yesterday, but i had a HTC Desire before.
If you can get in to Clockworkmod recovery you should be able to push the file via adb to the sdcard. That was possible on the Desire at least.
vippe said:
Hi
I'm also new here and got my SGS yesterday, but i had a HTC Desire before.
If you can get in to Clockworkmod recovery you should be able to push the file via adb to the sdcard. That was possible on the Desire at least.
Click to expand...
Click to collapse
Hey there, thanks for your response! What may I ask is 'adb'?
Android development....something
Just flash back to eclair again. The time it took you to get an answer on a forum is longer tham the time it takes to flash.
Sent from my GT-I9000 using XDA App
I'm guessing you screwed up without diabling lagfixes or something, just install JM8 with repartition enabled and using pit 512 file again then install clockwork update.zip then install whatever rom (but in this case darkys). It starts to become habbit when testing new roms to do all of them steps, The first time something happens you **** bricks but soon relize the SGS is alot more brick poof then you think (unless you are one of the poor souls with broken recovery modes)
But anyways, calm the hell down. Everything is fine.
ickyboo said:
I'm guessing you screwed up without diabling lagfixes or something, just install JM8 with repartition enabled and using pit 512 file again then install clockwork update.zip then install whatever rom (but in this case darkys). It starts to become habbit when testing new roms to do all of them steps, The first time something happens you **** bricks but soon relize the SGS is alot more brick poof then you think (unless you are one of the poor souls with broken recovery modes)
But anyways, calm the hell down. Everything is fine.
Click to expand...
Click to collapse
I've absolutely no idea what files to flash... I'm a bit of a noob when it comes to flashing with the SGS. Quite embarrassing actually because I used to flash my old Omnia HD with no problems whatsoever! Don't suppose you could link to files.
Don't worry, your Galaxy is not bricked. Please see here how to reflash from a PC.
I've downloaded all necessary files... I've got a CODE a MODEM the 512.pit but no CSC? Am I okay to flash with no CSC?
Eddzz!! said:
I've downloaded all necessary files... I've got a CODE a MODEM the 512.pit but no CSC? Am I okay to flash with no CSC?
Click to expand...
Click to collapse
CSC contains all carrier-related (like APNs) data.
Depending on the type of packaging some CODE files are complete with CSC.
In any case, you can flash a CSC (like ITV or XEU) even later.
Before to go with flash, I'd like to advise you to backup /efs folder on your SD and/or your PC. This is the only folder with information (like your IMEI configuration) that cannot be recovered in case of a total data loss.
After a long gruelling process of flashing and reflashing, I'm back on Darky's ROM. Problem though - App market is messed up. I can't download anything from the Market and it's also the 'old' Market theme... I think has something to do with the fact that I've flashed from Eclair straight to Darky's? (Which I was advised to do...) - How can I get my Market working again?! Everything is fine besides that!
[EDIT] I now have the new market interface but still cannot download a thing!
Hi. I have been trying to find an solution to my problem for 3 days. I have looked all over here and the rest of the internet. I believe what I need is an update zip file that will pass the standard e3 recovery.
I have downloaded several zips already(a couple from here), that say they are the stock samsung firmwares, but everytime I put it on an sd, then try to apply the update with it, in the e3 recovey I get E: signature verification failed.
I got to this point by trying to apply the OTA update. ( ok, you can all throw rotten food at me now). I thought I was safe as I didn't have any custom firmware on there. I had, however gained root access. The update went fine and seemed to work, then it finished and tried to reboot, only to get stuck on the samsung logo for over an hour before I decided it had gone wrong and panicked.
The usual ways of fixing I know about are odin, heimdall, adb. None of these are working. I think it's my computer being too old. Odin doesn't detect, Heimdall sees there is a device there but has problems connecting to it. adb will only see it in the e3 recovery mode and not in odin mode and even then because it doesn't seem to be root anymore it can't really do much.
I am open to suggestions on how to get something to work. My thoughts are that I just need a gingerbread rom that has some samsung siigning on that I can put on an sd and use that in E3 to flash from there. I can then work from there if that works. Feel free to laugh and point and tell me that's not gonna work, but if you know a way that will work I would be very grateful.
Thank you for listening and I hope someone can help.
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks for getting back so soon. I have had kies up on the screen actually. It's been trying to connect for about 3 hours now lol.
I did the troubleshoot thing earlier where it reinstalled drivers. Restarted pc but same. Won't actually connect in either odin mode or recovery.I'm pretty sure it's a pc issue, at least partly anyway, but don't have anything else to try it on.
Is the signed zip idea a definite no go?
Not sure about zip,
Close Kies, open pc odin,
Gp into download mode, connect phone, confirm downloadmode with volume up and try tp flash
Let me know how that goes
Sent from my GT-N7000 using Tapatalk 2
No Odin pc refuses to recognise there is anything attached. I'mgiving up for the night now anyway. thank you for looking in. I'll try again in the morning. I might have to buy a new pc before I can get this thing to work.
Connect the usb to back port, sometimes helps with connection. Use stock usb cable.
please hit thanks if i helped
thanks but I've tried all the basics, but if it would help I'd stick a wire up my nose, so it's all helpful. It could be something simple I just forgot.
PC specs? Is it a Mac maybe? Reboot phone and PC and use another cable. Download latest kies and update it restart PC and then connect the phone.
Sent from my GT-N7000 using Tapatalk 2
Umm, did you wipe after the flash?
1. A data wipe will, in all probability, solve the bootloop after the upgrade from GB to ICS.
2. A data wipe on an ICS kernel CAN result in a hardbrick, as I'm sure you must have noticed, on the forums.
I'd say wipe it. The bricks are not all that common. Just this once. I faced a similar situation, and I KNEW the thing would boot after a wipe, so I just crossed my fingers and did it. All went well.
By they way, what do you mean by e3 recovery? I've been assuming stock.
Sent from my GT-N7000 using xda premium
the PC is a 7-8 year old laptop. Our desktop died a few months ago and we've not really had the spare cash to replace it yet. The desktop was even older and was a real pain. The technical gremlins have really infested my house.
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else. (yes I'm looking dumber with every post). My next thing to try I guess is see if I can borrow my sister in laws PC for a few hours or something. That is if if cannot find a rom that the recovery will accept to put on my sd.
yes -the e3 recovery s the stock one.
Feel for ya.... if you can enter stock recovery then the connection problem most likely lies either with the cable and port or drivers being out of date
Sent from my GT-N7000 using xda premium
almost positive it's my knackered computer that won't let me do anything. Still can't believe that a rom doesn't exist with samsung signing, somewhere in the world. What is the point of having a standard recovery at all if you can't use it to recover stuff?
I need to be borrow or steal the use of someones computer now I think. I'll keep an eye on this thread incase someone knows of a signed zip file, and I will report of any news incase someone else has the same problems and wants to fix it without sending to Samsung so they can keep their data.
kyllerbuzcut said:
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else.
Click to expand...
Click to collapse
I understand the reluctance.
Although, the pictures would survive the wipe, as they would be in /sdcard/DCIM/Camera. A wipe wouldn't affect anything in /sdcard, although, you'd lose your contacts if they aren't backed up. Your best bet would be to borrow someone's computer for a while.
thanks for all the advice.
Finally found a zip that the e3 recovery thinks is signed.
It was the 2.3.6 gingerbread, uk cpw one.
It seems to pass the signing check and then it looks like it's doing domething for a few minutes, then nothing seems to happen afterwards. just stays in recovery. If I do it a few times in a row it will sometimes think for longer, then reboot itself like it has all worked, but then get stuck at the samsung logo again.
Can I ask, what exactly is getting wiped then? Just the main android folders and not the sdcard folder? Is that for definite?
Yes. Just the android partition should get wiped, internal SD should remain intact.
Try taking out the battery for five minutes or so before powering on again. Sometimes after flashing the rom needs a breather to "settle".
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Just an update on my situation. I finally managed to get use of another computer and got it to work properly, so managed to flash the stock ICS rom through odin.
Thanks a lot Samsung for forcing me to put the yellow triangle on my device. At least there are people willing to help with fixing mobile phones' software, even if the manufacturers themselves don't care about you losing all your data. I managed to get everything back. Nothing was lost. If only they allowed you to flash the stock rom from their stock recovery. It's ridiculous that it doesn't.
Anyway there is the triangle away app for that I suppose and now I might try some new roms out to see which I prefer.
Yeah you would have to make a flashable zip. Not sure how to do that.
Good you are back
Sent from my GT-N7000 using Tapatalk 2
I strongly advice the following since I hard bricked my note twice!
1. When using Odin make sure the firmware is compatible with your Note.
2. When partitioning using the pit file, make sure the file corresponds to your Note.
3. As a general rule, always wait for any flashing operations to finish before unplugging your Note.
--- I hard bricked my note due to the following
1. I used pit partition via pc odin and it took too long. I was impatient and unplugged my Note even if the operation was not finished. Good thing was I previously reset my binary counter and removed yellow triangle before my phone got bricked.(Samsung will not trace this.)
2. I flashed the wrong kernel...
3. I flashed many roms over and over until such time that my Note wouldn't open.
Sent my Galaxy Note to Samsung Service Center.
Luckily, my phone had no trace of any custom firmware flash and no yellow triangle. Samsung replaced my phone's mainboard free of charge as my phone is still in it's full warranty status.
After receiving my revived phone, as stupid as I am, I tried flashing firmware again via pc odin. This time it is the German Official Ics ROM thinking that it would do no harm. Same thing happened. Phone got hard bricked. So I told Samsung that my phone is dead again. I went to the service center again and Samsung asked me if I have done something with the software or Rom inside. I told them that I haven't done anything. They did not know because may binary counter is zero and I have no yellow triangle. They replaced again my mainboard free of charge.
That's all folks.
As of now, I stick to the ICS that the Samsung service center installed. I wouldn't risk again as I think I am one of those Galaxy Note owners who have the emmc bug.
All I did was to root my Note and that's it. No flashing...
SaXxO said:
I strongly advice the following since I hard bricked my note twice!
1. When using Odin make sure the firmware is compatible with your Note.
2. When partitioning using the pit file, make sure the file corresponds to your Note.
3. As a general rule, always wait for any flashing operations to finish before unplugging your Note.
--- I hard bricked my note due to the following
1. I used pit partition via pc odin and it took too long. I was impatient and unplugged my Note even if the operation was not finished. Good thing was I previously reset my binary counter and removed yellow triangle before my phone got bricked.(Samsung will not trace this.)
2. I flashed the wrong kernel...
3. I flashed many roms over and over until such time that my Note wouldn't open.
Sent my Galaxy Note to Samsung Service Center.
Luckily, my phone had no trace of any custom firmware flash and no yellow triangle. Samsung replaced my phone's mainboard free of charge as my phone is still in it's full warranty status.
After receiving my revived phone, as stupid as I am, I tried flashing firmware again via pc odin. This time it is the German Official Ics ROM thinking that it would do no harm. Same thing happened. Phone got hard bricked. So I told Samsung that my phone is dead again. I went to the service center again and Samsung asked me if I have done something with the software or Rom inside. I told them that I haven't done anything. They did not know because may binary counter is zero and I have no yellow triangle. They replaced again my mainboard free of charge.
That's all folks.
As of now, I stick to the ICS that the Samsung service center installed. I wouldn't risk again as I think I am one of those Galaxy Note owners who have the emmc bug.
All I did was to root my Note and that's it. No flashing...
Click to expand...
Click to collapse
I think when you flash the lpy with one file you click the re-repartition so you break your phone while using the pc odin which you should not do. Its only check if you have pit file or more than three files, others even when they have 4 files they still dont check the re repartition to be safe, the pc odin will automatically check for you anyway.
That`s what happens when you do stuff without any knowledge or background orientation (reading) :silly:
gee2012 said:
That`s what happens when you do stuff without any knowledge or background orientation (reading) :silly:
Click to expand...
Click to collapse
+1 Dont do anything without reading properly.
richness adsttl
+ Be patient when flashing firmware. I've flashed many times before when I was on gingerbread and I was successful.But when it comes to ICS much precaution should be taken. After my note got repaired I immediately installed the bugbrick checker and after almost 500 seconds my phone is bug free! Or my insane chip is asleep.
Deleted by myself..
Be patient. Why dont you try to search for zedomax in youtube. He's a good teacher on flashing roms and stuff. Follow his guide. His guides are safe. Learned a lot from him.
Sent from my GT-N7000 using xda premium
Pecityma March
@andnote. Install the eMMC brickbug check from playstore. It's free. You must be rooted. Just run the app after installation. It wilk tell you your phone passed the check.
I don't get it how could it brick when only trying to flash a stock ICS ROM??doesn't make sense...
galaxynotes said:
I don't get it how could it brick when only trying to flash a stock ICS ROM??doesn't make sense...
Click to expand...
Click to collapse
Why wouldn't it make sense? It's a bug introduced by Samsung itself ! Apparently in the eMMC driver, which can damage permanently the eMMC flash storage. It happens (not always) when you do a Wipe, or flash FROM THE RECOVERY. If you flash from outside (Odin), and do not wipe, it shouldn't affect you.
AlexProfesor said:
Why wouldn't it make sense? It's a bug introduced by Samsung itself ! Apparently in the eMMC driver, which can damage permanently the eMMC flash storage. It happens (not always) when you do a Wipe, or flash FROM THE RECOVERY. If you flash from outside (Odin), and do not wipe, it shouldn't affect you.
Click to expand...
Click to collapse
and yet the OP flashed via odin on a stock rom not via recovery and does not mention wiping at all, his issue is nothing to do with the emmc bug
That's what I'm sayin'!
So what went wrong?!
Great info mate. Useful to me and many
galaxynotes said:
That's what I'm sayin'!
So what went wrong?!
Click to expand...
Click to collapse
User error.
Sent from my GT-N7000 using xda app-developers app
galaxynotes said:
That's what I'm sayin'!
So what went wrong?!
Click to expand...
Click to collapse
Interrupting pit re partitioning is as good as setting off some tnt inside you're device, instant brick.
Sent from my GT-N7000 using xda premium
I know this is a common thing, as I searched before coming to the conclusion that I had to create my own thread about this topic. However, everyone says to re-flash to stock, which is what caused this problem for me. I had a huge error with the phone, and after 2 weeks of flashing, I am able to get it to this stage where it will boot up, but after booting up, the screen turns black, but the bottom buttons light up, and can be pressed, but no action.
I can access recovery and download mode. Odin recognizes my phone. I can charge with phone off (the battery image shows it charging.)
Here is the thread where I discussed my issues if you care to learn more about my issues (it was a dbdata error).
androidforums.com/samsung-galaxy-s/567335-factory-reset-wont-fix-galaxy-s-infinite-boot-mode.html
Anyways, now there is no errors (no red lines during recovery mode). But I have no idea what to do.
No one has a clue? This really sucks, I've spent so much time trying to fix it when all along it can't really be fixed it seems.
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I've tried that. With that rom it boot loops and gives me a dbdata error.
Edit. Just tried again and after the att screen during boot up it gives me different variations of this screened like a grainy type of image. I snapped a pic below. I tried going into recovery and it gave me the same image on the screen.
Imgur.com/qyo5P.jpg
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
(I've tried that as well, and I tried it again)
After flashing it booted in recovery, and tried to do the wipes.
Failed to mount /sdcard (I/O error) -- (There's no SD card inside, so that's probably why)
E:copy_dbdata_media: can't mount /sdcard your storage not prepared yet, please use UI menu format and reboot actions.
--Wiping data
Formatting /data...
Formatting/dbdata...
Formatting /cache...
Data wipe failed.
Then I tried a wipe data/factory reset. And this time it said Data wipe completed.
Then when I rebooted it said
Failed to mount /data (invalid argument)
And then it said another error but it was in yellow, so I didn't really catch it.
And it boot loops.
[Thank you for attempting to help me by the way!]
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
4-2ndtwin said:
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
Click to expand...
Click to collapse
I've tried 3 different roms with Odin3 v1.85. (that contain dbdata.rfs in the tar)
Maybe with that rom I'll have better luck. I searched for that rom at samfirmware and downloaded it. I searched in the dev forum, and all I got was an odin one click for that rom, and you said to do the regular version.
I flashed it, and it gave me the same error as before. With the data wipe failed and other errors. Then when it boots, it boot loops only the att logo.
Att logo, darkness for a second. Then repeat.
Also. I've done numerous searches for the words I'm getting, and every one says to flash back to the kk4 stock rom, but that's what causes the problems for me.
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
albokid2468 said:
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
Click to expand...
Click to collapse
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
crt60 said:
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
Click to expand...
Click to collapse
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
albokid2468 said:
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
Click to expand...
Click to collapse
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
qaler2010 said:
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
BWolf56 said:
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
Click to expand...
Click to collapse
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
qaler2010 said:
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
Click to expand...
Click to collapse
Try using Odin KK4 with bootloaders. JF6 is really outdated.
BWolf56 said:
Try using Odin KK4 with bootloaders. JF6 is really outdated.
Click to expand...
Click to collapse
Thanks again for your quick reply.
//Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I was using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
--------
Found the link:http://www.mediafire.com/?zqpip6uac4n7ov7
qaler2010 said:
Thanks again for your quick reply.
Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I wasing using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
Click to expand...
Click to collapse
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
BWolf56 said:
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
Click to expand...
Click to collapse
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
qaler2010 said:
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
Click to expand...
Click to collapse
Sorry but this isn't very clear.. Did you manage to flash Odin KK4 with bootloaders? Did it say complete and reboot the phone? If so, what exactly happened and what exactly did you do?
I have tried to find more about my situation but asking seems to be the only way since all the info is either scattered or not available!
For two weeks I've been trying to fix my note from this ics emmc bug which made me loose efs folder and I have tried several methods with no luck, so I thought that repartitioning sd might kill the bug, so I repartioned just (parts)7,9,10,11 and also went for efs part that was empty anyway thought it might clear bad blocks, although afterwards I flashed efsfix.zip from another thread on here somewhere, because of which network and everything works just no lock screen and power button dialog? And when I flash any rom stock/custom it says (in red) error mounting efs, I found a solution for that by using terminal emulator and commanding "mount", But gotta do it manually afer every reboot?
And my imei is not the same as under my fone, how could I manually edit the imei and insert original fone info?
Could anyone help or guide me to a link so that I can recreate efs partition to ext 4 and the sort out other issues?
Edit: info in-depth!!
Thanks!
Does anyone know how to create/recreate an efs ext 4 partition on galaxy note? Is there a command or certain way to mount efs part as ext 4?
without efs backup you have lost your emei. Unless you resort to illegal methods in most countries (expensive z3x box)
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it.
Anyway, how did you analyze its efs thats corrupted, cause if you can flash gb from pc odin succesfully its not super bricked
Sent from my GT-N7000 using Tapatalk 2
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
That emei stuff is so overrated by secret agencies.
Sent from my GT-N7000 using Tapatalk 2
Thanks for the reply baz77.
Basically, I wasnt aware of this emmc wipe bug when I bought Note, I got my rom flashing experience and knowledge from SGS2, so after like a week of purchase I tried to flash ICS stunnner on my Note with squeaky clean, but resulted in getting my fone back from samsung after being revived, took 3weeks to return.
At this point I still didnt know about the bug because I had assumed that my own doing caused the super hardbrick, till I flash a criskelo rom with a wipe and my problems started off with not registered on network, after that I have been krazily searching and flashing to have the fone working flawless again without having to send the fone back to samsung becasue of the wait and tiny chips n crack on my fone.
And I figured that efs is corrupted by googling and gathering info about my particular problem and everything pointed towards efs being corrupted!
I am really hoping for them release a fix and I can get my fone back working as a whole again!
Edit: added missing words! Lol
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + no lock screen and power button dialog!?!?
Could I plz ask, where can I get the stock gb with pit file samsung
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + No lockscreen and No Power button dialog!?!?
baz77 said:
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
Click to expand...
Click to collapse
Apparently, pitfile and efs clear option doesn't work, I tried GB with pitfile got the red 'error mounting efs' and tried stock UK ICS 4.0.3 from (thanks to) Dr.Ketan but Ive still got the error and no lockscreen and faulty power button?!? Plus:- Sim Network is gone :banghead: , i'll just have to flash that efsfix.zip and do the terminal "mount" procedure again!!! manually!
"Probaly Leagality issues there" I'll try the same pitfile procedure with rom from another country if it doesnt work then dont really want to but guess this fone's going back to Samsung for repairs before I sell it off.
Many Thanks for your help!!
<<SUNG>>from my <<SAM>> GT-N7000
baz77 said:
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it. 2
Click to expand...
Click to collapse
I have the custom binary count reset, so they shouldnt have any problems with repairing illegally then?? With stock UK ICS 403 Rom from this forum!?!
<SAMSUNG><ASONG> From GT-N7000!
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hey baz77,
I tried the same pitfile method with a GB236 Rom built from HongKong and flashed it twice, because I read on this forum somewhere that in the event of errors, missing files and apps after a flash, roms should be flashed atleast once more to get'em fully loaded but unfortunately even that method failed to mount the efs part.
Afterwards, I was just googling for more solutions and I decided to download and flash another GB236 rom Open europe built (wipe version) from Dr. Ketan's stock rom deposites and to my joyous surprise there were 2 extra tar. files, one named efs.md5.tar, so I quickly got my fone in download mode and flashed the rom with pitfile and when that was done, I got the fone back in download mode and Flashed the efs.tar (PDA), CSC, Modem (PHONE) and for the first time in 2 weeks the fone booted up normally as it should with the welcome screen, working lock screen and power button dialog! pheeeewwww!!!
But the imei is still not the same as under the hood, but I guess since the efs part had been corrupted, my fones probabaly using the emergency imei, Im using Alliance v1 with no apprent faults or errors.
i'll flash the GB Rom and try the factory rest code method by you and if it works then dont have to go to samsung and if doesnt then i'll keep using the fone as it is for as long as I have it and keep looking for solutions, if nothing happens then i'll get it sorted from samsung before selling it.
Your help is much appreciated, Thanks baz77!!! :thumbup: :thumbup:
<SAMSUNG><ASONG>from<GT-N7000
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
letters_to_cleo said:
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
Click to expand...
Click to collapse
Hi Letters_to_cleo,
Thank you for the suggestions mate, at the moment Im on Alliance v.1 403 rom, and I have just tried the fix from your link, did the steps1 & 2 restarted checked imei and it's the same serial (#to#) as you have stated, then i tried the step 3 which indicated that the nv_data.bin file is missing from that folder.
I have already gone to certain extents to return the fone in its generic state, so it won't matter if I tried once more besides trying repairs on GB rom is probably much safer then on ICS builts as long as the fone doesnt die on me,(completely again!), I 'll try your 2nd method in a bit and report back after!
Thanks for the support!!:thumbup:
<SAMSUNG><ASONG>from<GT-N7000
yeah that app wont work if you dont have efs backup. It distills from original. bak file the emei, now with the reflash of efs, even before you had lost it. only generic stuff left.
you need as mentioned before to go to samsung to repair emei, or find a phone place that can do it. You can yourself but in most countries its illegal. You need z3d box or equivalent for that, 150$$$$ lol, I have seen people who bought it offer that service for small fee. But be careful as ot could be illegal in your country, even if its going from generic emei to original emei lol.
Oh and you are welcome, been there done that, with the efs stuff. Samsung fixed mine.
My help is free, now if another has this you know how to help them
After Samsung fixes it,stay on gb, root phone and backup efs on multiple locations(pc, cdrom, floppy disk, bank vault you get it) In future when you buy android do that first. How to is in dr ketans toolbox thread in general section.
edit efs backup is not in nandroid, nor titanium backups. In fact still to date there is not one solution that can back everything up on your phone.
Sent from my GT-N7000 using Tapatalk 2
letters to cleo, corrupt emeis are empty or 0000000000000000000000000,
the 490000 emei is given when resetting efs. That is not corrupt anymore to my knowledge
Sent from my GT-N7000 using Tapatalk 2
oh I ran into missing lockscreen issues after fully fixing it, I have in my profile then statistics started a thread which links to a solution for that
Sent from my GT-N7000 using Tapatalk 2
Hi Enseven reporting,
@Letters_to_cleo, the methods you suggested dont work but thanks for trying to helping, i didnt find the bak file in efs folder but there 2 nv_data files, and they're both dated from Jan2011, renaming them just disable's the network and doent change the imei#, it remains the same!
@baz11, Yes mate, you are right this fone's going back to samung bcuz im not looking to $pend 150 on some box that I wont even use twice.
Im not really that fussed about imei not being as same on fone hardware, just as long the fone works, but like you said it probably is illegal to sell a fone with messed up serial no.
And on top of that fone's price would drop for having software issues, only wanted to fix it so that I could sell it on without loosing much $$ from the original price I paid for it, it'll be disapointing since Ive only had the fone for just over 2 months.
And I did manage to fix the welcome/lockscreen/power button issues by flashing efs.tar I got from that wipe version Open Europe Rom but even after the flash, it restore's the needed files but doesnt really prompt the features so I gotta insert this command through terminal emulator: "echo n- ON> /efs/imei/keystr" "sync"and factory reset, then the fone reboots normally with everything working but the IMEI ofcourse!
Wonder if your lockscreen fix works ive looked for it on your profile's statistic's tab but uable to find it, could you plz provide a link. Thanks
Ive tried all methods with some luck and no further progress apart from having to buy expensive equipment, so I guess i'll keep using the fone and looking for any miraculous solution till I resort to Samsung.
P.S: If they cant find a fix for the emmc bug by working on scripts , they should atleast invent a nano tech powder (gadget bug killer) to sprinkle on the motherboard, LOL!!!
because this problem goes way back, like another user said on here you could make a movie about now, and ithink it started off as a scifi now its a scifi/thriller, "shall I wipe before flashing & risk hardbrick Or shall I wait for samsung to pace up the support!!!
Thanks to xda and memebrs for being online 247 and all the support though!!
<SAMSUNG><ASONG>from<GALAXY-GTN7000>using xda premium!!!
Hi En7,
Sorry to hear my steps didn't work on your phone bud.
I checked some forums here in XDA and I've come across this one: http://forum.xda-developers.com/showthread.php?t=1804117. (I'm not sure though if you have come across that link before or not).
It is for the S3 forum but there's a tool in there that you can try to download and run to somehow restore your corrupted IMEI. It's worth taking the risk I should say but who knows..any given tool/info is highly useful and it could be a clear shot in bringing back your original IMEI back right?
Cheers bud!
lol that cracked me up nano powder hahaha good one.
you found the lockscreen fix, its the same fix I found while back from some guru.
I guess you can change emei to original with someone who has such a box. Finding is not to difficult, just need to go to a shop that can repair emei. Preferably Samsung thought, Just go to a samsung service centre, or store where you bought phone. Best unroot and put stock firmware that matches your phones original csc, to avoid anoying questions. Just tell the truth you updated phone and emei was gone/changed and you want original imei back. Samsung can fix it. Note, this time dont use pit or clear csc. Its not needed anymore.
I searched hard and long when I had that issue with emei, wasnt without a backup able to change it back to original, other then Samsung or such a box.
It annoyed the crap out of me. I can relate to what you were going through.
Everybody is nandroid this titaniun backup that, apparently efs is the only thing not standardly backed up with any standard mainstream solution.
Sent from my GT-N7000 using Tapatalk 2
oh, and good idea, maybe you should write a scifi thriller
Sent from my GT-N7000 using Tapatalk 2