Develop Bugs

Help with unlocking and rooting

I can't seem to get this to work. I'm trying to unlock my phone using the nexus toolkit but when I put my phone into fastboot mode and click the unlock option on the toolkit I just get '< waiting for device >'. Every video I watch just shows them plugging the phone in and then having the program unlock it for them. It's not doing the same for me. Any suggestions?

Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.

063_XOBX said:
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
Click to expand...
Click to collapse
Every guide and video I find uses that method. Do you have a link to the other method?

http://forum.xda-developers.com/showthread.php?t=1529058

063_XOBX said:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
I still get the 'waiting for device' when I do it this way too. I have the most current samsung drivers. I also did everything to set up ADB.

uninstall the drivers and reinstall using the naked drivers.

i need some files from a working phone to try to unbrick mine

hey
long story short, i bricked my nitro hd by mistake while going back to stock (typo error in dd command) and i need some files from a working phone to attempt a last attempt to save it before i send it to Jtagging service.
there is a small program in this thread that will collect all the bootloaders i need (it needs root access)
if you're in windows you should run backup.bat from Brixfix-2-1.zip.
if you're in linux then you should run get-part.sh and getpartbin.py
thanks in advance

bobo122 said:
hey
long story short, i bricked my nitro hd by mistake while going back to stock (typo error in dd command) and i need some files from a working phone to attempt a last attempt to save it before i send it to Jtagging service.
there is a small program in this thread that will collect all the bootloaders i need (it needs root access)
if you're in windows you should run backup.bat from Brixfix-2-1.zip.
if you're in linux then you should run get-part.sh and getpartbin.py
thanks in advance
Click to expand...
Click to collapse
there are unbricking files posted in the unbricking threads...

