Hello guys. I will try to describe my issue very short:
My S3 got bricked a couple of days ago where i did a "NAND FLASH" (yes i am stupid, and i dont know why i did it)
I managed to get my S3 up and running with different firmware, pit, modem, boot files. Now its running STOCK official firmware from S3 without root, and without clockwork...
The S3 is completely stock now, but my issue is:
1. I tried 4 different computers: WIndows XP, Windows 7, MAC etc. but none of them recognize my phone when i attached it, and yes the drivers are installed and i have tried different cables
2. The phone is very laggy and reboots without reason
Conclusion. I think there is something missing in the system files but i have tried every firmware (CYANOGEN too,) but the phone seems to have changed. I think there is a system android file that is still corrupt somewhere or the NAND has been affected by zombies
Please guys... i hope you can help me. -
Test the memory, search here in q&a for the app. I'd guess you have damaged the nand, which will require a motherboard replacement.
you can root using exynos abuse apk. it can be downloaded by qr code reader or directly from phone .after rooting you can use mobile odin to flash the stock rom . this requires no cable or connection to a pc. but first check the memory as boomboomer suggests. if it is damaged you might be able to replace with warranty. good luck
Memory test said "Test has passed" so i think the results are OK?
Ashraf: As i told before: I am already running stock firmware. The phone reboots by it self some times
Any other solutions?
Try the memory test from the freezing thread, if that passes then flash the stock rom again, make sure the csc in the rom matches your country and you have the right modem and RIL either included in the rom or flashed afterward.
Test fully before you log into Google or restore/install any apps. Remove the sd card during this testing.
hi
i had same problem.solved.see this post
http://forum.xda-developers.com/showthread.php?t=2285736
mostafaz said:
hi
i had same problem.solved.see this post
http://forum.xda-developers.com/showthread.php?t=2285736
Click to expand...
Click to collapse
Hello mostafaz... i dont know how to thank you but you solved my issue! I really really appreciate your help and for the solution!
It could be great if we had a database with the official PIT/PHONE etc. files :laugh:
Once again: Thank you!:good::good:
you are welcome
glad to hear u solved ur issue.
i wanna try many stock rom and have no fear ready for new problems
Related
I already posted my problems on this wall and I tried every solutions that people suggested me but it still not working....... bad.....
So I wanna say exactly what is my problems.
First of all, I rooted my phone when the version was 2.1 eclair and I did not use any custom rom I just used lagfix app
Secondary, I watched news that I was able to upgrade my phone to 2.2 froyo by official update. so I tried to update my version by kies mini without eliminating rooting system. the updating was working and my phone rebooted automatically but after I saw the hallmark as samsung galaxy s on the screen, my phone's screen was dark and I cannot see anything. Just sometimes it vibrated.
thirdly, I tried to recover by odin and official rom but it did not work.
at that time, odin stopped when it installed modem.bin (I used odin v1.0 first and I changed v1.7)
Finally, I posted my problems on this board and I got some suggestions from other great guys. so I tried 3 roms( T959UVJFD.tar, T959UVJI6.tar and another one) and I tried whole version odin to solve the problems. However, it did not work for me...........
WHatever I used different roms, odin always stopped when it installs modem.bin.... I think that is the most serious problem....
Please if you guys know how to solve this problems.... plz say me..... I will really appreciate guys..... Thanks
If I follow you guys instructions and my phone get back... I will give the poster 20 bucks by paypal...... plz help me..
Will you go to my noob guide and follow my instructions for the ALT METHOD? (its in my signature)
Be sure and download the correct files. And Please use the ODIN version I suggest.
I included videos and I suggest watching them to make sure you are not doing something silly.
If it works, give the money to a developer of your choice... or give it to me and I will give it to some I have not donated to recently.
ss10823 said:
I already posted my problems on this wall and I tried every solutions that people suggested me but it still not working....... bad.....
So I wanna say exactly what is my problems.
First of all, I rooted my phone when the version was 2.1 eclair and I did not use any custom rom I just used lagfix app
Secondary, I watched news that I was able to upgrade my phone to 2.2 froyo by official update. so I tried to update my version by kies mini without eliminating rooting system. the updating was working and my phone rebooted automatically but after I saw the hallmark as samsung galaxy s on the screen, my phone's screen was dark and I cannot see anything. Just sometimes it vibrated.
thirdly, I tried to recover by odin and official rom but it did not work.
at that time, odin stopped when it installed modem.bin (I used odin v1.0 first and I changed v1.7)
Finally, I posted my problems on this board and I got some suggestions from other great guys. so I tried 3 roms( T959UVJFD.tar, T959UVJI6.tar and another one) and I tried whole version odin to solve the problems. However, it did not work for me...........
WHatever I used different roms, odin always stopped when it installs modem.bin.... I think that is the most serious problem....
Please if you guys know how to solve this problems.... plz say me..... I will really appreciate guys..... Thanks
If I follow you guys instructions and my phone get back... I will give the poster 20 bucks by paypal...... plz help me..
Click to expand...
Click to collapse
Was there a lag fix in place when you tried to ODIN back to stock, My very first Rom I ever flashed I had OCLF in place and tried to ODIN back to the original files and it was a nightmare getting it to work. You can always blame TMO on there 2.2 update and they more than likely will give you a new phone, But follow ss10823's thread he has some good stuff out there.
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
dingo dog said:
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
Click to expand...
Click to collapse
Hi - Thanks for the tip, but I already tried with my wife's laptop. Should have mentioned in the original post.
Thanks again.
Older versions of Odin do work on SGS3 .
evelopment where I thought it should go but I haven't posted at all before so it won't let me.
Development only posts not Q&A nothing to do with 10 posts .
Two thoughts could be the usual flashed multiple stuff and phone is confused plus wrong PIT file flashed .
Thats just firmware not hardware problem .
Or indeed at some stage Nand is corrupt .
Solution would be
Try correct PIT file first before a repair centre .
jje
Just wanted to say that I have the same problem, but mine is even more strange. I can boot into the system but I have to disable wifi and mobile data right away otherwise the phone will reboot after a couple of seconds. I see the phone if I connect it to the computer but I can not write or read the files on the phone. But I tried the toolbox and could push an apk to the phone.
CWM works but if I try to wipe or flash another rom it reboots, some stuff works and other just reboots the phone.
Download-mode works and Odin finds the phone but everything I have tried fails. I have tried standard stock firmware, 3 part firmware and PIT but it always hangs on NAND Write.
If anyone has some solution I would be thrilled.
Bananafische said:
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable
My problem:
[*]Won't boot into recovery
[*]Will boot into download mode
[*]Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
[*]Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
Thanks
Click to expand...
Click to collapse
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
Click to expand...
Click to collapse
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
I am glad that It worked for you
I am still stuck, I am guessing that if none of the PIT´s work then it is officially bricked?
u didn't try the link posted by me?
theonlyanil said:
u didn't try the link posted by me?
Click to expand...
Click to collapse
it dosen't work ,stop at Get PIT for mapping..
help me
Hy guys Im from Hungary and i would like to flash my i9300 tmobile phone. My question is: can i flash the poland xeo to it or i just have to wait for the official tmobile rom? Thank you!
Where did you got the pit file
Bananafische said:
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
Click to expand...
Click to collapse
Where did you got the pit file
Hello, the PIT Flash didn't work for me either.
I was CF-rooted while overseas and stupidly forgot to disable auto-updates. The tricky part was that the auto update probably was for a different region as I was in Europe when the brick happened, but I live in Singapore.
Have tried to flash the firmware several times using Odin and even the PIT but all have been unsuccessful. I've been stuck a "Firmware upgrade encountered an issue....".
Have been able to get to the download screen but not the recovery mode.
Any pointers or is my phone rightly bricked?
I fixed my half brick using Android 4.0.4 ICS XXLAF2 stock firmware
My old stuff is still on my sd card, but not usable tho :s
Any tips? cant seem to restore with rom manager. It only fails
Help with encrypted at&t GS3
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Hey Anil,
I have encrypted at&t samsung gs3 running CM10.1 nightly. For some reason I cannot undo the encryption. I want to use the method described on this link that you posted here to get rid of encryption.
I have downloaded official firmware from sammobile. But the .pit file available on that site is for internation version. I have at&t GS3 so i should be using the .PIT for at&t version. Could you please provide me .PIT for 16GB at&t Samsung galaxy s3, if you have one or you know the link? Ii appreciate your help.
please help me with this man.
-Ravi
Click to expand...
Click to collapse
Worked well
The method given by Anil worked fine.
And since my device was encrypted before, it asked me password after installing the firmware by Odin.
So for this I just entered recovery (Sam recovery) and did a factory reset, and the encryption was removed.:good:
Dude don't post ur serial or imie
Bananafische said:
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Click to expand...
Click to collapse
For ur own safety mate
Flashed Xperia's miui rom on S3-i9300
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
xcanpolatx said:
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
Click to expand...
Click to collapse
Before you pay for a repair you can try flashing stock rom via Odin .
Hello, I'll try to explain what happened to get where I am now, and explain with details the last errors of my GT-9100.
I had a stock room jelly bean 4.1.2 installed. I had Android encrypted + SDCARD encrypted, and decided to format, but I didn't undo the encryption. As result, after master reseting it, it asked for a password do decrypt (as always asked when I turned the phone on), but it wasn't recognizing my password anymore. So I tried to clean and wipe all possible things, which ended on the device stucking at boot (doing boot loops, not asking for password anymore). I got an error on CW Recovery E: Could not load emmc (sounds like my internal storage is gone)
Later on, I tried to re-install the ROM, but got alot of trouble with windows drivers. Couldn't get any rom installed again. My device was then stuck at start, not even showing the white Samsung Galaxy S II GT9100 screen. After trying a variety of MODEMs, Kernels, I always get stuck on boot.info, zimage (kernel) on ODIN (Both 1.85 and 3.07 versions).
The only thing that has worked so far is changing the bootloader to the stock version. After doing this, my smartphone turns on on Chinese language. The ROM loaded is a jelly bean, but it has no status bar, can't open camera/folder explorer, can't do calls, can't acess internet, doesn't even show the configuration menu. And everything is chinese. BTW Calculator was working lol.
So this is the situation. Has my internal storage been gone forever? Is there a way I can flash without being stuck at boot.info or zImage when trying to flash kernel, both on Odin messages? Or is my phone really bricked? Thansk alot, I'll pay close attention to this.
EDIT: I haven't found after a day of research anyone that did data wipes in an encrypted phone, so this can be a guide for any future similar case.
gerijeb said:
Hello, I'll try to explain what happened to get where I am now, and explain with details the last errors of my GT-9100.
I had a stock room jelly bean 4.1.2 installed. I had Android encrypted + SDCARD encrypted, and decided to format, but I didn't undo the encryption. As result, after master reseting it, it asked for a password do decrypt (as always asked when I turned the phone on), but it wasn't recognizing my password anymore. So I tried to clean and wipe all possible things, which ended on the device stucking at boot (doing boot loops, not asking for password anymore). I got an error on CW Recovery E: Could not load emmc (sounds like my internal storage is gone)
Later on, I tried to re-install the ROM, but got alot of trouble with windows drivers. Couldn't get any rom installed again. My device was then stuck at start, not even showing the white Samsung Galaxy S II GT9100 screen. After trying a variety of MODEMs, Kernels, I always get stuck on boot.info, zimage (kernel) on ODIN (Both 1.85 and 3.07 versions).
The only thing that has worked so far is changing the bootloader to the stock version. After doing this, my smartphone turns on on Chinese language. The ROM loaded is a jelly bean, but it has no status bar, can't open camera/folder explorer, can't do calls, can't acess internet, doesn't even show the configuration menu. And everything is chinese. BTW Calculator was working lol.
So this is the situation. Has my internal storage been gone forever? Is there a way I can flash without being stuck at boot.info or zImage when trying to flash kernel, both on Odin messages? Or is my phone really bricked? Thansk alot, I'll pay close attention to this.
EDIT: I haven't found after a day of research anyone that did data wipes in an encrypted phone, so this can be a guide for any future similar case.
Click to expand...
Click to collapse
Tried installing Android 2.3 stock bootloader / rom ?
jiboncom said:
Tried installing Android 2.3 stock bootloader / rom ?
Click to expand...
Click to collapse
No I haven't. Is there any online link here? I couldn't find it.
Solved
After a day looking for it, I solved my problem
I tried several kernels, roms with almost all odin versions. The best one for gt-I9100 was odin 1.87.
This was the deal: After cleaning the encrypted internal storage, it got corrupted. So one of the first steps to get my phone reacting again to ODIN when installing new ROMs was installing the original GT-9100 .PIT file and re-partitioning (Even with every forum/site telling me I should never do it).
So, if you ever do the same mistake as me, try this:
Install a new kernel, then .PIT original file. Get a proper MODEM file, and finally try flashing your ROM.
I also got alot of problem with my USB cable, which is kinda damaged, so out of 10 plug-ins, only a few would work for ODIN. Try getting a brand new cable.
That's it.
gerijeb said:
After a day looking for it, I solved my problem
I tried several kernels, roms with almost all odin versions. The best one for gt-I9100 was odin 1.87.
This was the deal: After cleaning the encrypted internal storage, it got corrupted. So one of the first steps to get my phone reacting again to ODIN when installing new ROMs was installing the original GT-9100 .PIT file and re-partitioning (Even with every forum/site telling me I should never do it).
So, if you ever do the same mistake as me, try this:
Install a new kernel, then .PIT original file. Get a proper MODEM file, and finally try flashing your ROM.
I also got alot of problem with my USB cable, which is kinda damaged, so out of 10 plug-ins, only a few would work for ODIN. Try getting a brand new cable.
That's it.
Click to expand...
Click to collapse
Add [SOLVED] to the title.
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
Hi everybody,
hoping someone can help me as I am really frustrated now and have tried everything I can think of...
first a bit of info, I have an S6 edge, G925F and I was using a custom rom with no issues for a couple of months until all of a sudden I was having the same issue as others where I was getting "not registered on network" from damaged or corrupted /EFS, my imei had changed to 350000000000006 but I still had baseband version etc visible, just imei lost.
I have read on many threads that the answer is to change back to stock rom but no matter what rom i flash from sam mobile, it will not boot, when I go into recovery after booting it says "DM-Verity failed have to check DRK first", no matter what Rom I try but if I flash the odin flashable UNI Kernel after that then it will boot but then I have a rooted stock rom so not actually stock and an unstock kernel and still the not registered on network issue with same imei (350000000000006) .
so far I have tried flashing;
G925FXXS3COK5_G925FOXA3COK5_G925FXXS3COK5_HOME.tar.md5
G925FXXU3COI9_G925FBTU3COJ1_G925FXXU3COI9_HOME.tar.md5
and another one same as above but with XEU sales code as well as trying the EE (EVR) branded one with associated pit file and I've flashed every other pit file with each one as a last resort, to no avail...
nothing boots without flashing separate, non stock kernel, defeating the purpose of trying to return to stock.
p.S. Smart Switch doesn't work either as both it and kies say "SM-G925F does not support initialising, please contact support service"....
what can I do??
I've had 3 samsung phones now, s3, s4 and now s6, all rooted and have flashed countless roms on them and never had this issue and I also have no EFS back up as I have never selected it to back up in TWRP as I didn't know I should have and like I said, haven't had this problem before (kicking myself for not backing it up now...)
any help would be mucho appreciated as I am gutted to have broke my new phone and I am at my wits end with trying to fix it.... I thought I was quite good with tech and have done countless mods and rom flashes to various phones and solved many problems Ive encountered along the way but this is stumping me and I really need help..
Thanks in advance for your time and regards,
Elijah
anybody?
any ideas at all? anyone? how do I get the phone to rebuild or reset the EFS partition so that it refreshes it when I start it up with the sim card in it again? any ideas are more than welcome as I really can't accept Ive bricked my new phone, it's less than 3 months old and I know there must be a way to do it. any help would be appreciated, cheers in advance, Elijah
Elijah257 said:
any ideas at all? anyone? how do I get the phone to rebuild or reset the EFS partition so that it refreshes it when I start it up with the sim card in it again? any ideas are more than welcome as I really can't accept Ive bricked my new phone, it's less than 3 months old and I know there must be a way to do it. any help would be appreciated, cheers in advance, Elijah
Click to expand...
Click to collapse
I just managed to flash stock firmware on a SM-G925F (= model name in upper case) with Kies3.
It puts the phone on stock state (i.e. bootloader, efs partition, recovery, ... etc.)
but you have to be able to boot in Android in order to retrieve serial number in settings => about => state
Elijah257 said:
Hi everybody,
hoping someone can help me as I am really frustrated now and have tried everything I can think of...
first a bit of info, I have an S6 edge, G925F and I was using a custom rom with no issues for a couple of months until all of a sudden I was having the same issue as others where I was getting "not registered on network" from damaged or corrupted /EFS, my imei had changed to 350000000000006 but I still had baseband version etc visible, just imei lost.
I have read on many threads that the answer is to change back to stock rom but no matter what rom i flash from sam mobile, it will not boot, when I go into recovery after booting it says "DM-Verity failed have to check DRK first", no matter what Rom I try but if I flash the odin flashable UNI Kernel after that then it will boot but then I have a rooted stock rom so not actually stock and an unstock kernel and still the not registered on network issue with same imei (350000000000006) .
so far I have tried flashing;
G925FXXS3COK5_G925FOXA3COK5_G925FXXS3COK5_HOME.tar.md5
G925FXXU3COI9_G925FBTU3COJ1_G925FXXU3COI9_HOME.tar.md5
and another one same as above but with XEU sales code as well as trying the EE (EVR) branded one with associated pit file and I've flashed every other pit file with each one as a last resort, to no avail...
nothing boots without flashing separate, non stock kernel, defeating the purpose of trying to return to stock.
p.S. Smart Switch doesn't work either as both it and kies say "SM-G925F does not support initialising, please contact support service"....
what can I do??
I've had 3 samsung phones now, s3, s4 and now s6, all rooted and have flashed countless roms on them and never had this issue and I also have no EFS back up as I have never selected it to back up in TWRP as I didn't know I should have and like I said, haven't had this problem before (kicking myself for not backing it up now...)
any help would be mucho appreciated as I am gutted to have broke my new phone and I am at my wits end with trying to fix it.... I thought I was quite good with tech and have done countless mods and rom flashes to various phones and solved many problems Ive encountered along the way but this is stumping me and I really need help..
Thanks in advance for your time and regards,
Elijah
Click to expand...
Click to collapse
What happens when you just flash the stock FW, boot into recovery and make a factory reset from there? Cannot mount /EFS error???
AFAIK this IMEI is displayed when the EFS partition has been corrupted...
Some reported issues with param.bin (part of the BL file) in combination with EFS... and solved it by flashing the BL (which contains the param.bin) and the modem.bin
Try to flash a 4 part original FW, boot into recovery and make a factory reset...
Anyway if the EFS has lost data and you have not made a backup, you cannot fix / get back your original IMEI again.....
Check here: http://forum.xda-developers.com/galaxy-s6/help/help-restore-lost-imei-serial-sm-g920fd-t3239815