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 friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
jack man said:
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
Click to expand...
Click to collapse
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
omeadsthename said:
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
Click to expand...
Click to collapse
Yea tried with a class 10 16g micro sd like a million times and it wont work.and i think its because i dont have the 4.4.2 img if some one could help me out by uploading it. u et the img via busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70
So the phone won't power on at all? Can't get into download or recovery?
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
audit13 said:
So the phone won't power on at all? Can't get into download or recovery?
Click to expand...
Click to collapse
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
yowski said:
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
Click to expand...
Click to collapse
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
omeadsthename said:
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
Click to expand...
Click to collapse
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
yowski said:
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
Click to expand...
Click to collapse
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
omeadsthename said:
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
Click to expand...
Click to collapse
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
yowski said:
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
Click to expand...
Click to collapse
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
yowski said:
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
Click to expand...
Click to collapse
Unfortunately kids at my high school are afraid of rooting, so xda is basically my only bet. Im just surprised that some sr member hasnt added a debrick img to their threads. I mean its 4.4 and this is android central!
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
yowski said:
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
Click to expand...
Click to collapse
Cant they find out that you are root and hard bricked? like doesnt that void warranty. and if its a 4.3 h brick cant u just use the sd method?
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
yowski said:
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
Click to expand...
Click to collapse
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
omeadsthename said:
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
Click to expand...
Click to collapse
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
yowski said:
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
Click to expand...
Click to collapse
hmm i wish i could do that to my phone too. i mean, i dont even know how i would unroot without getting my phone on. but if im this hard bricked they probs cant tell anyways. im guessing?
uz unlock HARD BRICKING S3'S
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
I DID THE SAME THING ! but i used debrick (i535 vzw 4.3 ) and it pattially worked at least it will recovery and odin but i think it needs to be the 40 mbps type card the black micro would not work for me , then i flashed the wrong recovery and am starting all over but the debrick still getting me into odin thats ware you will sideload the right recovery and firmware ,rom what ever hope ( i even paid for cdma work shop and it aint did jack ) debrick then odin sideload look it up thats the best i got
Need someone to verify this for me. It says here that you can use a program called "EZ Unlock" to unlock the bootloader on the Galaxy S 3.
Can someone verify if this app would unlock my GS3 bootloader? I'm on 4.3 so mine is updated unfortunately. I would just get the bootloader unlock code from Samsung but I don't have an international model, that's the only one they would give you the BL code for.
EXTRA CREDIT I heard rumor of something called a "golden backup" supposedly a backup that exist on the phone of the older version you upgraded from, anyone?
drago10029 said:
Need someone to verify this for me. It says here that you can use a program called "EZ Unlock" to unlock the bootloader on the Galaxy S 3.
Can someone verify if this app would unlock my GS3 bootloader? I'm on 4.3 so mine is updated unfortunately. I would just get the bootloader unlock code from Samsung but I don't have an international model, that's the only one they would give you the BL code for.
EXTRA CREDIT I heard rumor of something called a "golden backup" supposedly a backup that exist on the phone of the older version you upgraded from, anyone?
Click to expand...
Click to collapse
No joy there, I'm afraid. Ol' Sam knew what he was doing with the 4.3 bootloader thing and a BL with EZ Unlock is a No-No. I just tried it now and whilst the whole process went well enough, the outcome was a hard brick. It, therefore, doesn't seem possible to 'unlock' your bootloader, at least, not for now.
The 'golden backup' is an option you see in the service menu. Not sure what it does though.
Larry2999 said:
No joy there, I'm afraid. Ol' Sam knew what he was doing with the 4.3 bootloader thing and a BL with EZ Unlock is a No-No. I just tried it now and whilst the whole process went well enough, the outcome was a hard brick. It, therefore, doesn't seem possible to 'unlock' your bootloader, at least, not for now.
The 'golden backup' is an option you see in the service menu. Not sure what it does though.
Click to expand...
Click to collapse
Really you tried it out? why?!?! also any information on the golden backup? how about accessing the service menu on android 4.3?
drago10029 said:
Really you tried it out? why?!?! also any information on the golden backup? how about accessing the service menu on android 4.3?
Click to expand...
Click to collapse
Yeah. Just to see if there was any way I could add to the body of knowledge... I'm aware EZ Unlock works with older firmware versions of the VZW model. The instructions on the site, however, suggested it works with the i747 as well. Apparently, this must be with older firmware versions as well and not the 4.3. After powering off the phone following the process, the phone just wouldn't power back on again. At least, not until, I'd inserted my debrick card and done a firmware restore.
I know I've seen the golden back function when accessing the service menu via *#197328640#. Never had to use it though so I wouldn't know if it does back up from older firmware.
Larry2999 said:
Yeah. Just to see if there was any way I could add to the body of knowledge... I'm aware EZ Unlock works with older firmware versions of the VZW model. The instructions on the site, however, suggested it works with the i747 as well. Apparently, this must be with older firmware versions as well and not the 4.3. After powering off the phone following the process, the phone just wouldn't power back on again. At least, not until, I'd inserted my debrick card and done a firmware restore.
I know I've seen the golden back function when accessing the service menu via *#197328640#. Never had to use it though so I wouldn't know if it does back up from older firmware.
Click to expand...
Click to collapse
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Back to stock
drago10029 said:
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2658486 As close as it gets for now...at&t
drago10029 said:
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Click to expand...
Click to collapse
Oh! I wouldn't risk "bricking" my phone if I wasn't reasonably sure I could recover. In fact, I've "intentionally" bricked this particular device in every way you can imagine just for learning purposes. I really think an unlock exploit is possible and we may be closer to one now than we know. Indeed I feel Touchwiz 4.3 has been unduly vilified because of the secure bootloader and other than the absence of a free unlock option, it's a major improvement on previous versions. I haven't seen the S4 unlock procedure. Can you send me a link to any thread on this?
There are a couple of threads dealing with recovery and return to stock for the 4.3. The first is a guide on how to recover from a hard brick caused by flashing the wrong bootloader. That was where I got my debrick file from ...
http://forum.xda-developers.com/showthread.php?t=2549068
Whilst the second is a guide on returning to factory stock (4.3) firmware via custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2658486
pckarma112 said:
http://forum.xda-developers.com/showthread.php?t=2658486 As close as it gets for now...at&t
Click to expand...
Click to collapse
Larry2999 said:
Oh! I wouldn't risk "bricking" my phone......
Click to expand...
Click to collapse
"I REPLIED TO THIS AT WORK FRIDAY, WONDER WHAT HAPPENED"
Thanks both you guys, I'm actually not concerned with warranty though. I'm ultra careful so I've never used once so far for something I broke on a phone lol.
And thanks for the stock guide pckarma, probably wouldn't of found that on my own. also would you 2 know if flashing any i747 rom with cmw/twrp would work on my phone with updated bootloader? (being that I don't flash a different bootloader of course lol)
drago10029 said:
"I REPLIED TO THIS AT WORK FRIDAY, WONDER WHAT HAPPENED"
Thanks both you guys, I'm actually not concerned with warranty though. I'm ultra careful so I've never used once so far for something I broke on a phone lol.
And thanks for the stock guide pckarma, probably wouldn't of found that on my own. also would you 2 know if flashing any i747 rom with cmw/twrp would work on my phone with updated bootloader? (being that I don't flash a different bootloader of course lol)
Click to expand...
Click to collapse
Yes, it should work - as long as you are not flashing a non-compatible bootloader. I noticed also from the development threads that someone has now put together an Odin flash-able image for 4.3
Larry2999 said:
Yes, it should work - as long as you are not flashing a non-compatible bootloader. I noticed also from the development threads that someone has now put together an Odin flash-able image for 4.3
Click to expand...
Click to collapse
The only compatibility problem I had was with the old TWRP version which I knew doesn't work with KK ROMs, just updated to the new TWRP and Kit Kat flashed fine. And "development thread"? You mean one of the stickies their?
drago10029 said:
The only compatibility problem I had was with the old TWRP version which I knew doesn't work with KK ROMs, just updated to the new TWRP and Kit Kat flashed fine. And "development thread"? You mean one of the stickies their?
Click to expand...
Click to collapse
I was referring to the one posted in this thread by enewman...
http://forum.xda-developers.com/showthread.php?t=2722660
Larry2999 said:
I was referring to the one posted in this thread by enewman...
http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
When the time comes hopefully it works.
I think I've hard bricked my gf's i747m to the point where there's no saving it, but I figured I would ask before I threw in the towel.
Short story is, after messing around with AOKP 4.4.4 (Kitkat) Task650 (9.10.2014), I would keep getting stuck in bootloop. I tried updating my bootloader via philz touch cwm and seemed to have bricked it.
I've tried a few different images in the debricking threads, is there any hope for me? I've tried numerous sd cards too and no luck.
Any help would be much appreciated.
What bootloader did you install? Does it boot into download mode at all?
audit13 said:
What bootloader did you install? Does it boot into download mode at all?
Click to expand...
Click to collapse
Bootloader was "boot_CWM_I747MVLUEMK5.zip"
It won't boot into download at all, without the battery in when I plug it into charge I just get a red led on the phone.
What stock ROM was on the phone before you tried to install a new bootloader?
You got the bootloader from here: http://forum.xda-developers.com/showthread.php?t=2321310 ?
audit13 said:
What stock ROM was on the phone before you tried to install a new bootloader?
You got the bootloader from here: http://forum.xda-developers.com/showthread.php?t=2321310 ?
Click to expand...
Click to collapse
Not sure if I got it from there or a different thread, but that was the bootloader. I think the stock rom was 4.4.2
The mk5 bootloader is a 4.3 bootloader. If you were running stock 4.4.2 bootloader and modem and flashed the 4.3 mk5 bootloader, you would wind up with a 4.4.2 modem on and 4.3 bootloader. From what I have read on this forum, this combination of bootloader and modem can only be fixed via jtag.
Which carrier is the phone with? If it's under warranty, maybe try and have it RMA'd.
audit13 said:
The mk5 bootloader is a 4.3 bootloader. If you were running stock 4.4.2 bootloader and modem and flashed the 4.3 mk5 bootloader, you would wind up with a 4.4.2 modem on and 4.3 bootloader. From what I have read on this forum, this combination of bootloader and modem can only be fixed via jtag.
Which carrier is the phone with? If it's under warranty, maybe try and have it RMA'd.
Click to expand...
Click to collapse
Debrick images don't work with that combination eh? It's a bell phone, well out of warranty.
tomlemange said:
Debrick images don't work with that combination eh? It's a bell phone, well out of warranty.
Click to expand...
Click to collapse
Not that I have seen on this forum.
I'm not sure where you are located but there are some jtag places I know of in Toronto that could probably fix the phone, but it would be expensive given the age of the phone.
here is a thread with jtag for $25 you can check on.
http://forum.xda-developers.com/showthread.php?t=2874113
cheapest i've seen.
good luck
err on the side of kindness
mrrocketdog said:
here is a thread with jtag for $25 you can check on.
http://forum.xda-developers.com/showthread.php?t=2874113
cheapest i've seen.
good luck
err on the side of kindness
Click to expand...
Click to collapse
Thanks for the head up, I couldn't find any cheaper either.
audit13 said:
Not that I have seen on this forum.
I'm not sure where you are located but there are some jtag places I know of in Toronto that could probably fix the phone, but it would be expensive given the age of the phone.
Click to expand...
Click to collapse
I'm in Halifax so there really isn't too many options here, if I can find one at all...
If I ordered a replacement motherboard online, would it need to be for the 747m specifically?
tomlemange said:
Thanks for the head up, I couldn't find any cheaper either.
I'm in Halifax so there really isn't too many options here, if I can find one at all...
If I ordered a replacement motherboard online, would it need to be for the 747m specifically?
Click to expand...
Click to collapse
If you order the motherboard, you should make sure it is for the i747 or i747m because you need to re-use the lcd screen, antenna, mic, etc.
You should also make sure you have the correct tools for assembling the parts into the new board. From what I have seen on ebay, the motherboard is not too cheap either. I suggest getting some quotes before ordering a new board.
Motherboard is the only fix here. 4.4.2 modem plus 4.3 firmware is an unfixable brick in nearly every case I'm afraid.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
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