KronicSkillz said:
there are unbricking files posted in the unbricking threads...
Click to expand...
Click to collapse
it doesnt have all the files i need (i mistakenly overwritten mmcblk0p2 when i was supposed to overwrite mmcblk0p27, i guess thats SBL1..
the little program in the thread i mentioned can bring me all the files i need (including SBLs and other files)
thanks for the reply though

If your phone is in unbooteable state, black screen, then you most probably need jtag. Describe the state of the phone.
Sent from my HTC One VX using xda premium

el_venga said:
If your phone is in unbooteable state, black screen, then you most probably need jtag. Describe the state of the phone.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
its black screen , and i was getting hsusb_qdload when connecting it to the computer (code 9008) , then i tried a chines program that flashes files to the emmc .. all i had was the su640 files (they were included in the same chines thread , p930 was mentioned there) ..
after the flash , its still black screen but now windows installs new drivers (code 9025) - check the attached photo.
as far as my understanding goes this is sd mode.. the flashing software is still able to see the cellphone, so i want to try to flash the original files this time and see what happens before i spend 80$ on jtagging

bobo122 said:
its black screen , and i was getting hsusb_qdload when connecting it to the computer (code 9008) , then i tried a chines program that flashes files to the emmc .. all i had was the su640 files (they were included in the same chines thread , p930 was mentioned there) ..
after the flash , its still black screen but now windows installs new drivers (code 9025) - check the attached photo.
as far as my understanding goes this is sd mode.. the flashing software is still able to see the cellphone, so i want to try to flash the original files this time and see what happens before i spend 80$ on jtagging
Click to expand...
Click to collapse
This is Qualcomm mode. Dunno why you got two different ids but I might give you the files in a day or two. I have a p930.
Sent from my HTC One VX using xda premium

el_venga said:
This is Qualcomm mode. Dunno why you got two different ids but I might give you the files in a day or two. I have a p930.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
great, thanks a lot

Mine bricked just now. Was testing a micro sdcard and afterwards just black screen and hsusb now. Did you repaired yours?
Sent from my LG-E970 using XDA Premium 4 mobile app

nope .. no luck ..

try this method
may this method works for you http://bbs.gfan.com/forum.php?mod=viewthread&tid=4520374&ordertype=1
all you need is correct files otherwise your phone will be totally dead even not jtagable

Brick problem (boot certification verify)

Ok so I have this issue with my phone.
I tried bringing it back by using the KDZ programm but everytime I try it I have a problem with the extraction of the file.
I tried the compatability issues but it doesn't seem to work.
Please could somebody say to me what to do?
I need the phone for tommorow and I made a fuss and trying to find a solution. If I hard reset it will it start?
Thank you in advance!
Ok so I tried to hard reset it but it pops out the same message.
What am I supposed to do please give me some feedback.

Ur phone bricked?if it is u could unbrick it just search the term in forums....only software brick can be unbricked not hardware
Sent from my A240 using XDA Premium 4 mobile app

Trustlover™ said:
Ur phone bricked?if it is u could unbrick it just search the term in forums....only software brick can be unbricked not hardware
Sent from my A240 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is software brick. I updated it today, it tryed to restart and it couldn't do it!

I managed to unbrick my device but it seems that it doesn't have the root inside it.I tried to root it again and it says that the binary support is missing.Any ideas?
Sent from my LG-E975 using xda premium

wow,i'm still amazed. please,don't ask for support on PM. it's one thing i'll never do, at least not for free.
you have all the info you need here.if you can't find it,well, look further.
like i said, clicking on my signature will give you alot of answers. if you still can't fix it, it means you don't have the proper knowledge and it would be better to call someone who has it or start learning.
I always advice users to document themselves BEFORE,not after screwing up.

kimitza said:
wow,i'm still amazed. please,don't ask for support on PM. it's one thing i'll never do, at least not for free.
you have all the info you need here.if you can't find it,well, look further.
like i said, clicking on my signature will give you alot of answers. if you still can't fix it, it means you don't have the proper knowledge and it would be better to call someone who has it or start learning.
I always advice users to document themselves BEFORE,not after screwing up.
Click to expand...
Click to collapse
Ok we got your point.... You say some things, I tried some things and they didn't seem to work cause I didn't knew what the problem was... You know what... You can also block me from your pm and looking at my posts, and don't whine for it here like a baby.

I'm whining?If you only could see how many PM's i'm getting..you wouldn't say that. And most of those questions have been answered here,including by me.
Bottom line, use either kdz updater or lg mobile tool(for emergency firmware recovery) to get a clean phone,then start rooting and unlocking procedures.

kimitza said:
I'm whining?If you only could see how many PM's i'm getting..you wouldn't say that. And most of those questions have been answered here,including by me.
Bottom line, use either kdz updater or lg mobile tool(for emergency firmware recovery) to get a clean phone,then start rooting and unlocking procedures.
Click to expand...
Click to collapse
Ok I am sorry ok? But you seem to be the only one knowing things about this phone so expect pm's... If I update it through the LG tool will my stuff (apps etc) will also get erased? Cause I can't back up them.If I remember right titanium backup works only with rooted devices.
Sent from my LG-E975 using xda premium

You can try other methods to root. There are several ways. Again,my FAQ can help you.
I get you don't have a custom recovery,right?since you lost root and you didn't unlocked the bootloader.
And there is an app called hellium,developed by cm team if i'm not mistaking,which allows you to backup your apps without root.
Sent from Asylum via LG E975/smart phones,dumb people.

i747 Hard Bricked: QHSUSB - DLOAD : Needing a debrick.img

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

Nexus stop working out of nowhere

Hello, my brother have a nexus 5x and one day after a night his phone stop working, it could only enter to download mode, now sometimes it cant even get there, what can i do, its been like 2 weeks since that

Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk

berndblb said:
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked into that, but is it normal that the phone go to a bootloader, then to download mode and after that get stuck in the google animation?

No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229

berndblb said:
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
Click to expand...
Click to collapse
Thank you sooo much, i will try this and the ill tell you how it end up:good: