Hello people, I am a noob here.
I have T999 and i had it working on 4.3 then i wanted to downgrade to 4.1.1 so i can unlock it with region lock away (thats what i did with my S4)
but then after i was done, i wanted to upgrade to 4.3 and since i cant do that through OTA (tried triangle away, no luck) i thought i can just flash 4.3 through clockwork recover. thing is i think i flashed the wrong one, and i bricked my phone.
after following instructions and got it to boot up to recovery mode, eject SD and do all ODIN work, phone still doesn't turn on without the Unbrick sd
please help:crying:
So it does boot with the sdcard in it, right?
What firmware are you trying to flash with Odin? What version of Odin?
What does it say in the message box? (Copy into a post)
DocHoliday77 said:
So it does boot with the sdcard in it, right?
What firmware are you trying to flash with Odin? What version of Odin?
What does it say in the message box? (Copy into a post)
Click to expand...
Click to collapse
tried these two
T999UVUEMJC_T999TMBEMJC_TMB.zip
T999UVDLJC_T999TMBDLJC_TMB.zip
sorry cant post outside links in here i guess
even tried flashing pit file with the whole process and am still stuck, one weird thing i noticed is the back of the battery says I747 which is ATT
but recovery and ABOUT say its T999. tried Kies to restore but i get an error too
You probably just need to use the NC2 firmware. And if the I747 is printed on the casing (not the sticker), that's normal. If it wasn't a T999, the debrick for it wouldn't work.
DocHoliday77 said:
You probably just need to use the NC2 firmware. And if the I747 is printed on the casing (not the sticker), that's normal. If it wasn't a T999, the debrick for it wouldn't work.
Click to expand...
Click to collapse
have to clarify it says I747 behind the battery ON the back of the phone, not the case or box. but when going into recovery mode it says T999, am guessing someone changed things around before i bought it? the weird part is when i install i747 it takes att sim and works, and when i flash t999 firmware it takes tmobile fine too.
am still stuck at this roadblock, i even tried stock bootloader files like
aboot.mbn
dd
rpm.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
i believe this should fix the issue but not yet
Dont flash partitions individually. Very good chance of a very hard to fix brick....trust me.
If it says I747 on the sticker, I might wonder, but if its printed on the inner casing, on the plastic middle housing, alk T999's have that. Its just usually covered by the sticker.
Have you tried fladhing NC2 firmware? If you're using an NC2 debrick.img, that's the ONLY firmware that'll work.
I have tried nc2 and even tried kies firmware update. still only turn on by sd
Ill put together a recovery flashable NC2 firmware package you can try. Might be a little later before I can get to it though...
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Just re-read the OP, can you let me know exactly what it was you flashed that caused the brick?
If I know exactly what was flashed I might be able to give you exactly what you need to fix it...maybe.
DocHoliday77 said:
Ill put together a recovery flashable NC2 firmware package you can try. Might be a little later before I can get to it though...
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Just re-read the OP, can you let me know exactly what it was you flashed that caused the brick?
If I know exactly what was flashed I might be able to give you exactly what you need to fix it...maybe.
Click to expand...
Click to collapse
idk whats the OP is, sorry and i honestly don't know what have i flashed. all i know it was 4.3 (plus i am not advanced at all this)
if the unbrick sd turns on the phone everytime, can i somehow duplicate it with the mmcblk0? assuming thats power management files partition
The debrick sd card has 14 separate partitions on it. So one of those was overwritten when you flashed whatever it was you flashed. Had it been something in the stock firmware, flashing that would've fixed it. So without knowing which partition was overwritten, we won't know what you need. It depends on which it was whether or not we can actually do anything more to help.
And you can't just copy the sd to your device. It doesn't work that way and if you forced it you'd end up with all sorts of problems and probably an unusable, unfixable device.
Related
Hey all,
So I've checked as much as I could to try and help myself before posting, so hoping some kinds souls can help out with my issue.
Got a samsung galaxy s3 SGH-T999V on Wind Mobile (Canada), android 4.3. My aim is to root the phone, then play with some roms later on, but at least get the rooting part done. I started with this hxxp://theunlockr.com/2012/07/23/how-to-root-and-install-clockworkmod-recovery-on-the-samsung-galaxy-s3-sgh-t999v-canadian-version guide, but the CMW didn't get installed when I went into recovery mode, just had the stock phone recovery options.
So then, went on to try pretty much the exact same procedure but with the root66_GLW_T999VVLALH2.7z..but Odin gave me the failed sbl2 error or something like that. Now i didn't have anything to backup so I didn't really care wiping the phone to factory default so I did so ( as well as the cache partition using the default android recovery menu.) But even still, no luck. When I tried again, it (Odin that is) just seemed to hang at the phase that stated "get PIT" or something like that (apologies I'm pulling this all from memory).. Had no real choice but to interrupt it restart, try again, back to the sbl2 error again. Doing this from a Win7x64 Ultimate OS (if that's relevant). I HATE the phone the way it is, I cannot stand the bloatware and I have a lot in mind to have fun with if I can ever get this bloody thing to root.
I think that's about all I can mention atm, did the usual stuff like try different usb ports, the phones USB cable 'seems' to be ok and working, I'm just beyond frustrated and finally at the part where I need to ask for help. Any and all help is deeply appreciated. Cheers
i also want help rooting my T999v version 4.1.2 cant seem to find a tutorial for rooting of version 4.1.2
ksec said:
Hey all,
So I've checked as much as I could to try and help myself before posting, so hoping some kinds souls can help out with my issue.
Got a samsung galaxy s3 SGH-T999V on Wind Mobile (Canada), android 4.3. My aim is to root the phone, then play with some roms later on, but at least get the rooting part done. I started with this hxxp://theunlockr.com/2012/07/23/how-to-root-and-install-clockworkmod-recovery-on-the-samsung-galaxy-s3-sgh-t999v-canadian-version guide, but the CMW didn't get installed when I went into recovery mode, just had the stock phone recovery options.
So then, went on to try pretty much the exact same procedure but with the root66_GLW_T999VVLALH2.7z..but Odin gave me the failed sbl2 error or something like that. Now i didn't have anything to backup so I didn't really care wiping the phone to factory default so I did so ( as well as the cache partition using the default android recovery menu.) But even still, no luck. When I tried again, it (Odin that is) just seemed to hang at the phase that stated "get PIT" or something like that (apologies I'm pulling this all from memory).. Had no real choice but to interrupt it restart, try again, back to the sbl2 error again. Doing this from a Win7x64 Ultimate OS (if that's relevant). I HATE the phone the way it is, I cannot stand the bloatware and I have a lot in mind to have fun with if I can ever get this bloody thing to root.
I think that's about all I can mention atm, did the usual stuff like try different usb ports, the phones USB cable 'seems' to be ok and working, I'm just beyond frustrated and finally at the part where I need to ask for help. Any and all help is deeply appreciated. Cheers
Click to expand...
Click to collapse
If you're on 4.3 stock you'll have to deal with this new thing they added called "Knox". Also you cannot downgrade to older versions of official firmware if you have updated to 4.3 stock. Root66 won't work for you unless there's a version of root66 firmware that is 4.3 (which there isn't). Here's a thread that should solve this problem for you: http://forum.xda-developers.com/showthread.php?t=2563955
dorian2kx said:
i also want help rooting my T999v version 4.1.2 cant seem to find a tutorial for rooting of version 4.1.2
Click to expand...
Click to collapse
Since you haven't updated to 4.3 yet, you don't have to deal with Knox, so use the root66 method here: http://forum.xda-developers.com/showthread.php?t=1949687
adslee said:
If you're on 4.3 stock you'll have to deal with this new thing they added called "Knox". Also you cannot downgrade to older versions of official firmware if you have updated to 4.3 stock. Root66 won't work for you unless there's a version of root66 firmware that is 4.3 (which there isn't). Here's a thread that should solve this problem for you: http://forum.xda-developers.com/showthread.php?t=2563955
Since you haven't updated to 4.3 yet, you don't have to deal with Knox, so use the root66 method here: http://forum.xda-developers.com/showthread.php?t=1949687
Click to expand...
Click to collapse
Hey adslee, thnks for the reply. I noticed the Knox app. Well then, that explains somethings. It did give me the impression that something was inhibiting the process. I'll check out the link you provided and let you know. Cheers
Thanks bro but can u please tell me how can i know what type my phone is, i mean is it a wind, videotron etc? Or it doesn't matter? Are they the same
dorian2kx said:
Thanks bro but can u please tell me how can i know what type my phone is, i mean is it a wind, videotron etc? Or it doesn't matter? Are they the same
Click to expand...
Click to collapse
Look Under the Battery on thw White Sticker. What do you have in there for a Model Name?
i have there a SGH-T999V
dorian2kx said:
i have there a SGH-T999V
Click to expand...
Click to collapse
Well then that's the Device you have. Anything said in Settings > Model is suspect. If I modify ro.device in Build.prop then My Galaxy S3 will appear instantly as S4 or Nexus 5. That does not mean it is one.
You always go by what's under the Battery and not by Settings > Model.
Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Note that if you reinject IMEI, it might screw up your network
audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?
chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it
Hello people, I randomly tried to flash internation model rom on my i747 model s3
it gave wrong model error so i went and modified asserts in the update file and made it pass the check. but phone wont turn on now. i do get red led when charging it. I know it sounds stupid but i just wanted to give a try (was assuming I would unlock the phone :laugh
anyways i do know that 16gb sd un-brick method. but i was wondering if there's a possible different method.
thanks for your time.
Only paying for a jtag service
looks like SD Unbrick method isn't working either, it's not turning on with unbrick sd. i did do a backup before all this. can anyone help here?
Dont give up. Many people have to run through the sd creation process several times before it worked.
It could also be the sd card you are using.
DocHoliday77 said:
Dont give up. Many people have to run through the sd creation process several times before it worked.
It could also be the sd card you are using.
Click to expand...
Click to collapse
the thing is, all debrick img's posted on threads are for 4.3 and up. my phone was on 4.1.2 with an i747 bootloader.
going to order a usb jig (since diy's failed)
If you are on pre-4.3 firmware, it shouldn't matter what debrick.img you use. But if you do get it to boot it will not let you flash anything older than what the image is.
---------- Post added at 03:31 AM ---------- Previous post was at 03:31 AM ----------
Of course it wouldn't hurt to have a 4.1.2 image.....
troolplay1 said:
the thing is, all debrick img's posted on threads are for 4.3 and up. my phone was on 4.1.2 with an i747 bootloader.
going to order a usb jig (since diy's failed)
Click to expand...
Click to collapse
It is a good idea to have a jig handy. But you many not even need it for that one. The exact same thing happened to me (I747m - Fido).
Just make sure the SD card is the same size as your phone for the image.
I am assuming you already found all the steps? You can pm me if you need the necessary files.
distorsun said:
It is a good idea to have a jig handy. But you many not even need it for that one. The exact same thing happened to me (I747m - Fido).
Just make sure the SD card is the same size as your phone for the image.
I am assuming you already found all the steps? You can pm me if you need the necessary files.
Click to expand...
Click to collapse
I have tried many many debirck img's. both for t999 and i747, for 4.3 and whatnot. today i got the jig in the mail but the try failed, still wont turn on. i lost hope and i feel like sending it to ebay service is my only resort. the sd card i was using was a pixar class 10 16GB. idk what would go wrong with that.
the reason that i bricked it, again, is flashing wrong bootloader.
any help would be appreciated.
Idk bro the international s3 is a whole nother phone, it has a quad core exynos processor while we got a dual core snapdragon, it's got a gig of ram we got 2.... That's too name a few differences.....I think the only way to fix it is by a JTAG.......sorry bout the luck bro
O don't think he's got an international version. Thought he mentioned having an I747 before??
Sent from my SAMSUNG-SGH-T999 using Tapatalk
If you don't mind shipping to Canada I have a riffbox and could fix the issue for you.
The debrick method should work though. If it were me I wouldn't give up just yet. I'd at least try a few more times on every sdcard I could get a hold of. Often doesn't work on the first couple of tries, and AFAIK there's no way to know which sdcards will or won't work. Just gotta keep trying.
It is possible that for some reason this method simply won't work, but it has worked in the past for similar types of bricks.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
My situation is different from everyone's so i figured i'd share this with you all. I accidently turned off OEM Unlocker/USB Debugging in developer options and when i start my phone i'm completely locked out I CAN get into download mode but CANT flash anything at because the bootloader is locked. So im just writing this to let all you (Sprint Galaxy S6 G920P owners) not to do this unless u want a really expensive high end paperweight.... i can't flash anything because the bootloader is locked...... :crying::crying::crying:
Your not able to odin the OE7 tar?
Sent from my SM-G920P using XDA Free mobile app
wvebert said:
Your not able to odin the OE7 tar?
No in fact like i said my situation is different in a sense i'm locked out of the binary via the OEM switch being off im assuming....And the FRP will not let me modify ANYTHING lol crazy right...
btw can u please PM the proper locations of all the stock 5.11 firmware aka The BL, AP,CP & CSC stock files if they exist lol and all the full stock firmware. BTW anyone interested in this situation i attached pix of my screen after flashing Stock OE7
tar via Odin 3.10.6
Click to expand...
Click to collapse
I just had the same problem. I ended up re-flashing the stock OF7 tarball in Odin.
OF7 tallball
What is "OF7 tallball".
Where can i find that.
My phone is: G920T.
what is that, i want to know too
I am having the same Issue with the G920T, did anyone find a solution for it?
Having tbe same exact problem as the OP. Everthing I flash through ODIN fails. Even flashing stock 5.1.1 OF7 fails. I believe it's because I was on OGA so I have to wait until the tarball for that comes out I guess.
I had this problem yesterday. The way I fixed it was to flash the F8 bootloader, and then I could get the unroot rom to load.
Maybe a fluke, but that is what I did to fix mine.
Now I am unable to unlock it. I tried ChainFire CF-Auto-root and TWRP - both give the custom recovery is blocked. Any help on this is appreciated.
Thanks.
BigBirdie said:
I had this problem yesterday. The way I fixed it was to flash the F8 bootloader, and then I could get the unroot rom to load.
Maybe a fluke, but that is what I did to fix mine.
Now I am unable to unlock it. I tried ChainFire CF-Auto-root and TWRP - both give the custom recovery is blocked. Any help on this is appreciated.
Thanks.
Click to expand...
Click to collapse
when you got the custom binary block did you just plug it in and odin and flash it or did you managed to get it in download mode ?
was it just plugging it the same way it was showing the block .. thanks
I had same issue as first post. so I odin to the stock 5.1.1 firmware. Now when I reboot and it asks to verify my gmail account I set up when I got device. I did that but it takes my info then pops back up with the verify screen I know I'm entering the correct info because I try a wrong pw and it says check pw. Has anyone else had it basically got back to verify gmail account ? also if you look in google at linked devices it shows tha last activity of you signing in? I hope I don't have a $600 paperweight!
Looking for help
XXX01 said:
My situation is different from everyone's so i figured i'd share this with you all. I accidently turned off OEM Unlocker/USB Debugging in developer options and when i start my phone i'm completely locked out I CAN get into download mode but CANT flash anything at because the bootloader is locked. So im just writing this to let all you (Sprint Galaxy S6 G920P owners) not to do this unless u want a really expensive high end paperweight.... i can't flash anything because the bootloader is locked...... :crying::crying::crying:
Click to expand...
Click to collapse
----------
I have the same exact problem with my Sprint S6.
I have tried all possible stock Firmwares :
G920PVPU1AOCF
G920PVPU1AOE2
G920PVPU2BOF7
G920PVPU2BOH1
None of them workes. any idea, please keep update.
I got this same exact problem yesterday on my SM-G920P as well. Been up all night trying to figure it out, has anyone found a solution to this?
Just got mine working again Apparently the original firmware I had on my phone was "G920PVPU3BOI1" so I just downloaded and flashed that in Odin and it flashed without the "Custom Binary Blocked by FRP Lock" error I kept on usually getting. So for anybody with this problem, if you are unsure which firmware you originally had on your phone before the brick, just try to flash all the possible ones via Odin until one works
How to find proper firmware while bricked.
sebasvinti said:
Just got mine working again Apparently the original firmware I had on my phone was "G920PVPU3BOI1" so I just downloaded and flashed that in Odin and it flashed without the "Custom Binary Blocked by FRP Lock" error I kept on usually getting. So for anybody with this problem, if you are unsure which firmware you originally had on your phone before the brick, just try to flash all the possible ones via Odin until one works
Click to expand...
Click to collapse
You can just go into recovery mode and the proper version is put on the top of the screen.
---------- Post added at 08:59 PM ---------- Previous post was at 08:49 PM ----------
ameenz77 said:
I am having the same Issue with the G920T, did anyone find a solution for it?
Click to expand...
Click to collapse
I have the same issue too, have you tried to flash it with the stock firmware? If not then there may be another solution...
i am having the same problem .
on my samsung galaxy SM J500H/DS
it says *CUSTOM BINARY BLOCK BY FRP*
the problem was I disable developing option
where you can see the OEM and USB DEBUGGING. what can I do.?
i just got the g920p from sprint and i rootd it the turned off oem and im having the same problem I can get to download mode and recovery mode I just dont know what to do. Ive tryed a few different firmware and nun of them have worked. Any suggestions? Thanks
I just downloaded the newest update of line and installed it through odin and it booted up and asked me for my gmail and it worked just fine and it's still factory unlocked
I wanted to update my S3 from whatever version it was on to the newest one available. I essentially wanted to start with a blank phone I went into the TWRP recovery and wiped cache, system, data, etc. I guess that was the entirely wrong way to do it because after that I installed the dirty unicorn rom (DU_d2att_5.1.1_20150723-1444.v9.4-UNOFFICIAL), and it got stuck on the boot screen. Thinking there was something wrong with the install I tried a factory reset and reflashing. It got stuck on "patching system image unconditionally" because there was something wrong with the system partition I think. I let it sit overnight and it stayed on this part.
The next day I read a bunch of things and thought it was just a bad ROM file or something. I went and downloaded the newest stable cyanogenmod (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att) to try and make it work. It installed without error and looked like it was going to work, i even wiped dalvik cache to up the chances of success. It also hung on the boot screen. I left it alone for a few hours and it still didn't progress.
After some more research I found a post that I thought would correct my partitions and make it bootable again. It was using adb commands to do something:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
I did this from recovery and the first two commands worked. The third shot back an error. I tried modifying it according to other users who have found success and it didn't work for me. I went ahead and hit reboot anyway and now the phone doesn't respond. It doesn't power on, it only has a charging light when plugged in without the battery.
I have tried to fix this as well, I tried a slew of different debrick.img files on a 16gb sd card formatted with Win32 Disk Imager. None of those were able to get me back to download mode. This is where I'm stumped. Is there a debrick.img I'm supposed to use and haven't found yet? Or am I just SOL with this method?
Thanks in advance
Have you tried using different SD cards?
audit13 said:
Have you tried using different SD cards?
Click to expand...
Click to collapse
I've tried two 16gb, an 8gb, and 64gb.
Not sure why the images didn't work. Did you try the recommended SD cards? The phone is an i747 according to the label under the battery?
audit13 said:
Not sure why the images didn't work. Did you try the recommended SD cards? The phone is an i747 according to the label under the battery?
Click to expand...
Click to collapse
Yes, I've tried the recommended SD cards and the phone is i747. I'm thinking maybe I need to find a debrick image from the android versions I was trying to upgrade to?
scyther3989 said:
Yes, I've tried the recommended SD cards and the phone is i747. I'm thinking maybe I need to find a debrick image from the android versions I was trying to upgrade to?
Click to expand...
Click to collapse
I think it would be more successful to use a debrick image made for the bootloader and modem on your phone rather than that matches the Android version of the ROM you were trying to flash.
Both of the ROMs you mentioned were Android 5.1.1, but the highest bootloader you could have is 4.4.2 on the i747. To get more precise, for the i747 there would be three different 4.4.2 bootloaders; NE4, NJ1, or NJ2. I'm fairly certain that I have seen a debrick image for at least one of these. Do you recall what bootloader is on your phone?
dawgdoc said:
I think it would be more successful to use a debrick image made for the bootloader and modem on your phone rather than that matches the Android version of the ROM you were trying to flash.
Both of the ROMs you mentioned were Android 5.1.1, but the highest bootloader you could have is 4.4.2 on the i747. To get more precise, for the i747 there would be three different 4.4.2 bootloaders; NE4, NJ1, or NJ2. I'm fairly certain that I have seen a debrick image for at least one of these. Do you recall what bootloader is on your phone?
Click to expand...
Click to collapse
I don't remember any of the specs on what version it was before I started tinkering with it. But if it's down to those three bootloaders, can't I just find debricks for all three of them and try them out?
Another thing I'm curious of is I think I had a i747m rom installed as they were very similar when I was using the s3 is it possible to have a i747m bootloader on an i747 device?
scyther3989 said:
I don't remember any of the specs on what version it was before I started tinkering with it. But if it's down to those three bootloaders, can't I just find debricks for all three of them and try them out?
Another thing I'm curious of is I think I had a i747m rom installed as they were very similar when I was using the s3 is it possible to have a i747m bootloader on an i747 device?
Click to expand...
Click to collapse
The ROMs should be interchangeable, but I don't think the bootloaders are. I expect using the other bootloaders would brick a working phone.
There would be a lesser chance of problems using the debrick image with the newest bootloader you can find. (Best would be the one that matched your bootloader, but not possible in this case.) One with an older bootloader than you were running probably wouldn't fix your phone.
dawgdoc said:
The ROMs should be interchangeable, but I don't think the bootloaders are. I expect using the other bootloaders would brick a working phone.
There would be a lesser chance of problems using the debrick image with the newest bootloader you can find. (Best would be the one that matched your bootloader, but not possible in this case.) One with an older bootloader than you were running probably wouldn't fix your phone.
Click to expand...
Click to collapse
So my best bet would be to find the newest i747 and i747m debricks around until one works?
scyther3989 said:
So my best bet would be to find the newest i747 and i747m debricks around until one works?
Click to expand...
Click to collapse
I don't know if the i747M images would work on the i747. But the normal method of using a debrick image would have you booting from the external sdcard and then installing the bootloader and modem. Even if you could boot from a i747M debrick image, I think loading the bootloader and modem from one would be bad. I guess you could boot from the i747M debrick image and then be certain that it is an i747 bootloader and modem you install.
So, I would say the newest i747 that you can find. What say you @audit13 ?
Please keep in mind that I have not used a debrick image of any kind, I am only making suppositions from what I have read and recall from the relevant threads. (Although, it looks like I will be using on to resurrect the i535 I bought for hacking and modding. :fingers-crossed: )
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
See if this post helps. He was in your same predicament.
The only life the phone had was remove battery and plug charger in and the red light came on.
Click to expand...
Click to collapse
dawgdoc said:
I don't know if the i747M images would work on the i747. But the normal method of using a debrick image would have you booting from the external sdcard and then installing the bootloader and modem. Even if you could boot from a i747M debrick image, I think loading the bootloader and modem from one would be bad. I guess you could boot from the i747M debrick image and then be certain that it is an i747 bootloader and modem you install.
So, I would say the newest i747 that you can find. What say you @audit13 ?
Please keep in mind that I have not used a debrick image of any kind, I am only making suppositions from what I have read and recall from the relevant threads. (Although, it looks like I will be using on to resurrect the i535 I bought for hacking and modding. :fingers-crossed: )
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
See if this post helps. He was in your same predicament.
Click to expand...
Click to collapse
After a few more hours of trying a bunch of different debrick images, I haven't been able to make it work. I have about 15 debrick images from anyone who said "this one worked for me." I think at this point I'll just look for some of the newer images around to see if that helps. Also, I see some debrick files coming in 256 and 512 variants, what is that about?