Related
SGH-I747 (4.1.2 i747's please)/ SGH-i747m( If you have a official 4.3 i747m, please post a debrick.img) only:
Hi, I recently hard bricked my phone into QHSUSB DLOAD and I am going to attempt repairing it through the SD Card boot method.
http://forum.xda-developers.com/editpost.php?do=editpost&p=47431259
I need a debrick.img to flash to the SD card in a Linux OS.
I would have gotten it myself but my phone is obviously dead. I found one before on XDA, but it did not work on my device and it gave me an error in the Linux terminal when it should not have.
-snip-
The end of the 3rd boot-loader stage in mmcblk0 is at 77.3 megabytes. If you are going to help out using your device, try to refrain from uploading an image with a different ROM other than root.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=2m count=81054925
The count is the amount of bytes. I am not sure if it is meant to be 1000 bytes=kilobyte or 1024 bytes=kilobyte. The count above is for 1024.
I need someone to install the Galaxy S III unified toolkit, and pull the first 7 partitions from mmcblk0 ,which is where the third bootloader stage ends.(Don't upload a heavily modified device please) http://www.skipsoft.net/?page_id=213 Once you get the files, PM me.
If anyone has a link to a working one, please post that. If you want to get your own image to help me, go ahead.
Thanks guys.
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
what happened?
winosxbuntu said:
what happened?
Click to expand...
Click to collapse
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
99ytrewq9111 said:
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
Click to expand...
Click to collapse
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Thanks for that link! It looks very promising, and I can probably find a stock boot.IMG in there. I will work on tomorrow. If I succeed, I'll edit the OP and make a debrick guide for this drvice forum. A word of advice, try not to mess with your bootloader or you end up like me
winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Hi, the toolkit didn't fix my phone, but its defiantly a step up. Since I'm assuming you have the toolkit installed that you suggested it, could you do me a favor?
It will be a bit easier using the toolkit to extract the partition files. If you could pull the first 7 partitions from "mmcblk0" of your device through the toolkit, it will probably set the next step to fix my phone. (Assuming you have a 16g i747... I don't really know)
You don't have to do this of course.
Thanks man.
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
99ytrewq9111 said:
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
winosxbuntu said:
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
Click to expand...
Click to collapse
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
99ytrewq9111 said:
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
Click to expand...
Click to collapse
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Bradkirk said:
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
Click to expand...
Click to collapse
Did you use an i747 or a i747m device?
If a i747m image works on an i747, it will basically fix all of my problems.
spensa said:
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Click to expand...
Click to collapse
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bradkirk said:
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately that's the download I found that didn't work.
Thanks for trying though
damn! the only other help I can offer then, is that there is a pretty good thread on this over in the d2tmo section. someone there wrote a little tool to easily download the relevant data. might help you on your quest. or at least make it so you could ask someone that doesnt know ADB. best of luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
99ytrewq9111 said:
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
when connected to the computer written QHSUSB-DLOAD,
spensa said:
when connected to the computer written QHSUSB-DLOAD,
Click to expand...
Click to collapse
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
99ytrewq9111 said:
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
Click to expand...
Click to collapse
I took it to a service to repair
My i9192 s4 mini got hard bricked while charging I don't know how or why it happened..
I found this somewhere in the forum.. can anyone make me a dump file for i9192 because I don't know anyone who has the same phone as me so I'm asking for help. I tried to bring it to a programmer but they said they have to j-tag it for 3days up to a week. but I don't want to leave my phone on other people's hand so I'd rather fix this myself.
help would be really really appreciated. TIA
initial situation:
- we have a brick with killed bootloader after unsuccessful flashing, not turning on, no reaction on buttons, no any mode available (recovery, download).
What is needed:
- any Linux, like Ubuntu, but more convinient is PartedMagic of any version;
- MicroSD card;
- working phone of the same model or dump of its first 139008 blocks (about 70MB).
How to make a dump:
- on rooted device download from Google Play app "TerminalEmulator" and run it;
- Enter su, appears "[email protected]:/ #", enter "dd if=dev/block/mmcblk0 of=sdcard/mmcblk0uptop7.img count=139008";
- after completion copy file "mmcblk0uptop7.img" from the phone to PC, for example to drive C:/.
How to revive the phone:
- insert MicroSD into PC and launch "PartedMagic";
- copy dump to MicroSD, for this open Terminal, we see "[email protected]:~#", enter "dd if=/media/WIN7/mmcblck0uptop7.img of=/dev/mmcblk0", where "/media/WIN7/" - it's your drive C:/, where stored a dump, and "/dev/mmcblk0mmcblk0" - your MicroSD in PartedMagic;
- wait for completion, remove MicroSD;
- put MicroSD to non-working phone, connect the phone to PC using USB;
- if all steps are done correctly, phone will boot by pressing the keys, using bootloader from external MicroSD;
- now it is possible to re-flash internal eMMC using Odin, to make a possibility to remove external card;
- that's all, phone completely revived.
Supported devices:
- tested on i9190, will work on i9192/i9195, should work on smartphones of other brands with new Qualcomm chips.
Technical details:
- details are too big to write. If you are interested - read about MSM8930 boot architecture and etc.
Some conclusions:
- Qualcomm has made a good modern chip, with a lot of feasibility, but not placing many information to open sources;
- Samsung - trying to complicate life of users by integrating of its own digital signature, what is leading to immediate bricking of devices when trying to modify bootloader. Be careful.
Click to expand...
Click to collapse
Update:
Please try to send me an unbrick.img file from a stock i9192 that came from Saudi.. but if not from Saudi at least a stock ones..
If someone could send me a full or even half image file from a i9192 stock device
thank you.
I just need the "make a dump" part.
Bcoz of knox m not rooting my phone but I really want to help you
Is there any othet way to make dump file without a rooted device?
NafeesTyagi said:
Bcoz of knox m not rooting my phone but I really want to help you
Is there any othet way to make dump file without a rooted device?
Click to expand...
Click to collapse
I don't know if there's another way tho. but thanks anyway. even my phone is not rooted. I'll bring it to a service center today but I doubt they can get it fixed because the warranty of my phone is in another country and I'm in the Philippines right now. probably I will have to pay for it if they try to fix it but it's gonna be expensive.. I just want to save some bucks and try to fix it myself but unfortunately I don't have another phone like this one to do that, neither my friends.
EDIT:
Unfortunately they keep refusing to J-TAG my unit.. they said that they don't have software to j-tag i9192.
I'll upload mine when I get to the office
Sent from my GT-I9192 using Tapatalk
fburgos said:
I'll upload mine when I get to the office
Sent from my GT-I9192 using Tapatalk
Click to expand...
Click to collapse
Thanks!! I hope I can fix my phone.. it's been a month since I last used it.
here you go, its from a the latest firmware
https://www.dropbox.com/s/89yodahtvig6lhc/debrick.img
fburgos said:
here you go, its from a the latest firmware
https www . dropbox . com s 89yodahtvig6lhc debrick.img
Click to expand...
Click to collapse
Thank you bro! is that from i9192?.. gonna update if I fixed my phone so ppl who has same problem will be able to use this thread.
EDIT: IT has some improvements its vibrating now when I plug it in my PC but the problem is ODIN won't detect my phone. Hmm
Hi I have some improvements but I could not flash my phone.. it keeps failing on ODIN, sorry im just a newbie on this kind of stuff and still learning.. I used the stockfirmware which is the md5 file that is 1.4gb for my phone is that the right one for the bootloader?
its like this
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 SECTORS
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
now that you have a debrick image follow this guide , hope it helps.
http://forum.xda-developers.com/showthread.php?t=2600869
btw you don't need to follow step 2.2 of that guide
dovakinn said:
now that you have a debrick image follow this guide , hope it helps.
http://forum.xda-developers.com/showthread.php?t=2600869
btw you don't need to follow step 2.2 of that guide
Click to expand...
Click to collapse
same thing happened still on that root recovery mode.. the problem is I'm stuck at flashing my phone.. probably the problem is the version of the firmware @jburgos gave me.. I need to know what version is his firmware and where it came from so I can download the stock firmware for that version.
can you get into download mode ?? a quick glance a jburgos proflie shows he is most likely using a Latin American firmware , though i really doubt that it will make diffrence, if you can get into download mode you can try flashing it again with your stock firmware.
by mistake i had deleted my image file and right now i am on a really bad connection uploading another image will tale me 3 days
dovakinn said:
can you get into download mode ?? a quick glance a jburgos proflie shows he is most likely using a Latin American firmware , though i really doubt that it will make diffrence, if you can get into download mode you can try flashing it again with your stock firmware.
by mistake i had deleted my image file and right now i am on a really bad connection uploading another image will tale me 3 days
Click to expand...
Click to collapse
I can't get into download mode.. btw mine is the Saudi Arabia version..
Its not download mode and I took a picture of it so you guys can see:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 SECTORS
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
Man I'm stuck.. I thought I had it but its not flashing through root recovery mode
I wonder if I need the exact same phone as dump, or I need a longer address on dump, anymore opinion guys I'm kinda getting annoyed on my phone. idk what is root recovery mode either..
I'm currently stuck on Boot Recovery Mode that has no android logo.. can't go to download mode.
If someone could send me a full or even half image file from a i9192 stock device it would be very helpful.
this is the rom i used for the image, http://forum.xda-developers.com/showthread.php?t=2620621
i have another image from a past firmware but its at home and i dont the firmware version
fburgos said:
this is the rom i used for the image, http://forum.xda-developers.com/showthread.php?t=2620621
i have another image from a past firmware but its at home and i dont the firmware version
Click to expand...
Click to collapse
which model did u use tho?
I'm stuck at boot recovery mode I can't go to download mode.. I hope someone who has stock rom will share their .img file.. but still I'm going to download that custom rom and try to flash it.
jhetz09 said:
which model did u use tho?
I'm stuck at boot recovery mode I can't go to download mode.. I hope someone who has stock rom will share their .img file.. but still I'm going to download that custom rom and try to flash it.
Click to expand...
Click to collapse
mi device its a i9192 from panama
sorry to hear didnt work, i use this guide to get the debrick.img,
[HARD BRICK ?] - I919x - Make your debrick.img and have it on extSdCard by security http://forum.xda-developers.com/showthread.php?t=2625628
i have another .img but not with me, broke my screen, next week ill upload when i get my phone back, i think the other firmware was from ubmh1 odin firmware but im not shure wich firmware but im shure it was a stock samsung that came without knox
do you remember wich firmware was in your device, was a knox one?
fburgos said:
mi device its a i9192 from panama
sorry to hear didnt work, i use this guide to get the debrick.img,
[HARD BRICK ?] - I919x - Make your debrick.img and have it on extSdCard by security http://forum.xda-developers.com/showthread.php?t=2625628
i have another .img but not with me, broke my screen, next week ill upload when i get my phone back, i think the other firmware was from ubmh1 odin firmware but im not shure wich firmware but im shure it was a stock samsung that came without knox
do you remember wich firmware was in your device, was a knox one?
Click to expand...
Click to collapse
my device model is either
KSA-I9192XXUAMH3
KSA-I9192XXUBNB1
I dont think my phone is with knox
well finally i was on stable connection , here is the my debrick image this also made from the guide http://forum.xda-developers.com/showthread.php?t=2625628 suggest you use this to write to your SD http://forum.xda-developers.com/showthread.php?t=2600869 and if your cell boots try go imd into download mode and flash your stock rom ,
this from firmware I9192DDU1BML1 , btw this img was created after i had deleted knox and other bloat ware from the rom , hope it helps.
https://www.dropbox.com/s/i6ul61hisnvrjog/debrick.img
dovakinn said:
well finally i was on stable connection , here is the my debrick image this also made from the guide http://forum.xda-developers.com/showthread.php?t=2625628 suggest you use this to write to your SD http://forum.xda-developers.com/showthread.php?t=2600869 and if your cell boots try go imd into download mode and flash your stock rom ,
this from firmware I9192DDU1BML1 , btw this img was created after i had deleted knox and other bloat ware from the rom , hope it helps.
https://www.dropbox.com/s/i6ul61hisnvrjog/debrick.img
Click to expand...
Click to collapse
gonna try it.. thanks for sharing. gonna post if there's an improvement..
I'll consider this as my last resort.. ill send it to the seller since I still have warranty for this phone.. I never flashed or rooted this phone. but if I send it back it'll take a month to get it back.. but better than nothing.
I was updating an s3 running cyanogenmod 10.2.1 to 11. I realized that the bootloader needed to be updated long story short i accidentally flashed the i9300 bootloader instead and now my phone is hard bricked. I heard about a method using the sd card to allow the phone to enter boot recovery so i could get into download mode could someone help me to do this?
The only fix that I personally know of is using a jtag service. If there is an sd card fix floating around out there, you'll need to search for it. If you fail, mobiletechvideos.com can help. Expect a week to 10 day turn around time
Sent from my SAMSUNG-SGH-I747 using Tapatalk
purelight97 said:
I was updating an s3 running cyanogenmod 10.2.1 to 11. I realized that the bootloader needed to be updated long story short i accidentally flashed the i9300 bootloader instead and now my phone is hard bricked. I heard about a method using the sd card to allow the phone to enter boot recovery so i could get into download mode could someone help me to do this?
Click to expand...
Click to collapse
You are probably referring to the method posted in the thread below ....
http://forum.xda-developers.com/showthread.php?t=2549068
You have nothing to lose in giving it a try. Doubtful if it will work, however, since it is specifically for recovering from a brick caused by flashing an older bootloader after 4.3 upgrade. As BrianRay advised, when you have a brick caused by flashing a different model's bootloader, a JTag operation may be required.
Larry2999 said:
You are probably referring to the method posted in the thread below ....
http://forum.xda-developers.com/showthread.php?t=2549068
You have nothing to lose in giving it a try. Doubtful if it will work, however, since it is specifically for recovering from a brick caused by flashing an older bootloader after 4.3 upgrade. As BrianRay advised, when you have a brick caused by flashing a different model's bootloader, a JTag operation may be required.
Click to expand...
Click to collapse
Thanks, you wouldn't happen to have a 4.1.2 debrick.img?
purelight97 said:
Thanks, you wouldn't happen to have a 4.1.2 debrick.img?
Click to expand...
Click to collapse
Sadly, no, I don't. You could create one, however, if you know someone who has a similar device running 4.1.2. If you need further instructions on how to do this, you would need to contact the author of the original post. He is the expert there. A JTag may still be your best option, however.
Hey, try to get the phone into a download mode by using at USB jig. You can buy one for 3 bucks from ebay. If that doesnt do it, then you can go to the method of using the debrick image.
Once you exhaust all of these possibilities, then you can try the JTAG. But the Jtag service is expensive too. Good luck.
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 have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere
also
please pm me if u fixed yours
Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now
Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?
The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.
I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore
need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?
Hola, alguien lo consiguió hacer..???
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/
m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse
ayuda
ATT ZE500CL/Z00D rom